Importing Your Catalog

Create your Product Catalog and load products in bulk with a CSV import.

Every tenant starts with an empty catalog. You create it once, then keep it current by re-uploading a CSV file whenever your assortment changes.

🛠️ Step-by-Step Setup

1

Create a Catalog

• From the left-hand menu, go to Modules → Product catalog.

• If no catalog exists yet, click Create Catalog.

2

Name and Describe Your Catalog

• Name (required) — how the catalog is referenced across the system.

• Description (optional) — shown alongside the catalog to explain its meaning or context.

• Use Add translation if you need the name/description in additional languages.

Click Create Catalog to save. You'll see a confirmation and land on an empty product list.

3

Prepare Your CSV File

Download and fill in the sample file before uploading.

• Required column: sku — a unique product identifier.

• Optional columns: action, name, category, brand, unit, unit_base_price, unit_cost, and any custom attr_<name> attributes (e.g. attr_color).

• Use upsert in the action column to create or update a row, and delete to remove a product. Leaving action empty behaves like upsert.

• Save the file as UTF-8 CSV.

For the full column reference and a downloadable sample file, see the article below:

Product Catalog

4

Upload the File

• Click Import in the top-right corner of the Product Catalog list.

• Click Click to upload or drag and drop your CSV file (max. 100 MB).

• Click Import.

5

Confirm and Track Progress

The import runs asynchronously and can take up to a few minutes for large files.

• Click View list of imports to track progress, or Continue to go back to the catalog.

• Once finished, review the import report for any rows that failed — valid rows are still imported even if some rows are rejected.

---

🔄 Keeping the Catalog Current

Re-importing does not replace your whole catalog — it works as an upsert by SKU:

• A SKU present in both the existing catalog and the new file is updated — all its metadata is overwritten by the new row. Leaving a column empty clears the previous value for that SKU.

• A SKU present only in the new file is added to the catalog (unless its action is delete, in which case it's simply not added).

• A SKU present in the catalog but absent from the new file stays unchanged — it is only removed by uploading a row for it with action set to delete.

Check your SKUs before uploading. A missing sku column, a missing header row, or a duplicate SKU rejects the entire file. Other issues — like an invalid price or category — only affect the individual row; the rest of the file still imports.

Custom attributes added in a re-import only apply going forward — they're not retroactively attached to transactions that were already processed by a campaign.