Images by destination
Every marketplace wants its photos its own way: size, aspect ratio, background, weight and name. In “Media” → “Images by destination” you choose where to and which products, test with 5, and Bruxel prepares the rest from your photos, shows you the progress and lets you know when it's done.
What it is
Your photos stay as you uploaded them. From them, Bruxel builds one image for each format the destination asks for: it frames it, changes the background if the format asks for it, brings it to the required canvas and weight, and gives it the expected name. It does this with its own engine and a model that runs inside Bruxel to find the product in the photo: generating doesn't use credits.
A destination is a marketplace or a store: Amazon, Mercado Libre, your online store… Under the hood it's an export channel, so it also shows up in Channels → “Channels & templates”, where the file's columns are set. Everything about images lives in the “Media” area of the menu: Images by destination, To review, Library, Brand rule and The Studio.
It belongs to the retailer: the supplier doesn't see it. Suppliers still see in “Requirements” what they can fix, such as uploading a larger photo; generating, reviewing and approving is up to you.
The path, in three steps
In Media → “Images by destination” you see one card per destination with its ready, to review, not compliant and in-progress images. “New destination” —or “Create your first destination”, if you don't have one yet— opens the assistant:
- Where to? You choose the marketplace and check the formats it asks for.
- Which products? All the ones with a photo, the ones a search finds, or a selection.
- Test and generate: “Test with 5” shows you the before and after, and “Generate” prepares the rest.
On the card of a destination you already have, “Open” takes you to the same assistant with that destination chosen. The three steps belong to whoever operates the account (an operator or an admin); everyone else sees the progress and what's waiting for review.
Step 1: Where to?
You choose between Amazon, Mercado Libre, Walmart México, Liverpool, Shopify, Google Merchant Center, Meta (Facebook and Instagram) or a generic square. If you already have it as a destination, the assistant goes on with that one and doesn't create another.
If you don't, before creating anything it shows you how it will look: the marketplace's name, the formats it asks for and the columns of its export file (Walmart México and Mercado Libre bring their own; the rest start with generic columns you adjust in Channels). Nothing is created until you choose “Create the destination”.
Formats show up as cards that read on their own: each one's name, size and background, how many images it takes and whether it's required or optional. “Edit formats” opens the full editor, explained in the next section.
Formats, in detail
With “Edit formats” you adjust each format from the template, or build your own. A destination allows up to 20 formats, and each one applies to all your products or only to the families you choose.
| What you define | What it does |
|---|---|
| Which images it takes | The main one, the additional ones or the color swatch, and how many at most. |
| Canvas | An exact size, or the long side without changing the aspect ratio. |
| How it fits | Always whole, always cropped, or whatever your brand rule says. |
| Background | Pure white, the photo's own, transparent, a color, or whatever your brand says. You can also forbid a digital background. |
| Margin or fill | An exact margin, or how much of the canvas the product takes up. |
| File | JPEG, PNG or WebP, with its quality, its maximum weight and its DPI. |
| File name | It carries the SKU, or an attribute that identifies the product such as its EAN, and the view code: MAIN, PT01…, SWCH. |
| Counts toward “ready” | A product without an image that meets this format counts as incomplete in the channel, just like a required column. |
Before anything is generated, required formats are already checked against each photo's dimensions: if one is smaller than the format's minimum, the product isn't ready for the channel, and you see it in “Measure” and in the missing list. Bruxel doesn't make up pixels.
Step 2: Which products?
You choose “All the ones with a photo”, “The ones a search finds” (by name or SKU, the same search as Products) or “A selection or a finer filter”. The selection is made in Catalog → Products: you tick the boxes or filter the list and use “Channel images” in the bar.
The assistant counts how many have a photo and how many don't; only the ones with a photo are generated. For the rest, “Upload photos to the library” or the link to each product page takes you to upload them.
Step 3: test with 5 and generate
“Test with 5” takes five random products that have a photo and shows you the before and after. Previews aren't saved or charged; “Test with another 5” picks five more.
Once you're happy, “Generate” and “Yes, generate” put the chosen products on their way. Whatever was already up to date isn't generated again. Bruxel works in the background: you can close the tab.
Progress and the notice
While they're being generated, the request shows up in the progress panel as “Channel images”, and the destination's card counts the ones still in progress. While a whole destination is being generated it can't be requested again: the button stays on “Generating…” and, if you try from another screen, Bruxel tells you they're already being generated.
When it's done, a notice reaches the bell, “A channel's images are done”, with how many ended up ready, to review and not compliant. No email is sent: a batch usually takes minutes and you're normally still in Bruxel.
A destination with thousands of products takes hours, not minutes, because the queue is shared between organizations.
Review and fix
When Bruxel can't guarantee something on its own —the product touches the edge, there are several similar objects, a person shows up who wasn't expected, or it couldn't find the product—, the image goes to review, with the reason. An image to review isn't sent to any destination until someone approves it; a rejected one isn't sent either.
In Media → “To review” is the queue for all your destinations: you approve or reject one by one, or the ones you check. The decision belongs to that image: if it's generated again, it has to be decided again. Approving and rejecting is for an editor; whoever has access limited to part of the catalog decides from each product page. Each image is shown next to your original photo, and you can filter the queue by destination. With the keyboard, A approves the focused image, R rejects it, and J/K or the arrow keys move to the next or previous one.
If your organization has “Fix with AI”, it only shows up when some image needs it —it doesn't comply, or it went to review for something the AI fixes—, with the options already chosen and what it costs in credits before charging. It's the only paid part of images by destination, and the “Fix channel images with AI” guide explains it.
Your brand rule
In Media → “Brand rule” you write in your own words how your brand wants its photos, for example “the shoe always whole, never crop the sole”. Bruxel reads it once with AI and shows you what it understood: how much can be cropped, the space around, the background when the channel doesn't set one, what to do if the aspect ratio doesn't match, and what happens with people. You fix whatever needs fixing and save: what you save is what rules, the same across all your photos.
There's one rule for the whole organization and, if a family needs something different, one of its own. A product uses its family's rule; if there's none, the organization's; and if there's none at all, the default: the product always whole, no heads cropped. The channel is the law and your brand is the style: if your rule says “keep the background” and the channel requires white, the channel wins.
Before saving, the preview tries the rule on a product and a channel. It isn't saved or published.
People and captions
If your photos have a model, check it in the rule (“My photos include people”): that way a person in the photo doesn't send it to review. And choose what happens with the head:
- Keep the head, the default: if cropping is needed, the crop moves just enough for the head to fit; if it doesn't fit, the whole photo is used or the image goes to review.
- The head may be cropped: the crop doesn't move for it.
- The head must be removed, for photos of minors: before composing, Bruxel removes the top of the photo, below the chin. If it can't find the face, it cuts at a conservative height and the image goes to review.
A format can also carry a caption: a short text inside the image. Bruxel draws it on a band that doesn't cover the product, with a free typeface that has accents and special letters, and picks the color by contrast. If it doesn't fit, if it has a character the typeface lacks (an emoji) or if it covers the product, the image goes to review. Templates don't include a caption and the formats screen doesn't edit it: if one of your channels asks for one, write to us.
Framing
Bruxel works out on its own where the product is in each photo. If it got it wrong, fix it with “Adjust framing” on the product page, “Images” tab, or in the library when you open the photo: move the product box and the focal point. With the keyboard, the arrows move 1 % and with Shift 5 %. The correction overrides what Bruxel worked out, applies to all your destinations and leaves that photo's images out of date. Correcting is for an editor.
On a product page
The product page, “Images” tab, tells you in one line how that product's images are doing in each destination and takes you to the “Media” area for everything else. Framing is corrected right there.
Up to date
Once a product has images in a channel, Bruxel checks it every 6 hours: if a photo, its version, a format, the rule or the framing changed, it regenerates only what changed. A product you never asked images for in a channel isn't generated on its own.
Where they go
A ready image is sent, or one to review that someone approved. Every output reads the same rule:
| Where | What goes out |
|---|---|
| The channel's CSV | The channel image instead of the original, if the channel has formats. If it isn't ready, the cell stays empty: never the original, which is exactly what the channel would reject. |
| The ZIP per channel | In “File packages”, if your organization has them, a template with “Channel images (ZIP)” brings the ready ones with the name each format asks for. |
| The public API | GET /v1/products/:id/channels/:slug/images, with the channels:read permission: each image with its status and, if it goes out, its URL. |
| In the store | The channel image; if it doesn't go out, the original with the reason. |
| The “Images by channel” report | In Reports: each generated image, whether it goes out and, if not, why. |
Limits
- From one product, a channel takes up to 60 photos and 200 channel images at once; if it goes over, lower “How many at most” in its formats.
- A photo smaller than the format's minimum doesn't comply. Between the minimum and the recommended size, or if it has to be enlarged to fill the canvas, it's enlarged and goes to review.
- A photo quarantined by the virus scan isn't processed, nor is one over 80 megapixels.
- Up to 3 single-product requests can be in progress per organization; a destination's batches go through their own queue and don't block them.