- Bruxel.AI Blog
- The catalog in Bruxel: attributes, families, categories and variants
The catalog in Bruxel: attributes, families, categories and variants
By Manuel Mattar4 min read
In short
In Bruxel, the catalog is built from typed attributes, families that say what each product type needs, your own category tree and variants that hang from a parent. With that, Bruxel works out what each product is missing, and the grid lets you fix dozens of values in one sitting.
The problem it solves
A catalog grows in layers: first a list of SKUs, then columns someone adds, then sizes and colors entered as separate products. A year later nobody knows what data each product should have or what it is missing. The note on product attributes explains why that matters; here we describe how Bruxel organizes it, piece by piece, from the Catalog area of the menu.
How it works in Bruxel
Typed attributes
An attribute is a structured piece of data: color, size, material. Bruxel has seven types —list, multi-select list, Yes/No, free text, number, date and measure (a number with a fixed unit, such as 250 ml)— and the type decides how it is entered and validated. A few pieces that save work:
- Groups: split the product page into sections (for example, master data, ERP, ecommerce) so teams can share the work.
- Shared value lists: when two attributes use the same values, they are written once and a change to the list reaches all of them.
- Value rules: convert a unit, replace a text, forbid or require a pattern. A "1.7 OZ" can come in as "50 ml" with the factor you confirm; Bruxel does not ship a conversion table.
- Capture rules: when a value is requested, when it is hidden in the supplier form and when the system sets it from another attribute, the category or the brand.
If your attributes already live in a spreadsheet, "Import attributes (CSV)" shows you what it would do before touching anything, and nothing is deleted.
Families: what each product type needs
A family groups the attributes of a product type and marks which ones are required. It is what lets Bruxel know what a product page is missing. With that it computes completeness, up to 100 points: 25 for brand and category, 25 for the required attributes of its family, 35 for languages with a published description and 15 for the main image.
Your own category tree
The tree allows up to 6 levels and 5,000 categories, and a product can sit in several. You build it by hand or with AI: from a photo of a store's category menu or from your site's URL (15 credits each), and "Organize with AI" to reorder what you already have (10 credits). Proposals create nothing until you accept them. "Auto-categorize with AI" picks the most specific category in your tree for each product, never invents one and costs 5 credits per product it places.
Each category can carry a default family that its subcategories inherit: a product without a family gets it when it enters there. A family already set is never changed, and for products already in place there is "Apply", a thousand at a time.
The grid
The grid puts products in rows and attributes in columns, up to 40 at a time. You paste a block from Excel or Google Sheets and each text is read according to its column's type; anything that does not match an option is flagged, not invented. You save up to 500 cells in one go: if one fails, none is saved and the screen tells you why. Every save lands in the history of each product page, from which an administrator can go back to an earlier version.
Variants
Each size or color is a product with its own SKU, hanging from a parent. The axes —the attributes that tell the children apart— are declared on the parent: lists or Yes/No only, up to four. They are linked with the parent_sku column when importing or from the product page. The variants guide has the details and the note on product variants explains how to model them.
An example
Suppose, as a hypothetical example, a tool brand with 3,000 products in a single spreadsheet. First it defines three families (power tools, hand tools, consumables) and marks what is required in each. Then it builds the tree from its site's URL and gives each branch its default family. On import, every product that lands in a branch inherits its family, and completeness starts saying what is missing. With a saved "Incomplete" view in the grid, the team fills the gaps block by block.
Who it is for
For whoever runs the catalog: the ecommerce, master data or category management team. Creating categories and changing default families takes the Operator role or higher; assigning categories and editing in the grid, Editor or higher.
What you need to start
Your catalog loaded (the attributes and families guide and the import guide explain it), an idea of your product types to build the families and, if you will use AI for the tree, credits. Everything else is configured in Bruxel. The module summary is on Catalog.
Honest limits
- The grid edits attributes; not name, brand, category or content.
- The tree is not uploaded from a file: it is built by hand or with AI.
- The number next to each category counts only its own products, not those of its subcategories.
- A category's codes for your channels cannot be edited on the categories screen yet.
- The product history does not bring back images or files: they have their own lifecycle.
Frequently asked questions
What happens if a product has no family?
Bruxel has nothing to compare its required attributes against. For completeness, the 25 attribute points are spread across all the attributes in your catalog. The practical fix is to give each branch of the tree a default family.
Can I use the grid to edit the name or the description?
No. The grid edits attributes only. The name, brand, category and generated content are edited on each product page.
Do variants cost less when generating their description?
No. The child receives the parent's description as a reference so it sounds the same, but each variant is generated and charged like any product. If you want a single description, generate the parent and export only that one.
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
· 4 min read
Importing and linking products in Bruxel: from file to catalog
How Bruxel imports your catalog from CSV or Excel, what it does with each column, how it builds related products, cross-sells and kits, and what views do.
· 4 min read
Source reconciliation: when your ERP and your spec sheet disagree
How Bruxel keeps what each system says about the same field, shows you where they disagree and lets you decide which one wins, without one overwriting another.
· 4 min read
Versioned files: datasheets, certificates and packages in Bruxel
How Bruxel stores each product's documents: file types, versions with approval, virus scanning, expiry dates and ZIP packages with an index of every file.