↑↓ selectEnter openEsc close

    1. Elbuz
    2. Ukrainian marketplaces

    How to import orders from EVA.UA into Elbuz

    11 min readUpdated

    Elbuz pulls orders from your EVA.UA seller account via the EVA API (Merchant Center API) into documents, queued with other channels. It connects with your account login and password; the status and waybill can go back to EVA.

    When you need this:

    • Your catalog goes to EVA as an Elbuz feed — lines land on your cards.
    • Managers won't change statuses twice — confirmations and cancellations reach EVA themselves.
    • EVA requires a waybill on confirmation — it goes with the status.
    • The customer canceled on EVA — the document becomes “Canceled”, even if posted.

    Where to start: “Data import” → “Add” → “EVA.UA”, then your account login and password.

    What the EVA connection can do

    • Orders — customer, recipient, delivery, waybill, payment and comment go into the document.
    • Catalog matching — order lines find cards by the offer ID from your feed, or by SKU and name.
    • EVA statuses — mapped to yours with no setup.
    • Status back to EVA — confirmation, waybill and cancellation with a reason.
    • Schedule — every 5 minutes, changed orders only.

    This connection doesn't send products, prices or stock: the EVA API handles orders only. Your assortment goes to the marketplace as an XML feed.

    How to connect EVA with a login and password

    The EVA account has no separate keys or tokens. Elbuz signs in to the API with the same login and password you use for your EVA seller account.

    1. In the “Data import” window, click “Add” and choose the “EVA.UA” type. The form has no “What to import” switches: the connection handles orders only.
    2. In the “Connection” card, enter the “Login” and “Password” of your EVA seller account. The form saves itself; there is no save button.
    3. Click “Check connection”. On success you see “Connection works. EVA (your login)”. On failure — “Connection failed:” and EVA's response, for example about a wrong login or password.
    4. 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”.
    5. Open a few orders and check the lines, totals, customer and status.

    The password in the template is the same as for your account. If you change it on EVA, the next import is rejected, and the log shows “EVA: API request error.” with the reason. Enter the new password in the template and check the connection.

    What goes into the order

    An order lands as a “Customer order” document. EVA returns the list without details, so Elbuz reads each order with a separate request — EVA's documentation requires this too.

    EVA dataWhat it becomes in Elbuz
    order numberexternal number and the key by which the order is recognized on re-import
    customer: first name, patronymic, last name, phone, emailcontact and document contacts
    recipient: first name, last name, phonedelivery recipient
    delivery methodcarrier and method, written in Ukrainian: «Нова пошта (Відділення)», «Нова пошта (Поштомат)», «Нова пошта (Кур'єр)» (Nova Poshta branch, parcel locker, courier), «Укрпошта» (Ukrposhta), «Meest (Відділення)», «Meest (Поштомат)», «Meest (Кур'єр)» (Meest branch, parcel locker, courier)
    delivery addressone line: city, branch or street
    delivery costseparate from the products; document total = products + delivery
    shipment numberdocument waybill
    payment methodEVA code as is: CASH_ON_DELIVERY (cash on delivery) or LIQPAY
    payment statusauthorized — “Paid”, anything else — “Pending”
    customer commentorder description
    order statusdocument status (table)

    Currency is the hryvnia. The order creation and change dates on EVA are saved in the document.

    How order lines find catalog cards

    An EVA order line carries the offer ID — the offer id EVA got from your feed — plus the SKU, name, price and quantity. The search order is the same for all marketplaces (how lines find a product); for EVA it works like this:

    • First — the card Elbuz already created for this EVA offer on earlier imports.
    • Next — by SKU together with the name, then by name alone. In the Elbuz EVA template, the SKU is the manufacturer SKU from the card.
    • Last — by the offer ID as an Elbuz product number: in the EVA template, offer id is this number. If the feed wasn't built in Elbuz and its IDs are numeric, a line may land on an unrelated card with the same number.
    • Nothing found — Elbuz creates a card in the service category “Products - eva - ‹template name›”. The category is created disabled, so these cards don't go into feeds on their own.

    You can move cards from the service category to your own categories: a document line links to the product, not the category. Delete the service category itself last — it takes with it the products for which it is the main one.

    How EVA statuses become yours

    The mapping is built into the connection; you don't need to set it up:

    Status on EVACodeDocument status in Elbuz
    Нове замовлення (New order)1New
    Підтверджене продавцем (Confirmed by seller)11Confirmation
    Підтверджене покупцем (Confirmed by customer)12Picked
    Відправлено (Dispatched)5Shipped
    Скасовано покупцем (Canceled by customer)9Canceled
    Скасовано продавцем (Canceled by seller)10Canceled

    EVA sets “Dispatched” itself when the waybill shows the parcel was handed to the carrier. The built-in table knows no other codes: for them Elbuz takes the row from the template's “Order statuses” table, and without one the document gets “New”.

    Order statuses window with the marketplace statuses found in imported orders
    1Marketplace status column
    2Your status column
    3Row mapped from the table
    1. Marketplace status — the status name as EVA sends it.
    2. Your status — the Elbuz status the order gets.
    3. Rows marked 'from the table' use the built-in mapping.
    An order's path on EVA. The “Elbuz sends” arrows work when status sending is on, and cancellation by AI support always does; only EVA moves an order to “Dispatched”, and a canceled order can't move anywhere
    customer orders on EVAElbuz sends the statusElbuz sends the status withthe waybillEVA itself, by waybilltrackingwith a reasonwith a reasonwith a reason1 New order — in Elbuz “New”11 Confirmed by seller —“Confirmation”12 Confirmed by customer —“Picked”5 Dispatched — “Shipped”9 or 10 Canceled — “Canceled”
    • Start
    • State
    • End

    How the status and waybill go back to EVA

    Change the status of an EVA order in Elbuz, and the new status goes to EVA. For manual status changes this is off by default; cancellation by AI support always goes to EVA. To turn it on:

    1. Turn on the “Send order status to the marketplace” switch: “Tickets” → gear → “Autonomous support” → the “Channels and proactive” tab.
    2. Open the EVA template, click “Order statuses” and enter EVA codes next to your statuses: “Confirmation” — 11, “Picked” — 12, “Canceled” — 10. EVA receives the code set next to the document status.
    3. Make sure the login and password in the template work: Elbuz changes the status with the same sign-in.

    EVA accepts only these transitions:

    Now on EVACan move toCondition
    1 New order11, 9, 10—
    11 Confirmed by seller12, 9, 10for 12 — a waybill in the document
    12 Confirmed by customer9, 10—
    9, 10 Canceled—final status
    • Waybill. The EVA API has no separate way to send a waybill: the number goes with status 12. If the document's waybill is empty, Elbuz doesn't send the status and notes this in the document history. Enter the waybill and set the status again.
    • “Dispatched” (5) is not sent — EVA sets it itself. Don't enter 5 in the template's status table: the marketplace will return an error.
    • Cancellation goes with a reason. A manager set “Canceled” manually — 1012 «Інше» (Other). If AI support cancels on a customer ticket, the reason follows the ticket's reason:
      • customer request, changed their mind, or no reason given — 1001 «Передумав» (Changed my mind);
      • found it cheaper — 1003 «Купив в іншому місці» (Bought elsewhere);
      • duplicate — 1008 «Дубль замовлення» (Duplicate order);
      • any other reason — 1012 «Інше» (Other).
    • The result is in the document history: “Status sent to the marketplace: 11” or the reason it wasn't — no mapping, no template credentials, an EVA error (message guide).

    The “Order statuses” table works both ways. If the “Canceled” row has the list “9,10”, EVA receives the first code. A seller cancels with code 10, so put it first or alone.

    What happens to an order that is already imported

    An order is recognized by its EVA number, so no copy appears. The rules are the same as for other marketplaces (two statuses of one order):

    • The document is posted — the status changes only to a cancellation: if EVA sent 9 or 10, the document moves to “Canceled” and the reservation is recalculated. The import doesn't touch the rest of a posted document.
    • Not posted, same EVA code — your status stays; a manager's edit is left alone.
    • Not posted, EVA code changed — the status is overwritten from the table.

    After a status is sent to EVA successfully, Elbuz remembers the code it sent. So the next import that brings the same code won't overwrite your status.

    Totals, quantities and prices in lines don't change on re-import, and lines aren't deleted. In an unposted document, only empty contacts and the address are filled in, and the payment status is updated.

    Automatic import

    EVA doesn't send instant notifications, so Elbuz polls it: the “Marketplace orders” system task pulls orders every 5 minutes for all active EVA templates with a login and password. No template schedule is needed. More in automatic order import.

    • The first run pulls orders for the last 30 days.
    • Later runs — only orders changed after the latest one already imported.
    • Run size — pages of 100 orders, up to 500 pages. Every 200 orders are saved as a separate batch: a break-off keeps everything up to the last batch.
    • Network failures — 30 seconds per request to connect and 120 for the response. On “too many requests” (429) and a server error — up to three attempts with a pause, then a log line with the reason.

    Log lines: “EVA: page N, orders received: M” and at the end “EVA: order import finished, total: N”.

    How to pause the import

    Switch the “Active” / “Disabled” badge in the “State” column of the import list. Automatic import skips a disabled template, but a manual “Import” works. Documents, cards, login and password stay, and once you turn it back on, the run picks up everything that changed on EVA during the pause.

    Status sending to EVA looks for an active EVA template. Disable the only one, and statuses stop going to the marketplace, while the document history shows “the marketplace import template has no credentials”.

    Scenarios

    Orders should arrive on their own

    Enter your EVA login and password, click “Check connection” and make sure the template is “Active”. Every 5 minutes the run pulls changed orders, the first one — for 30 days. New orders land unposted, and stock doesn't move until they're posted.

    A manager confirms in Elbuz, and EVA finds out on its own

    Turn on “Send order status to the marketplace” and enter 11 next to “Confirmation” and 12 next to “Picked” in the template's “Order statuses”. The manager sets “Confirmation” — on EVA the order becomes “Confirmed by seller”. Once the parcel is booked, enter the waybill and set “Picked”: EVA gets status 12 with the waybill and then moves the order to “Dispatched” itself.

    The customer changed their mind — cancel on both sides

    Set “Canceled” in the document: with sending on and code 10 in the table, EVA gets “Canceled by seller” with the reason “Other”. If the customer canceled on EVA themselves, the next import moves the unposted document to “Canceled” without you.

    Lines should land on existing cards

    Export your catalog to EVA with an Elbuz template and don't change offer id in it. The offer ID in the order then equals the product number, and the line finds its card even if EVA renamed it during moderation. A line with no match gets a card in the service category, and the next order with the same offer lands on it.

    What to do when orders don't arrive or the status doesn't go through

    What you seeWhyWhat to do
    “EVA: seller account login or password is not set” The template's login or password is empty — EVA wasn't even contacted Enter your seller account login and password (how to connect)
    “Connection failed: …” with code 401 EVA didn't accept the login or password — often after a password change in the account Enter the current password and check the connection again
    “EVA: API request error.” in the log EVA returned an error; the reason is on the same line. On “too many requests” (429) and a server failure, Elbuz tries three times first; other errors are logged right away A one-off network or EVA server failure — the next run in 5 minutes picks up the rest. The error repeats every time — read the reason: most often it's the login and password
    “Status 12 not sent to the marketplace: the marketplace requires a waybill for it” The document has no waybill, and EVA doesn't accept customer confirmation without one Enter the waybill in the document and set the status again (status back)
    “Status not sent to the marketplace: “…” is not mapped to a marketplace status” The template's “Order statuses” table has no EVA code next to this status Enter a code if this status should mean something on EVA; otherwise do nothing
    “Status 11 not sent to the marketplace: …” with EVA's response about a forbidden transition EVA doesn't allow this transition — the order there is already canceled or further along the chain Compare the status on EVA with the transition table; a canceled order can't be restored
    Lines land in the service category, not on your cards The offer ID in the feed isn't an Elbuz product number, and the SKU and name didn't match the catalog Export your catalog with the Elbuz EVA template (matching)

    FAQ

    Can I use this connection to upload products or update prices on EVA?

    No. The EVA API works with orders only, so products, prices and stock go to the marketplace as an XML feed — export to EVA.UA.

    Where do I get a token in my EVA account?

    Nowhere: the account has no separate tokens. Elbuz signs in to the API with your seller account login and password and gets a temporary access key itself.

    For what period are orders pulled on the first run?

    For the last 30 days. After that, only orders changed after the latest one already imported are pulled. 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.

    Why can't I set “Dispatched” on EVA?

    EVA sets this status itself once the parcel is on its way by waybill. Your job is to send the waybill with status 12 (status back).

    Does EVA interfere with an Epicentr or Prom connection?

    No. Each marketplace has its own template, orders have their own source, and status tables are kept separately for each template.

    Where to find it and who has access

    Menu
    Operations → Data import → template of the “EVA.UA” type
    Access right
    the “Import” window in “Group permissions”
    Have ready
    your EVA seller account login and password

    One template — one connection to one seller account.

    EVA.UA connection card with Login and Password fields and the Check connection button
    1Login field
    2Password field
    3Check connection button
    1. Login — the EVA seller account login.
    2. Password — the EVA seller account password.
    3. Check connection — tests the credentials against EVA.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free