PIM
The PIM that fills itself in
Structured records, typed attributes, families per product type and completeness measured product by product — on the same catalog you already use to generate descriptions.
A traditional PIM hands you the structure and the work of filling it. Bruxel hands you the structure and fills it with AI, with human review before publishing.
What you can do today
Everything on this list is built and deployed. If something isn't here, it's because it doesn't exist yet.
Typed attributes
Define each attribute with its real type — number, text, list, yes/no — and validate values as they're entered. Whatever already came in your import is mapped automatically: you're never charged to extract data you supplied.
Families per product type
Group the attributes that belong to each product type and apply them in one go. AI can also suggest which family a product belongs to.
Measured completeness
A percentage per product and a dashboard for the whole catalog: what's missing, where and how much. And a PDF report with what's missing by brand and category, to send to people who don't use Bruxel.
AI fill, in bulk
Select products and have AI complete the empty attributes. It runs in the background in batches, and you pay for what gets filled.
Review before publishing
Draft → review → published states, optional per organization, so nothing reaches your channels without someone approving it.
History and one-click rollback
Two histories: the AI-written text, and the listing itself —fields, attributes, categories and family—. Every version records who made it, with differences between versions and one-click rollback.
Product images
Upload photos into the same catalog: drop them onto a product page and they upload and get assigned in one go. They come out in your export with the columns Adobe Commerce expects, and AI can write their alt text in four languages. We store them: a 30-day trash, recoverable previous versions, and you can take them all with you whenever. Serving them to your shoppers is your store's job.
AI photography: the Studio
Create fictional models once and reuse them across the catalog: the photo comes from your real photos, not from a description. The model holds the product, or wears it if you sell clothing, in the scene and with the expression you ask for. It also makes the studio main image and five-second video. Every image ships with the generated-content metadata Amazon and Google ask for.
Variants
Size, colour and format as variants of one product, along the axes you declare. The parent gives context to its children, so content comes out consistent across them instead of repeated.
Outgoing webhooks
Your system finds out the moment a product changes, signed so you can verify the notice is ours. If your endpoint stops responding it disables itself and we tell you — without penalising you for an outage that isn't yours.
Your team, on the same listing
Comments with mentions to discuss a product where the product is, and assigned tasks with a date and a note to split the work: everyone opens their own queue and closes what they finish, without leaving the catalog.
Your filters, saved by name
Save the search, filters and columns you use every day under a name, and come back to them in one click. Share them with your organization so your team opens exactly the same screen, and the link you keep in your bookmarks still works just as before.
The sheet in sections, by team
Group attributes into sections —Master data, SAP, Merch, Ecomm— and each team finds its part of the sheet and of the grid without hunting through forty fields. Groups also travel in the public API and in the definitions CSV.
Ready for each channel, product by product
Mark which columns are required for each destination and the catalog tells you how many products come out complete, which ones do not and what they are missing. Export only the ones that are ready, or download the list of the ones that are not.
Related and cross-sell products, both ways
Your Adobe Commerce export already carries `related_skus` and `crosssell_skus`: Bruxel reads them on import, lets you curate them product by product —in the order your customers will see— and returns them in each channel's CSV. A SKU your export left out is skipped and counted for you, instead of breaking the file. And if your catalog does not carry them, AI proposes them from your own products, with the reason for each choice: nothing is linked until you accept it.
Reports to view and download
Thirty-four reports in eight families —supplier uploads, catalog changes, channels, content, team, images, audit log and usage— with a period, filters by supplier, brand and status, to view on screen or download as CSV. Save your favorites with their filters: “last month” recalculates itself every month.
Flows: where each product is
Lay out the stages of your operation —supplier onboarding, master data, your ERP, the store— and each product shows its journey: which step it’s on, what was sent to each system and what came back. A board per flow with stuck and late products, alerts in the bell, tasks assigned on their own when a product reaches a step, and webhooks for your middleware. Suppliers only see their milestones.
What's next — and why we're asking
None of this exists yet. The order we build it in depends on what the people already using Bruxel need, so if something here matters to you, tell us: it counts toward the decision.
- Export straight to ShopifyOn the roadmapA column preset for the CSV Shopify expects, with its importer's rules. Today you export in Adobe Commerce or generic format.
- Pull in your store's imagesOn the roadmapLet the photos already living in your store flow into the Bruxel catalog, so you don't upload them twice and can use them in the Studio.
Tell us what you're missing
Leave your email and we'll let you know when we ship what's next. No newsletters.