Elbuz spreads a Prom.ua or Satu.kz Excel catalog across product cards itself and keeps even columns the standard card has no place for — no manual column mapping needed.
When you need this:
- Looking for a file column — the table shows which card field it went to.
- Preparing a file for Prom yourself — formats and field length limits.
- Export availability differs from the file — the Prom symbol comes from the product's current status.
- Managing variants and groups on Prom — the links are kept and go back to Prom on export.
Where to start: the “file column → card field” table.
What the Prom file import keeps
- Two file sheets — products and groups are read by column names; column order doesn't matter.
- Main card fields — name, price, quantity, category, description, and photos go into the card's own fields.
- Value formats — which lengths and codes Prom accepts.
- Availability — Prom symbols become statuses, and on export they're calculated from the current status.
- Additional fields — all other Prom columns are kept in the card in full.
- Attributes, variants, and groups — carried over into attributes, the variants field, and the category tree.
- The way back — the same fields are exported back to Prom.
How Elbuz reads the file: two sheets
The official format description is in the Prom help center: Import via Excel: XLS(X) and CSV file formats (in Ukrainian). Here we explain how Elbuz specifically reads and stores that same format.
A Prom Excel file (XLS/XLSX) contains two sheets, and Elbuz reads them by name:
- “Export Products Sheet” — products. Every row except the first is one product; the first row holds the column headers.
- “Export Groups Sheet” — groups (categories): their numbers, names, IDs, and parent–child links.
In format there's only one sheet (products only), encoded in or UTF-16.
The first row of each sheet holds the headers: Elbuz matches them against known field names and that's how it works out what each column contains. Names are recognized in both Russian and Ukrainian (Код_товара = Код_товару, Название_позиции = Назва_позиції, and so on), so both language versions of the file are read the same way.
Column order doesn't matter — what counts is the name in the header. If a column is missing, the matching field stays empty.
Of the three formats Prom can export, Elbuz reads only .xlsx. The file picker accepts only that extension, and the server also checks that the file starts like an Open XML workbook — a legacy .xls or .csv renamed to .xlsx won't pass either.
The wrong file stops the run before parsing with the message “The file is not an XLSX workbook. Prom.ua and Satu.kz export the catalog as .xlsx — the legacy .xls format is not supported. Open the file in Excel and save it as “Excel Workbook (.xlsx)”.”, and the catalog doesn't change at all.
Where the main card values go
Some columns go straight into the card's own fields — the ones every Elbuz product card has:
| File column | Card field in Elbuz |
|---|---|
| Назва_позиції / Назва_позиції_укр (item name) | product name (the Ukrainian version goes into the card's Ukrainian language) |
| Ціна + Валюта (price + currency) | price (converted to your base currency at the exchange rate) |
| Кількість (quantity) | quantity in stock |
| Наявність (availability) | stock status (see the section on symbols) |
| Номер_групи / Назва_групи / Ідентифікатор_групи (group number / name / ID) | product category (link to the tree from the groups sheet) |
| Виробник (manufacturer) | manufacturer (Elbuz adds a new manufacturer to the directory on its own) |
| Опис / Опис_укр (description) | product description (the Ukrainian version goes into the Ukrainian language) |
| HTML_заголовок / HTML_опис / HTML_ключові_слова (+ _укр) | the card's meta title, meta description, meta keywords |
| Вага, Ширина, Висота, Глибина, Довжина (weight, width, height, depth, length) | the card's weight and dimension fields |
| Код_маркування_() | GTIN (barcode for Google Merchant) |
| Посилання_зображення (image link) | product photos (several s separated by a comma and space; the first is the main one) |
The SKU (Код_товару) is written to two card fields at once — SKU and .
Before saving, the price is converted to your base currency: for prices in another currency, Elbuz takes the rate by currency code and recalculates. The category is linked to the group tree from the “Export Groups Sheet”; if the product's group isn't there, it's created automatically from the number and name in the product row.
Prom has a separate rule: for the Ukrainian version of a product to update, both Ukrainian fields must be filled in the file — Назва_позиції_укр and Опис_укр. If only one of them is filled, the translation on Prom's side won't update.
Elbuz takes the Ukrainian fields into the card's Ukrainian language as is — but keep this Prom rule in mind when you prepare a file to export back.
Which formats and value limits Prom accepts
Prom fields have specific formats, and it's worth preparing the file with them in mind — otherwise the marketplace will reject the row or truncate the value:
- Код_товару (product code) — up to 25 characters (digits, Cyrillic, Latin, the characters
- _ . /, and space). - Назва_позиції (item name) — up to 110 characters (Russian), Назва_позиції_укр — up to 130.
- Опис / Опис_укр — up to 12160 characters; HTML_заголовок/опис — up to 250 (Russian) / 270 (Ukrainian).
- Ціна — a number from 0.01; Валюта — a code (UAH, USD, EUR, PLN, KZT…) or an abbreviation (грн, дол, $).
- Тип_товару (product type) — a letter:
r— retail only,w— wholesale only,u— both wholesale and retail,s— service. - Одиниця_виміру (unit) — from the Prom list (шт., упаковка, комплект, пара, м, кг, л, набір…).
- Оптова_ціна (wholesale price) and Мінімальне_замовлення_опт (minimum wholesale order) — several values separated by
;; Подарунки/Супутні (gifts/related) — row numbers or s separated by;. - Знижка (discount) — a number or a percentage (for example,
12.5or30%) with “from/to” validity dates.
Elbuz stores these values as they are in the file (in the matching card fields — see below), and the marketplace itself checks them against Prom's requirements during export. So a clean, correctly formatted file saves time on both ends.
How availability is converted: Prom symbols and the reverse formula
Availability in a Prom file is coded with symbols, and Elbuz converts them into its own stock statuses:
+(or!— “ready to ship”) → In stock;-→ Out of stock;&→ Coming soon;- a digit (for example,
7) → Preorder (number of days to delivery); - an empty field or any other value (including
@) → your catalog's main “In stock” status.
The availability field works both ways. Together with the additional field “Наличие_xls”, Elbuz creates a formula for it that calculates the Prom symbol not from the old file value but from the product's current stock status in your catalog:
- “In stock” status →
+; - “Out of stock” →
-; - “Coming soon” →
&; - “Preorder” →
5; - a status you created yourself →
+if the quantity is greater than zero, otherwise-.
The formula recognizes standard statuses by their number, so renaming a status doesn't affect it. That's why when you export the catalog back to Prom, availability is always fresh — what's in your system now, not frozen at the moment of import.
Where Prom fields that the card doesn't have go
Prom has far more fields than the standard product card. So that nothing from the file is lost, during import Elbuz creates the matching additional fields in the base catalog on its own and writes these values there.
In other words, the card doesn't “truncate” the Prom file to a few standard fields — it keeps all of its content. Here are the main groups of such fields that appear in the card after the first import:
- Prices and ordering: Оптова_ціна, Мінімальний_обсяг_замовлення, Мінімальне_замовлення_опт, Ціна_від, Знижка, Термін_дії_знижки_від/до (wholesale price, minimum order, discount and its dates).
- Logistics and packaging: Можливість_постачання, Термін_поставки, Спосіб_пакування (+ Ukrainian), Одиниця_виміру, Де_знаходиться_товар, Країна_виробник. Гарантійний_термін (warranty) doesn't get a separate field — it's written to the card's standard warranty field.
- Prom classification: Тип_товару, Ярлик, Номер_групи, Назва_групи, Ідентифікатор_підрозділу, Ідентифікатор_групи, ID_групи_різновидів, Номер_пристрою_(MPN).
- Content and : Ключові_слова, Пошукові_запити, Особисті_нотатки (keywords, search queries, personal notes) and Ukrainian versions of the name, description, and meta fields.
- Links and system fields: Подарунки, Супутні (gifts, related, and their IDs), Товар_на_видалення and Причина_видалення (deletion flag and reason), Унікальний_ідентифікатор (a separate indexed field for Prom's internal number).
In the card these fields have the names from the Russian version of the Prom file: “Оптовая_цена”, “Тип_товара”, “Уникальный_идентификатор”, and the discount is “Скидка_xls”. They're shown next to the standard ones, and you work with them like regular fields: filter, show in the grid, use in formulas, and — most importantly — export them back.
1
Unique identifier field2
Wholesale price field- The unique identifier field holds the internal Prom number of the item.
- The wholesale price field is one of dozens of fields from the Prom feed kept on the product.
How attributes are imported
Prom keeps product attributes in column triples that always come in strict order: Назва_Характеристики (name), Одиниця_виміру_Характеристики (unit), Значення_Характеристики (value). A file can have many triples, one per attribute; the unit column must be present even if empty. Multiple values are separated by | (for example, Aluminum | Plastic).
Elbuz recognizes these triples by header and carries them over into the product's attributes: the name becomes an attribute, the value becomes its value, and the unit (cm, kg, W…) is added to the units directory automatically if it isn't there yet.
Attributes are imported automatically along with the rest of the file data — you don't need to turn them on separately. If a product has no attributes, the file either had no matching column triples or they couldn't be recognized by header.
How product variants are kept
Prom marks variants of one product (colors, sizes, and so on) with the ID_групи_різновидів (variant group ID) field: all rows with the same value in this field and filled-in attributes are treated as variants of one product, and the first row in the group is the main one.
Elbuz keeps this field, so the variant link isn't lost on export back. If you manage variants on Prom, keep ID_групи_різновидів filled in the file — it's what holds the variants together.
How the groups sheet becomes a category tree
Elbuz builds the category tree from the groups sheet.
- Each group has a Номер_групи (group number on the Prom site), a name (and its Ukrainian version), and an Ідентифікатор_групи (external ID — for example, the group number in your ). Nesting is set by the parent group number and parent group ID fields (empty for root groups).
- There are also group SEO fields and descriptions “before” and “after” the product list.
- Groups are matched by ID first, and by number if there's no ID; new ones are created, existing ones are updated.
- If a product refers to a group that isn't on the groups sheet, Elbuz creates it from the product row's own data so the item isn't left “homeless”.
- Action or result
- Decision: the path depends on the answer
How these fields go back to Prom
In the Prom format, the import file and the export file are the same. So the fields the import filled are the ones later exported back to Prom. For example, our product goes back into the Ідентифікатор_товару (product ID) column on export, and the additional field “Унікальний_ідентифікатор” goes into the column of the same name.
A product created in Elbuz goes into the export file with its own UUID in the product ID column and an empty unique ID — Prom adds it as new and updates existing ones. The full exchange order: export to Prom (XLSX).
The product UUID (the product ID on Prom) and “Унікальний_ідентифікатор” are sync keys. If you change the UUID of an existing product, Prom will treat it as new on the next export and duplicate the item. That's why these fields aren't edited by hand — import and export manage them themselves.
Don't delete the automatically created Prom fields, even if you don't need one of them right now. They're what makes a lossless export back possible: if you remove a field, the matching column will go to Prom empty on export.
FAQ
Can I import a legacy .xls or CSV file from Prom?
No, the template accepts only .xlsx. Open the file in Excel and save it as “Excel Workbook (.xlsx)”. A failed attempt doesn't change the catalog. More: how Elbuz reads the file.
Why didn't the Ukrainian product name or description update on Prom?
Prom updates the Ukrainian version only if both Ukrainian fields are filled in the file — the Ukrainian item name and the Ukrainian description. If only one is filled, Prom ignores it. More: main card values.
Why doesn't availability on export match what was in the file?
Because the availability symbol is calculated by a formula from the product's current status in your catalog, not taken from the file “as is”. Prom gets the current availability. More: how availability is converted.
Why weren't the attributes imported?
The file didn't have attribute name / unit / value column triples, or they weren't recognized by header — the columns must come in exactly this order. You don't need to turn attributes on separately. More: attributes.
Why are the additional fields in the card named in Russian?
Elbuz creates them under the column names of the Russian version of the Prom file — “Оптовая_цена”, “Тип_товара”, “Уникальный_идентификатор” — regardless of your file's language. The same values go into them. More: Prom fields that the card doesn't have.
Where it is and who has access
- Menu
- Directories → Operations → Data import → the “XLSX - prom.ua, satu.kz” template
- Where to see the result
- product card, “Other fields” → “Custom fields”
- Access right
- the “Import” window in “Group permissions”
- Prepare
- an .xlsx file exported from Prom
How to set up the template and run the import: see moving a catalog from Prom.ua with an XLSX file.
Related topics
- If you need the big picture — how to move and regularly update a catalog from Prom: importing a catalog from Prom.ua with an XLSX file.
- If a repeat import created duplicates — how Elbuz recognizes a product.
- If you need to send the catalog back to Prom — export to Prom.ua (XLSX).
- If the marketplace provides the catalog in XML — importing a catalog from XML / YML.
