Product Data for Configurable Furniture: Taming the Variant Explosion

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.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Configurable furniture is the extreme case of variant logic: one sofa with 3 sizes, 40 fabrics and 5 legs is 600 variants — maintaining every row by hand does not scale.
  • The option data lives in proprietary manufacturer configurators. There is no GDSN/ETIM/eCl@ss equivalent for the combination and surcharge logic — it is different per brand.
  • Feeds either ship an unusable exploded mega-Excel or a list of options without valid-combination rules.
  • Productbay stores the article once and models options as linked, structured attributes, then generates the exploded variants each channel needs — one compact source of truth instead of 600 rows.

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.

Why does the variant explosion break normal product data?

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:

  • Maintenance: if every combination is its own row, then price, image, availability and description have to be correct hundreds of times per article. Change one fabric surcharge and you touch hundreds of rows.
  • Validity: not every combination exists. A given fabric may not be offered on the large size; a leg may be incompatible with a corner configuration. The valid set is a subset — and the raw data rarely tells you which.
  • Feed shape: manufacturers deliver one of two bad forms — the fully exploded matrix as an unusable mega-Excel, or a flat list of options with no combination rules attached.
  • Pricing logic: the price is rarely fixed. It is a base plus per-option surcharges (fabric group, size, extras), so the "price" of a variant is a calculation, not a column.

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.

Which standard covers configurator data — and where does it stop?

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 layerWhat standards deliverWhere it stops
Master-article exchangeBMEcat / DATANORM carry finished-article recordsNo option axes, no combination logic
ClassificationeCl@ss / ETIM classify the product typeNo made-to-order configurator structure
GTIN / EAN keysIdentify a fixed, finished variantConfigured combinations often have no GTIN
Option / surcharge logicProprietary per-manufacturer configuratorNo cross-brand standard exists at all
Sales contentNot the job of any of the aboveDescriptions, 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.

How does Productbay tame configurable furniture?

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:

  • Model as linked attributes: the configurable article is stored once; its options — size, fabric group, leg, arm, filling — are structured, linked attributes, with the manufacturer's valid-combination and surcharge rules attached. You maintain option axes, not 600 duplicated rows.
  • Import the proprietary options: pull the configurator's option and pricing data from the supplier's Excel, feed or datasheet PDF, and map its codes into your consistent structure — done once per supplier, not per combination.
  • Enrich once, across the set: AI writes descriptions, assigns categories, normalizes fabric and finish attributes and translates via DeepL across the whole option set at once — with a review step before publishing — instead of authoring hundreds of near-identical rows.
  • Generate variants per channel: two-way sync to Shopify and Shopware produces exactly the variant matrix each shop expects, and a marketplace that can't handle full configuration gets a filtered subset — the explosion happens only at export.

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.

Frequently Asked Questions

Let's look at your product data process

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