Bruxel modules

Every product photo in the format each marketplace asks for

You pick the destination and the products, test with five, and Bruxel prepares the rest in the background. Your original photos stay as you uploaded them.

What it solves

Every marketplace wants its images its own way, and adapting them by hand product by product eats up weeks. Here you define the formats once and Bruxel keeps them up to date: if a photo or a format changes, it regenerates only what changed.

  • Templates for Amazon, Mercado Libre, Walmart México, Liverpool, Shopify, Google Merchant Center, Meta or a generic square, with formats you can edit.
  • Your brand rule, written in your own words (“never crop the sole”), decides the crop, the margin and the background when the channel doesn't set them.
  • What Bruxel can't guarantee goes to “To review” with its reason, and doesn't go out to any destination until someone approves it.

What it looks like

Bruxel's Images by destination screen with one card per demo destination and its images ready, to review, non-compliant and in progress.
Destinations and their progress, in Media → Images by destination. · Demo data

Who it is for

  • Brands and retailers that sell the same catalog on several marketplaces.
  • Visual content teams that crop and rename photos by hand today.
  • Anyone who delivers images in a channel's CSV, in a ZIP or through the API.

What it needs

  • Photos of your products in the library: Bruxel doesn't invent pixels, and a photo smaller than the format's minimum doesn't comply.
  • Generating a destination's images costs no credits. Library storage includes a free allowance and grows in monthly blocks.
  • Creating destinations and generating takes an operator or an administrator; approving or rejecting what is to review, an editor.

Its guides

Read more: Images by destination in Bruxel: one photo, each marketplace's format

Try it with your own catalog.

Every product photo in the format each marketplace asks for · Bruxel