- Bruxel.AI Blog
- Use case: one catalog on three marketplaces, with each one's photos
Use case: one catalog on three marketplaces, with each one's photos
By Manuel Mattar4 min read
In short
In this example, the brand sets up one channel per marketplace, with templates for Walmart México and Mercado Libre and a generic one for Amazon, and lets Bruxel prepare from its original photos the image each destination asks for. It reviews doubtful images in a queue and downloads each ready file, without rebuilding the catalog three times.
This is an example scenario, not a customer. The numbers describe the hypothetical situation; they are not measured results.
The situation
A footwear brand has 1,200 products with studio photos: gray background, the shoe in profile, some with a model. It wants to sell on Amazon, Mercado Libre and Walmart México. Each marketplace asks for its own file with its own column names, its own length limits and its photos at another size, with another background and another file name.
Until now, a designer cropped photos by hand for each marketplace and someone on the team copied the catalog into three different sheets. Every photo or text change had to be repeated three times.
What the team does in Bruxel, step by step
1. One channel per marketplace
In Channels → Channels & templates, “Create from template” offers Walmart México and Mercado Libre. Each template creates a channel with that marketplace's column names, order and limits, and links each column to what the catalog already has: name, brand, description, keywords or images. The screen says which official source the template came from and on what date it was read.
What Bruxel does not know where to get —the barcode, the condition or the marketplace category— starts unlinked. The team links it in “Edit columns” to a product field, an attribute or a column from its file.
There is no column template for Amazon yet. The team creates a generic channel and names the columns the way the template downloaded from its seller account asks for them.
2. The values each marketplace understands
The color “Black” may need to come out differently in each file. In the channel's column editor, “Channel values” lets you write the destination's value next to each option. If the marketplace only accepts its own list, “Strict” makes an option without a value count as incomplete instead of sending something the destination would reject.
3. Each destination's photos
In Media → Images by destination, “New destination” opens a three-step assistant:
- Where to? The team picks Amazon, then Mercado Libre, then Walmart México, and reviews the formats each one asks for: size, background, how many images it takes and whether it is required.
- Which products? All the ones with a photo. The assistant counts how many have none and takes you to upload them.
- Test and generate. “Test with 5” shows the before and after of five random products. Once convinced, “Generate” prepares the rest in the background.
The original photos do not change. Before generating, in Media → Brand rule the team writes how it wants its photos, for example “the shoe always whole, never crop the sole”, and since some photos include a model, it marks that in the rule. The channel rules and the brand is the style: if the marketplace requires a white background, the marketplace wins.
4. Review the doubtful ones
When Bruxel cannot guarantee something on its own —the product touches the edge, an unexpected person appears—, the image is left to review with the reason and does not go to any destination until someone approves it. In Media → To review the team approves or rejects, also with the keyboard. If a framing came out wrong, it is fixed with “Adjust framing” and applies to every destination.
5. Measure and download
In the channel list, “Measure” says how many products would come out complete in each one and which columns are most often missing, and “Download gaps (CSV)” downloads the list to share out. A title longer than Mercado Libre's 60-character limit is not trimmed: the product is not ready until it is fixed. Then, in Channels → Downloads, the team downloads each channel's CSV, with the channel image instead of the original. With Media → Packages, a ZIP per channel brings the images with the name each format asks for.
What gets solved
- One catalog and one photo library for three destinations.
- Each file comes out with its marketplace's columns, limits and values.
- Each destination's photos come from the originals and stay up to date: if a photo, a format or the rule changes, Bruxel regenerates only what changed.
What does not get solved
- Bruxel does not upload anything to the marketplace and does not promise the marketplace will accept the file or the image: it promises they meet what the template says.
- Price, inventory, shipping, warranty, tax data and each category's attributes are entered on the marketplace.
- Amazon uses a generic channel: the team names the columns from its seller template.
- A photo smaller than the minimum does not comply: Bruxel does not invent pixels.
- A destination with thousands of products takes hours, because the queue is shared between organizations.
To go deeper, read the guides on images by destination, marketplace templates and exporting, or the Channels and Images by destination pages.
Frequently asked questions
Does Bruxel have a column template for Amazon?
Not yet. Amazon's columns can only be verified with the template downloaded from a seller account, so you create a generic channel with that file's column names. Amazon's image formats are, however, among the destinations in Images by destination.
Does generating the images for each destination cost credits?
No. Bruxel frames, changes the background, adjusts the canvas, the file size and the name with its own engine and a model that runs inside Bruxel. Test with 5 does not charge or save anything either.
Does Bruxel upload the products to the marketplace?
No. Bruxel gets each channel's file and images ready, plus the API to read them. Price, inventory, shipping, warranty, tax data and each category's attributes are entered on the marketplace.
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
· 3 min read
Use case: syncing content with Adobe Commerce without editing the store by hand
A step-by-step example: an Adobe Commerce store sends its products to Bruxel and gets the published descriptions back, without copying anything into Magento.
· 4 min read
Channels and marketplace templates in Bruxel: one ready file per destination
How Bruxel channels work: columns, values per destination, Walmart Mexico and Mercado Libre templates, what each product is missing, and signed feeds.
· 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.