Yes, natively. Krokul CRM fetches orders from the Rozetka seller account through the Seller API. An order becomes a deal with items from your catalog, and the buyer becomes a contact. The order status and the waybill number go back to Rozetka along with item prices and stock from the Krokul warehouse, and return requests are visible on the deal.
Krokul reads /orders/search with expanded purchases and creates a deal «Rozetka № …» in the connection pipeline. Each order line is matched to a Krokul catalog item by your product ID, so the reservation and margin are calculated the same way as for a deal a manager creates. The order number becomes the external key, and there is no duplicate.
Krokul checks the recipient name and phone from the order against existing contacts. If the buyer has ordered before, the deal attaches to that contact, and the manager sees all purchases of the person on Rozetka and elsewhere.
A manager moves the deal to the «Shipped» stage, and Krokul updates the order with a PUT /orders/{id} request. The seller account gets the new status from the /order-statuses/search directory and the number of the waybill created on the deal card. You map stages to statuses in the connection settings.
When the stock of an item changes in the Krokul warehouse, Krokul sends the new stock and price in a batch through PUT /items/mass-update. An item that is out of stock stops selling on Rozetka, and the manager does not keep stock in two places.
Krokul links return requests from /item-return/ticket/search and refunds from /order-refund/search to the deal by order number. The deal feed shows the reason and state of the request, and the owner gets a task.
| Rozetka | Direction | Krokul | When |
|---|---|---|---|
| Order (/orders/search) | Rozetka → Krokul | Deal «Rozetka № …» with an external key | Background polling, every five minutes by default |
| Order lines (purchases) | Rozetka → Krokul | Deal lines with catalog items | Together with the deal |
| Recipient (full name, phone) | Rozetka → Krokul | Contact, found by phone or new | Together with the deal |
| Order status (PUT /orders/{id}) | Krokul → Rozetka | Deal stage | The deal stage changes |
| Order waybill (PUT /orders/{id}) | Krokul → Rozetka | Waybill on the deal card | After the waybill is created |
| Price and stock (PUT /items/mass-update) | Krokul → Rozetka | Item and warehouse stock | Stock or price changes |
| Return request, refund | Rozetka → Krokul | Entry in the deal feed and a task | Background polling |
Yes, a native one. Krokul turns orders into deals with catalog items, sends the status, waybill, prices and stock back to Rozetka and shows return requests.
The login and password of the Rozetka seller account. The Seller API works with the same credentials, and there is no separate key.
By default, no. The first pass remembers the latest order in the account, and Krokul starts from the next one. A separate switch in the connection settings lets you import the history.
Rozetka sends no webhooks, so Krokul checks the seller account in the background, every five minutes by default.
Update the seller account password in the connection settings if it was changed in Rozetka.
Rozetka sends no webhooks, so Krokul polls the seller account in the background, every five minutes by default. The connection uses the seller account login and password, and Rozetka issues no separate key.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Rozetka is a trademark of its owner. Krokul is not affiliated with Rozetka.