One article, hundreds of sellable combinations: why configurable furniture breaks a normal variant setup, why no standard carries the option logic, and how to keep one compact source of truth.
Take one sofa. It comes in three sizes, forty upholstery fabrics and five leg options. That single article is already six hundred sellable variants — and any real furniture range has dozens of such articles, plus corner combinations, arm choices and filling grades that push the number higher still. Configurable furniture is where the variant logic every retailer knows stops being an inconvenience and becomes a genuine data problem.
Product data for configurable furniture is the extreme case of variant logic: a handful of option axes multiply into hundreds or thousands of combinations per article. This is a specialised corner of the broader furniture retail data challenge — and it needs its own answer, because the tools that handle a T-shirt in five sizes buckle at a made-to-order sofa.
The maths is unforgiving. Options don't add, they multiply: 3 sizes times 40 fabrics times 5 legs is 600 combinations from one article. Add an arm choice and a filling grade and you are into the thousands. Two things break at that scale:
Maintaining that by hand does not scale — it is exactly the multi-supplier problem of consolidating and normalizing data, but with the row count multiplied by every option axis.
This is the uncomfortable part: essentially none does. The classification and exchange standards that help elsewhere in retail were built for finished, catalog-style articles, not for made-to-order combinatorics.
| Data layer | What standards deliver | Where it stops |
|---|---|---|
| Master-article exchange | BMEcat / DATANORM carry finished-article records | No option axes, no combination logic |
| Classification | eCl@ss / ETIM classify the product type | No made-to-order configurator structure |
| GTIN / EAN keys | Identify a fixed, finished variant | Configured combinations often have no GTIN |
| Option / surcharge logic | Proprietary per-manufacturer configurator | No cross-brand standard exists at all |
| Sales content | Not the job of any of the above | Descriptions, filter attributes, imagery absent |
So the option logic — which combinations are valid, which surcharge applies, which fabric group a fabric belongs to — lives in each manufacturer's own configurator, in its own proprietary format. There is no GDSN-style pool you can subscribe to. That means the structure has to be captured and mapped per supplier, and that mapping is precisely where the manual effort concentrates today.
The core idea is to stop fighting the explosion and instead model the article the way it actually is — one product with a set of option axes — and let the exploded form be generated only where a channel demands it. That is what Productbay is built for:
The result is a single compact source of truth that stays editable, instead of an explosion you re-maintain everywhere. For the full furniture picture — from flat-pack to made-to-order — see the furniture retail overview. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs of every size.
600 variants from one sofa, option logic locked in a manufacturer's configurator, no standard to lean on — configurable furniture is the hardest variant case there is. See how Productbay models it as linked attributes and publishes clean products in a 30-minute walkthrough.
Get started