Elbuz pulls orders from your Kasta HUB seller account through the Kasta API with a token and adds them as documents to the same queue as your other channels. The status and waybill number can go back to Kasta.
When you need this:
- Your Kasta catalog comes from an Elbuz feed — order items land on your product cards.
- Managers don't want to change the status twice — confirmation, waybill and cancellation reach Kasta on their own.
- A customer canceled or is returning an item — the document status changes by itself.
Where to start: “Data import” → “Add” → the “Kasta” type, then a token from your HUB account.
What the Kasta connection does
- Orders — the customer, recipient, Nova Poshta branch, waybill, payment and comment go into the document.
- Catalog matching — items find your product cards by SKU and name or by the product ID from your feed.
- Kasta statuses — mapped to yours with no setup, including cancellations and returns.
- Status back to Kasta — confirmation, packing, waybill and cancellation with a reason.
- Schedule — every 5 minutes, changed orders only.
This connection doesn't send products, prices or stock: your assortment goes to Kasta as an XML feed, and Kasta updates prices and availability from it.
How to connect Kasta with a token
- In your Kasta HUB account, open “Налаштування” (Settings) → the “API” tab and copy the token.
- In the “Data import” window, click “Add” and choose the “Kasta” type. The form has no “What to import” toggles: the connection handles orders only.
- Paste the token into the “Token” field of the “Connection” card. The form saves itself.
- Click “Test connection”. Success: “Connection works. Kasta (your organization name)”. Failure: “Connection failed:” followed by Kasta's response.
- A template with the “Active” badge starts pulling orders on its own within 5 minutes, the first time for the last 30 days. Don't want to wait? Click “Import”.
The token lets anyone read your orders and change their statuses. Don't send it in open chats. If you deleted or replaced the token in HUB, paste the new one into the template, or imports will be rejected.
What goes into the order
The order arrives as a “Customer order” document.
| Kasta data | What it becomes in Elbuz |
|---|---|
| order number | external number and the key used to recognize the order on later imports |
| customer: first, middle and last name, phone; email from the delivery address | the contact and the document's contact details |
| recipient: first name, last name, phone, city | delivery recipient |
| Nova Poshta delivery | delivery type “Nova Poshta”, the branch by its code, with the address from the Nova Poshta directory |
| shipment number | the document's waybill number |
| payment method | the Kasta code as is: card, cod (cash on delivery), bnpl (pay in installments) |
| a successful card charge or the “Paid” status in the order history | payment status “Paid”, otherwise “Pending” |
| comments | order description |
| status | document status (see the table) |
| items | document lines with the price the customer paid; items removed by an adjustment aren't carried over |
The document total is what the customer paid for the products. The delivery cost isn't added to the document.
How items find catalog cards
In an order line, Kasta returns the product ID from your feed (offer id) with the rzid_ prefix, plus the SKU, brand, color and size. The general search order is described in how items find a product:
- First — the card Elbuz already created for this Kasta item on previous imports, then the internal product code.
- Next — by SKU together with the name, then by the name alone. Elbuz builds the name from the product type, brand, color and size in the Kasta line.
- Last — by the feed ID as the product number in Elbuz: in the Elbuz Kasta template,
offer idis exactly that number. - Nothing found — Elbuz creates a card in the service category “Products - kasta - ‹template name›”. The category is created disabled, so these cards don't go into feeds on their own.
How Kasta statuses become yours
The mapping is built into the connection. Kasta doesn't return the current status as a separate field, so Elbuz works it out from the order history: cancellations and returns override delivery, and among delivery stages the latest one wins.
| Status on Kasta | Code | Document status in Elbuz |
|---|---|---|
| Created | Created | New |
| Confirmed | ConfirmedBySupplier | Confirmation |
| Packed; Registered with the courier service | Packed; AnnouncedForDelivery | Picked |
| Sent | SentToDelivery | Shipped |
| Arrived at the branch | AtLocation; ReceivedAtSelfDelivery | Delivered |
| Delivered | Delivered | Issued |
| Canceled | Cancelled | Canceled |
| Cancellation request (until the seller declines it) | CancellationRequested | Awaiting cancellation |
| Return created, sent, at the branch, delivered (unless the return is canceled) | ReturnCreated and others | Awaiting return |
| Return accepted; Refunded | ReturnArrived; Refunded | Returned |
1
Marketplace status2
Your status3
Packed row, mapped from the table- Marketplace status — the status name as Kasta sends it.
- Your status — the status your document gets in Elbuz.
- Packed — this row is marked 'from the table', so the mapping comes from the status table.
How the status and waybill go back to Kasta
When you change the status of a Kasta order in Elbuz, the new status goes to Kasta. For manual status changes this is off by default. A cancellation by AI support goes to Kasta regardless of the switch, as long as “Canceled” has the Cancelled code in the table. To turn it on:
- Turn on the “Send order status to the marketplace” switch: “Tickets” → gear → “Autonomous support” → the “Channels and proactive” tab.
- Open the Kasta template, click “Order statuses” and enter Kasta codes next to your statuses, for example: “Confirmation” — ConfirmedBySupplier, “Picked” — Packed, “Shipped” — SentToDelivery, “Canceled” — Cancelled. There's also AnnouncedForDelivery for registering the waybill, and Delivered for “Delivered”.
- You can skip intermediate stages. Elbuz asks Kasta to fill in the skipped stages itself, so you can set “Shipped” right away without “Confirmed” and “Packed”.
- Waybill. Kasta accepts “Registered with the courier service” and “Sent” only with a waybill number. If automatic shipment tracking is on in HUB, Kasta sets “Sent” itself and won't accept it from you — then enter AnnouncedForDelivery next to “Shipped”. If the document has no waybill number, Elbuz doesn't send the status and notes this in the document history. Enter the waybill number and set the status again.
- “Packed” — Elbuz takes the items and total from the order on Kasta itself. For card payments, Kasta charges the customer's card at exactly the “Packed” moment.
- A cancellation goes with a reason. A customer request, “changed my mind” or “found it cheaper” in a ticket to AI support — “Buyer requested cancellation”. A duplicate — “Duplicate order”. All other cases, including a manual “Canceled”, — “Seller's personal decision”.
- Resending is safe. Kasta accepts the same status for the same order only once, so sending it again doesn't create a duplicate.
- The result shows in the document history: “Status sent to the marketplace: Packed” or the reason it wasn't — the status isn't mapped, the template has no credentials, or Kasta returned an error.
For Kasta, the “Order statuses” table is only needed to send statuses back: on import, the built-in table maps them. If a row has several comma-separated codes, Kasta gets the first one.
What happens to an order that's already imported
The order is recognized by its Kasta number, so no copy appears. The rules are the same for all marketplaces (two statuses of one order):
- Document not posted, status on Kasta changed — the document status is overwritten according to the built-in table; if it's the same, your status stays.
- Document posted — it changes only to statuses that release the reservation: a cancellation or return on Kasta moves even a posted document, and the reservation is recalculated.
After a status is sent to Kasta successfully, Elbuz remembers the code it sent, so the next import with the same code won't overwrite your status. Totals, quantities and prices in the lines don't change on later imports.
Automatic import
The “Marketplace orders” system task pulls orders for all active Kasta templates that have a token every 5 minutes. The template doesn't need a schedule. Details: automatic order import.
- The first run pulls orders for the last 30 days.
- Later runs pull only orders changed after the most recent one already imported, with a 10-minute margin: statuses appear on Kasta with a delay.
- Run size — batches of 100 orders, up to 100 batches. A Kasta error breaks off the run without saving anything: the next run rereads the same window in full.
- Kasta limits. On “too many requests” (429), Elbuz waits longer and retries up to three times; on a server failure, also up to three times.
Log lines: “Kasta: page N, orders received: M” and, at the end, “Kasta: order import finished, total: N”.
The on/off switch is the “Active” / “Disabled” badge in the “State” column of the import list. Automatic import skips a disabled template, and statuses stop going to Kasta too: sending looks for an active Kasta template.
Scenarios
Orders should arrive on their own
Paste the token, click “Test connection” and make sure the template is “Active”. Every 5 minutes a run pulls changed orders; the first one covers the last 30 days.
A manager creates the waybill in Elbuz, and Kasta finds out by itself
Turn on status sending and enter SentToDelivery next to “Shipped”. Enter the waybill number in the document and set “Shipped”: Kasta gets the “Sent” status with the number; Elbuz asks Kasta to fill in the skipped stages itself. With auto-tracking in HUB, enter AnnouncedForDelivery next to “Shipped”.
A customer asks to cancel
A cancellation request from Kasta moves the document to “Awaiting cancellation”. Set “Canceled” — with status sending on and the Cancelled code in the table, Kasta gets the cancellation with the reason “Seller's personal decision”. Through AI support, a cancellation at the customer's request goes with the reason “Buyer requested cancellation”.
Items should land on existing cards
Export your catalog to Kasta with the Elbuz template and don't change offer id in it: then the ID in the order equals the product number, and the item finds its card.
What to do when orders don't arrive or the status doesn't get through
| What you see | Why | What to do |
|---|---|---|
| “Kasta: access token is not set” | The “Token” field in the template is empty | Paste the token from “Налаштування” (Settings) → “API” in your HUB account |
| “Kasta: API request error.” in the log | Kasta returned an error; the reason is on the same line | A one-off failure — the next run in 5 minutes rereads the same window. If the error repeats, check the token with the “Test connection” button |
| “Status … not sent to the marketplace: the marketplace requires a waybill for it” | The document has no waybill number for “Registered with the courier service” or “Sent” | Enter the waybill number and set the status again |
| “Status not sent to the marketplace: “…” is not mapped to a marketplace status” | This status has no Kasta code in the “Order statuses” table | Enter a code if the status should mean something on Kasta |
| “Status … not sent to the marketplace: …” with a Kasta response about an impossible status or auto-tracking being on | Kasta didn't accept the transition: the order there is already canceled or further along the chain, or Kasta tracks “Sent” itself | Check the status in your HUB account; with auto-tracking, send the waybill with the AnnouncedForDelivery code |
FAQ
Does this connection update prices and stock on Kasta?
No. Elbuz sends your assortment, prices and stock to Kasta as an XML feed, and Kasta updates them from it — see export to Kasta.
Why is the document total lower than in my Kasta account?
The document gets only the amount the customer paid for the products. Elbuz doesn't add the delivery cost.
What period do orders cover on the first run?
The last 30 days. Need a different period? Enter a date in the “Import orders from date (YYYY-MM-DD)” field in the “Advanced” section of the template form.
The customer dropped some of the items — what happens to the document?
Items removed by an adjustment on Kasta don't go into a new document. In a document that's already imported, lines and the total don't change on later imports — fix them manually.
Does Kasta interfere with a Rozetka or Prom connection?
No. Each marketplace has its own template, and status tables are kept separately for each template.
Where to find it and who has access
- Menu
- Operations → Data import → template of the “Kasta” type
- Access right
- the “Import” window in “Group permissions”
- Have ready
- a token from your Kasta HUB account (“Налаштування” (Settings) → “API”)
1
Token field2
Check connection button- Token — paste the token from your Kasta HUB account (Settings → API tab).
- Check connection — tests the token without importing anything.
Related topics
- If your catalog isn't on Kasta yet — exporting products to Kasta as an XML feed.
- If an order got attached to the wrong customer — importing orders via API.
- If you also sell on Rozetka — catalog and orders from Rozetka.
