↑↓ selectEnter openEsc close

    1. Elbuz
    2. Ukrainian marketplaces

    How to import your catalog and orders from Rozetka into Elbuz

    24 min readUpdated

    Elbuz pulls your Rozetka catalog via the API with a seller account key, no files, and merges it into the base catalog with your other channels.

    When you need this:

    • Your catalog lives in your Rozetka account — products arrive with prices, stock, attributes and photos.
    • Rozetka rejects some listings — the run log shows how many are under moderation, invalid or rejected.
    • You get orders from Rozetka — they arrive as documents with returns, waybills and commission.
    • You changed an order status in Elbuz — Rozetka gets it with the waybill number.

    Where to start: generate an API key and paste it into the “Rozetka” template in “Data import”.

    What the Rozetka connection does

    • Catalog — name, description, prices, stock, SKU, manufacturer, category, photos and attributes go into the product card.
    • Listing states — products with errors, under moderation, hidden or rejected show up in the log, and problem listings are added to the catalog.
    • Orders — together with returns, waybill statuses, commission and money movements.
    • Status write-back — your order status goes back to Rozetka along with the waybill number.
    • Schedule — the template updates prices and stock and adds new products on its own.

    What you need from Rozetka

    Elbuz connects to the Rozetka Seller in one of two ways. Choose the key: it doesn't let anyone sign in to your account, and you can revoke it without changing your password.

    MethodWhat to enter in the templateWhen to use it
    API keythe “Rozetka API key” field; the string starts with gapi_the main method for new connections
    Login and passwordthe seller account “Login” and “Password” fieldstemplates set up earlier — they keep working

    If both the key and the password are filled in, Elbuz uses the key. The key is sent with every request as is. With a login and password, Elbuz first signs in to the Seller API, gets a temporary token and signs in again when it expires.

    How to get a key and connect the template

    1. In your Rozetka seller account, open “Налаштування” → “Безпека API” (Settings → API security).
    2. Click “Генерувати API токен” (Generate API token). A row appears in the table with the key, your role and the expiry date.

    The key gets the permissions of the role it was generated under. Elbuz needs a role with access to both products and orders. A key for the “Контент-менеджер” (Content manager), “Менеджер з фінансів” (Finance manager) or “Менеджер з обробки замовлень” (Order processing manager) role only opens that role's data, so orders or products won't load.

    1. Copy the key with the copy button at the end of the row: the table shows it truncated.
    2. In Elbuz, open the import window → the “Rozetka” template → the “Connection” card, paste the key into the “Rozetka API key” field and save the template. “Active” and “Orders” are already on in a new template: 5 minutes after saving, Elbuz starts pulling the account's whole order history. Elbuz maps the marketplace statuses to yours by itself, by name; what arrived and how it was mapped is shown in the template's “Order statuses” window. Want to test it first? Clear “Orders”.
    3. Click “Test connection”. A success message means Rozetka accepted the key. “Невірний токен доступу” (Invalid access token) means the key was copied incompletely, deleted or became inactive.

    The key is tied to an employee's role: “Власник” (Owner) and “Адміністратор” (Administrator) create keys for other managers too, other roles only for themselves. A manager can have up to ten keys. “Видалити всі токени” (Delete all tokens) revokes access for all integrations at once — then paste a new key into the template.

    Rozetka deactivates a key unused for more than 24 hours; the key's expiry date is in the “Безпека API” table. An active template with “Orders” contacts Rozetka every 5 minutes, so the key stays active; schedule a catalog-only or reviews-only template at least once a day. After a pause or past the expiry date, paste a new key into the template.

    The API key is covered in the Rozetka seller help center (section “Особистий кабінет → Інструменти”, Seller account → Tools). Method reference is in the Seller API documentation. If access doesn't work, contact Rozetka support under the topic “Акаунт, особистий кабінет, API” (Account, seller account, API).

    What to turn on in the template

    In the “Select data to import” card, three checkboxes matter for Rozetka:

    • Products — pulls the catalog into the Elbuz base catalog and, once the catalog has been read to the end, also collects listing states.
    • Orders — brings in orders, returns, waybill statuses and finances.
    • Reviews — pulls store reviews and product questions into your moderation inbox, along with the marketplace's service requests about orders.

    Next to them are the catalog refinement checkboxes: Photo (import images) and Attributes (pull attributes). Categories and Manufacturers are created from product data automatically. With “Products” cleared, the catalog isn't updated — this way you can pull only orders.

    All API sources share this set of checkboxes, and some don't apply to Rozetka. Rozetka works by polling: it has no instant notifications, so the “Use webhooks” checkbox has no effect. A new order usually appears in Elbuz within 5 minutes (schedule).

    What goes into the product card

    Each Rozetka product is mapped to Elbuz card fields as follows:

    Rozetka dataElbuz card field
    name_ua / name / name_ru (by database language)Product name
    descriptionFull description
    pricePrice
    price_oldOld price (before discount)
    stock_quantityStock (availability)
    articleSKU
    rz_producer / price_producer_nameManufacturer
    price_category / rz_categoryCategory (catalog structure)
    photo (list of s)Images — when the “Photo” checkbox is on
    params (separate /goods/details request)Attributes — when the “Attributes” checkbox is on
    rz_item_idMarketplace link key (used to update prices and stock)
    price_offer_idSecond link key (offer)
    • Name — in your database language: a Ukrainian database takes the Ukrainian name, any other takes the Russian one; if that one is missing, whichever exists is used.
    • Category — from the seller's category, or from Rozetka's own category if there is none.
    • Manufacturer — first from the Rozetka manufacturer list, and only if that's empty, the name from the seller's data.
    • Marketplace link — Elbuz later uses it to update prices and stock, so every product arrives with it.

    Attributes and images

    Rozetka returns attributes separately for each product; it has no bulk export of parameters. So the first import of a large catalog with “Attributes” on takes longer: Elbuz requests parameters one product at a time.

    Later runs skip products whose attributes are already filled in: the first pass fills the catalog, after that only new products are added. Elbuz takes values even when Rozetka hasn't matched them to its own reference list — the seller's own value is used.

    Images are imported only with the “Photo” checkbox — all of a product's pictures, in the order the marketplace returns them. If you keep your own media library, leave this checkbox cleared.

    The “Products - rozetka” service category

    Categories and manufacturers are looked up in your directories by name and created if missing — the general rules. Specific to Rozetka: products with no category name at all go into the “Products - rozetka” service category. It is created disabled and excluded from exports.

    Moving cards from it to your categories is safe. The Rozetka link is stored apart from category and manufacturer; the card shows it as the “ID rozetka #template number” row. A repeat run doesn't move the product in the tree: the category is set only on card creation. Deleting the service category is pointless: the next run recreates it, empty.

    Which listings Rozetka rejects

    After the catalog, Elbuz makes a separate pass to collect the state of your listings on Rozetka. The pass runs only when the catalog has been read to the end: after “Stop” or an API error it doesn't start, and the marks from the previous run stay.

    Elbuz goes through six sections of your seller account and records a state for each product along with the reason text (error, stop words, blocking reason):

    • products with errors;
    • invalid;
    • under moderation;
    • hidden by a moderator;
    • outside the allowed price range;
    • with changes awaiting confirmation.

    You see the result in the run log; the interface has no state column. First comes a summary: products in the account, on sale, inactive, under moderation and rejected. Then a line per group, for example “Rozetka: invalid products: … — the marketplace rejects the listing (usually required attributes are missing)”. The last line is the status of moderation requests.

    Problem listings (invalid, rejected) don't appear in the regular Rozetka catalog output. So you don't lose them, Elbuz adds them to the catalog and marks their state right away.

    The state mark doesn't stick. The pass first clears all marks of this template, then sets them again on the products it found in the account this time. A product that was fixed or disappeared from Rozetka is left without a mark.

    A product disappeared or was taken off sale on Rozetka

    Nothing happens to the card in Elbuz: a product missing from the run keeps its last price and stock, isn't disabled, and nothing about it is written to the log — the general rule. The Rozetka template has no switch that deletes missing items: remove them by filtering in the “Products” window and bulk deletion.

    Elbuz doesn't carry over the active flag from Rozetka: every product that arrives, new or existing, is set to “Enabled”. A card you disabled in Elbuz but still listed on Rozetka gets re-enabled by the next run. Only the “Do not update” flag in “Import protection” keeps it disabled, and it also locks the card against all other updates.

    The Import protection group in the product card: Do not update, Do not update attributes, Do not update photo, Fixed Price.
    1Do not update
    1. Do not update — the Rozetka import will not change this product's status, price or stock.

    If the product didn't disappear but was hidden by a moderator or rejected, you'll see it from the listing state pass. Nobody disables the card or zeroes its stock in that case.

    Orders, returns and finances

    With the “Orders” checkbox, the same connection brings in:

    • new orders — as “Customer order” documents;
    • return requests — as “Return from customer” documents with the return reason;
    • delivery statuses for waybills of all carriers;
    • finances: commission is written into the order itself, actual balance movements become cash receipts and cash payments, and monthly sales reports become certificates of completion.

    Elbuz maps a Rozetka order status to yours by itself, by name; you can refine it and map payments and delivery with the buttons in the “Related settings” card. The first run pulls all orders in the account, later runs only those changed since the previous one. There are no duplicates: the document is found by the Rozetka order number together with the source code.

    Orders and stock: when inventory moves

    The import itself doesn't touch inventory. The order arrives as an unposted “Customer order” document. Such a document doesn't write off goods but reserves them, and the reservation appears only after posting.

    • You posted the order — stock stays the same, but the available quantity drops by the ordered amount.
    • The order reached a final status (completed, delivered, canceled, returned) — the reservation is released. Payment doesn't release it: a paid but unshipped order keeps holding the goods.
    • You issued a sales invoice — the shipped quantity is written off the stock and no longer counts as reserved.
    • Inventory tracking is off (for example, dropshipping) — no reservation is kept, and posting doesn't affect availability.

    A “Return from customer” document records the customer's request; on its own it doesn't add stock back.

    Two rules for orders already in Elbuz:

    • The document isn't posted — every run updates it, but your processing status changes only if the status on Rozetka's side changed since last time. The manager's work isn't overwritten.
    • The document is posted — the import no longer touches it: not the status, payment or delivery. The exception is the marketplace commission, which is always written.
    What the next run does with an order. The main branch point is “Document posted?”: for a posted document, the import changes only the commission and the waybill number and status
    NoYesYesNoYesNoAn order arrived from RozetkaIs there already a document withthisRozetka order number?A “Customer order” is createdunpostedDocument posted?Import doesn't change itexcept the marketplace commissionand the waybill number and statusPayment and delivery are updatedby the mappingDid the status on Rozetka changesince the last run and is it mapped?Your processing statuschanges by the mappingThe status set by the managerstays
    • Action or result
    • Decision: the path depends on the answer

    How an order finds the customer and the product in the catalog — the general order import mechanics.

    Writing order status back

    The order link with Rozetka is two-way: when a manager moves an order through your statuses, Elbuz sends the matching status to the marketplace. The customer sees the current state, and you don't have to repeat the action in your Rozetka account.

    • The mapping comes from the same status matching table used for import, in reverse.
    • Only orders whose status changed since the last send are sent.
    • The waybill number is sent along with the status if it's filled in.

    For statuses related to handing an order to a carrier, Rozetka requires a waybill number. If the field in the document is empty, the order is skipped and the log gets an entry with its number. Get the waybill first, then move the order to the shipping status.

    When a status change reaches Rozetka and when it doesn't. A yellow diamond is a branch point
    NoYesNoYesYesNoA manager changed the orderstatus in ElbuzDid the status actually changesince the last send?Nothing is sentIs it a status for handingover to a carrier?Status goes to RozetkaIs the waybill numberfilled in?Status and waybill numbergo to RozetkaOrder skipped,log entry with its number
    • Action or result
    • Decision: the path depends on the answer

    Status write-back is done by an export task, not the import template, and it has its own schedule. If statuses on Rozetka aren't updating, check the export task.

    Scheduled updates and run size

    Elbuz fetches orders by itself every 5 minutes if “Orders” is checked in the template and the key is filled in — along with returns, waybill statuses and finances. This is done by the shared “Marketplace orders” task in the “Job schedule” window, where you can also change the interval. The catalog and reviews aren't imported in this pass, and orders also picked up by the template's own schedule aren't duplicated.

    The catalog and reviews are updated by the template's own schedule — the “Schedule setup” button in the “Related settings” card. Run it rarely, for example at night: while the catalog is importing, the orders pass is skipped until the next one, so a long daytime run delays orders. How scheduling works — updates and scheduling for API sources.

    How much data one run pulls

    • There's no cap on the number of products. The catalog is read in pages of 100 items until Rozetka reports there are no more pages. Each page leaves a log line: “Rozetka: catalog page 3 of 12, products received: 300”.
    • Products are written to the catalog in batches of 500, so you see results before the run finishes.
    • Attributes take a separate request per product that doesn't have them yet, with a 0.1-second pause between requests. At the end, the log says: “Rozetka: attributes loaded for N products, M already had them”.
    • The listing state pass after a full catalog adds six more passes through the account, also in pages of 100.

    Elbuz waits no longer than 180 seconds for one request (30 to connect). On a server error or “too many requests”, the request is retried — up to three attempts with pauses of 3 and 6 seconds. If the third attempt also fails, catalog reading stops and the log gets a “Rozetka: API error —” line with the marketplace's reason.

    Catalog pass: the inner loop is the products of one page, the outer loop is pages. Two branches cut catalog reading short: an API error and “Stop”, and only “Stop” writes what was collected after the last batch. The listing state pass runs only after a full catalog pass
    YesNoYesNoYes — separate requestand 0.1 s pauseNoYesNoYes — batch is written tothe catalogNoYesNoA catalog page is read100 items per pageDid Rozetka return an error?(server failure — after threeattempts)Catalog reading stopslog shows “Rozetka: API error —”listing state pass doesn't startWas “Stop” clicked?Collected items are written to thecataloglog shows “import stopped”listing state pass doesn't start“Attributes” is onand the product has no attributesyet?Product is added to the batchMore products on the page?500 or more in the batch?More pages?The rest of the batch is written to thecatalogthen the listing state pass
    • Action or result
    • Decision: the path depends on the answer

    You don't need to watch the window: the run log lives in the Operations Center, and you can close the template card — how to track a run.

    Run a large catalog the first time with “Attributes” off — the run skips per-product requests. On the next run, turn “Attributes” on: it fills in attributes for products that don't have them yet.

    Scenarios

    You keep your catalog in Elbuz and need only orders from Rozetka

    Turn on “Orders” and clear “Products” — orders will arrive by themselves every 5 minutes; you'll need the template's schedule only for “Reviews”. The run brings orders, returns, waybill statuses and finances. The catalog isn't read: prices, stock and listing states aren't updated. Inventory doesn't move from the import — the order arrives unposted.

    First connection of a large catalog

    Do the first run with “Products” on and “Attributes” cleared: the catalog arrives without per-product requests. On the second run, turn on “Attributes” — Elbuz requests attributes only for products that lack them. This run doesn't erase existing values; it only adds missing ones to existing cards.

    You keep photos in your own media library

    Clear the “Photo” checkbox — catalog products arrive without images. The exception: problem listings (invalid, rejected) added by the state pass arrive with photos regardless of the checkbox.

    You need to see in Elbuz which listings Rozetka rejects

    Turn on “Products” and let the run read the catalog to the end, without “Stop”. The log shows an account summary and a line per problem group, and the pass adds products you don't have yet on its own. The mark isn't kept between runs — each pass sets it anew.

    A card disabled in Elbuz must not be re-enabled by a run

    In the card's “Import protection” section, turn on “Do not update”. A Rozetka run won't change its status, name, price or manufacturer. The flip side: price and stock from Rozetka stop updating for it too.

    What to do when the connection misbehaves

    Common problems
    What you seeWhyWhat to do
    Authorization error in the log The key was copied incompletely, deleted in the account, or deactivated after more than 24 hours unused; with password sign-in, the password was changed on Rozetka Generate a new key in “Безпека API”, paste it into the template and click “Test connection” (how to get a key)
    The catalog is read, but for orders the log says “В доступі відмовлено” (Access denied) The store hasn't passed Rozetka verification yet — the status is shown in the account: “Налаштування” → “Мій магазин” (Settings → My store) Complete store verification; there's no need to reissue the key
    Products arrived with the “under moderation” state The items haven't passed review on Rozetka's side yet — this isn't an import error Wait for moderation; the state is shown in the log (listing states)
    Some attributes are empty Elbuz carries over exactly what Rozetka returns Fill in the cards in the Elbuz catalog
    The order status on Rozetka didn't change Write-back is done by the export task; delivery statuses need a waybill Check the export task and the waybill number (status write-back)
    A disabled card is enabled again A run sets “Enabled” on every product that arrives The “Do not update” flag in the card (missing products)
    The run broke off or was stopped Connection loss, three API errors in a row, or “Stop” Run it again — there won't be duplicates (broken-off run)
    Someone else's catalog was pulled in, or unwanted photos and attributes Another store's key or login, or “Photo” and “Attributes” were left on Find and delete the run's products (the run did the wrong thing)

    Before putting the catalog on a schedule, do a test run and check a few products: names, prices, images, categories, statuses.

    If a run broke off midway

    The catalog keeps everything that arrived in batches of 500; the rest keeps its old data. Running again is safe — how this works for all sources is described in the overview. Specific to Rozetka:

    • Attributes don't start from scratch — per-product requests repeat only for products not reached last time.
    • Orders won't be duplicated — the document is found by the Rozetka order number.
    • State marks stay from last time after a break during the catalog. A break during the state pass itself leaves some products without a mark until the next full run.
    • “Stop” in the operation card writes what was already read to the catalog and logs “Rozetka: import stopped by the user, processed: …”. You can't resume from the same spot: the next run reads the account from the first page.

    If the run did the wrong thing

    New products from the run are found in the “Products” window by the “Source - name” column, overwritten ones by “Date updated” (how to roll back a run). Deleted cards take their Rozetka link with them. Which template a card came from is shown in its list of identifiers: the “ID rozetka #template number” row.

    • Photos are added only to products the run created — the extras disappear along with those cards.
    • Attributes are only added to existing cards. To remove what was added, use the trash icon “Clear product attribute values” in the card.
    The Attributes section of the product card with the tooltip on the red trash icon.
    1Clear product attribute values
    1. Trash icon — clears the attribute values of this product (tooltip: Clear product attribute values).

    Cleared values leave empty attribute rows in the card, and the next run treats them as loaded — they won't come from Rozetka again. To have attributes requested again, delete the rows with “Delete attribute”.

    FAQ

    Rozetka issues a token or a key — where do I get it?

    You generate the key in your seller account: “Налаштування” → “Безпека API” → “Генерувати API токен” (Settings → API security → Generate API token). Paste it into the template's “Rozetka API key” field (step by step).

    Do I have to enter my account password?

    No. The key doesn't let anyone sign in to your account and is revoked separately, so the template doesn't need a password. Templates set up earlier with a login and password keep working.

    Why does the first import take so long?

    Rozetka returns attributes one product at a time, so a large catalog with “Attributes” means many requests. Later runs skip attributes that are already filled in (run size).

    Can I pull only orders from Rozetka, without the catalog?

    Yes: leave only “Orders” checked in the template, and orders will arrive by themselves every 5 minutes (scenario).

    I have several stores on Rozetka — what should I do?

    Create a separate template with its own key for each account. The templates don't interfere with each other, can have different schedules and merge products into one base catalog.

    Where do Rozetka reviews go?

    With the “Reviews” checkbox, store reviews and product questions arrive in your moderation inbox along with the marketplace's service requests about orders.

    Where to find it and who has access

    Menu
    Operations → Data import → template of the “Rozetka” type
    Access right
    the “Import” window in group permissions
    Prepare
    an API key from your Rozetka seller account (or the account login and password)

    One template is one connection to one Rozetka account. If you have several stores on Rozetka, create a separate template with its own key for each.

    Rozetka API connection form: credentials card, connection test button and data selection checkboxes
    1Rozetka API key field
    2Login field
    3Password field
    4Test connection button
    5Products checkbox
    6Orders checkbox
    1. Rozetka API key field — paste the key from your seller account here.
    2. Login field — your Rozetka seller login.
    3. Password field — your Rozetka seller password.
    4. Test connection button — checks the credentials without starting an import.
    5. Products checkbox — include products in the data to load.
    6. Orders checkbox — include orders in the data to load.

    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