↑↓ selectEnter openEsc close

    1. Elbuz
    2. Feeds and marketplaces

    How to export your catalog to Prom.ua as an XLSX file

    22 min readUpdated

    Elbuz builds a Prom.ua-format Excel file (also satu.kz) from your catalog with a product ID in every row, so Prom updates items instead of duplicating them.

    When you need this:

    • You run the catalog in Elbuz and sell on Prom — the file carries prices, stock and all Prom columns.
    • You added products in Elbuz — Prom adds them, existing ones get updated.
    • The file updates overnight on a schedule — a stop rule holds back a file with stock gone.
    • Descriptions and photos live in your Prom account — drop those template columns.

    Where to start: import your catalog from Prom, then add a Prom template in “Data export”.

    What the Prom export can do

    How to create a Prom template

    In the export window, create a template and choose the Prom format. Elbuz fills the template with the full set of Prom columns right away. Then choose which products to export — the whole catalog, specific categories, or by filter rules — and build the file.

    You can build the file manually with the “Export” button or on a schedule. You hand the finished file to the marketplace yourself: Elbuz doesn't connect to Prom. It puts the file on a permanent link and, if FTP is set up, uploads it there too.

    The marketplace's official description: exporting products and product groups and the XLS(X)/CSV file format. The general exchange section is Import and export in Prom Help (in Ukrainian).

    What goes into the file and where the values come from

    Two sheets

    The output file has the same structure as a Prom import file — two sheets. That's why Prom accepts it without any rework.

    • “Export Products Sheet” — products with the full set of Prom columns (name, price, availability, IDs, attributes and dozens of additional fields).
    • “Export Groups Sheet” — the structure of groups (categories): numbers, names, IDs and the parent–child links.

    Card fields and fixed values

    Columns are filled from product card fields. Some come from built-in fields (name, price, quantity, dimensions, , category, manufacturer, description, meta). Dozens of Prom-specific columns come from additional fields the first import created: wholesale price, discounts, product type, packaging, labels, gifts. The export sends back what came from Prom, plus your changes.

    Six columns don't take a card field but a fixed value set when the template is created:

    • Тип_товару (product type) — r (retail);
    • Валюта (currency) — your main currency code;
    • Одиниця_виміру (unit of measure) — «шт.» (pcs);
    • Мінімальний_обсяг_замовлення (minimum order quantity) and Можливість_поставки (supply capacity) — 1;
    • Термін_поставки (delivery time) — «день» (day).

    The fixed value sits in the “Formula” column on the template's “Select fields” tab and overrides the card field of the same name: every row in the file gets the same value. To send values from the cards, clear the “Formula” cell for that column.

    The availability column

    Availability (Наявність) takes its value from a separate card field, «Наличие_xls», which appears together with the Prom template. It's filled by a formula that the catalog import from Prom creates. The formula looks at the product's stock status:

    Product stock statusProm symbol in the file
    standard “In stock”+
    standard “Out of stock”-
    standard “Coming soon”& — Prom imports it as out of stock
    standard “Preorder”5
    a status you created yourself+ if the quantity is above zero, otherwise -

    According to Prom Help, empty availability, zero stock and & (expected) mean out of stock on Prom. Prom also accepts @ — service, ! — ready to ship (only for high-rated companies), and a number — delivery days for made-to-order items. To keep “Coming soon” products orderable, change their symbol in the formula to 3 (custom statuses).

    The formula recognizes standard statuses by something other than their name, so renaming them doesn't break it. If you edited this formula for your own statuses earlier, it stays yours. The formula itself is in the “Base catalog field formulas” window.

    The formula doesn't run at export time: it runs when you save a product card or when products go through batch price list processing. So the file gets the value saved in the card at that moment.

    If you built the catalog in Elbuz yourself and never imported it from Prom, there's no formula: the import is what creates it. The «Наличие_xls» field stays empty, and Prom reads an empty availability as out of stock. Fill in the field or set up the formula yourself.

    Discounts and promotions in the Prom file

    In the Prom file, the discount is carried by three columns next to the regular price: the discount amount and its validity period. Prom calculates the discounted price itself.

    Prom columnName in the Elbuz fileWhat it holds
    Ціна (price)Ценаthe regular price — Prom subtracts the discount from it
    Знижка (discount)Скидкаa percentage (7%) or an amount (12.50)
    Термін_дії_знижки_від (discount valid from)Cрок действия скидки отdiscount start date
    Термін_дії_знижки_до (discount valid to)Cрок действия скидки доdiscount end date

    Where Elbuz gets the discount

    The discount columns take their values from the card fields «Скидка_xls», «Cрок действия скидки от» and «Cрок действия скидки до», which appear together with the Prom template. You don't fill them in by hand — applying “Promotions / Discounts” rules does it:

    • a percentage rule puts that percentage without the sign into Скидка (-7 → 7%); a rule with a fixed price, coefficient or amount puts the difference between the regular and sale price (12.50);
    • only rules for the retail group (the default) that aren't “Signed-in customers only” give a discount; a manual sale price from the card doesn't go into Скидка;
    • the discount dates are the rule's “Start Date” and “End date”; an empty date gives an empty cell. A discount with a future start date goes into the file right away, together with the dates — unlike the “Sale price” field, which waits for the start date;
    • the fields are filled only for a real discount — when the sale price is lower than the regular one. A rule with a positive percentage (a markup) gives no discount on Prom;
    • when the end date has passed or the rule is disabled or deleted, applying the rules clears all three fields — the next file won't have the discount.
    • all of this works only when the “Sale price” field has no active formula: with a formula, the rules neither fill nor clear the discount columns.

    The price column (Цена) stays the regular price — Prom subtracts the discount. Don't put the “Sale price” field into Цена: Prom would then apply the discount a second time.

    Export template check window for the Prom XLSX template, showing the discount columns for the tested product
    1Discount
    2Discount valid from
    3Discount valid until
    1. Discount = 10% — the percentage taken from the active promotion rule.
    2. Discount valid from — the date the promotion starts.
    3. Discount valid until — the date the promotion ends.

    Prom Help on YML says a discount date isn't passed by link, and the discount is set for 45 days. For XLSX by link, Help is silent — assume the dates may not work and check your Prom account. By link, the file content is what reliably ends a promotion: Elbuz clears Скидка after it ends, and the next Prom update removes the discount.

    Rules with the “Quantity price (wholesale)” checkbox (a price based on quantity) don't go into the Скидка column. Prom takes wholesale prices in the Оптова_ціна (wholesale price) and Мінімальне_замовлення_опт (wholesale minimum order) columns — they're filled by the card fields that came from Prom.

    Prom column reference

    Product sheet columns per Prom Help and their Elbuz sources. The template writes headers as Prom's export used to, in Russian (Скидка, Cрок действия скидки от), while current Help lists Ukrainian names. If Prom ignored a column after import (say, the discount period), rename it in the template to the Ukrainian name below. Column set and order: the template's “Select fields” tab. “Prom field” is an additional card field the Prom template created and the catalog import from Prom filled.

    Prom columnMeaning and Prom limitsSource in Elbuz
    Ідентифікатор_товару (product ID)required key Prom uses to match a row to a product; up to 255 charactersthe product UUID (why there are no duplicates)
    Унікальний_ідентифікатор (unique ID)Prom's internal number; required for products already added, never changed by handProm field; empty for new products
    Код_товару (product code)SKU up to 25 characters“SKU (internal)”
    Назва_позиції / Назва_позиції_укр (name / Ukrainian name)name up to 110 / 130 characters; the Ukrainian one is updated only together with Опис_укр“Name” / Prom field
    Опис / Опис_укр (description)description up to 12,160 characters“Full description” / Prom field
    Пошукові_запити / _укр (search queries)comma-separated, up to 1,024 characters, a word up to 50Prom fields
    Тип_товару (product type)r retail, w wholesale, u wholesale and retail, s servicefixed r (fixed values)
    Ціна (price)from 0.01 to 9,999,999,999“Price”
    Ціна_від (price from)+ — show “price from”Prom field
    Валюта (currency)UAH, USD, EUR and othersfixed — main currency
    Одиниця_виміру (unit of measure)pcs, pack, set, pair, kg, m and others from Prom's listfixed «шт.» (pcs); the product's unit if you clear the column formula
    Мінімальний_обсяг_замовлення (minimum order quantity)a numberfixed 1
    Оптова_ціна / Мінімальне_замовлення_опт (wholesale price / wholesale minimum order)several values separated by ;Prom fields
    Кількість (quantity)stock on hand“Quantity”
    Наявність (availability)+, -, @, !, number of days; & and empty mean out of stock«Наличие_xls» (how it's calculated)
    Знижка / Термін_дії_знижки_від / _до (discount and its dates)a percentage or an amount; discount datespromotion rules (discounts)
    Посилання_зображення (image link)several URLs separated by a comma and a space, the first is the main oneproduct photos, up to 10
    Вага,кг / Ширина,см / Висота,см / Довжина,см (weight, width, height, length)numberscard weight and dimensions
    Виробник (manufacturer)up to 255 characters; imported only if it's in Prom's manufacturer database“Manufacturer”
    Країна_виробник (country of manufacture)up to 255 charactersProm field
    Ярлик (label)always updated, even without «Оновити примусово» (force update)Prom field
    HTML_заголовок / HTML_опис (and _укр)SEO up to 250 / 270 characters; empty values don't erase existing ones on importmeta title / meta description; _укр — Prom fields
    Подарунки / Супутні, ID_Подарунків / ID_Супутніх (gifts / related products and their IDs)row numbers or IDs separated by ;; a variant can't be a giftProm fields
    Номер_групи / Назва_групи (group number / name)the group on the Prom site; the name isn't importedProm field / category
    Ідентифікатор_групи (group ID)your group IDProm field or category UUID
    Ідентифікатор_підрозділу / Посилання_підрозділу (subsection ID / link)marketplace category; Prom advises not to change itProm field; if empty — the Prom category number (ID) or the Prom category link (address)
    ID_групи_різновидів (variant group ID)a number from 1 to 999,999,999; rows with the same number and filled-in attributes are variantsProm field
    Де_знаходиться_товар (product location)up to three towns separated by ;Prom field
    Спосіб_пакування, Особисті_нотатки (packaging, personal notes)up to 500 characters; notes separated by commasProm fields
    Продукт_на_сайті (product on site)the product's address; not importedthe product's “External link”
    Код_маркування_(GTIN) / Номер_пристрою_(MPN)for the Google Merchant feedGTIN / Prom field
    Назва_ / Одиниця_виміру_ / Значення_Характеристики (attribute name / unit / value)a triple for each attribute, in exactly this order; several values separated by |product attributes

    The groups sheet carries the group number, name (and Ukrainian name), group ID, parent group number and ID, and the group's image and SEO fields. According to Prom Help on YML, group descriptions and photos aren't passed by link.

    How Elbuz updates products on Prom without duplicates

    The exchange relies on IDs. In the export file, they're filled like this:

    Prom columnSource in Elbuz
    Ідентифікатор_товару (product ID)our product — the item's unique key in the catalog. Filled always, for every product.
    Унікальний_ідентифікатор (unique ID)Prom's internal number from an additional field. If the product was created in Elbuz rather than coming from Prom, the field has no number, and the cell is empty.
    Ідентифікатор_групи (group ID)the product card field of the same name. If it's empty or zero, the file gets the UUID of the category the product is in.
    Ідентифікатор_підрозділу (subsection ID)the product card field of the same name. If it's empty or zero, Elbuz takes the Prom category number stored in the category itself.

    Why Prom doesn't duplicate products from Elbuz

    Prom duplicates products when a file is edited by hand and uploaded back without IDs: the marketplace can't tell existing items from new ones. That's why Prom Help advises exporting from your Prom account first, so the file gets its IDs.

    Elbuz doesn't have this problem: the export always puts our UUID into the product ID column — even for products you've just created. Prom recognizes existing items and updates exactly those. You don't need an export from Prom just to get the IDs.

    Don't edit the Ідентифікатор_товару and Унікальний_ідентифікатор columns in the file by hand. These are sync keys: manually changing the UUID of an existing product makes Prom treat it as new and duplicate the item.

    Step-by-step exchange with Prom

    1. Import. Bring your catalog from Prom into Elbuz with XLSX import. Each product gets a UUID equal to its product ID on Prom.
    2. Work in Elbuz. Change prices and stock, edit cards, add new products. New items get their own UUID; they have no Prom number in the unique ID field.
    3. Export. Build the file in Prom format. Every product has a product ID (UUID), and new ones have an empty unique ID.
    4. Upload to Prom. Hand the file to the marketplace. Existing products are updated, new ones are added, and Prom assigns them its internal number.
    The same cycle over time: the two columns are the two systems, and the arrow shows which way the data goes
    PromElbuz2. Work in Elbuz: prices, stock,new products with their own UUID4. Existing items updated,new ones added — Prom gives them its own numberloop[Every following export]1. XLSX catalog import —product UUID equals itsproduct ID on Prom3. Export file:every product has a UUID,new ones have an empty unique IDsame UUIDs — the same items are updated
    • Request or action
    • Reply
    • loop — repeats
    • Note

    Then the cycle repeats: later exports carry the same UUIDs, so Prom updates the same items.

    For updates without duplicates, a reverse import isn't needed: matching relies on our UUID. Import the catalog from Prom again to pick up changes on the marketplace side: moderation, manual edits in your Prom account, and the unique ID Prom assigned.

    What a run changes in the catalog and what it overwrites on Prom

    The export mostly just reads the catalog, but it changes three things in it — before it starts building the file rows.

    • Recalculates the category tree. A run from the button updates category levels and paths. The parent category link is reset where it's empty or doesn't match the parent — on any run, scheduled ones included.
    • Fills the Prom fields on cards — group number, group ID, subsection ID, subsection address. The value is taken from the product's category, or, if that's empty too, from another product in the same category. Only empty fields are filled (for group number and group ID, also those set to zero).
    • Assigns internal SKUs — if you turned this on. With the “Unique internal SKU” setting (“Account” → “System settings” → “Catalog” → “Data processing rules”), a run gives a random number to products with an empty internal SKU and adds a suffix to duplicate SKUs.

    The run doesn't change the name, price, description, quantity, stock status or photos. Card field formulas aren't recalculated during export.

    Running the export again won't fix a Prom field that's already filled: as long as the field has something in it, the export leaves it alone. Clear the field in the product card (or with batch processing on a filtered set), and the next run fills it again from the category.

    Running again over edits in your Prom account

    Each run builds the file from scratch from the catalog's current values: whatever is in the card now goes to the marketplace. The old file with the same name is deleted at the start of the run.

    The file gets exactly the columns listed on the template's “Select fields” tab. An empty card field gives an empty cell. Remove a field you manage in your Prom account with “Delete field” — then the file has neither its header nor values. What Prom does with a column missing from the file is up to Prom.

    Your values in Elbuz itself can be overwritten not by the export but by field formulas: they run when a card is saved and during batch price list processing. Formulas skip products marked “Do not update” (the “Import protection” group in the product card).

    Edited IDs by hand and got duplicates on Prom? Build the file again: the product ID comes from the card's UUID, and the next upload updates the right items. To pull in the numbers the marketplace assigned, run a catalog import from Prom. An extra listing on Prom itself can only be removed in your Prom account.

    Why a product is missing from the file

    A product silently stays out of the file if it fails the template's filters: the “Export to file (to website)” flag, an active category, the filter, the store, the warehouse. The full list of conditions and how to check a specific product: Why a product didn't make it into the file. For a Prom template, add two more conditions:

    • a product without a category doesn't get into the file: rows are built from the product–category link;
    • the product needs a description in the language the export is built in.

    You can check the filtered set before a run in the “What will be exported” window, which opens from the “Export” button: the preflight summary.

    Elbuz doesn't flag products on Prom that dropped out of the file. The template does have the «Товар на удаление» (product to delete) and «Причина удаления товара» (deletion reason) columns, but their values come from the card fields of the same name, which you fill in. How Prom treats items missing from the next file is the marketplace's rule.

    Schedule, log and file link

    Runs, the schedule, the log, stop rules and the permanent link are the same for all templates — Manual and scheduled runs, Where the file goes. Below is what's worth knowing specifically about the Prom template.

    How to make sure the file was built

    The run log opens in “Operations” and stays under the template's “Run history” button. The Prom template logs progress as “Rows exported N of M” every thousand products. Success is “Data export completed” and a “Download file ‹name›” link; failure is “Data export NOT completed: the file was not generated”. How to read the other lines: Run log.

    In the template list, the pair of numbers in the “In stock” column catches a collapse: the file was built, but it has half as many products.

    Export window: list of export templates with state, file, last export and in-stock columns
    1File column
    2Last export column
    3In stock column
    1. File — link to the generated file with its size in MB under it.
    2. Last export — when the template was last exported and how long that run took.
    3. In stock — number of products in stock, the change since the previous run and the total below.

    Column content is checked on one product with the flask button — “Trial export of one product”. It builds a separate test file, shows “column = value” pairs and errors, and doesn't touch the live file, the link or FTP.

    If a run broke off or was stopped

    The new link, size and date are written to the template only after the file is uploaded successfully. A break-off at any step before that leaves the previous file on the link. Running again is safe: the file is built from scratch, and Elbuz sends nothing to Prom.

    Three diamonds are the three places where a run ends without a new file: a stop rule before building starts, a failed product query, and a failed cloud upload. Only the bottom branch reaches a new link and date
    yesno, or warning onlynoyescloud modelocal modenoyesTemplate run startsCategory tree and internal SKUsStop rule in“Stop the export” modetriggered?“Export stopped by a stop rule”previous file stays on the linkOld file with the same namedeleted from the temp folderEmpty Prom fields on cardsfilled from the categoryProduct queryran without errors?“Data export NOT completed”date not updatedFile built in the temp folderand sent to FTP if configuredNew fileuploaded to the cloud?Link, size and datewritten to the template“The file was not uploaded to cloudstorage”previous file stays on the linkOld files removed fromthe template folder in the cloud“Data export completed”
    • Start or end
    • Action or result
    • Decision: the path depends on the answer

    The stop flag is checked between templates in “Export all templates” mode. A single Prom template run doesn't read it and finishes the file, even though the line “Export stopped by the user!” appears in the log: the button itself writes it. The file is updated anyway.

    Disable a template or delete it

    • The schedule skips a disabled template silently, with no log line, and “Export all templates” doesn't include it. The “Export” button on the template itself works even when it's disabled. The file, link and settings are kept.
    • Deleting removes the column set, FTP, category selection, schedule binding and the link to the last file. The only way back is to create the template again.

    Limits and volumes

    • Rows in the file — as many as products that passed the filters; there's no cap. On a demo account it's 100 products, and the log has a line about it.
    • An XLSX cell holds 32,767 characters. Longer text (usually a description) is cut at that limit.
    • Photos — the first 10 links. The image link column gets ten photos in sort order.
    • A bulk run — one hour. “Export all templates” runs as a separate process, templates one after another, with one hour for the whole process.

    XLSX or XML/YML: which to choose

    Prom accepts both formats, and both carry the same product ID — our UUID.

    FormatHow it worksWhen to use it
    XLSX (this article)a file with all Prom columns that you hand to the marketplaceElbuz is the main system: the full catalog, new products, attributes, all fields
    XML / YML feeda feed by link that Prom fetches on its own scheduleyou mainly need to keep prices and stock fresh with minimal effort

    You can load the catalog with an XLSX file first and then keep it fresh with an XML feed — the items stay the same.

    If the same products go both as XLSX and as a feed

    There's no conflict in Elbuz itself. Both templates read the same card, so they won't bring different prices or stock. Each template has its own folder in storage and its own link, so running one doesn't touch the other's file.

    What they share are the Prom fields on cards (group number, group ID, subsection ID, subsection address): a run of any Prom template fills them, and only empty ones. Two scheduled exports don't run at the same time — the second is canceled with a log line about a data processing conflict.

    Whose value stays on Prom when a product arrived both by file and by feed is up to the marketplace. So give one format the full catalog role and the other whatever the first doesn't have, or separate them with the template filter.

    Scenarios

    You manage the catalog in Elbuz and add new products to Prom

    What to set up. First bring the catalog from Prom with XLSX import, then create a Prom-format template and build the file with the “Export” button. Don't remove the Ідентифікатор_товару (product ID) column on the “Select fields” tab.

    The result. Prom recognizes items that came from Prom by their UUID and updates them. Products created in Elbuz go with an empty Унікальний_ідентифікатор (unique ID), and Prom adds them as new.

    What won't happen. Elbuz won't send the file to Prom on its own and won't remove items missing from the file from Prom.

    You manage descriptions and photos in your Prom account, everything else from Elbuz

    What to set up. Open the template, go to the “Select fields” tab, and remove the columns you manage on the marketplace with “Delete field”. Keep Ідентифікатор_товару.

    The result. The removed columns won't be in the file at all.

    What won't happen. Edits from your Prom account don't get into Elbuz on their own: that takes a separate catalog import.

    The file updates on a schedule, and you can't hand over a catalog with missing stock

    What to set up. In the export window, open the “Additional operations” menu → “Export stop rules”. For the “in-stock count collapsed versus the previous run” rule, set the “Stop the export” mode and click “Save for this template”. The default threshold is 30%.

    Export stop rules window with thresholds and modes for the selected template
    1In-stock collapse rule
    2Mode column
    1. The rule that compares the in-stock count with the previous run; the threshold is a percentage.
    2. Mode — Off, Warn or Stop the export for each rule.

    The result. If in-stock products drop by more than the threshold compared to the last successful run, the run — manual or scheduled — ends with the line “Export stopped by a stop rule: …”. The previous file stays on the link. All rules and modes: Stop rules.

    What won't happen. The schedule doesn't run a disabled template at all, and stop rules have nothing to do with it. Make sure the “State” column says “Active”.

    You have custom stock statuses

    What to set up. Nothing: the «Наличие_xls» field formula outputs a custom status by quantity — + if it's above zero, otherwise -. If you want a different Prom symbol for your status, add a branch to the formula in the “Base catalog field formulas” window, then save the cards or run batch price list processing.

    The result. The availability column in the next file gets the symbol set by the formula.

    What won't happen. The export run itself doesn't recalculate the formula: until the cards are saved or batch-processed, the file gets the old field value.

    Only part of the catalog goes to Prom

    What to set up. Category selection in the template, or conditions on the “Export limit (filter)” tab. Before building the file, check the numbers in the “What will be exported” window; “Show these products in the catalog” shows the list itself.

    The result. Only products that passed the filters go into the file.

    What won't happen. Products that stopped passing the filters aren't flagged for deletion on Prom: they just disappear from the file.

    A 7% discount on a category from the 1st to the 30th

    What to set up. In “Promotions / Discounts”, a rule: “%” -7, “Quantity price (wholesale)” cleared, “Additional filter” — the category, plus “Start Date” and “End date”. Apply the rules, build the file and upload it manually in your Prom account. The Скидка and Cрок действия скидки от/до columns must stay on the template's “Select fields” tab.

    The result. Rows for products in the category get Скидка = 7% and the rule's dates. Prom applies the discount from the 1st to the 30th and removes it after the end date on its own.

    What won't happen. If Prom fetches the file by link, the dates may not work (Help on YML says the discount is set for 45 days), so the discount lasts as long as the file carries it. In that case, apply the rules after the promotion ends (Elbuz clears the discount columns) and wait for the next Prom update.

    A promotion has to end early

    What to set up. Disable the rule in the “Promotions / Discounts” window — saving it as disabled recalculates promotions right away. Build the file and hand it to Prom.

    The result. For the rule's products, Скидка and the discount period columns are empty, and Цена is the regular price. After import, Prom shows the price without a discount.

    What won't happen. An empty discount cell means no discount only for fields Prom updates. If the discount field was unchecked in Prom's import settings, the old discount stays on the marketplace — remove it in your Prom account.

    What to do when the file comes out wrong

    What you see, why, and what to do
    What you seeWhyWhat to do
    “Last export” didn't move, and the log says “Data export NOT completed: the file was not generated” The run failed before the file was saved, or the file wasn't uploaded to the cloud — the date and link update only after success The previous file is still on the link; don't hand it to Prom. Look at the line above the error (how to read the log) and check the template with the trial export button
    The availability column in the file is empty, and products on Prom became out of stock The «Наличие_xls» field is empty: the catalog wasn't imported from Prom, the formula was deleted, or the cards haven't been recalculated yet Check the field formula (availability column) and save the cards or run batch processing so the values are recalculated
    A product is in the catalog but not in the file, and the log says nothing about it It didn't pass one of the filter conditions — the export flag, category, filter, store or warehouse Go through the list of conditions and check the numbers in the “What will be exported” window
    The scheduled file isn't updating, and there are no errors in the log The template is disabled — the schedule skips it silently. Or another export was already running at that moment Check the “State” column in the list: if it's “Disabled”, enable it (details). If the state is “Active”, look for a data processing conflict line in the log
    You clicked “Stop”, but the file was updated anyway The stop flag is checked between templates of a bulk run; a single Prom template doesn't read it Wait for the run to finish — running again is safe and doesn't duplicate anything (what happens on a break-off)
    A product description in the file is cut off mid-word An XLSX cell holds 32,767 characters, and longer text is cut Shorten the description in the card: the cell won't fit more (format limits)
    You set up a promotion in Elbuz, but the Скидка column in the file is empty The rules weren't applied; the rule has the “Quantity price (wholesale)” checkbox (a quantity-based price) or a positive percentage; the promotion has already ended; the rule isn't for the retail group; the “Sale price” field has a formula Use a percentage with a minus sign, clear “Quantity price (wholesale)”, click “Apply rules to products”, and build the file again (discounts in the file)
    “Coming soon” products became out of stock on Prom The formula outputs & for this status, and Prom reads it as out of stock Change the status symbol in the «Наличие_xls» formula to the number of delivery days, for example 3 (availability column)

    FAQ

    Why does Prom duplicate products when I edit the file by hand, but not through Elbuz?

    Prom duplicates items when the file has no product IDs. Elbuz always puts the product ID (our UUID) in every row, so Prom recognizes existing products and updates exactly those.

    Do I need to export from Prom again after adding new products?

    Not for updates without duplicates: Elbuz sets the IDs itself. Import the catalog from Prom again only to pick up changes on the marketplace side: moderation, manual edits, numbers of new products.

    How does Prom pick up a new product created in Elbuz?

    Such a product goes with its own UUID in the product ID column and an empty unique ID. Prom sees an unknown ID, adds the product as new and assigns its own number.

    Why is availability in the file different from what's in the card now?

    The file gets the «Наличие_xls» field, and its formula is recalculated when a card is saved or during batch price list processing, not during export. Save the card, and the next file carries the fresh symbol (availability column).

    What happens to my edits in the Prom account after the next export?

    The file carries the current values from Elbuz for all template columns. Remove a field you manage in your Prom account from the template with “Delete field” (running again).

    I clicked “Stop” — will the export stop?

    A single Prom template run won't: the file is finished. The stop flag is checked only between templates in “Export all templates” mode. Running again doesn't duplicate anything.

    What happens if I disable a template?

    The schedule skips it silently, and “Export all templates” doesn't include it. The “Export” button on the template itself still works. The file, link, columns, filter and schedule are kept.

    How do I pass a discount with dates to Prom in an XLSX file?

    Create a “Promotions / Discounts” rule with a negative percentage and dates, then apply rules. Elbuz fills the Скидка and Cрок действия скидки от/до columns; Prom applies the discount. Dates are reliable with a manual upload; by link, they may not work (discounts in the file).

    What happens to the discount on Prom when the promotion ends in Elbuz?

    The next time the rules are applied, the discount columns are cleared, and the new file goes without it. With a manual upload with dates, Prom removes the discount on the end date itself; by link, after the next update.

    Which Prom columns are required?

    Назва_позиції (name), Опис (description), Ідентифікатор_товару (product ID), and for products already added, also Унікальний_ідентифікатор (unique ID). The Elbuz template fills them all. The full list: column reference.

    Where to find it and who has access

    Menu
    Directories → Operations → Data export
    Stop rules
    list menu → “Export stop rules”
    Access right
    the “Data export” window; for the template card — “Export Template Setup”
    Prepare
    a catalog imported from Prom with XLSX import

    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