The part only you can write. Demand spaces, thresholds and your own taxonomy, coded onto every product in scope the same way and re-applied every run.
Three kinds of definition, all of them fields on the product.
The internal schema your team codes by hand today, applied to every product in scope automatically and re-applied every run. Your department, category and segment naming, with no translation layer between our taxonomy and yours.
Better-for-you, premium, value, single serve. You set where the cut falls, and a product moves in or out of the set on the run its facts change.
A demand space that spans three aisles, own brand against national brand, a watchlist. Each one becomes a field on the product, applied the same way every run.
One definition of the set, on the product, that everyone reads the same way.
Run the review on your own segment structure and your own thresholds, against the same product attributes everyone else reads.
Cut the category the way the strategy frames it, including groupings that span aisles and appear in no standard hierarchy.
The definition lives with the product, versions with it, and arrives already applied to every UPC in the feed.
A Fortune 100 CPG was coding its product file by hand, and coverage stalled near 68 percent. A custom catalog now codes the whole file to their own taxonomy every cycle, including the 26,185 products no one had reached. The same mechanism carries customer-defined demand spaces.
Custom is one of three layers. Core is what the product is. Contextual is what the market says about it.
Pick the one that fits where the work happens. The attributes underneath are identical.
Custom attributes are the part only your team can write. Once your definitions sit alongside the rest, every system reads the set the same way.
One consistent reference for product attributes and language, across every system and category.
Thirty minutes on your categories. How the attributes get built, and the questions your team could put to them.