↑↓ selectEnter openEsc close

    1. Elbuz
    2. Feeds and marketplaces

    How to export your catalog to Rozetka: XML feed and API

    19 min readUpdated

    Elbuz builds an XML feed for Rozetka from your catalog, at a permanent link: the marketplace fetches it and creates and updates product pages.

    When you need this:

    • You list on Rozetka for the first time — the feed creates pages with names, descriptions, photos, attributes, prices.
    • Prices and stock change daily — the feed is rebuilt on schedule; between runs an API template updates price and quantity.
    • Products must go into Rozetka categories — the app inserts their category and attribute numbers.
    • An item goes off sale but keeps its page — the stock status gives available="false".

    Where to start: create a Rozetka.UA template in the “Data export” window.

    What the Rozetka export can do

    This is one of three different exchanges with Rozetka (in Ukrainian often written Розетка), and people mix them up all the time. The feed creates product pages. The updates prices and stock of products that are already on the marketplace. And import from Rozetka works the other way: it brings the catalog from the marketplace to you.

    How to create a template and give the feed to Rozetka

    1. Match your categories with the Rozetka category list. Only the ones whose products you plan to sell on the marketplace are needed — the rest can stay empty.
    2. Match the attributes inside the matched categories. Rozetka requires a different set of attributes for each category, and it's best to cover the required ones completely.
    3. In the “Data export” window, add a template of type Rozetka.UA. In the product template, replace the sample address with your own site's address (what goes into a product).
    4. Run the template and check the resulting file: categories must not have an empty rz_id.
    5. Copy the link to the file with the “Copy link” button.
    6. Check the feed in the Rozetka seller account: “Управління товарами” → “Валідатор” (Product management → Validator). Paste the link into the “Пряме посилання на файл” (Direct link to file) field and click “Перевірити” (Check). The check status appears in the table below the field. Before your store is even registered, you can use the public Rozetka validator: a link or file, an email and a captcha; the report arrives by email. In the Rozetka.UA template form, the checkmark button in the window header opens it.
    7. Give the link to Rozetka through support: in the seller account, write under “Робота з товарами, прайс-лист” → “Питання по вивантаженню XML” (Working with products, price list → XML export questions) and paste the link. The account has no “add feed” button, and the API can't pass the link either. You don't need a separate service like Pricecreator: Rozetka accepts a feed from any system, Elbuz included.
    8. A connected feed shows up as a row in “Управління товарами” → “Управління прайс-листами” (Price list management) with the link, period and last sync date. To fetch the feed out of turn, use “Синхронізувати” (Sync) in the row menu, at most once every 3 hours. New items land in “Товари” → “Нові” (Products → New). Send them with “Відправити на модерацію” (Send for moderation), or turn on “Автозаявку для нових” (auto-request for new items) in the price list row — then the request is created daily at 08:00 by default.
    9. In Elbuz, put the template on a schedule.
    10. To keep prices and stock updated between feed runs and to receive orders in Elbuz, connect import from Rozetka with an API key and an API export template (feed or API).

    The most common first-run mistake is exporting the feed before matching. The file is built and Rozetka takes it, but products either don't get created or land in a random category, and you have to sort it out on the marketplace side.

    Rozetka fetches the feed by itself, from the link. So the file must sit where the marketplace can reach it: on your site, on or in cloud storage — delivery options are described in “Where the file goes”.

    The copied link ends in a different ?uuid=… tail every time — it's an anti-caching tag. The file address itself stays the same from run to run, so you don't need to change the link in the Rozetka seller account.

    Don't put {DATE}, {DATETIME} or {TIME} in the file name: each run then saves a file under a new name, and the link Rozetka has points to yesterday's file or stops opening. A new Rozetka.UA template has a permanent name, export_rozetka.xml; clearing “File name” gives export_elbuz.xml and a new link. More: file name and FTP.

    What the app adds to the feed specifically for Rozetka

    When you create a Rozetka.UA template, the app prepares an XML template with three differences from basic YML. They decide whether the marketplace accepts the feed properly or puts products “somewhere else”.

    DifferenceWhat it looks likeWhy
    Marketplace category IDcategories get an rz_id attributeRozetka puts a product into its own category, not yours. Without this number the marketplace doesn't know where the product goes
    Marketplace attribute IDattributes get a paramid attributeRozetka matches your attribute with its own by number, not by name — “Diagonal” and “Screen diagonal” are different things to it
    Quantitya stock_quantity node is addedbasic YML only has an “in stock / not in stock” flag, while Rozetka shows the buyer the stock as a number

    The numbers for rz_id and paramid are stored in your categories and attributes. You fill them in once, in the marketplace matching window; the Rozetka columns are also visible in the attribute list.

    The app inserts these three things into the template by itself. You don't need to rewrite the template by hand — but if you have already edited it, check against this table: a missing rz_id or paramid looks like “the feed seems fine, but products don't get created on the marketplace”.

    Rozetka.UA export template: the category sub-template with the rz_id attribute
    1rz_id attribute
    1. rz_id — the Rozetka category number from the Rozetka directory is substituted here; without it the marketplace does not know where to place the product.

    What reaches the marketplace

    A product in the feed has the standard YML contents, plus quantity for Rozetka.

    In the feedWhere it comes fromWhat to check
    The id of the offer nodethe product's internal Elbuz a product deleted and created again is a different product for Rozetka
    Product linkproduct templatethe template has a sample address — replace it with your own site's address
    Price and currency, category, name, manufacturer, manufacturer part number, descriptionproduct card—
    Photosproduct cardno more than 15, see below
    Attributesproduct card; paramid — matchingvalues up to 255 characters
    Quantity stock_quantitythe “Quantity” field of the product card, as iszero in the card gives zero in the feed, even with the “In stock” status
    Availability flag availablethe template's “Stock-based update setup” windowsee below
    Barcodenot in the templateif the Rozetka category requires a barcode, add a line with the {ean} macro to the product template

    Numbers from the “Stock-based update setup” window don't go into the XML feed: they serve other export types. Only available comes from this window:

    • for each stock status, the feed gets your text from the “Title on site (in file)” column;
    • if the column is empty — true for a status marked as “in stock” and false for the rest;
    • for a status turned off in this window — true only for “In stock”, false for the rest.
    Stock-based update setup window with the stock status grid
    1Title on site (in file)
    2Active
    3Quantity
    1. Title on site (in file) — this text goes into the available attribute of the feed verbatim; an empty cell means true/false is set by the status flag.
    2. Active — an unchecked box turns on the fallback rule (true only for “In stock”).
    3. Quantity — this number does not go into the Rozetka XML feed; stock_quantity is taken from the product card.

    What the app trims specifically for Rozetka

    Three things in a product are handled differently than in regular YML. This happens silently: the log has no separate lines about it.

    • Photos — no more than 15. The rest don't go into the file, even if the product card has thirty. Identical links count as one. If the “Max Photos” field has a smaller number, that number applies.
    • An attribute value is at most 255 characters. A longer value is cut, and the truncated value goes to the marketplace.
    • Images and links are removed from text. The <img> and <a> tags are stripped from product fields inserted into the template — above all, from the description.

    A template counts as a “Rozetka” one by contents, not by type. The app looks for rz_id= in the category line, Rozetka in the attribute line template, or “rozetka” in the template description; one is enough. Rewrite the template without any, and the three limits stop working: all photos and descriptions with links go into the feed.

    What a repeat export overwrites and how to take a product off sale

    Each run builds the file from scratch: all products passing the template filter go into the XML template with current catalog values. Each product carries the full set of template nodes — a feed can't send one changed field alone. You can only narrow the product list, with the “Only export new data” checkbox.

    The same product always goes under the same UUID — that's how the marketplace sees an update of an existing item rather than a new one.

    The marketplace gets what is in the product template. If you maintain names in the seller account rather than in Elbuz, remove the <name> node from the template — whatever isn't in the file, Rozetka won't get from the feed. The same goes for the description, price and photos. The export has no “don't update this field” checkbox.

    What the marketplace does with the values it receives is up to its own rules: some changes land in the seller account under “на модерації” (in moderation) and “оновлення очікують підтвердження” (updates awaiting approval). To see the state of each product page without opening the seller account, use Rozetka catalog import.

    How to take a product off sale

    A feed has no “delete product” command. The file tells the marketplace about sales only through the availability flag and quantity inside the product. An item missing from the file sends no signal at all. So to stop selling, keep the item in the feed with a stock status giving available="false" (scenario) rather than dropping it from the filter.

    A product disappears from the file as soon as it stops passing the template filter: the export flag is cleared, the category is disabled, it fails the “Additional filter”, and so on. The full list of conditions is in “Why a product didn't make it into the file”. Two more matter for Rozetka:

    • the product is an option product (variant), and “Options” isn't checked in the template — in a new template this checkbox is cleared;
    • the template has a warehouse selected where the product has neither stock nor the “In stock” status.

    How to fix products that landed in the wrong category

    It's not the products you need to fix. The Rozetka category number lives in your category, so one matching fix changes the rz_id for all its products at once.

    1. Open the matching window and find the category with the wrong number.
    2. Replace the matching with the correct one (how to replace a link).
    3. Run the export again and wait for Rozetka to fetch the fresh file on its own schedule.

    Auto-matching won't help here: it fills in only empty matches. It doesn't touch a category that already has a number — even a wrong one. A wrong match is replaced by hand.

    Attributes have matches on two levels: a general one for the attribute and a separate one inside a specific category. The category match takes priority — if it's filled in, it's what goes into paramid. So an attribute that means different things in different Rozetka categories is matched at the category level.

    Schedule, interrupted runs and pausing the feed

    The schedule in Elbuz must run at least as often as Rozetka comes for the file. Otherwise the marketplace will pick up yesterday's prices, and it will look like “Elbuz doesn't update the data”. How to set a schedule and what happens when two templates overlap in time is covered in “Running manually and on a schedule”.

    If a run is interrupted

    A break in the middle of a run doesn't spoil what Rozetka already has: the file is built in a temporary folder and moved to the permanent address in one piece, as the last step. The link keeps serving the previous run's file — complete, if outdated — and the “Last export” column keeps the old date.

    Repeating an interrupted run is safe: the next run builds the file again. How to spot an interruption in the log is covered in “Run log”.

    The top two forks apply only to scheduled runs — running one template manually skips them. Then look at the “Did the run finish?” diamond: the “no” branch doesn't touch the file at the link, and old files are removed from storage only after the new file has been uploaded
    yesnoyesnono — “Stop” was clickedno — empty filtered set or afailureyesnoyesRozetka.UA template startsScheduled run while anothertemplate is exporting?Scheduled export canceled — a linein the logScheduled run while the template isdisabled in the “State” column?Template skipped silently — the fileat the link doesn't changeThe file is built in the account'stemporary folder, appended inportions of 500 productsDid the run finish?Export stopped by the user — awarning, the link keeps the previousrun's fileData export NOT completed — thelink keeps the previous run's fileWas the new file uploaded tostorage?The file was not uploaded to cloudstorage — Data export NOTcompleted, the previous file and linkunchangedThe link and export date in thetemplate are updated, other files inthe template folder are removed ifthe storage allows itIf “Only export new data” is on —the run's products are marked asexportedData export completed
    • Start or end
    • Action or result
    • Decision: the path depends on the answer

    Disable a template or delete it

    • You disabled the template with the “State” switch. The schedule skips it silently. The file at the link stays as the last run built it, and Rozetka keeps fetching it: prices and stock freeze at the moment you disabled it. The marketplace sees no error.
    • You enabled it again. The next scheduled run builds the file at the same address.
    • You deleted the template. The file itself isn't deleted from storage — the link keeps working and serves the last built file. To really stop Rozetka from taking your catalog, remove the link in the seller account.

    How much fits in a feed

    There is no cap on products: whatever passes the filter goes into the file. A demo account exports no more than 100 products. The run reports every 500 products with “Export products ‹N› of ‹M›” — while the number grows, the run is going. If your Rozetka feed is large, schedule it apart from other templates.

    Feed or API — which one when

    Rozetka has a second exchange channel, and it solves different tasks.

    What you needXML feedAPI
    Creates new product pagesyesno
    Updates prices and stockyes, together with the whole feedyes, item by item
    Returns order statuses and the numbernoyes
    What it takes to connectnothing but the file addressan API key from the seller account (or the account login and password)

    In the API export template, paste the key into the “Rozetka seller account password or API key (gapi_…)” field — the login can then stay empty. A template set up earlier with a login and password keeps working.

    The typical working setup uses both: the feed creates and expands the assortment, while the API keeps prices and stock fresh between feed exports and brings back to Elbuz what happened to orders.

    What exactly the API sends

    Only three values: price, old price and quantity — and only for products that already have a Rozetka product page number. The API doesn't touch names, descriptions, photos or attributes. It skips items without a page number and writes to the log: “Rozetka: items skipped without a marketplace link: ‹N› (product cards are published by the YML feed export)”.

    The page number doesn't come from the feed but from the opposite direction — Rozetka catalog import brings it. The order: the feed creates pages → catalog import brings their numbers to Elbuz → the API updates prices and stock by them. Until the second step has run, the API will skip everything.

    The left column is Elbuz, the right is Rozetka. The page number, without which the API sends nothing, comes by the right-to-left arrow — through catalog import, not the feed
    RozetkaElbuzProduct pages are created from the feedA product without a page number is skipped — the log gets a line about skipped itemsThe Rozetka.UA template builds the XML feed and puts it at a permanent addressFetches the file from the link on its own scheduleRozetka catalog import requests the seller's product pagesPages with numbers — Elbuz stores the number next to its productThe API template sends price, old price and quantity in batches of 100
    • Request or action
    • Reply
    • Note
    • A sharp price change isn't applied right away. A price raised more than 1.5 times or cut more than 2 times goes to a marketplace manager for review. After the run, Elbuz writes: “Rozetka: prices awaiting marketplace manager approval: ‹N›”. The other prices from the same run are already applied.
    • An empty old price removes the strikethrough price on the marketplace. If the old price in Elbuz is empty, the API sends −1 instead, and Rozetka removes the old price from the page.
    • Items go in batches of a hundred per request, and after each one the log gets a line “Rozetka: items updated: ‹N› of ‹M›”.

    Which one wins when both write the price

    Neither channel has priority: these are two templates with their own filter, schedule and price source. The feed takes the price from an XML template macro, the API template from its field list. Point both to one price field and they match. Otherwise the feed overwrites prices of all filtered products, the API only of those with a page number.

    Scenarios

    List products on Rozetka and keep prices fresh between feeds

    What to set up. Three templates, each with its own schedule: a Rozetka.UA template for the feed, a Rozetka catalog import, and a Rozetka API template with the seller account API key.

    What you get. The feed creates product pages. Catalog import brings the numbers of those pages to Elbuz and stores them next to your products. The API template sends the price, old price and quantity by those numbers.

    What won't happen. The API won't create a page or change the name, description, photos or attributes. A product not yet in the imported catalog is skipped by the API. A sharply changed price isn't applied until a Rozetka manager reviews it.

    Stop selling an item without removing its page

    What to set up. Give the product a stock status other than “In stock” — for example, “Out of stock” — and keep it in the template filter. In the “Stock-based update setup” window, leave the “Title on site (in file)” column for this status empty or enter false.

    What you get. The item stays in the feed, and available gets false. A “Pre-order” status without its own text in that column also gives false.

    What won't happen. The text from the column goes into the feed literally: a word like “None” ends up in available instead of false. If the template has a warehouse selected, a product with no stock and no “In stock” status in that warehouse drops out of the filter entirely.

    Pause the feed

    What to set up. Disable the template with the switch in the “State” column.

    What you get. The schedule skips the template, and the file at the link stays the one built by the last run. You can still check the feed with the run button — it works for a disabled template too.

    What won't happen. Rozetka doesn't learn about the pause: it keeps fetching the last file with prices and stock as of the moment you disabled it. To make the marketplace stop selling the items, use the previous scenario or remove the link in the seller account.

    One attribute means different things in different Rozetka categories

    What to set up. In the matching window, match the attribute inside each category where it's needed, not only at the general level.

    What you get. For products of that category, paramid gets the number from the category match. The same goes for the Rozetka attribute name: the category one takes priority over the general one. If there's no Rozetka name anywhere, your attribute name goes.

    What won't happen. In categories without a category match, products keep going with the general number.

    What to do when products don't appear on Rozetka

    What you seeWhyWhat to do
    Products don't get created on the marketplace categories have an empty rz_id — they aren't matched with the Rozetka category list match the categories and export the feed again (steps)
    Products were created, but without attributes empty paramid — the attributes aren't matched match the attributes in the categories you use (how)
    Rozetka shows “out of stock” for products you have the product's stock status doesn't give available="true" check the status in the template's “Stock-based update setup” window (where available comes from)
    The marketplace shows zero stock although you have the product stock_quantity comes from the “Quantity” field of the product card, and it's empty fill in the quantity in the card — the template's stock settings don't replace this number
    The product on Rozetka has fewer photos than the card no more than 15 photos go into the Rozetka feed put the ones you need first in order (limits)
    An attribute value on the marketplace is cut off for Rozetka, values longer than 255 characters are trimmed shorten the attribute value in the catalog
    The link you gave Rozetka stopped opening the file name contains a date macro: each run creates the file under a new name remove {DATE} from the file name and give the marketplace a permanent address (file name)
    The feed doesn't update, and the log has no errors the template is disabled in the “State” column — the schedule skips it silently enable the template; all this time the link served the old file (pause)
    Product links lead nowhere the template still has the sample site address replace it with your store's address
    Prices on the marketplace lag behind Rozetka comes for the file more often than Elbuz updates it make the schedule more frequent or connect the API
    “Rozetka: items skipped without a marketplace link” the products don't have a Rozetka page number yet create the pages with the feed and run Rozetka catalog import (order)
    Extra products got into the feed, or needed ones are missing the template's product filter what to do when the file has the wrong products

    FAQ

    What is rz_id and where does it come from?

    It's the category number in Rozetka's own category list. It's stored in your category after you match it with a marketplace category and is inserted into the feed automatically. You don't need to type it into the template by hand.

    Do I need to match all catalog categories?

    No, only those whose products you sell on Rozetka. Unmatched categories go without a marketplace number, and if their products don't pass the filter, they don't go at all.

    Can I do without the feed, using only the API?

    No, if your products aren't on the marketplace yet: the API updates prices and stock of existing pages, while pages are created by the feed.

    How do I check the feed before giving it to the marketplace?

    Do a test run in the template card — the app builds the same file with a test_ prefix in its name. Open it and check that rz_id isn't empty, the product links are correct and prices are there.

    I fixed a product name in the Rozetka seller account. Will the next feed overwrite it?

    The feed sends values from the Elbuz catalog — it doesn't know about edits in the seller account. If you maintain a field on the marketplace side, remove the matching node from the product template (what the feed overwrites).

    The Rozetka export says “items skipped without a marketplace link”. Why?

    This is a line from the API template, not the feed. The API updates only products with a Rozetka page number, and that number comes from Rozetka catalog import. Create the pages with the feed → import the catalog → the next API run updates these products.

    I changed prices, but some didn't apply on Rozetka: “awaiting marketplace manager approval”. What is it?

    It's Rozetka's own rule: a price raised more than 1.5 times or cut more than 2 times is applied after a manager reviews it. Elbuz has sent it, and the other prices from the run are already applied. Check the state of these prices in the seller account.

    I see the same template for Kasta. Is it the same thing?

    No. For new templates, the “Kasta (XML)” type has its own preset built to the Kasta spec: offer id is the product number, rz_id with the Rozetka code in categories, stock_quantity, price_old and up to 20 photos. More: exporting products to Kasta.

    Where it is and who has access

    Menu
    Directories → Operations → Data export
    Create
    “Add” → type Rozetka.UA
    Configure
    template card: product filter, template, file name, schedule
    Access right
    the “Export” and “Export Template Setup” windows in “Group permissions”
    Prepare
    categories and attributes matched with Rozetka

    The general mechanics of templates — product filter, file delivery, schedule, log — are the same for all types and are covered in the article on exporting products. The format itself is explained in the article on exporting in YML format. This article covers only what is specific to Rozetka.

    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