↑↓ selectEnter openEsc close

    1. Elbuz

    How to export your catalog to a YML (XML) feed for any service

    24 min readUpdated

    Elbuz builds a YML feed from your catalog — an XML file for marketplaces, price comparison sites, CMSs and accounting systems — and updates it at a permanent link.

    When you need this:

    • A service wants an “XML feed” or a “YML price list” and has no ready-made type — edit the universal template.
    • A partner or your website needs the file — it's rebuilt on a schedule.
    • The receiver wants other node names — change a template line.
    • You fear breaking the feed — a test export shows the XML and errors for one product.

    Where to start: create an “XML” template in the “Data export” window.

    What the YML feed can do

    • A ready feed right away — a new template is created with the header, currency, categories and products.
    • Nodes for any receiver — you add, rename or remove template lines, and macros fill in the values.
    • A stable identifier — the receiver updates existing items and groups variants into one product.
    • Your own words for availability — a dozen internal statuses are mapped to what the receiver understands.
    • A partial feed — only products changed since the last export go into the file.
    • Test export — for one product, unrecognized macros and markup errors before going live.

    Specific marketplaces and formats: Rozetka, Prom.ua XML and XLSX, Epicentr, EVA.UA, Kasta, Google Merchant, the OpenAI feed; marketplace categories and attributes — category matching.

    How to create a YML template

    In the “Data export” window, click “Add”, open the “XML feed (YML)” group in the list of types and choose “XML”. This is the universal feed; the other items in the group are set up for specific marketplaces.

    One template — one file. Make feeds for different services with different data as separate templates instead of reconfiguring one.

    When to use a ready-made type instead of the universal one

    A well-known marketplace usually has its own type covering its required nodes, limits and identifiers. Use the universal when there is no ready-made type: your own website, a partner exchange, an analytics service, a niche price comparison site. Search the list of types for the service name; if it's not there, choose “XML”.

    How to send a feed to Kasta

    Create a template of the “Kasta (XML)” type. The template follows the Kasta spec: offer id is the product number, categories get rz_id with the Rozetka code if it's filled in, products get stock_quantity and price_old, plus up to 20 photos. Kasta templates created earlier are left unchanged. More: exporting products to Kasta.

    How to send a feed to E-Katalog

    Create a template: “Add” → “XML feed (YML)” → E-Katalog. The template follows E-Katalog's price list requirements: the required vendor, name, price, url and categoryId, plus photos, part number, EAN and warranty. The description goes out as plain text, without HTML.

    Availability is sent as true, false or request (made to order). The warranty comes from the product card: a bare number such as 24 is sent with a months unit, because E-Katalog reads a number without a unit as days; text like “1 year” goes out as is.

    Paste the link from the “File” column into your E-Katalog account: its robot fetches the price list on a schedule set by your manager. Shops are connected on request at account.ek.ua and pay per visit. Keep only the brand and model in the product name: E-Katalog treats specs in the name as an error.

    Every service adds its own conditions to the format: required nodes, title length, photo limit, set of currencies, category requirements. Open the requirements of the service you send the feed to and fit the template to them. Elbuz doesn't check these requirements — the service itself will report violations.

    What goes into the file

    A new template is created with a ready feed — you don't need to write it from scratch. The file has three parts:

    File partWhat it contains
    HeaderThe root node yml_catalog with the export date, then shop: store name, company, website address, service details about the platform and email. The currencies block is here too — the feed currency and its rate
    CategoriesThe categories block with a category line for each category: its own ID, the parent category ID and the name. This is how your tree is reproduced in the file
    OffersThe offers block with an offer for each product: link, price, currency, category, photos, name, manufacturer, SKU, description and attributes

    The app repeats the category and product lines itself: the template has each once, the file has one per category and product. Which products make it into the file is decided by the filter conditions, which are the same for all formats: why a product didn't make it into the file.

    Categories, photos, attributes

    SettingWhat it does
    Categories (checkbox)Whether to include the category block in the file. Some services accept a feed without the tree — then you can clear the checkbox
    Category delimiter characterWhat separates levels in the full category path when it comes as a single line
    Photo (checkbox)Whether to export images
    Product image linkThe address the receiver downloads photos from: domain and folder. Photos are sent as links, not files
    Max PhotosThe limit per product — most marketplaces have their own, and they either drop extra photos or reject the whole feed
    Attributes, Options (checkboxes)Whether to export product attributes and options

    If the directory has an , the file gets one parameter with the main attribute's name, and the values of all linked attributes are collected into it.

    A product with both “Temperature” and “Color temperature” filled exports a single “Color temperature” with both values. There is no separate checkbox for this: the rule applies in all YML templates.

    Whose stock and which language

    The “Export limits” section sets which store, warehouse and language version numbers and texts are taken from for products that have already passed the filter. The “In stock at this store only” checkbox is here too. How these fields narrow the selection — in the table of filter conditions.

    How “Only export new data” works

    This checkbox in the “What to export” section exports only products changed since the last export. The mark lives in the product, not the template: a successful run sets “Exported” on the exported products, and any product edit — in the card or the catalog grid — clears it.

    • No changes — no file update. The log shows “Data export NOT completed: the file was not generated”, the last export date doesn't move, and the previous file stays at the link. The exception is Prom mode (see below).
    • The mark is shared by all templates. If the checkbox is on in two templates, the changes go to whichever run finishes first; the second gets nothing.
    • The receiver must understand partial files. A service that treats the feed as a full list will decide the rest of your products are gone (what happens to a product that disappears from the feed).

    How to change the feed contents: XML template and macros

    You define the file contents yourself, in the “XML template” field. It is one continuous document — the feed as it should come out — with macros in curly braces instead of values: {name}, {price}, {uuid} and so on. During export, each macro is replaced with the value of a specific product.

    Need an extra node — add a line; a different name — rename it; an unneeded one — remove it.

    Formulas in double square brackets help calculate values: for example, the RRP if it's filled in, otherwise the regular price. Syntax and examples — in price in the export.

    Press Ctrl+Space or type { — a suggestion list appears. Next to the field there is a macro reference grouped by meaning. Clicking a macro inserts it at the cursor position.

    Unrecognized macros simply disappear from the export result — with no warning and no log entry. A typo in the name gives an empty node in the feed, and you'll notice it only on the service's side. Before the first live run, do a test export — it shows the macros the app didn't recognize.

    Sub-templates: photos and attributes

    A product has several photos and attributes, so they have sub-templates — lines repeated once per photo or attribute. In the main template they are replaced by the {image_list} and {attribute_list} macros, and the lines themselves are set in the “Sub-templates” card. A sub-template line is up to 255 characters.

    Photos as a picture or an image node — that's an edit of one sub-template line.

    Which wins — the checkbox or the macro

    The same field is set in two places: by a checkbox in the “What to export” card and by a line in the template. When they contradict each other, these rules apply:

    WhatWhich winsResult
    Photos and attributesMacro{image_list} in the product line exports photos even with “Photo” cleared; {attribute_list} likewise ignores a cleared “Attributes”. To keep photos out of the feed, remove the macro
    CategoriesCheckboxWith “Categories” cleared, the file has no category lines, only an empty <categories></categories> wrapper
    ProductsCheckboxWith “Products” cleared, the file has the header, categories and no offer. The run finishes normally, and this empty file lands at the permanent link
    Empty sub-templateThe appWithout a “Photo sub-template”, the file gets <picture>address</picture>; without an “Attribute sub-template” — <param name="Name" unit="unit">Value</param>. The app inserts its own line with none of your nodes

    Inside the product line, substitution follows a fixed order: first formulas in double square brackets, then individual attributes {attribute_61}, then product fields, then the lists {image_list}, {video_list}, {attribute_list}. Anything still left in curly braces after that is cut from the file.

    The app detects a known marketplace not only by type but also by text: the Latin words “rozetka” or “prom” in the template name or in the attribute sub-template, and the selling_type, portal_category_id, portal_id nodes in the template. Then the rules change silently:

    • Rozetka mode — photos are cut to 15 per product, attribute values to 255 characters, and links and images are stripped from text fields;
    • Prom mode — photos are cut to 10, and the main card of a product with variants stays out of the feed, only variants go. It never gets “Exported”, so with “Only export new data” a run with no changes puts a file with no offer at the link instead of “the file was not generated”.

    Don't name a universal template “like Rozetka” or “Prom-style”: one Latin word in the name is enough.

    How to avoid duplicates on the receiver's side

    By default, the offer identifier is the product — the card's own permanent key in Elbuz. As long as the identifier is stable, the service updates existing items; if it changes from export to export, duplicates pile up on that side.

    The import reads the same UUID: when a feed from Elbuz is loaded back — by you or a partner — products are recognized by it and not duplicated. Change the identifier in the template only when the receiver explicitly requires another one (for example, a numeric code).

    Variants of one product (colors, sizes) get the main card's shared ID in the grouping attribute, and the receiver combines them into one product. If the service doesn't support grouping, remove this attribute from the template.

    What a repeat run does to your edits

    Export writes nothing to product cards: the next run doesn't touch the price, name, description or photos in Elbuz. In the database, it changes only the “Exported” mark in products and the template row with the file's link, size and date.

    Data you edited in the service's account is up to the service. Your one lever in Elbuz is the set of nodes in the template: with no <name> node in the file, the service gets no new name, and yours stays. Manage a field by hand on the service's side — remove its line from the template (scenario).

    How to pass stock availability and take a product off sale

    Offer availability is the available attribute, set by the {xml_stock_status} macro. In the “Related settings” card, the “Stock-based update setup” button opens a table that sets, per status, what goes into the feed (the “Title on site (in file)” column) and what quantity to show. By default, “In stock” gives true, the rest false; your own words go there too.

    Stock-based update setup window with the table of stock statuses
    1Active column
    2Title on site (in file) column
    1. Active — whether the stock status is used when the file is generated.
    2. Title on site (in file) — the text that stands for this status in the export file.

    A table row works only while “Active” is checked in it. Without it, the built-in rule applies: “In stock” gives true, the rest false, and the quantity follows the product's state: 1000 if active, 0 if disabled. If “the setting was saved, but the file has the old value”, check this checkbox first.

    The quantity from the table goes into the file via the {xml_stock_quantity} macro. The {stock_quantity} macro sends the product's real stock, and for a product with no stock, the quantity from the table; a status set to 0 in the table gives 0 even when there is stock. It's for marketplaces where a product counts as in stock only while the quantity is above zero, such as EVA.UA.

    The first branch is the “Active” checkbox: without it, the table doesn't apply to this status at all, and your text won't get into the file
    NoYesYesNoProduct with its stock statusIs “Active” checkedfor this status?available: true for the built-in“In stock” status, false for the restIs “Title on site (in file)”filled in?available — your textavailable: true if the status means instock,false for out of stock, pre-order andothers
    • Action or result
    • Decision: the path depends on the answer

    What happens to a product that disappears from the feed

    YML has no “product deleted” flag. The file is a full list of what you sell right now, and an item no longer in it gets no command at all. One service unpublishes it, another leaves it as it was last time; Elbuz can't see this.

    There is one controlled way to say “no longer for sale”: keep the product in the feed with an out-of-stock value through the stock status table (scenario). Exclude a product from the filter when you no longer need it on this marketplace at all, not when it has run out.

    How to test the feed before going live

    Click “Check” in the template card header. The app runs the same code as a full export, but for one product (you can enter its number), saves the result to a separate file and shows it. The live file and its link aren't touched.

    The check shows:

    • the finished XML as the receiver will see it — the first 200 KB;
    • the list of unrecognized macros;
    • markup errors with line and column numbers — found by a real XML parser, the same kind receivers use;
    • formula errors — a field that doesn't exist and formula syntax, reported separately;
    • the number of the product the check ran on.

    If the product you entered doesn't match the template conditions, the app says so: “Product #… was not exported: it does not match this template conditions”.

    Schedule and the file link

    Elbuz puts the finished file in your storage and gives it a permanent link — that's what you give the service. The file is rebuilt on a schedule, and the link stays the same. Schedule and are set with the “Schedule” and “FTP Setup” buttons in the “Related settings” card.

    The preflight summary, stop rules, manual run, schedule, FTP and log are the same for all formats: summary, stop rules, running manually and on schedule, where the file goes, run log. Exporting to a file isn't billed: nothing is charged to your balance for runs.

    What's at the link when a run doesn't finish

    The file is built from scratch every time and published in one final step: the new file goes to storage first, and only then are the template's other files removed. So after a stop, a lost connection, a crashed process or a failed upload:

    • the previous file stays at the permanent link, and the receiver never gets a half-built one;
    • the last export date isn't updated, and the log shows “Data export NOT completed: the file was not generated”;
    • “Exported” marks aren't set, so the next run with “Only export new data” won't lose anything;
    • you can retry right away — nothing gets duplicated.
    The three side branches are where a run ends without a new file: the previous one then stays at the link. The file in storage changes only on the straight path at the bottom
    YesNoYesNoNoYesStart: “Export” button,schedule or “Export all templates”Preflight summaryand stop rule checkDid a rule in“Stop the export” mode trigger?“Export stopped by a stop rule”.The previous file stays at the linkThe file is built from scratch:header, categories, productsNo product passed the filteror “Stop” was clicked?“Data export NOT completed:the file was not generated”.The previous file stays at the linkThe file goes to FTP if FTP is set up.An FTP failure doesn't stop the runDid the new fileupload to storage?“The file was not uploaded to cloudstorage”.“Data export NOT completed”.The previous file stays at the linkThe template's other filesare removed from storageThe link, size and dateare written to the templateProducts get “Exported”if “Only export new data” is on“Data export completed”
    • Action or result
    • Decision: the path depends on the answer

    A broken-off scheduled run holds a lock: while the app thinks it's still running, next tasks are skipped with the line “Scheduled export canceled because another template is being exported (data processing conflict).” A watchdog releases a dead run's lock — no earlier than an hour after the start and half an hour of log silence.

    Two ways a scheduled task ends without a run: busy with another export — with a line in the log; template disabled — silently
    YesNoNoYesRun died, mark remainedA scheduled task is dueIs another scheduled exportstill running?Task canceled:“Scheduled export canceled…”The task is markedas runningIs the task's template “Active”?The template is skipped.Nothing in the logRegular template runwith stop rulesA watchdog removes the mark: anhoursince the start and half an hour oflog silence
    • Action or result
    • Decision: the path depends on the answer

    The {DATE}, {DATETIME} and {TIME} macros work in the file name. But then each file gets a new name, and after the upload the app removes the template's other files from storage: yesterday's address stops updating or stops working. Put a date in the name only when the file is downloaded by hand.

    The ?uuid=384512 “tail” in the link is different every time; you can give the service the link without it.

    Disable or delete a template

    A disabled template (the “Active” / “Disabled” switch in the card header) doesn't run on schedule and isn't included in “Export all templates” — silently, with no line in the log. It still runs manually. The file stays in storage, and the service keeps downloading the last feed: disabling doesn't remove products from the marketplace, it freezes the file.

    Deleting erases the settings: template text, sub-templates, stock status table, FTP, filter and schedule. The file in storage isn't deleted here either. To stop the service from getting your data, remove the link on its side.

    If a faulty feed has already been picked up

    1. Fix the template and click “Check” — make sure the second attempt won't be the same as the first.
    2. Run the export. The file at the permanent link is replaced entirely.
    3. Wait for the service to reread the file, or click its “update from feed” button in its account if it has one. You can't speed this up from Elbuz.
    4. If the faulty run used “Only export new data”, clear the checkbox and send one full feed — otherwise only products changed after the error get the fix.

    You can't roll back to yesterday's file: the new one replaces the previous one, and the temp folder keeps only the last three, and only until the next run. There is no template edit history either. Before a major rework, copy the template text somewhere.

    Scenarios

    You manage names and descriptions on the marketplace by hand

    Task: you rewrote product names in the service's account yourself and don't want the next feed to overwrite them.

    What to do: in the “XML template” field, remove the <name> node from the product line (and <description> too, if you manage descriptions there as well).

    Result: the file won't have these nodes, so the service has nowhere to get a new name from. Price, availability and other nodes go into the file as before. Names in Elbuz cards won't change — export doesn't write to product cards.

    A product ran out but must stay on the marketplace

    Task: an item is temporarily unavailable and should show as “out of stock” on the marketplace instead of disappearing.

    What to do: keep the product in the template's filter. In the “Related settings” card, open “Stock-based update setup”, check “Active” in your status row and, if the receiver expects something other than false, enter its word in “Title on site (in file)”.

    Result: the product goes into the feed, and {xml_stock_status} fills in the value from this row. A product excluded from the filter just stops being visible to the service, with no “off sale” command.

    A large catalog, and the receiver understands partial files

    Task: send the service only what changed on a schedule, not the whole catalog every time.

    What to do: turn on “Only export new data” in one template and set the frequency with the “Schedule” button.

    Result: products without the “Exported” mark go into the file. If nothing changed, no new file is built and the previous one stays at the link (how the checkbox works).

    Keep a stock collapse off the marketplace

    Task: if stock suddenly “disappears” in the base catalog, the feed must not go to the marketplace.

    What to do: in the summary before the run, click “Configure thresholds” and choose “Stop the export” for the stock collapse rule. The default threshold is 30%; for a product count collapse, 50%.

    Result: neither a manual nor a scheduled run starts, the log shows “Export stopped by a stop rule: …”, and the previous file stays at the link. Until the template has exported successfully at least once, the collapse rules stay silent — there's nothing to compare with (stop rules).

    The service doesn't accept photos in the feed

    Task: the receiver rejects a file with photo nodes or takes images from another source.

    What to do: remove the {image_list} macro from the product line in “XML template”.

    Result: the file won't have photo nodes. Clearing the “Photo” checkbox alone isn't enough (which wins — the checkbox or the macro).

    What to do when the feed isn't right

    Here are cases specific to the YML template. Empty selection, selected store, stop rules, schedule conflict and FTP — in the general troubleshooting table.

    Troubleshooting common YML feed problems
    What you seeWhyWhat to do
    “Data export NOT completed: the file was not generated”, though there are no errors “Only export new data” is on, and no product has changed since the last run That's expected: the previous file is at the link. Need a full feed — clear the checkbox (how the checkbox works)
    The feed stopped updating, and the schedule log is empty The template is disabled: the schedule skips it silently Switch the state in the card header to “Active” (disable or delete)
    “Macros were not recognized and will be stripped from the file: …” or the service says a field is empty A typo in the macro name: there is no such field Insert macros from the suggestion list (Ctrl+Space) or from the reference next to the field, not by hand
    “The repeatable product node was not found in the template… Changes were NOT saved.” The product node was renamed or broken, and the app doesn't know which line to repeat Put the tag back or enter its new name in “Advanced” → “Product row tag”
    Photos or attributes are in the file even though the checkbox is cleared The macro in the template wins over the checkbox Remove {image_list} or {attribute_list} from the product line (which wins)
    The file has the header and categories but no offer, and the log shows a normal finish “Products” is cleared, or the template name contains “prom” and the selection is only main cards with variants Check “Products”; remove “rozetka”/“prom” from the template name (marketplace mode)
    Duplicates appear on the service's side after every export The offer identifier changes from run to run Put the stable {uuid} back in offer (product identifier)

    FAQ

    What is YML and how is it different from regular XML?

    YML is XML with a predefined structure for product catalogs: the yml_catalog root, with the store, currency, category and offer blocks inside. Receivers understand such a file without extra markup.

    Do I need to edit the template if the standard feed suits me?

    No. A new template is created with a working feed already. Edit it only when the receiver asks for extra nodes or different names.

    The marketplace isn't in the list of types (for example, MAUDAU). How do I export to it?

    If it accepts an XML feed by link, create an “XML” template and fit the tags to its documentation. If it takes Excel or CSV, use the “Price list (XLSX, CSV)” type. There is no direct connection to such a marketplace.

    Does Elbuz check that the feed meets the service's requirements?

    No. The test export checks only XML validity and macros. Required nodes, title length, currencies and photo limit are checked by the service — you'll learn about violations from it.

    Can I see in Elbuz that the service picked up the file?

    No. The log ends when the file is placed in storage. When the service read it and what it did with it, check in the service's account.

    A run broke off — what's at the link now?

    The previous file: the new one is published in one final step. You can rerun right away (what's at the link).

    If I disable the template, will the feed disappear on the service's side?

    No. The file stays in storage, and the service keeps downloading the last built feed — it just no longer updates. Deleting the template doesn't remove the file either.

    How many photos go into the feed, and where do the links come from?

    No more than set in “Max Photos”. The address is built from the “Product image link” field; the receiver downloads the files themselves by link.

    Where it is and who has access

    Menu
    Directories → Operations → Data export
    Access right
    the “Data export” window; the template card — “Export Template Setup”
    Have ready
    the receiver's feed requirements: required nodes, photo limit, currency
    The XML template card with the beginning of the YML file and placeholders in curly braces
    1Template text field
    1. Template text field — the YML file body with yml_catalog and offer, where placeholders in curly braces are replaced with product data.

    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