↑↓ selectEnter openEsc close

    1. Elbuz

    How to move a catalog from Prom.ua to Elbuz with an XLSX file

    24 min readUpdated

    Elbuz takes the Excel catalog from Prom.ua or Satu.kz — from your computer or a link — and moves categories, products, prices, stock, photos, and attributes into the base catalog.

    When you need this:

    • Moving from Prom to Elbuz — the whole range arrives in one file; groups become categories.
    • Prices and stock live on Prom — a scheduled template updates cards without duplicates.
    • Products removed from Prom must go — mirror mode deletes what isn't in the file.
    • Some cards are checked by hand — card flags protect them from the file.

    Where to start: open the “XLSX - prom.ua, satu.kz” template and import a file exported from Prom.

    What the Prom file import does

    How to set up the template and run the first import

    • Source — a file from your computer or a link that Elbuz uses to fetch the file itself. Only .xlsx is accepted: legacy .xls and won't go through (how Elbuz reads the file).
    • What gets imported — categories, products, manufacturers, and attributes are taken from the file automatically; you don't need to turn them on separately.
    • The only switch — full mirror mode, “Delete entries in the base catalog that are not in the imported file”; everything else is preset and has no switches.

    Run the first import on a small or test file and check the result using the log figures and grid columns. Only once you're sure everything came in correctly, import the full file and put the template on a schedule.

    Import setup form of the prom.ua XLSX template
    1Data source (file or link)
    2What to import block with checkboxes
    1. Choose the source of the file: upload from the computer or a link.
    2. The “What to import” block with checkboxes for categories, products, manufacturers, attributes and photos.

    The two most common surprises are currency and empty availability. If prices in the file aren't in your base currency, make sure an exchange rate for that currency is set in the system, otherwise no conversion happens. And Elbuz records an empty availability field as “In stock”, so explicitly mark products you don't actually have with -.

    How Elbuz recognizes a product and avoids duplicates

    What matters most for repeat imports is how Elbuz recognizes that a product from the file is already in the catalog. That decides whether an existing card is updated or a duplicate is created. Several columns are responsible for this, and Elbuz uses them in this order:

    File columnWhat it isRole in matching
    Ідентифікатор_товару (product ID)Prom's internal product ID (in Prom itself this is a required field for unambiguous matching)main key: the product is recognized by it first (stored in an internal card field)
    Унікальний_ідентифікатор (unique ID)Prom's numeric service number for the product; Prom fills it in automatically on export, and it can't be changed by handfallback key: used if the product wasn't found by the first one
    Код_товару (product code)your item code (), up to 25 charactersnot a Prom key: written to the card as the SKU and

    The logic: Elbuz first looks for the product by the product ID. If it isn't found that way (the column is empty, or your catalog doesn't have that ID yet), Elbuz searches by the unique ID. And if the product isn't found by either ID, it's treated as new and gets its own internal key.

    This is where the typical trap lies: if the file has no stable IDs, every repeat import creates duplicates instead of updating. That's why a file exported from Prom itself (where the IDs are already filled in) is the most reliable source; test a home-made file without IDs on a small part first.

    Which key Elbuz uses to recognize a product. The dashed arrow shows where a file without IDs leads
    YesNoYesNoYesNoa file without IDstakes this path every timeProduct row in the fileIs the“product ID” column filled?Search for the card by it —this is the main keyIs the“unique ID” column filled?Search for the card by it —fallback keyThe product is treated as newCard found?The existing card is updatedA new card is createdwith its own internal keyA repeat importcreates duplicates
    • Action or result
    • Decision: the path depends on the answer

    Prom distinguishes your SKU (the product code — you set it) from its own internal ID (the product ID and unique ID — Prom assigns them). To update repeatedly without duplicates, Elbuz relies on Prom's internal ID, not the SKU: sellers sometimes change SKUs, but the internal stays the same.

    Where these IDs go — the keys for syncing with Prom:

    • Ідентифікатор_товару is stored in the product's system field “UUID” — the product's unique key in Elbuz. This is the main matching key: on import, the product ID from the file goes into the , and from then on the UUID is the item's permanent key in your catalog.
    • Prom's Унікальний_ідентифікатор goes into a separate additional field with the same name (Prom's numeric service number for the product).

    What a repeat import overwrites

    The Prom template writes fields from the file as they are: an empty cell in the file doesn't keep the card's old value. Product photos that come in the file are replaced completely. More: what a repeat run overwrites.

    Attributes behave differently from other fields: for a product that has attribute column triples in the file, the existing attributes are deleted first, and then the ones from the file are written.

    A flag keeps your own value in the card: “Do not update” protects the whole card, “Fixed Price” only the price, “Do not update photo” only the photos. More: how to lock your own value. Flags only affect updates: they don't protect against mirror mode.

    How to make the catalog an exact copy of the Prom file

    The template has a separate full mirror mode — the “Delete entries in the base catalog that are not in the imported file” checkbox. When it's on, the catalog becomes an exact copy of the file.

    Internally the order is: first Elbuz marks the entire base catalog for deletion, then unmarks the categories and products found in the file, deletes the rest — and only then adds and updates what's in the file. In other words, deletion happens before the new data is imported, not after the results are checked.

    Know this before turning the mirror on: the Prom form has no “Check uniqueness of records based on this import source” switch like the one in the YML template. The mirror ignores where a product came from: cards created by hand, from price lists, or by the parser are deleted too if they aren't in the Prom file.

    A deleted product takes with it its description, category and store links, attributes, photos, Q&A, and “Related products” links. A deleted category takes its description, store links, place in the tree, its price list distribution rules, and its selection in export templates. Price list rows stay, but lose their product link and are left without a card.

    An empty or unreadable file won't wipe the catalog: if not a single product row was recognized in the file, product deletion doesn't start; the same applies separately to categories. But a file with even one product is already considered complete. More: a product disappeared from the source.

    The two “is there anything in the file” checks come before each deletion separately — for categories and for products. Adding and updating always runs, after deletion
    NoYesYesNoYesNoThe file has been read to the endIs the “Delete entriesin the base catalog that are notin the imported file” checkbox on?Categories and products from thefileare added and updatedAt least one grouprecognized in the file?Categories not in the fileare deletedAt least one productrecognized in the file?Products not in the file are deletedwith their description, photos,and attributesPrice list rows remainwithout a link to a card
    • Action or result
    • Decision: the path depends on the answer

    How to restore what the mirror deleted

    No “cancel import” button, no Trash for deleted cards: rows leave the database for good. The one way back is to import the same file again, but complete. Products return under the same product ID, so the cards get the same UUID and the Prom link holds — the export back to Prom still recognizes its items.

    A repeat import doesn't bring everything back. These won't return:

    • Q&A on the card — the Prom file doesn't have this data, and there's nowhere to get it from; “Related products” links — the Супутні and ID_Супутніх (related, related IDs) columns go into the card's additional fields, but the import doesn't restore the links themselves;
    • links between price list rows and cards — re-importing the price list itself restores them;
    • price list distribution rules that were linked to the deleted categories, and the selection of those categories in export templates;
    • photos — only if the Посилання_зображення (image link) column is filled in the file; attributes — only if the file has attribute column triples.

    One more thing that isn't obvious right away: the card's internal number will be new. In rows of documents already issued, the name and SKU are stored as text and won't go anywhere, but the link from the document to the product card will no longer work.

    A database backup is taken every night, and the last seven automatic backups are kept (free accounts aren't included in nightly backups).

    There's no restore button in the interface — only support can restore the database from a backup. And it's not a matter of “pulling a few products out of it”: the backup replaces the whole database, so along with the catalog all settings roll back a day, and everyone working at that moment is signed out.

    How to check that the import worked

    The run log is in the “Operations” panel; right after the start you'll see the hint “Import started — follow it in Operations”. You can close the template window: only the “Stop” button stops the import. More: how to check that the import went through.

    As the run goes on, the log records the steps in the same order the work happens:

    1. “Creating temporary tables” → “Importing data into the base catalog” → “Identifying records already in the database”.
    2. “Adding product categories”, “Updating product categories”, and “Updating category keys”.
    3. “Determining manufacturers for products” → “Determining product availability” → “Adding products” and “Updating products”.
    4. “Importing product attributes” → “Importing product photos”.
    5. “Updating values based on formulas” → “Data integrity check” → “Product indexing”.

    The last line is “Data import completed!”, followed by “Time elapsed:” with the run duration.

    The log has exactly two figures, and you should read them literally:

    • “Total items imported: N” — during reading, it counts the file rows read, updating every 500 rows. At the end the same line shows the total: how many product rows the file had. It's not the number of cards created or updated — the log doesn't count new versus updated cards.
    • “Total categories imported: N” — the same for the groups sheet.

    Two more lines appear only when needed:

    • “Photos not imported: N” — if some photo links turned out to be unusable;
    • the red “Some data was not saved: the database rejected a query.” — if the database rejected at least one query. This line means the run reached the end, but not all data made it in; don't confuse it with the final “Data import completed!”.

    Now, where to look in the grids:

    • In the template list, the “Last import” column shows when the template last ran and how long it took. “never imported” means there hasn't been a single run.
    • In the base catalog grid, the “Update date” column confirms the update: for all updated cards it becomes the run time. New cards show up in the “Date added” column and in “Source: name” — it will contain your template's name, and “Source: code” will show prom_xlsx.

    The “Source: name” column is filled only when a card is created: a product that once came from a price list keeps the price list as its source. The sign of an update is “Update date”, not “Source”.

    The “Run history” button shows the duration and results of runs for 30 days — it's in the template form header and on the list toolbar.

    Run history window of the prom.ua template
    1Average duration and longest run summary
    2Run row in the table
    1. The summary shows runs in the period, average duration, longest run and runs with errors.
    2. Each row of the table is one run with its status, duration and result.

    If the import broke off or was stopped

    The work happens in two passes.

    First Elbuz reads the whole file into staging tables without touching the base catalog. The transfer starts only after that — the “Importing data into the base catalog” line in the log. So a break during reading (lost connection, damaged file, “Stop” clicked) leaves the catalog exactly as it was, and it's safe to try again.

    The “Stop” button in “Operations” doesn't work instantly. Elbuz checks it every 500 rows while reading, then before deleting extra records, after updating categories, and after products and photos; with the integrity check enabled, also after the check and at the very end. In the panel the operation is marked “Stopped” right away, but the run itself continues to the nearest of these points. Then:

    • if you stop during reading, the log shows “Operation aborted by user!”, and the catalog stays unchanged;
    • if you stop after the categories have been updated, the categories will be new and the products still old. This isn't a malfunction: a repeat run finishes the job.
    Diamonds are the points where the run notices “Stop”. What managed to change in the catalog depends on which one it stopped at
    YesNoYesNoYesNoYesNoReading the file into staging tables“Stop” clicked?checked every 500 rows“Operation aborted by user!”categories and products unchanged“Importing data into the basecatalog”“Stop” clicked?checked before deletionDeleting extra records (mirror only),adding and updating categories“Stop” clicked?checked after categoriesAborted — categories alreadyupdated,products not yetProducts, attributes, photos“Stop” clicked?checked after products and photosAborted — products alreadyupdated,formulas and integrity check not runFormulas, integrity check,“Data import completed!”
    • Action or result
    • Decision: the path depends on the answer

    If the run died on its own (time limit, lost database connection), there's no rollback: whatever was written stays written. Only one place is wrapped in a transaction — photo replacement: if it fails midway, the old photos come back, so you never end up with “old photos gone, new ones not there yet”.

    A stuck run whose log hasn't had new lines for 15 minutes is marked as aborted, and the next scheduled run starts normally. More: if a run broke off.

    Running it again is safe. Staging tables are recreated before each run, and products that were already created are found by ID and updated. Only a file without product IDs creates duplicates (how Elbuz recognizes a product).

    How long a run takes and where the limits are

    There's no cap on the number of rows in the file: Elbuz reads the file to the end, however many rows it has. Other things are limited:

    • Two hours per run — that's how much time an import of a file from your computer gets. If the work isn't done in two hours, the run breaks off wherever it was, with the consequences described in the section on breaks.
    • Every 500 rows — the step at which Elbuz writes the read count to the log and checks the “Stop” button. Between these points the log is silent, and a stop also waits for the nearest one.
    • Up to 20 photos per product — that's how many links Elbuz takes from the Посилання_зображення column; the 21st and beyond won't be imported.
    • SKU — 25 characters (Prom itself allows the same), product name, group name, and meta fields — 255 characters, GTIN — 14. Longer values won't fully reach the card.
    • File size is limited by the server, not by Elbuz. A file that didn't get through shows up right away: “The file could not be sent to the server. It may be too large or the connection was lost. Error code ...” — the catalog doesn't change.

    Two scheduled imports don't start at the same time: a run that runs into another template waits until next time (two runs at once). How long your particular file takes is shown by “Average duration” in the “Run history” window after the first or second run.

    Disable or delete the template

    The “Active” / “Disabled” badge in the form header or in the list's “State” column turns scheduled runs on and off. Manual runs work on a disabled template too, and deleting a template doesn't touch the imported products. More: disable or delete a template.

    While this template is running a scheduled import, the “State” column shows “Running”, and clicking doesn't toggle the state at that time. The ready-made “XLSX - prom.ua, satu.kz” template is a system one: it can't be deleted, only disabled.

    Import template list with the State and Last import columns
    1State pill of the prom template
    2Last import value
    1. The State pill shows whether the template is active or disabled.
    2. The Last import column shows when the template was last run.

    Scenarios

    Move your catalog from Prom to Elbuz for the first time

    Task: your whole range is managed on Prom, and you need it in the base catalog.

    What to turn on: in the “XLSX - prom.ua, satu.kz” template, in the “Data source” block, the “Local file” tab, the “Select file - Catalog” button — the .xlsx file exported from Prom. Leave the “Delete entries in the base catalog that are not in the imported file” checkbox off.

    What you get: groups from “Export Groups Sheet” become categories, products become cards. A card's UUID is the Prom product ID, or the unique ID if that's empty. Fields with no place in the standard card go to additional fields, attributes to attributes, photos — up to 20 per product. New cards show the template name in “Source: name”.

    What won't happen: no existing card is deleted, and cards from price lists or created by hand stay as they were.

    Update prices and stock from Prom on a schedule

    Task: prices and availability are managed on Prom, and in Elbuz they should stay fresh without manual runs.

    What to turn on: in the “Data source” block, the “External link” tab, the “Link to product file (Catalog)” field. In the “Related settings” block — the “Schedule setup” button. Template state — “Active”.

    What you get: on schedule, the template fetches the file from the saved link, finds products by UUID, and updates price, quantity, availability, and other fields; prices in another currency are converted at the exchange rate. Products not yet in the catalog are added. The list's “Import this template” button also takes the file from this link.

    What won't happen: a template in the “Disabled” state doesn't run on schedule. If another template is already importing at the scheduled time, the run is skipped with the line “Scheduled import canceled…” and waits until next time.

    The catalog must match the Prom file exactly

    Task: products removed from Prom should disappear from the base catalog too.

    What to turn on: the “Delete entries in the base catalog that are not in the imported file” checkbox. If it's grayed out and can't be clicked, your group doesn't have the right to this setting.

    What you get: before adding and updating, Elbuz deletes categories and products that aren't in the file, along with descriptions, photos, attributes, Q&A, and “Related products” links.

    What won't happen: a file in which no product was recognized won't delete products; the same applies separately to categories. Price list rows aren't deleted — they only lose their link to the card. Deletion can't be undone; you bring things back by re-importing the complete file.

    Manually checked cards must not be overwritten

    Task: you finish some cards by hand, and the file updates the rest of the catalog.

    What to turn on: the “Do not update” checkbox in the product card. If you only need to keep the price — “Fixed Price”; only the photos — “Do not update photo”.

    What you get: with “Do not update”, the file doesn't change the card's price, stock, availability, category, Prom additional fields, name, description, meta fields, or photos. With “Fixed Price”, everything except the price is updated. With “Do not update photo”, everything except the photos.

    What won't happen: flags don't protect against full mirror mode — if such a card isn't in the file and the mirror is on, it will be deleted.

    What to do when an import goes wrong

    What Elbuz shows, why, and what to do
    What you seeWhyWhat to do
    “The file is not an XLSX workbook. Prom.ua and Satu.kz export the catalog as .xlsx — the legacy .xls format is not supported.” The import reads only .xlsx; .xls and .csv are rejected before parsing Open the file in Excel and save it as “Excel Workbook (.xlsx)”; the catalog hasn't changed (how Elbuz reads the file)
    “The file could not be sent to the server. It may be too large or the connection was lost. Error code ...” The file didn't reach the server: it hit the size limit or the connection dropped Try again, or provide the file by link instead of uploading it from your computer (limits)
    “Could not read the file:” followed by the error text The workbook is damaged or it's the wrong workbook — parsing failed at the very first step Re-save the file in Excel and run it again; nothing changed in the catalog (break-off)
    “Some data was not saved: the database rejected a query.” The run reached the end, but some queries failed — not all data from the file is in the catalog Run the import again: repeating is safe and doesn't create duplicates (running again)
    “Operation aborted by user!” Someone clicked “Stop”; what changed depends on when it was stopped Check which step the log reached and run it again (break-off)
    “Scheduled import canceled due to another template being imported (data processing conflict).” Two imports don't run at once — another template was importing at that moment Nothing: the run will go next time on schedule. If you need it now, wait and run it manually
    “No file selected for upload.” The “File” tab is open, but no file is selected Select a file, or switch to the link tab and enter the address
    The run finished, but nothing changed in the catalog The cards have “Do not update” set, or the file has no columns with the expected headers Check “Update date” in the grid and the log figures (checking), then the card flags (what a repeat overwrites)

    FAQ

    What happens if the product ID isn't filled in the file?

    Elbuz looks for the product by Prom's second ID, the unique ID. If that's missing too, the product is treated as new, and every repeat import of such a file creates duplicates. A file exported from Prom itself is more reliable. More: how Elbuz recognizes a product.

    Is the product code the ID used for updates?

    No. The product code is your SKU (up to 25 characters); it's written to the card's “SKU” and “MPN” fields. On a repeat import, Elbuz recognizes the product by Prom's internal ID, because sellers sometimes change SKUs.

    I created a new product in Elbuz — will Prom pick it up on export?

    Yes. A new product goes into the export file with its UUID in the product ID column and an empty unique ID — Prom adds it as new. Don't fill in the unique ID by hand. More: export to Prom (XLSX).

    Can I import a Prom catalog in XML instead of XLSX?

    Yes, with XML / YML import. also has a product ID that Prom uses to tell a new product from an existing one: the matching principle is the same, only the file format differs.

    I import two Prom accounts into one catalog — won't the products get mixed up?

    They will, if the IDs match: the template searches the whole catalog, and the card keeps the values from the last run. This template has no “Check uniqueness of records based on this import source” switch. More: two templates for the same product.

    Where to find it and who has access

    Menu
    Directories → Operations → Data import → the “XLSX - prom.ua, satu.kz” template
    Access right
    the “Import” window in “Group permissions”
    Mirror mode
    a separate right for this setting: without it the checkbox is grayed out
    Prepare
    an .xlsx file exported from Prom, or a link to it
    Import window with the list of import templates
    1XLSX - prom.ua, satu.kz template row
    2Add (new template) button
    1. The row of the template of type “XLSX - prom.ua, satu.kz”.
    2. The Add button creates a new import template.

    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