In the store
How a product’s page would look in your store, built from what your channel would receive from Bruxel.
Video transcript
In this video, you'll see how a product would look in your store and what it still needs.
“In the store” builds a product page with what your channel would receive from Bruxel.
It isn't your store's design: it's the content that would reach it, from the category to the description.
It uses your store channel, or the first one that sends photos; “View as” switches channels.
At the top it tells you whether the product is ready for the channel or how many required fields it's missing.
Each gap says “Missing” and takes you to where you fill it in.
Below, this is how it would show up in a search engine: the title and description, cut where a search engine cuts them.
And “What feeds what” tells you which channel each piece of your catalog goes to.
Search for another product at the top and the page changes in place, without reloading.
“Show where each piece of data comes from” tags each block with the Bruxel data that feeds it.
In the gallery, each piece says whether it travels through the channel: a file only carries images, not the video.
In the next video, you'll find, view and save your organization's reports.
What it shows
Search for a product by SKU or name and you’ll see a generic store page: the category as a breadcrumb, the images, the brand, the name, the description and the details. It isn’t your store’s design —your store sets that—: it’s the content your store would get.
- Whatever shows up empty or generic here arrives that way in your store: the preview uses the same cells as the channel’s file.
- It doesn’t write anything. To fill in what’s missing, each gap links to the tab of the product page where it’s filled.
Which channel is “the store”
It uses the channel you marked as your store in Channels (“Use as the store”). If you haven’t marked one, your first channel that sends photos; if none sends photos, your first channel; and if you don’t have channels yet, the Adobe Commerce template, which carries everything Bruxel has for the product. The screen tells you which one it chose and why.
With “View as” you switch to another channel or to “Everything available”. A dashed block is something that channel doesn’t send, even if the product has it.
Going through many products
The search stays at the top: open a result and the page changes in place, without reloading. Use ↑ ↓ and Enter to move through the results, and “Previous” and “Next” to go to the neighboring result. “View as” and “Show where each piece of data comes from” stay as you left them, and the page address changes so you can share the product you’re looking at.
Where each piece of data comes from
“Show where each piece of data comes from” tags each block with the Bruxel data that feeds it —an attribute, a field of the generated description, the base data— and with the name of the column in the channel’s file.
The gaps
A required field that’s missing says “Missing” and, if you can fill it in, links to where it’s filled. At the top, the screen sums up whether the product is ready for the channel or how many required fields it’s missing: it’s the same count as “Measure” in Channels.
Photos, video and 3D
The gallery shows everything the product has in the library: photos, videos and the 3D object. With “Show where each piece of data comes from”, each piece says whether it’s sent through the channel: the first photo as the main image and the rest as additional images, if the channel asks for them.
What a search engine and an assistant read
Below the page, “How it would show up in a search engine” builds the result with the URL key, meta title and meta description the channel sends, cut where a search engine cuts them: about 60 characters for the title and 160 for the description. If a text runs over, the screen says how many characters it has.
“What an AI assistant reads” (collapsed) shows the product’s assistant context and JSON-LD. If the JSON-LD can’t be read as data, it says so and shows it as it arrives.
What feeds what
Below the product, “What feeds what” shows which channel each field of your catalog goes to, and which ones go nowhere: if you fix one, this is where the change ends up. With one or two channels you see it as cards; with three or more, as a field-by-field table. Suppliers don’t see it.
If you’re a supplier
You see the same page for your products, built from what your client would receive. You don’t see the names of their channels or the columns of their file, and it only takes you to fill in what’s yours.