↑↓ selectEnter openEsc close

    1. Elbuz
    2. Feeds and marketplaces

    How to export your catalog to Epicentr: XML feed

    23 min readUpdated

    Elbuz builds an XML feed for Epicentr with its category and characteristic codes; the marketplace fetches it by link and updates your products, prices and stock.

    When you need this:

    • You're starting on Epicentr — the “epicentrk.ua (XML)” template already has the required file structure.
    • New products should go out without manual work — matching is done once per category and inherited.
    • Elbuz calculates prices and stock for several channels — Epicentr gets the same data.
    • Your catalog collapsed after a failure — a stop rule won't send such a feed.

    Where to start: the connection steps — from matching directories to the link in your Epicentr account.

    What the Epicentr export can do

    How to connect Epicentr: from scratch to products on the marketplace

    1. Get Epicentr's directories. You need the codes of the marketplace's leaf categories and characteristic codes (attribute sets). Epicentr provides them itself — in your account or on request from its directory.
    2. Match categories in Elbuz (how). In each category, fill in “ID epicentrk.ua” and “epicentrk.ua category”. You do this once: all new products in the category inherit the matching.
    3. Match characteristics. Give characteristics Epicentr's codes and names, and for lists, value codes too.
    4. Prepare product cards. Ukrainian name and description, photos that meet Epicentr's requirements, dimensions in millimeters, weight in grams, barcode.
    5. Create an export template of the “epicentrk.ua (XML)” type, choose the data set and, if needed, narrow the assortment with a filter.
    6. Check the file. Run the export manually once and look at the result: did all products get in, are the category codes filled.
    7. Give Epicentr the feed link and turn on auto-update on their side.
    8. Put the template on a schedule in Elbuz so the file is rebuilt with fresh prices and stock.

    Steps 1–3 take the longest, but you do them once. After that, the job comes down to keeping product cards in order: the feed picks up new products automatically if their category is already matched.

    What reaches the marketplace

    Epicentr works with its own directories: the category and each product characteristic must be identified by an Epicentr code, not by your name.

    Feed elementWhere it comes from in Elbuz
    product identifier in offerin the default template — the internal product number in Elbuz (not the uuid, as for Prom); you can change it in the template
    availability flagproduct stock
    price, price_oldprice and old price
    category (code attribute)the “ID epicentrk.ua” category field
    category name in the feedthe last level of the path from the “epicentrk.ua category” field
    attribute_setthe same Epicentr category code
    name and descriptionthe product name and full description, in Ukrainian
    imagesproduct photos
    characteristicsname, code and value from Epicentr's directory
    dimensionsthe Width, Height, Depth product fields
    weightthe Weight product field
    barcodethe barcode product field
    unit of measure and multiplicityfixed values: piece, multiplicity 1

    Note the first row. In the default template, a product is identified by its internal product number in Elbuz — not the code used for Prom. You can change this value in the XML template: put the product code (uuid) or SKU instead of the number, whichever is easier for matching items on the marketplace.

    Whatever you choose must stay unchanged: Epicentr recognizes the product by this value on every update, and order lines come back by it too (see importing orders from Epicentr).

    • Don't change the identifier in the template after the catalog has been exported: the marketplace will treat all products as new.
    • Don't delete and recreate a card to fix it — the new one gets a different number and becomes a separate product on the marketplace, while the old one is left “hanging”.

    How to prepare directories and product cards

    The feed builds without any preparation, but the marketplace won't accept such products. Here's what to do.

    1. Match categories. Each of your categories has the “ID epicentrk.ua” and “epicentrk.ua category” fields. The first is the category code from the marketplace's directory, the second is its full path.

    The code goes into the feed, and the last level of the path is used as the name: if you entered “Tools / Power tools / Drills”, the file gets “Drills”. Without a category code, the product goes out with an empty value, and Epicentr doesn't know where to put it.

    2. Match characteristics. For each characteristic, Epicentr expects its own code and name from its directory, and for values, a value code. The characteristic card has the “Epicentr name” and “Epicentr code” fields for this, and the marketplace matching window has the “Name on EPICENTR”, “Epicentr code” and “Epicentr value” columns.

    If the Epicentr name is empty, Elbuz uses your own characteristic name — the file stays valid, but the marketplace may not recognize the characteristic. The Epicentr columns are shared by all categories (attribute directory).

    How one product characteristic becomes a param line in the file. The left branches are when there's no line at all; below you can see that without matching the characteristic doesn't disappear — it goes out with your name and empty codes
    NoYesNoYesYesNoProduct characteristicIs “Export to site (file)”on for the characteristic?Not included in the fileDoes the product have a valuefor this characteristic?Is “Epicentr name” filled in?name — Epicentr namename — your characteristic nameparamcode — the “Epicentr code”value,empty if the code isn't filled invaluecode — code from the“Epicentr value” column,empty if the value isn't matched
    • Action or result
    • Decision: the path depends on the answer

    3. Fill in dimensions, weight and barcode. Width, height, depth, weight and barcode go into the feed as separate parameters with fixed codes. For a marketplace this isn't a “nice extra”: shipping is calculated from dimensions and weight, and the barcode is used to match the product to an existing listing on the marketplace.

    4. Check the Ukrainian texts. The name and description go into the feed only in Ukrainian — the template has no separate fields for another language. If the card is filled in another language, that's the text that appears on the marketplace.

    Almost all problems with Epicentr come down to unmatched directories. A category without a code and characteristics without codes make a formally valid XML that the marketplace rejects or accepts only partly. So before the first run, go through the matching, not the feed settings: the Elbuz template already provides the required structure.

    Epicentr accepts package measurements only in millimeters and grams. Elbuz sends product field values to the feed as is, without conversion. If your dimensions are in centimeters and weight in kilograms, the marketplace gets a product that “weighs 2 grams” and is “40 millimeters wide”.

    Epicentr data requirements

    The marketplace checks not only the file structure but also the content of the cards. Below is a summary of the requirements that most often cause rejections; the full texts are in Epicentr's help.

    WhatRequirement
    SKUUnique, up to 64 characters, no separators. You can't use the product name as the SKU
    NameUp to 150 characters, in Ukrainian. Order: product type → feature → brand → model → additional characteristics → color → SKU in parentheses
    What the name must not containCAPS LOCK, punctuation (except parentheses), special characters, the words “Promotion”, “Discount”, “Sale”, links, slang
    DescriptionRequired in Ukrainian. Content requirements set up to 1500 characters (about 1000 recommended); the technical limit of the file itself is much higher
    Allowed tags in the descriptionp, br, b, ul, li, table, tr, td — the rest is stripped
    What the description must not containPayment and delivery terms, store contacts, links, third-party advertising, mentions of other products
    PriceIn hryvnias, kopecks after a dot (25.78). Old price — only when there's a discount, and always higher than the current one
    CategoryOnly a leaf category (one with no subcategories)
    Dimensions and weightMillimeters and grams
    CharacteristicsTop characteristics and the main required ones — search filters work on them; package parameters are required too
    PhotosHTTPS links, 1 to 10 photos (2–8 is optimal), at least 500×500 (1280×1280 is better)
    Main photo requirementsThe product takes up at least 80% of the frame, white or plain background, no watermarks, text, logos, collages or packaging

    The Ukrainian name is required. A Russian one (name with the ru language attribute) is needed only if you want the product shown in Russian too — the default Elbuz template doesn't export it. If you need it, add the corresponding line to the XML template in the export form.

    Likewise, you can add a separate availability tag with the values «в наявності / під замовлення / немає» (in stock / made to order / out of stock) if needed: Epicentr prefers it over the regular availability flag.

    Where to check the requirements: Epicentr's help

    The marketplace's requirements change, so check disputed points against its own help:

    How to turn on auto-update on the Epicentr side

    The feed updates nothing on its own — the marketplace has to fetch it. In your Epicentr account, go to “Products” → “Import”, the “Stock auto-update” (Автооновлення залишків) subsection, paste the link to your feed and click “Save”. After saving, the marketplace tells you the import has started.

    WhatHow it works
    Default frequencyOnce a day, at 24:00 UTC
    More oftenEvery 12, 4 or 1 hours — turned on only through your manager or Epicentr support
    How products are recognizedBy SKU: the value in the feed must match exactly the product SKU in the account, otherwise the update won't work
    If a product drops out of the feedThe marketplace doesn't remove it automatically — you need to separately select the option to change the status to “Out of stock”

    There are two schedules: Elbuz rebuilds the feed, Epicentr fetches it. Rebuilding hourly makes no sense if the marketplace reads the file once a day. Instead, ask your manager how often Epicentr will fetch the feed, and set Elbuz to update slightly more often — then the file always has fresh data when it's read.

    Feed schedule and updates

    Once the template is set up, put it on a schedule and the feed rebuilds itself. Choose the frequency by how fast things change and how often the marketplace reads the file (auto-update). Setting the schedule — see “Manual and scheduled runs”. Each run leaves a log entry with the product count and errors — check it after the first runs.

    Now and then, compare the number of items in the feed with what you expect to send. If it's lower, look for the cause in the template's filter conditions. An unmatched category or empty dimensions don't remove a product from the file: it goes into the feed with empty values, and Epicentr rejects it.

    Each run builds the file from scratch, and until the run finishes, the link serves the previous file: a break-off, a stop rule or an upload error doesn't touch it. What goes into the file, when it's replaced and how to tell from the log that the file is built — see “Export file”.

    One run of the Epicentr template. The four branches that lead to a stop or to “NOT completed” all end with the previous file staying at the link; it's replaced only on the bottom path
    YesNoNoYesYesNoNoYesStart: “Export” buttonor schedulePreflight summaryand stop rule checkDid a rule in“Stop the export” mode trigger?“Export stopped by a stop rule”.The link keeps the previous fileDid the filter condition run withouterrorsand return at least one product?“Data export NOT completed:the file was not generated”.The link keeps the previous fileThe file is built in the working folder,written in chunks of 500 productsWas “Stop” clicked?The new file is written to storageDid storage accept the file?“The file was not uploaded to cloudstorage.The previous file and its linkare left unchanged”Other template filesare removed from storage“File Link (#1)” is writtento the template“Data export completed”
    • Action or result
    • Decision: the path depends on the answer

    Edits in your Epicentr account and the next update

    Each run builds the file from scratch from the Elbuz catalog. Price, old price, name, description, photos, characteristics, dimensions, weight and barcode are taken from the product card at build time. Elbuz doesn't read what you changed in your Epicentr account: the channel is one-way. So the file at the link always has values from Elbuz, not from the account.

    • If a value should stick, change it in Elbuz: the next file carries it.
    • If you want to maintain a field only in the account, remove its line from the XML template. What's not in the template isn't in the file.
    • Whether Epicentr overwrites account edits with values from the file on the next read is up to the marketplace. The program has no control over this; see Epicentr's help on auto-update.

    If you changed the identifier or recreated cards

    The program doesn't send Epicentr “delete product” commands. An item that's no longer in the file doesn't disappear from the marketplace by itself, so duplicates are removed in your Epicentr account, not in Elbuz.

    • If you replaced the identifier in the offer line of the template, restore the placeholder the catalog was exported with before (in the default template — {product_id}) and export again. The file will again contain identifiers the marketplace already knows. Items Epicentr has already created under the new identifier stay in the account until you remove them there.
    • If you deleted a card in Elbuz and created it again, you can't give it back the old number: the new card goes into the file under a new number. Remove the old item on the marketplace in your Epicentr account.

    What disabling the template does

    The “Active” / “Disabled” switch in the template form header only controls whether the template runs automatically. It doesn't touch the file at the link.

    • If the template is disabled, the schedule skips it, and the log has no line about it. “Export all templates” and the task queue skip it too.
    • The file at the link stays as the last run built it. Epicentr keeps fetching it, so it gets prices and stock as of the last run.
    • The “Export” button for a single template works even when it's disabled: the file is built and replaces the previous one.
    • Disabling doesn't delete the schedule. If you turn the template back on, the next scheduled run builds the file as before.
    What happens when a scheduled task is due. A disabled template is filtered out at the second check, and this leaves no trace in the log
    YesNoNoYesA scheduled task is dueIs another scheduled exportstill running?Task canceled:“Scheduled export canceled…”The task is markedas runningIs the template “Active”?The template is skipped, no line inthe log.The link keeps the file from the lastrunRegular template runwith stop rules
    • Action or result
    • Decision: the path depends on the answer

    Do you need an Epicentr API token

    Epicentr has its own with tokens for integrating the account with a and other systems. Exporting your catalog from Elbuz needs no token: the exchange goes through the XML feed, and the export template takes no key. If you've already generated a token in the account, that's not a mistake — it's for other scenarios, not this feed.

    The “API” tab appears under “Settings” → “Company settings” after you turn on the corresponding switch in the additional settings. There, the “Generate” button creates a token, the icon next to it copies it, and “Update key” issues a new one (the previous one stays in the list of active ones).

    Tokens have no expiry date and work until you delete them with the trash icon; there's no limit on their number, and all created keys are active at once. More in Epicentr's help on working with the API.

    Scenarios

    Send only part of the catalog to Epicentr

    Task. Only a few product groups should go to Epicentr, not the whole catalog.

    What to set up. On the template's “Export limit (filter)” tab, set a filter condition, for example by categories or manufacturer. For categories that shouldn't get into any feed, you can turn off “Export to file (to website)”, but this flag affects not only the Epicentr template but other XML feeds too.

    The result. Only products that pass the condition go into the file. What won't happen: products that were already on Epicentr and have now dropped out of the file won't disappear from the marketplace by themselves. The program doesn't send Epicentr “delete product” commands, and what to do with an item missing from the file is up to the marketplace.

    Export only what's in one warehouse

    Task. The store ships Epicentr orders from one warehouse, and the marketplace should show only what's stored there.

    What to set up. On the “Select data to export” tab, in the “Export limits” block, choose the warehouse in the “Warehouse ID” field.

    The result. Only products in stock in this warehouse or with stock above zero go into the file. What won't happen: a product that ran out there won't go into the file marked “out of stock”. It disappears from the file completely, and then the previous scenario applies: the item doesn't leave your Epicentr account by itself.

    Hide an internal characteristic on Epicentr

    Task. The catalog has characteristics for internal accounting that buyers shouldn't see.

    What to set up. Clear the “Export to site (file)” flag for such a characteristic.

    The result. The file won't have a param line with this characteristic. What won't happen: the flag belongs to the characteristic, not the template, so it disappears from all XML feeds, not just Epicentr. Conversely, you can't hide it by clearing its “Epicentr name” or “Epicentr code”: without an Epicentr name, it goes into the file under your name.

    Don't send Epicentr a collapsed feed

    Task. If most products or all stock suddenly disappeared from the catalog after a failure, such a file must not reach the marketplace.

    What to set up. In the export window, select the Epicentr template and open “Export stop rules” from the toolbar menu (or with the “Configure thresholds” link in the summary before the run). For the rules you need, choose the “Stop the export” mode and click “Save for this template”.

    The result. If the difference from this template's last successful run exceeds the threshold, the run stops before the file is built. The log shows “Export stopped by a stop rule”, and the link keeps the previous file. Scheduled runs work the same way.

    What won't happen. In “Warn” mode, the run doesn't stop, and the file is replaced. The stop rule doesn't fix the catalog data itself: after fixing it, run the export again.

    What to do when Epicentr rejects products

    What you seeWhyWhat to do
    The feed is built, but products aren't accepted the category has no “ID epicentrk.ua”, or characteristics have no Epicentr codes — the file is formally valid, but the marketplace doesn't know where to put the product match categories and characteristics (how)
    The marketplace doesn't recognize a characteristic “Epicentr name” or “Epicentr code” is empty — your name goes into the file with empty codes fill in the codes in the matching window
    A product on Epicentr “weighs 2 grams” or has odd dimensions dimensions are in centimeters and weight in kilograms — Elbuz sends values without conversion fill in Width, Height, Depth in millimeters and Weight in grams
    The name or description on the marketplace isn't in Ukrainian only the card's Ukrainian name and description go into the feed fill in the card's Ukrainian texts (preparing cards)
    Duplicate items on Epicentr you changed the identifier in the template or recreated a card in Elbuz restore the identifier and remove the extra items in your account (how)
    A product dropped out of the feed but is still on sale on Epicentr the marketplace doesn't remove a product that's missing from the file in your account, select the option to change the status to “Out of stock” (auto-update)
    Prices on Epicentr don't update, and there are no errors in the log the template is disabled, or Epicentr reads the file once a day turn the template on (about disabling); your Epicentr manager can turn on more frequent reading
    “Export stopped by a stop rule” the difference from the last run exceeds the threshold check the catalog and run the export again (stop rule)

    FAQ

    The Epicentr category is given as a path — what goes into the file?

    The category code goes into the file, and only the last level of the path is used as the name: from the path “Tools / Power tools / Drills”, the feed gets “Drills”.

    What language are names and descriptions exported in?

    Ukrainian — the Epicentr template has no separate fields for another language. If needed, a Russian name is added as a line in the XML template.

    What happens if I delete a product and create it again?

    Epicentr recognizes products by the card's internal number in Elbuz. A new card has a different number, so the marketplace treats it as a separate product, and the old item is left “hanging”. Fix the existing card instead of recreating it.

    Why are dimensions and weight required?

    The marketplace calculates shipping from them, so they go into the feed as separate parameters. A product without dimensions and weight is either rejected by the marketplace or its orders can't be processed correctly.

    How do I get orders from Epicentr?

    The feed only publishes your assortment. Orders are fetched by a separate template — importing from Epicentr; it matches order lines to products by the same identifier as in the feed.

    Where it is and who has access

    Menu
    Directories → Operations → Data export
    Create
    “Add” → type “epicentrk.ua (XML)”
    Access right
    the “Export” and “Export Template Setup” windows in “Group permissions”
    Have ready
    Epicentr category and characteristic codes, dimensions in millimeters, weight in grams

    One template is one feed. The general template mechanics — filtering, file delivery, schedule, log — are described in the article on exporting products; here we cover only what's specific to Epicentr.

    Epicentr XML feed template form with the feed settings
    1Template name and type
    2Feed settings
    1. Template name and type — the window title shows it is an Epicentr XML feed.
    2. Feed settings — what to include in the feed: categories, products, photos, attributes.

    The template form has two tabs. On the “Select data to export” tab, checkboxes set the feed contents — Epicentr needs Categories, Products, Photos and Attributes. Keep “Only export new data” off when the marketplace should get the full catalog. The “Export limit (filter)” tab narrows the assortment if not the whole catalog goes to Epicentr.

    Below that, the form shows the template itself — the file text with placeholders like {Field}. You can see and edit it: the program repeats the category line and the product line for you, and placeholders are suggested with Ctrl+Space. Change the template only when Epicentr asks for something specific: the default one already meets the marketplace's requirements.

    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