Elbuz creates a Rozetka Delivery waybill under your partner contract right from the order card, prints the label and brings parcel statuses every 10 minutes in a single request.
When you need this:
- You ship via ROZETKA points — the recipient, city and amount come from the order; one click per waybill.
- The customer pays on delivery — cash on delivery for the order amount is set automatically.
- The order isn't from the marketplace — Rozetka Delivery works for any order, not only Rozetka ones.
Where to start: create a static Rozetka Delivery partner token → enter it in Elbuz.
What Rozetka Delivery can do in Elbuz
- A waybill from the order — to a pickup point or an address, with dimensions, number of parcels, payer choice and cash on delivery; one at a time or in bulk.
- Cities and points — a list shared by all Elbuz stores that updates itself; drop-off points (where you ship from) and pickup points (where to) are kept separately.
- Parcel statuses — every 10 minutes, all waybills in one request.
- Label — a PDF from the order card or from “Shipments”.
This integration runs under your contract with Rozetka Delivery. A waybill for an order from the Rozetka marketplace using the seller's credentials is a different action: “Waybill via Rozetka”.
Extending storage, returns and deleting a waybill aren't available from Elbuz — they're done in the Rozetka Delivery account. Returns and deletion from Elbuz exist only for Nova Poshta.
How to connect Rozetka Delivery: token and drop-off point
Where to get a Rozetka Delivery token
Elbuz works with a static partner token. Per the Rozetka Delivery API documentation, the partner creates it with the «Створення статичного токена партнера» (create a static partner token) method after signing in with a phone number and password. Tokens are listed and deleted there too.
Documentation: rz-delivery.rozetka.ua/api/docs. If you don't have API access yet, contact your Rozetka Delivery manager.
A regular session token lives 72 hours from its last use — it won't work for Elbuz; you need a static one.
Where to enter the token in Elbuz
Where: External services and integrations → “Delivery” group → the “Rozetka Delivery” entry.
- Paste the static token into the “Token” field.
- Turn on “Active”.
- In the “Sender” block, fill in “Last name”, “First name”, “Phone” and “Company name”.
- Choose “Region”, “City” and “Branch” — the drop-off point where you hand over parcels.
1
Token2
Sender branch- Token — the key issued by Rozetka Delivery; it is stored masked.
- Sender block — Region, City and Branch, the drop-off point where you hand over parcels.
Elbuz doesn't check the token when you save: you'll see an error on the first waybill.
City and point directories
Elbuz takes Rozetka Delivery cities and points from a list shared by all stores, which updates itself. There's nothing to load: the “Service directories” block only shows how many points Elbuz knows and when the list was updated, and “Update directories” checks that it's up to date.
1
Branch2
Pickup points row3
Update directories- Branch — the pickup point where you hand over parcels.
- How many pickup points Elbuz knows and when the shared list was last updated.
- The button only checks whether the shared list is fresh; nothing has to be downloaded.
The “Sender” block shows only points that accept parcels, and the waybill form shows only those that hand them out. Until the shared list is updated, the previous one applies.
Rozetka Delivery status codes
The order status changes only in the marked order statuses and by the three tables in “Notification settings” — as for Ukrposhta. Elbuz enters the codes from the table into “Delivery statuses” itself; add your own comma-separated, in Latin letters — as in the Rozetka Delivery API documentation:
| Your delivery status | Rozetka Delivery codes |
|---|---|
| Awaiting sender | planned, acceptedFromMerchant, acceptedFromReception |
| On the way | readyToCarrier, acceptedByCarrier, inTheWay, arrivedToDistributionCenter, acceptedOnDistributionCenter, forwarding |
| At destination | acceptedInDepartment, placedInStore, readyToIssueOctopus, storageDateIncreased |
| Delivered | gaveOut |
| Partially delivered | gaveOutPartially |
| Refused | clientCanceled, storageDateExpired, readyToReturn, inTheWayReturn, returned |
Without codes, parcels in “Shipments” are in the “Unknown” state.
How to create a Rozetka Delivery waybill from an order
Where: order card → “Delivery” section → “Create waybill”. The link is there if the order's delivery type is Rozetka Delivery; after the form is opened for the first time, it's called “Edit waybill”.
What the form fills in itself and what to check
| Field | Where it comes from |
|---|---|
| Shipping method | “Branch” or “Address” — by the order's delivery method; without it, “Branch” |
| Last name, First name, Middle name, Phone | From the order |
| City | By the city name from the order; among identical names, the largest city |
| Branch | The point from the order; if empty, on creation Elbuz looks for a point whose name matches the delivery address |
| Total weight, kg | The sum of product weights; if empty, 1 kg is sent |
| Length, Width, Height, cm | If empty, 30 × 20 × 10 cm is sent |
| Number of parcels | 1 |
| Declared cost, UAH | The order amount; must be greater than zero |
| Delivery payer | “Sender”; you can choose “Recipient” |
1
Length, width, height2
Delivery payer3
Cash on delivery, Money4
Create waybill- Length, width and height of the parcel in centimetres.
- Who pays for delivery: the sender or the recipient.
- Cash on delivery paid by the recipient, with the Money option.
- Creates the waybill (the button was not pressed).
For “Address”, fill in “Street”; “Branch” is required here too — without it the waybill won't be created. The form is saved to the order on every field change.
What happens after “Create waybill”
- Elbuz checks the sender in the entry (city, point, last name, first name, phone), the recipient in the form (last name, first name, phone, city, point) and the declared cost.
- It creates the waybill in Rozetka Delivery; Elbuz passes the order number to the waybill as your number.
- It writes the waybill number to the order.
Elbuz won't create a second waybill for the same order: “Waybill already exists: … — skipped.” The description is cut to 250 characters.
In bulk: order list → check the orders → “Create waybill (shipping)” (waybills in bulk).
Cash on delivery and who pays the fee
“Return delivery (recipient)” → “Money” is set automatically if the order isn't paid and payment is on delivery; the amount is the order amount. “Not required” means the parcel is handed over without payment.
According to the Rozetka Delivery API documentation, the recipient pays the cash-on-delivery amount at the point plus a fee of UAH 15 + 1.5%. How and when the money reaches you depends on your contract with Rozetka Delivery.
Parcel statuses and label printing
Every 10 minutes Elbuz asks Rozetka Delivery for statuses in one request for all waybills — up to 100 per pass. Orders from the last 60 days or in the marked statuses are tracked until the parcel code is next to “Delivered” in “Delivery statuses”. All parcels are in “Shipments”, and their state follows your code table.
Label: order card → “View waybill” → “Print”, or “Shipments” → row → “Print waybill”. Elbuz downloads the PDF from Rozetka Delivery and opens it in a window; the token never reaches the browser.
Scenarios
First connection
What to do. Create a static token, enter it in “Token”, fill in the sender, choose the drop-off point and check the codes in “Delivery statuses”.
What you get. The waybill form has cities and pickup points, and statuses come in by themselves.
Payment on delivery
What to do. Leave payment on delivery in the order and don't mark it as paid.
What you get. The waybill has cash on delivery for the order amount; the customer pays it plus a UAH 15 + 1.5% fee.
Home delivery
What to do. In the waybill form, set “Shipping method” → “Address”, fill in “Street” and keep the selected “Branch”.
What you get. A waybill for delivery from your point to the recipient's door.
What to do when something goes wrong
| What you see | Why | What to do |
|---|---|---|
| “The delivery service is not connected: fill in its API settings…” instead of the form | The Rozetka Delivery entry has an empty “Token” or “Active” is off | Enter the static token and turn on “Active” (connection) |
| “Error: sender department is required (API settings)” (or sender city, first_name, last_name, phone) | The sender or drop-off point isn't filled in | Fill in the “Sender” block (connection) |
| “Error: city is required for recipient” or “department is required for recipient” | The recipient's city or point wasn't found in the directory | Choose the city and branch in the form manually |
| “Error: Unauthorized” or “HTTP 401” in the waybill | The token isn't valid: it was deleted, or a session token was entered | Create a new static token and enter it (token) |
| Rozetka Delivery parcels in “Shipments” are in the “Unknown” state | The entry's “Delivery statuses” table is empty | Enter the codes (code table) |
FAQ
How much does the Rozetka Delivery integration cost?
Elbuz charges nothing for waybills, labels and statuses. You pay Rozetka Delivery for delivery under your contract.
How is this different from “Waybill via Rozetka”?
Here it's your contract and your token, for any order. “Waybill via Rozetka” is for marketplace orders, using the seller's credentials (more).
Can I extend parcel storage from Elbuz?
No, storage is extended in the Rozetka Delivery account. Elbuz shows the parcel in “Shipments”, and you can send the customer an SMS.
Why dimensions if I don't know them?
Rozetka Delivery requires them. Elbuz fills empty fields with 30 × 20 × 10 cm.
Can I send a shipment as several parcels?
Yes, the form has “Number of parcels”. Weight and dimensions are set once for the whole waybill.
Where to find it and who has access
- Menu
- Account → System settings → Other settings → External services and integrations → Delivery
- Other entry points
- Directories → Documents → Shipments → “Delivery services”; order card → “Delivery” section
- Access right
- connection — “API & access tokens”; waybill — the “Delivery waybill creation” window; parcels — “Shipments”
- Prepare
- a Rozetka Delivery partner contract, a static token, the drop-off point you ship from
A waybill can be created only for an order the user can see under the “Data scope” setting.
- Create a static tokenRozetka Delivery
- Enter the token and senderExternal services and integrations → Rozetka Delivery
- Choose a drop-off pointSame place, “Service directories”
- Fill in status codesSame place, “Notification settings”
- Create a waybillOrder card, “Delivery” section
Related topics
- If you want to see parcels of all services in one list — Shipments.
- If the order came from the Rozetka marketplace — waybill via Rozetka.
- If you also ship with Nova Poshta — Nova Poshta API in Elbuz.
- If you need waybills for dozens of orders — waybills in bulk.
