Rozetka sends no webhooks: to learn about a new order the seller has to ask the Seller API. So the CRM polls your cabinet every 15 minutes and turns whatever comes back into an ordinary CRM order — line items, total, buyer, payment and delivery. Your manager works in one window instead of keeping the Rozetka cabinet open next to the CRM and copying data across by hand. Every workspace is isolated: one business's credentials, catalog and orders are unreachable from another.
What the adapter does
Orders every 15 minutes
The CRM polls the Seller API on a schedule and creates the orders. A repeated run never duplicates what already exists — the idempotency key is built from the Rozetka order id.
Payment and delivery on the order
Every pass refreshes the status, payment method, delivery method and waybill number as soon as Rozetka returns them.
Statuses back to the cabinet
A manager changes the status in the CRM and the adapter logs into the Seller API and updates the order on Rozetka's side. An ambiguous transition is not written at all.
Rozetka products into the catalog
Published listings are pulled in: an existing SKU is linked, an unknown one becomes a draft in the review queue — nothing lands in your catalog without your decision.
Publishing through a price file
The Rozetka API cannot create a product — its price file can. The CRM serves one at a permanent link, you connect that link in your cabinet once, and from then on new catalog products reach Rozetka on their own and go through moderation.
Readiness before you send
Rozetka requires a name, price, photo, brand and characteristics, and reports a rejection hours later without naming the product. The CRM checks that by Rozetka's own rules locally: a list of what will not go, linked to each product.
Prices and stock back to Rozetka
Every hour the CRM updates the price and quantity of listings that already exist. Quantity is sent only for products where you actually track stock.
Buyer questions become leads
The same pass collects product-page messages and creates a lead sourced as "Rozetka", with an owner and a next step.
Technical detail
Exactly what the adapter does with the Seller API — for anyone who wants to check it against their own cabinet.
- API base
- api-seller.rozetka.com.ua
- Authentication
- Seller login + password → a 24-hour token. Credentials are encrypted at rest.
- Reading orders
- GET /orders/search with line items, delivery and buyer expanded
- Cursor
- Rozetka filters orders by date only, so the cursor is daily and every pass re-reads one extra day — so an order on the midnight boundary is never lost
- Writing status
- PUT /orders/{id} after login
- Prices and stock
- PUT /items/update-price-stock/{id} — matched by SKU (article = SKU)
- Publishing products
- An XML price file (yml_catalog) at a permanent link Rozetka fetches itself; the offer id derives from the CRM product id and never changes, and the article equals the SKU
- Categories
- Your own category tree with rz_id — the link to a Rozetka category; suggestions come from listings you already have there after an import
- Currency
- Hryvnia. A product priced in another currency is skipped rather than converted at an invented rate.
- Schedule
- Orders and messages every 15 minutes, catalog hourly, plus a manual "Sync now" button
Status mapping CRM → Rozetka
Rozetka statuses are numeric and depend on the individual cabinet's configuration, so the mapping lives in one block that we verify against a live account. A transition the adapter is unsure about is not sent.
Delivery and the waybill
Rozetka owns delivery for its own orders, so here the CRM reads rather than commands.
- The delivery method and waybill number arrive from Rozetka into the order's shipment block — on every pass, not once at creation.
- If you ship yourself, a Nova Poshta waybill can be created straight from the CRM order, with the address and recipient filled in from the buyer's data.
- Self-pickup is a first-class delivery method, not a free-text field: it has no carrier and no tracking number, and renders as "Self pickup" on the order.
- A delivery status never overwrites the order status: once a manager sets the status by hand, the CRM treats it as authoritative and the poller does not overwrite it.
No write direction is on by default
You arrive with products that already live in both the CRM and Rozetka. So reading works immediately, while every write direction — prices, stock, statuses, publishing through the price file — is armed by the owner separately and only after a dry run that shows exactly what would change while changing nothing. Publishing has its own dry run: it names every product that would not make it into the file, and why. An empty price file is never served — it could take your listings down. The adapter never deletes or archives products, in the CRM or on the marketplace.
Setup
- 1
Add the Rozetka adapter
Settings → Integrations → Platform adapters. The first step asks only for a name.
- 2
Paste the seller login
The login and password of your Seller API cabinet. Press "Test connection" — the CRM performs a real login and reports whether order access works.
- 3
Arm the directions you want
Orders start flowing on their own. The dry run shows what would happen to prices and stock — and only then do you switch writing on.
- 4
Connect the price file if you publish from the CRM
Copy the price-file link from the adapter page and add it as your XML price file in the Rozetka cabinet. Price-file categories are mapped to Rozetka categories there — products are not published without it.
Frequently asked
How do I connect Rozetka to the CRM?
Add the Rozetka adapter under Settings → Integrations, paste the login and password of your Seller API cabinet and press "Test connection". Once it passes, orders start arriving on their own — no workers and no code on your side.
Do I need a developer?
No. Polling Rozetka, reconciling orders and updating statuses is the CRM's job. A developer is only needed if you want to write into the CRM from your own system — there is a public REST API for that.
How quickly does a Rozetka order appear in the CRM?
Within 15 minutes: Rozetka sends no webhooks, so the CRM polls the Seller API on a schedule. That is the platform's trade-off rather than our choice — which is why the time of the last successful poll is visible in the interface.
Are delivery and the waybill number pulled in?
Yes. The delivery method and waybill number arrive from Rozetka into the order's shipment block and refresh on every pass. If you ship yourself, a Nova Poshta waybill can be created straight from the order.
Can I manage prices and stock from the CRM?
Yes. For listings that already exist on Rozetka the CRM matches them by SKU and updates price and quantity every hour. New products go out through the price file: the Rozetka API cannot create a listing, so the CRM serves your catalog as an XML price file at a link you connect in the cabinet once, and Rozetka creates the products from it.
Can I publish a new product to Rozetka from the CRM?
Yes — through the price file. Rozetka's Seller API cannot create products (it only updates the price and stock of an item that already exists), so the CRM serves your catalog as an XML price file at a permanent link. The owner arms that direction after a dry run and pastes the link into the Rozetka cabinet; from then on new products travel there on their own and pass Rozetka's moderation like any other seller product.
What happens to my catalog on the first import?
Nothing without your decision. A product whose SKU the CRM already knows is simply linked to the listing. A product it does not know becomes a draft in the review queue, where you either activate it or merge it into an existing card.
Can I reply to Rozetka buyers from the CRM?
Product-page questions become CRM leads with their history and an assigned manager. Replies are still written in the Rozetka cabinet — two-way chat for this channel is not open yet.
Is this the same pattern as Prom?
Intake is shared — both marketplaces are polled on a schedule and pass through one order-intake layer, so idempotency and stock commits behave identically. Writing is built against Rozetka's Seller API separately: we take each platform's contract from its own official documentation, never from another adapter.
Commonly connected together
Prom.ua
AvailableOrders, payments and delivery arrive on their own. Buyer questions become leads you answer straight from the CRM, without opening the Prom cabinet.
Learn moreNova Poshta
AvailableNo switching to the carrier's cabinet: the waybill is created in the CRM, and delivery statuses update themselves.
Learn moreMonobank
BetaThe buyer pays an invoice, the CRM receives a signed confirmation from Monobank, puts the payment on the order and tells your team at once. No reconciling statements by hand.
Learn moreOLX
AvailableEvery enquiry on a listing becomes a lead, and the whole thread lives in the shared inbox next to your other channels. Your team replies from the CRM — no need to open OLX.
Learn moreTelegram
AvailableCustomers message your Telegram bot and no enquiry is lost: messages land in the pipeline with the source “telegram” automatically.
Learn moreBeta: Beta: available to connect today; the channel’s capabilities are still being refined.
Connect Rozetka
Marketplace orders, payment, delivery and stock in the same workspace as the rest of your channels.
Start free