Elbuz order management software pulls orders from marketplaces, CRMs and POS systems via API into one document list, with no retyping.
When you need this:
- You sell on several marketplaces: every order becomes a “Customer order” document with your own numbering.
- A customer buys through different channels: Elbuz recognizes them and doesn't create duplicates.
- Each marketplace has its own status names: mapping tables convert them to yours.
- Managers work orders in their own statuses: the import keeps a status a manager set and still pulls payment and delivery from the marketplace.
Where to start: find your marketplace in the list and open its article for keys and specifics.
What order import can do
- Customer lookup: the order attaches to an existing contact, and a new one is created only when nobody matches.
- Matching lines to the catalog: each line looks for its product, and an unknown one isn't lost but becomes a product card.
- Status mapping: order status, payment status, delivery status and payment type are converted to yours.
- Protection of the manager's work: a status a manager set changes only after a new change on the marketplace.
- Automatic import without duplicates: Elbuz polls marketplaces by itself every 5 minutes, remembers where it stopped and recognizes orders it already imported.
Orders come from two kinds of sources:
- Catalog integrations that handle both products and orders: Rozetka, Shopify, WooCommerce, Amazon, eBay, Allegro, eMAG, and the SalesDrive. Orders are turned on there with a separate toggle in the template; see the marketplace articles and catalog import via API.
- Systems that bring only orders: the marketplaces Kaspi.kz, Prom.ua (EVO family), Epicentr, EVA.UA, Kasta, Forte KZ, ceneo.pl, and the dotykacka POS. Their products aren't pulled into the catalog; they arrive only as order lines.
| System | What it is and what you need |
|---|---|
| Kaspi.kz | the leading marketplace in Kazakhstan; you need a token from the seller account |
| Prom.ua (EVO) | the leading marketplace in Ukraine, EVO family; you need an account token |
| Epicentr | the epicentrk.ua marketplace; you need a token from the seller account |
| EVA.UA | the EVA Marketplace; you need the seller account login and password |
| Kasta | the kasta.ua marketplace; you need a token from your Kasta HUB account |
| Forte KZ | the Forte Market marketplace (Kazakhstan); you need an API key |
| ceneo.pl | a marketplace in Poland; you need an access key (exchanged for a token) |
| dotykacka | POS system (sales from a physical store arrive as orders); you need the instance and a token |
The list in the import window itself may be longer than this one, and it keeps growing. Orders from your own website also come in through the OpenCart 3 module and Horoshop.
The PrivatBank (Autoclient) connection sits in the same list, but it brings bank receipts, not orders: an account statement that payment documents are created from. That's a separate topic (payment reconciliation), not order import.
Why this matters for your business is covered separately: what it gives your store.
What happens to an order, step by step
Marketplaces differ, but every order goes through the same pipeline inside Elbuz. This is where you see why a customer got attached to an existing contact, where the document number came from, and why an order may be missing lines.
- Orders are fetched from the marketplace: new or changed ones, starting where the last run stopped.
- The customer is looked up among your contacts; if not found, a new contact is created.
- Lines are matched to the catalog: each order line looks for its product.
- Statuses are converted to yours: order status, payment status, delivery status, payment type.
- A document is created: a customer order with its own number in your numbering.
- The document's details are saved: lines, the number, weight and units of measure.
- The order lands on the board (pipeline) according to its status.
- Action or result
- Decision: the path depends on the answer
The document is created unposted: by itself it doesn't write off or reserve stock. What to do with it next is covered in the article on customer orders.
How the customer is found
Before creating a new contact, Elbuz tries to recognize an existing one. For comparison, the email address and phone number are normalized:
- case is ignored;
- only the digits of a phone number are used:
+38 (050) 123-45-67and380501234567are the same number; - for Gmail addresses, dots in the name and everything after the “plus” are ignored:
ivan.petrenko+shop@gmail.comandivanpetrenko@gmail.comare the same person.
Normalization happens only during comparison. The contact card and the order itself keep the address the customer entered, with dots and capitals. That's where your emails will go.
Then the customer is looked up step by step, and the first match ends the search:
| Step | What we search by |
|---|---|
| 1 | |
| 2 | phone |
| 3 | Telegram |
| 4 | the customer ID in this same source (a link created by earlier imports) |
| 5 | the contact's external ID in the contact card |
No match: a new contact is created, named after the company (or, without one, the first and last name), with phone, email, city and address, plus a link to this source. Next time the customer is recognized by it, even with a new email. If an order has no customer ID, Elbuz builds one from the email and phone.
Some sites put the store's own address into one-click orders, and all such orders would then pile up on a single contact. That's what the shared exception lists are for: the addresses and phone numbers in them are ignored when looking up a contact.
How order lines find products in the catalog
Each order line goes through a search, from the most reliable method to the most general:
| Step | What we match the line by |
|---|---|
| 1 | the product's link to this source (created when you import the catalog) |
| 2 | the product's internal code (uuid) |
| 3 | the product's checksum fingerprint |
| 4 | the SKU together with the name |
| 5 | the name alone |
| 6 | the Elbuz product ID the marketplace returned in the order (your feed sends it), only if that ID is numeric |
If the product isn't found, it's not lost: Elbuz creates a product card for it.
- Identical lines from different orders in one run get one shared card. Products are told apart by their marketplace ID, or without it by SKU plus name (in ceneo.pl, which sends neither ID nor SKU, effectively by name).
- The category is taken from the order itself, by name or external code. Some sources (Kaspi and Prom among them) don't send a category in the line, and then the line goes into a service category “Products — source — connection name”.
- The service category is created hidden and excluded from exports, so half-empty cards don't go out to your sales channels.
A card created from an order line holds only the name, SKU, price and quantity, with no description, photos or attributes. Every so often, move the products you find there to the right branch and fill them in, or match them to existing cards.
When a product is found and the order has no weight, the line takes it from the product card. The unit of measure is detected by name; if it isn't recognized, “piece” is used. Weight is needed to calculate the shipment.
How to map marketplace statuses to yours
Every marketplace has its own order status names. Elbuz converts them to yours by itself, trying these in turn until the first match:
- the marketplace's built-in table — available for Prom, Epicentr, Kaspi and Forte;
- the manual “Order statuses” table of this template — by code, by name, or by a row listing several external statuses separated by commas; rules of other templates aren't used;
- an exact match of the marketplace status code or name with your status — the name is compared in any of the app's languages;
- keywords in the code or name — per the table below, top to bottom.
| Word in the status code or name | Your status |
|---|---|
| unpaid, не оплач, очікує оплати | Awaiting payment |
| cancel, скасов | Canceled |
| refund, повернення коштів | Refund |
| return, поверн | Returned |
| delivered, received, отриман | Delivered |
| shipped, відправлен | Shipped |
| complete, виконан | Done |
| paid, оплачен | Paid |
| confirm, accept, підтвердж | Confirmation |
| process, оброб | In processing |
| new, pending, очіку | New |
If nothing matches, the order gets “New”.
To see how statuses were mapped, open the “Order statuses” window from the template form. The “Marketplace statuses in imported orders” block shows each marketplace status, how many orders came with it, your status and where it came from: “built-in marketplace table”, “from the table”, “by name” or “not recognized — “New””. Disagree? Enter the marketplace status code or name in the row of the right status in the table.
Payment status, delivery status, payment types and delivery types are mapped separately, each by its own button on the template's “Related settings” card: “Order statuses”, “Delivery statuses”, “Payment statuses”, “Payment types”, “Delivery types” (available for Kaspi, Prom, Forte and catalog marketplaces such as Rozetka). An unmapped external status doesn't lose the order: it gets the default status.
1
Order statuses2
Payment statuses- Order statuses — maps the marketplace order statuses to your own document statuses.
- Payment statuses — maps the marketplace payment statuses to your own payment statuses.
Delivery details come into the document along with the statuses: if the marketplace sends a waybill number, it goes into the field of its carrier (Nova Poshta, Justin, Ukrposhta), and you can track the order from Elbuz right away.
Two statuses of one order: yours and the marketplace's
- Your status: the “Status” column in the order list and the status in the document card. The manager maintains it: confirmed, packing, shipped.
- The marketplace status: what Rozetka, Prom or Kaspi thinks of the order. It appears in the next column, “Document status (site)”.
The two columns sit side by side, so you can spot a mismatch without opening the marketplace account. In the example below, the manager hasn't taken the order yet (“New” on our side), while the marketplace has it on hold:
1
Status (ours)2
Document status (site)- Status — our own order status, maintained by the manager.
- Document status (site) — the order status on the marketplace, kept separately.
Which status wins: yours or the marketplace's
An order lives in two systems, and both sides can change it. The rule for your status: the import changes it if the status in the source has changed since the last import or nobody has changed your status since the import. A status a manager set stays as long as the source keeps the same one.
“Changed” means any status change: in the window, by a pipeline, by a bulk action or by the import itself.
| What happened | What the next import does |
|---|---|
| The marketplace changed the status, you didn't touch the order | Your status updates according to the mapping |
| You changed the status, the marketplace didn't | Your status stays. The import doesn't touch it |
| The order was imported before you filled in the mapping, and you didn't touch it | Once the mapping is filled in, the status and payment are picked up by the next import, even if nothing changed on the marketplace |
| You set “Processing”, and a payment came in from the marketplace | The order status stays yours, and the payment status updates from the marketplace. They are separate fields and don't conflict |
| You moved the order to “Packing”, and the customer canceled it on the marketplace | The cancellation wins once, at the moment of the change on the marketplace. Later imports don't repeat it, and from then on you handle the order again |
| The delivery status comes from carrier tracking, and the marketplace doesn't send a delivery status | The delivery status stays. Only new orders get the default delivery status (“Awaiting sender”) |
| The order is already posted (signed) | Your status stays, with one exception: if the order was canceled, returned, handed over or delivered on the marketplace, the posted order gets the matching status and its reservation is released. Other status changes on the marketplace don't affect a posted order |
Payment, delivery, payment type and delivery type are always taken from the source if they have a mapping. Without a mapping, the field stays as it was.
The table above applies to Kaspi.kz, Prom.ua, Forte KZ, Horoshop, Epicentr, Rozetka, Kaufland, the tunnel, API v2 (POST /orders/sync), and catalog integrations when they fetch orders changed since the last import date. In Kaspi, Prom, Forte and Horoshop, a repeat import changes only the order, payment and delivery statuses; other document fields stay yours.
Cancellations from Kaspi, Prom and Horoshop come through only while the order is no more than 7 days old: to catch them, these templates reread the last 7 days of orders on every run. Forte KZ rereads the last thousand orders. If an older order is canceled, change the document by hand.
The dotykacka and ceneo.pl templates don't update imported orders at all: they send no cancellations, and every order arrives as “Paid”.
- Action or result
- Decision: the path depends on the answer
Modified date and the document change event
An order the import changed in any way (status, payment, delivery, marketplace status) gets a new modified date and the “Document: update” event. It fires triggers, processes (Flows) and the documents.updated webhook. If the order arrives unchanged, there's no new date and no events.
Marketplaces that accept status back (for example, Rozetka) receive it when you move the order on your side. The same status isn't sent twice, and your own update doesn't echo back to you.
The order disappeared from the marketplace
Order import never deletes documents. If the order was deleted, hidden or archived on the marketplace, the document in Elbuz stays:
- in dotykacka and ceneo, it doesn't change at all after the first import;
- for the other sources, it updates according to the table above while the source still returns the order; once it doesn't, nothing happens.
A repeat import doesn't touch the lines of an existing document: a line you deleted by hand won't be added back.
Automatic import and schedule
Almost all these systems work by polling: Elbuz contacts them for new orders by itself. A webhook (the marketplace pushes the order to you instantly) exists only in some integrations: Shopify, Wix, SalesDrive. How often:
- Marketplaces — automatically, every 5 minutes. The “Marketplace orders” system task fetches orders for all active templates with a key or app link, one by one. Prom, Epicentr, EVA.UA, Kasta, Kaspi, Forte — always; Rozetka, Allegro, Amazon, eBay, eMAG, Etsy, Kaufland, Bol, Cdiscount, Mirakl, OTTO, Newegg, ManoMano, Walmart, Zalando, TikTok — if “Orders” is checked in the template. The catalog and reviews aren't imported in this pass; they still follow the template's schedule.
- Other systems — on the template's schedule (or by webhook where available): OLX, Horoshop, Wix, Shopify, WooCommerce, SalesDrive, Odoo, ceneo, dotykacka. Set the schedule with the “Schedule setup” button in the template form: a dozen or more times a day for a busy store, less often for a quiet one.
The “Marketplace orders” task is shown in the “Job schedule” window (type “Import products”); that's where you change the interval. Don't disable or delete it, or marketplace orders will stop arriving.
If another import, including a manual one, is running, the pass is silently skipped and the next one fetches the orders. The pass doesn't recalculate product formulas.
To avoid fetching the same thing twice, Elbuz remembers the date and number of the last imported order. Both values are shown in the template form, in the “Advanced” block: the fields “Import orders starting from ID” and “Import orders from date (YYYY-MM-DD)”.
- Change them and save the template: the next run starts from the new value, within the limits the marketplace sets (Kaspi goes by date only and reaches back no more than 14 days).
- An empty field resets the remembered position.
- Each document stores the order ID on the marketplace, which is how an existing order is recognized and not duplicated.
Each run is logged: “Orders received” (from the marketplace), “Total orders imported” (new documents), and errors.
Imports run one at a time. A scheduled template doesn't start while another scheduled run is in progress: the log shows “Scheduled import canceled due to another template being imported (data processing conflict).”. It waits up to 10 minutes for the orders pass, and a manual run doesn't stop the template's schedule. General rules are in the data import overview.
How much one run fetches
Kaspi and Prom have no hard cap on the number of orders: Elbuz pages through until the pages run out. What differs is the period and the order states:
| Kaspi.kz | Prom.ua | |
|---|---|---|
| First import (the last order date in the template is empty) | Orders created in the last 14 days, separately in each of Kaspi's six states: new, signing, pickup, delivery, Kaspi Delivery, archive | No date limit: Elbuz pages through as long as the marketplace returns pages |
| Later imports | Orders in the same six states, created from the date of the last imported order to the end of today. If that date is older than 14 days, only the last 14 days are fetched | All orders from the start of the day the last imported order was created |
| Page size | Up to 1000 orders | 100 orders, with a one-second pause between pages |
Hence for Kaspi: if Elbuz hasn't fetched orders for long (template disabled, key expired), orders older than 14 days won't come in. For each Kaspi order, Elbuz requests the lines separately, plus two product requests per line; the limit is 20 seconds to connect and 2 minutes for a response. For Prom, Elbuz sets no time limit of its own.
The stop is checked before each order list request (in Prom, each page). In Kaspi, pages received before it are still saved, and the last order date moves to the newest of them. In Prom, a run stopped mid-paging saves nothing, and the next one requests the same orders. Prom also discards the whole run if a page fails to load.
Disable a template or delete it
Templates for Kaspi, Prom, Epicentr, Forte and universal connections (dotykacka, ceneo) have no separate “Orders” toggle: such a template brings only orders. You stop it with the state switch in the form header: “Active” / “Disabled”.
1
Template state badge- Template state badge — shows whether the template is Active or Disabled; clicking it switches the state at once.
- The scheduler skips a disabled template, but the “Import” button still works. Documents, contacts and links stay. Turn it back on and the run continues from the date of the last imported order (for Kaspi, no more than 14 days back).
- A deleted template disappears from the list along with its schedule. The documents, contacts and products it created stay. A new template for the same marketplace won't duplicate orders: a document is recognized by the order number and the marketplace code, not by the template.
If an import went wrong
You can't undo a run with one button, but everything it created is tagged with its source template, so you can clean up in bulk.
- Extra documents. In the order list, turn on the “Source: ID” column (template number) and filter by it, and by creation date if needed. Select and delete the documents. Posted ones aren't deleted, and Elbuz tells you how many remain; unpost them first. Deleted documents stay in “Document trash” for 30 days, and right after deletion the message has an “Undo” button.
- Extra contacts. In the contact list, filter by the “Source: name” column (the template name) and delete them; they go to the “Trash”. A contact in the trash doesn't leave the database, and the next import may attach orders to it again by email or phone.
- Product cards created from order lines can be filtered by the “Source: ID” column in the product list. A document line keeps its own copy of the name, SKU and price.
The last order date and number in the template don't roll back after cleanup. To start from a different point, change the fields “Import orders starting from ID” and “Import orders from date (YYYY-MM-DD)” in the “Advanced” block.
Scenarios
The marketplace provides both a catalog and orders
Goal: connect Rozetka, Shopify or another catalog marketplace so order lines land on your product cards.
What to do: import the catalog first, then turn on the orders toggle in the same template. Check the first import on a few orders: lines, totals, customer, status.
Result: every product has a link to the source, lines match on the first step with no accidental name matches, and the service category doesn't fill up with duplicates.
Managers use their own statuses without missing marketplace cancellations
Goal: work orders in your own statuses and see what's happening on the marketplace.
What to do: fill in the status mapping tables on the “Related settings” card and keep the “Document status (site)” column in the order list.
Result: a marketplace cancellation overrides your status once, even on a posted order, and its reservation is released; otherwise the status is yours. A canceled order you put back into work won't be canceled again by the same marketplace status. For dotykacka and ceneo, a mismatch shows only in the marketplace account; change the document by hand.
What won't happen: in Kaspi, Prom and Horoshop, a cancellation of an order older than 7 days won't come through.
Several marketplaces, one queue
Goal: process orders from all marketplaces in one list.
What to do: set up a separate template for each account, with its own key. A schedule is needed only for systems the “Marketplace orders” task doesn't poll.
Result: all orders come together in one “Orders” list with your statuses; a customer who bought on different marketplaces is recognized by email or phone.
You filled in the mapping after orders had already arrived
Goal: orders from a site or marketplace sit with the “New” status and no payment, because the “Order statuses” and “Payment statuses” tables were empty.
What to do: fill in both tables and wait for the next import, or click “Import”.
Result: for Epicentr, Rozetka, Kaufland, the tunnel and API v2, orders the source still returns and the manager hasn't touched get their status and payment from the mapping. Orders in work keep the manager's status but get the payment. Change orders outside the source's window (in the tunnel, those changed on the site more than 7 days ago) by hand.
Reimport a period after a mapping error
Goal: orders arrived with the wrong statuses because the mapping table was empty. In Kaspi, Prom, Forte and Horoshop, filling in the table is enough: orders the next run rereads pick up their status. A reimport is needed for dotykacka and ceneo, and for Kaspi, Prom and Horoshop orders older than 7 days.
What to do: fill in the table, delete the run's documents with a filter by “Source: ID”, change the fields “Import orders starting from ID” and “…from date” in “Advanced”, and run the template.
Result: the orders come in again, now with the right statuses. For Kaspi, the period can't go back more than 14 days.
What to do when orders arrive wrong
| What you see | Why | What to do |
|---|---|---|
| All orders arrive with the same status | The external status found no row in this template's mapping table | Add rows to “Order statuses” (mapping) |
| An order got attached to the wrong customer | The site puts in the store's own email or a shared phone number | Add the address or number to the exception lists (customer lookup) |
| The customer canceled the order on Kaspi or Prom, but Elbuz shows the old status | The order is older than 7 days and the template no longer rereads it; or an operator put the canceled order back into work | Change the document by hand (which status wins) |
| Old Kaspi orders didn't come in | Kaspi returns orders no older than 14 days | Don't leave the Kaspi template disabled for long (run limits) |
| A Prom run was stopped and there are no new orders | An interrupted Prom run saves nothing | Run it again: it will request the same orders |
| Order lines go into the service category | The product wasn't found in the catalog | Import the catalog from the same source or move the cards (line matching) |
| You filled in the mapping, but old orders are still “New” | Mapping is applied during import, not to documents already saved | Wait for the next import; change orders outside the source's window by hand (scenario) |
| There's no “Document status (site)” column | The column is past the right edge or turned off | Scroll the table right or turn the column on in the window's “Grid configuration” |
FAQ
Do I need to import the catalog first to pull orders?
No, order lines aren't lost: unknown products become product cards. But with a catalog, lines match precisely and without duplicates (scenario).
Do orders arrive instantly?
Almost everywhere, no: Elbuz fetches marketplace orders every 5 minutes and other systems' orders on the template's schedule. Instant delivery by webhook exists only in some integrations, such as Shopify and SalesDrive.
Will the import overwrite a status a manager set?
No, as long as the marketplace has the same status as last time. If the status on the marketplace changed, yours updates according to the mapping. A posted order gets a new status only if it was canceled, returned, handed over or delivered on the marketplace (table).
I filled in the mapping, but old orders didn't change. What should I do?
Wait for the next import: orders the source still returns and the manager hasn't touched get their status and payment from the mapping. Change older orders, and dotykacka and ceneo orders, by hand.
Will a repeat import duplicate orders?
No. The document stores the order ID on the marketplace, and an already imported order is recognized by it, even if the template was deleted and a new one created.
Can I connect several marketplaces at once?
Yes. Each account gets a separate template with its own key, and all orders flow into one queue. Marketplaces are polled automatically every 5 minutes; other systems need the template's schedule.
Where it is and who has access
- Menu
- Directories → Operations → Data import
- Where orders appear
- the “Orders” window, “Customer order” documents
- Access right
- the “Import” window in “Group permissions”
- Have ready
- an access key from the marketplace account, most often a single token
In the import window you create a template, pick the system from the list, enter the key and turn on order import. One template is one connection to one account; separate accounts or marketplaces get separate templates.
Related topics
- If the marketplace also provides products: Catalog import via API.
- If orders need to be posted, reserved and shipped: Customer order.
- If you sell on Kaspi: Kaspi.kz order import; on Prom: Prom.ua order import.
- If your site or accounting system should send orders itself: store orders via API v2.
- If you're choosing a CRM for your store: what it gives your store.
