Importing and linking products in Bruxel: from file to catalog

By Manuel Mattar4 min read

In short

Bruxel imports your catalog from a CSV or an Excel file, recognizes the key columns without renaming them and shows you a simulation before writing anything. The SKU is the key, so re-importing does not duplicate. The same file can carry variants, related products, cross-sells, up-sells and kits.

The problem it solves

Almost every catalog starts in a spreadsheet or an ERP export, with columns named differently in each system. The note from Excel to PIM explains how to prepare that migration. Here we describe what Bruxel does with the file: how it reads it, what it lets you decide before writing and how it then builds the relationships between products. It all lives in Catalog → Import and on each product page.

How it works in Bruxel

Uploading the file

Bruxel accepts UTF-8 CSV up to 256 MB and Excel (.xlsx) up to 10 MB, with up to 50,000 rows and 512 columns. The file is validated by its content, not just its extension. There is no need to rename columns: the SKU is recognized as sku, ean, gtin, codigo and other names; the name as name, nombre or title. SKU and name are required; brand and category are optional.

If your file has the same data twice, Bruxel always picks the same way: for the name, the enriched one wins over the raw ERP one, and for the category, the most specific wins. The column that loses is not lost.

Review before importing

Before writing anything, the simulation lists every column in your file and tells you what it would do with it:

  • It matches an attribute you already have: it fills itself, with no AI and no credits.
  • It does not exist as an attribute yet: if you leave it ticked, it is created during the import. If the cells carry several comma-separated values, it is created as a multi-select list.
  • It is not useful as an attribute: it tells you why (long text, a different value per product, empty…).

What you do not tick is stored as source data and keeps feeding description generation. An attribute is created with at most 500 values, and the simulation warns you first if a column has more.

What happens to what was already there

The SKU is the key. A new SKU creates the product; an existing one updates name, brand, category and source data; one you had deleted comes back. Attributes someone fixed by hand are not overwritten. The importing your catalog guide has the full column table.

The journey of a load

In the import history, "View journey" shows which stages the products of each load went through: imported, listing generated, quality check, published and delivered. That way you know whether a load got stuck halfway.

Linking products

A link says two products are offered together, in the three types your store understands: related, cross-sell and up-sell. They are added in the "Related" tab of the product page, or from the catalog with "Link with…" to link several against one. The order of each list is the one your customers will see. Links go one way; if you want both, tick "also the other way around".

On import, the related_skus, crosssell_skus and upsell_skus columns become links, and a SKU that does not exist is skipped and counted in the summary. Kits —a product made of others, with their quantity— are built on the product page or from the associated_skus or kit_components columns. You can also ask the AI to suggest links: it picks only among products in your catalog, each suggestion comes with its reason, nothing is linked until you accept it and it only charges if it found something. The related products guide covers it.

Saved views

A view stores your filters and, in the grid, the columns and the language, under a name. It starts private and you can share it with your organization. The saved views guide explains how to change and remove them.

An example

As a hypothetical scenario: a home goods store exports a CSV with 12,000 rows from its ERP, with a department column and a subcategory column, plus color and material columns. In the simulation it sees that color already exists as an attribute, ticks material to create it and leaves out an internal notes column. It imports, checks the load's journey and, with an "Incomplete" view, splits the pending work.

Who it is for

For whoever loads and maintains the catalog: ecommerce, master data or the team that receives supplier files. If suppliers enter data directly, also read the note on supplier onboarding.

What you need to start

A file with a unique SKU per product and its name. That is enough for the first load; the rest is decided in the simulation. The module summary is on Import.

Honest limits

  • Re-importing with fewer columns deletes the source data that is missing.
  • Up to 100 products per link list and per type, and a kit has a single level.
  • The journey's "In the store" stage always says "No data": Bruxel does not know when your store publishes each product. "Delivered" is only known if a system listens to webhook notifications.
  • Up to 100 saved views per organization.

Frequently asked questions

If I re-import the same file, are products duplicated?

No. The SKU is the key: an existing SKU is updated and a new one is created. Careful: the update replaces the source data, so if the second file has fewer columns, the missing ones are lost.

Does the import overwrite what my team fixed by hand?

For attributes, no. Filling an attribute from your file never overwrites a value that was already there; it only fills the gaps.

Can I bring related products over from my store?

Yes. If your file has the related_skus, crosssell_skus or upsell_skus columns, Bruxel turns them into links. A cell with SKUs replaces that list; an empty one changes nothing.

Sources

  1. Comma-separated values (Wikipedia)
  2. Cross-selling (Wikipedia)

About the author

Manuel Mattar

Founder of Bruxel.AI

In 2014 he founded Wolf Sellers, an e-commerce agency in Mexico City, and later Bruxel.AI, the AI-powered PIM.

See all posts by Manuel Mattar

Try it with your catalog

Create your free account and try Bruxel with your own products using the welcome credits.

Keep reading

Importing and linking products in Bruxel: from file to catalog