- Bruxel.AI Blog
- Channels and marketplace templates in Bruxel: one ready file per destination
Channels and marketplace templates in Bruxel: one ready file per destination
By Manuel Mattar4 min read
In short
A Bruxel channel stores how a destination wants its data: column names, order, language, separator, required columns and its own values. You set it up once, from scratch or from an Adobe Commerce, Walmart Mexico or Mercado Libre template, and every export comes out ready, with a count of which products are complete.
The problem: the same catalog, ten different files
Your store wants a CSV with some column names; the marketplace, others; your ERP wants codes instead of names and a different separator for lists. Every time you export, someone renames columns, reorders them, translates "Rojo" into "Red" and deletes the rows the destination is going to reject. The article on product feeds explains why it pays to stop rebuilding the file; here we describe how Bruxel does it with the Channels module.
How it works in Bruxel, step by step
1. Create the channel
In Channels → "Channels & templates" you create a channel in three ways:
- From Downloads, saving the column selection you already built with "Save as channel".
- From a template: Adobe Commerce (every column, with the names that CSV already sets), Generic (name, brand, category and content), Walmart Mexico or Mercado Libre.
- By duplicating an existing channel, with its columns, required columns, language and separator.
The channel stores each column's name, the order, the language and the multi-select separator (pipe, comma or semicolon).
2. Marketplace templates
The Walmart Mexico template creates 14 columns from its item schema, with "sku" as the key. The Mercado Libre one creates title, brand, model, barcode, condition, category and description, with "SELLER_SKU" as the key, a 60-character cap on the title and the description without tags. Each column is linked to the first thing your catalog already has; what Bruxel does not know where to get —the barcode, the country of origin, the marketplace category— starts unlinked, with an empty cell, and the channel card says how many remain. The marketplace templates guide explains how to link them.
A length cap does not trim the text: if the title goes over 60 characters, the product is not ready for that channel and Bruxel tells you how long it is.
3. Required columns, complete rows and values per channel
In each channel you mark which columns are required. With "Export only complete rows", the CSV, the API and the feed leave out the products missing any of them; this matters for destinations that erase the data when the cell arrives empty, as Shopify does.
In addition:
- Channel values: a column that comes from a list can write a different value per option. "Rojo" comes out as "Red" in one file and as "001" in another, without changing the option in Bruxel. With "Strict", an option without a value leaves the product incomplete instead of sending something the destination will reject.
- A value of its own per channel: a free-text attribute can have a different text for each channel, with the master value as fallback.
- Codes: if your ERP wants the category or the brand by code, a column can emit it.
4. Know what each product is missing
On the product page, the "Channels" section says whether the product comes out complete in each channel or which required columns it is missing, with a link to where it gets fixed. In the channel list, "Measure" walks the catalog and says how many products would come out complete, and the missing-items CSV download gives you the list of incomplete products with what each one lacks.
5. See the product page as your store would
"In the store", in the Catalog menu, builds a generic product page with what your channel would receive: images, name, description, details and how it would appear in a search engine. What comes out empty here arrives empty there. The In the store guide explains how to read it.
6. Deliver the file
From Channels → Downloads you get the channel's CSV. If a tool can only request an address, an administrator creates a signed feed: a URL that serves the CSV without signing in, expires within the period you choose —from 30 days to a year— and can be revoked instantly. The export options are in the export guide.
Who it is for
A hypothetical example: a home goods brand that sells in its Adobe Commerce store, on Mercado Libre and on Walmart Mexico, and sends a file to its ERP. With one channel per destination, the team fixes the catalog once and each file comes out with its names, its values and only complete rows.
It serves anyone who publishes the same catalog in more than one place.
What you need to get started
- Your catalog in Bruxel, with published content in each channel's language.
- The official sheet for each destination, to compare names and values.
- Knowing which columns each destination requires and which ones erase data if they arrive empty.
Honest limits
- Price, inventory, shipping, warranty, tax data and each marketplace category's own attributes do not come from Bruxel: they are entered in the marketplace.
- Bruxel does not promise that the marketplace accepts the file: it promises that the content meets the template.
- Amazon does not have a template yet.
- A CSV only carries images: video and the 3D object do not travel through a channel, only through the public API.
- A product without published content in the channel's language does not come out in that file.
To see the whole module, open the Channels page.
Frequently asked questions
Does exporting cost credits?
No. The cost is in generating. A description that has already been generated can be exported as many times as you want, with the columns you want.
Does Bruxel guarantee that the marketplace accepts the file?
No. It promises that the content meets what the template says, and the screen shows which official source it came from and when it was read. If the marketplace changes its sheet, compare it with the channel.
Is there an Amazon template?
Not yet: its columns can only be verified with the template downloaded from a seller account. For Amazon or another destination you create a generic channel and name the columns as its file requires.
Can I send a different text to each channel?
Yes. A free-text attribute marked as a value per channel lets you write a text of its own for each channel; until it has one, the channel uses the master value.
Sources
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 MattarTry it with your catalog
Create your free account and try Bruxel with your own products using the welcome credits.
Keep reading
· 4 min read
Images by destination in Bruxel: one photo, each marketplace's format
How Bruxel prepares your product photos for each marketplace: size, background, weight and file name, with a three-step assistant and a review queue.
· 4 min read
Bruxel integrations: public API, webhooks, Adobe Commerce and custom domain
How Bruxel connects with your systems: permission-based API keys, signed webhooks, connected systems, the Adobe Commerce module and your own domain.
· 4 min read
AI content in Bruxel: brand voice, generating and translating
How Bruxel generates product content: the brand voice you set, what generating one or in batch costs, how to fix a wrong fact and how it translates.