Configure Good–Better–Best product architecture

configure good–better–best product architecture business goal create a clear value ladder that maintains intended price separation between comparable products, protecting customer choice and preventing unintended price overlap prerequisites open price management docid\ rs0z8lfkdpage86wko0qc and select the category or top level where the product architecture (pa) should apply confirm that the products to be compared are in scope and have accurate current price, cost, brand, and product class data have permission to configure product architecture (pa) and category level pricing settings align the intended good–better–best positioning and acceptable price gaps with category stakeholders before making changes step by step instructions step 1 select the architecture scope on the 'price management/category top level tab product architecture' screen, use the category tree to select the category or retain top level for an assortment wide setup, then open the product architecture tab business reason the selected scope determines which products inherit the product architecture (pa) and where category specific exceptions can be managed select the architecture scope step 2 open the gbb architecture on the 'price management/category top level tab product architecture' screen, click gbb to open the good–better–best configuration instead of own brand, size architecture, or pricing levels business reason product architecture (pa) is a value ladder enforced by min gap and optional max spread from an anchor level; when enabled, it overrides generic price rules step 3 create value ladder groups click add group in the gbb workspace and create the groups that represent the planned ladder, such as good, better, and best; repeat for each required tier business reason grouping comparable products into explicit levels gives shoppers meaningful price choices and gives the optimization algorithm a structure for preserving their relative position step 4 assign comparable products to each group select products from unassigned products and place each product in its appropriate gbb group; use the search fields and product details such as current price, cost, brand, and supplier to validate the assignment business reason only comparable alternatives should share a ladder, so the enforced gaps reflect a real customer choice rather than unrelated products step 5 set gap exceptions where needed use set exception for a group without local settings, or edit exception for a group with existing settings, and define the min gap and, where appropriate, max spread from the anchor level business reason min gap protects visible separation between levels, while optional max spread prevents the premium end from becoming disproportionately distant; exceptions let you tailor the ladder to a category’s price points step 6 review coverage and maintain the configuration review the grouped and unassigned products lists, resolve products that belong in the ladder, and revisit exceptions after material assortment, cost, or reference price changes business reason complete, current group coverage prevents comparable products from being priced outside the intended value ladder during optimization you're done when gbb is selected in the product architecture tab for the intended category or top level comparable products appear in good, better, and best groups rather than remaining in unassigned products each relevant group displays the intended min gap, with an optional max spread where configured future new price proposals for grouped products follow the product architecture (pa) instead of generic price rules pro tips start with a small, highly comparable set of products; expand coverage after the ladder produces commercially sensible new prices use exceptions sparingly product architecture (pa) overrides generic price rules, so overly broad settings can constrain the optimization algorithm more than intended