How Manufacturers Should Manage Product Specifications Across a Range
A practical method for keeping furniture dimensions, materials, variants and commercial specifications correct as a range changes.
A corrected seat depth is easy to change in one spreadsheet. The difficult part is knowing which variants, assets, retailer listings and sales documents still contain the old number.
Managing specifications across a range is less about checking every SKU one by one. It is about storing shared facts once, defining real variant differences and giving every change a route through the business.
Separate shared facts from variant facts
A frame may share construction, care and overall depth across every fabric. A leg finish, orientation or size may change dimensions, price or imagery.
Model the specification at the level where the fact is true:
- Product-level facts apply across the parent product.
- Variant-level facts apply only to the sellable configuration.
- Material facts belong to the reusable fabric or finish record.
- Channel values describe how a destination needs the fact presented.
This reduces the chance of correcting one row while leaving 40 copies wrong.
Decide the variant axes early
Product development should decide which choices create a sellable variant before the range reaches ecommerce.
Do not assume every design attribute should become a channel option. Shopify currently allows up to 2,048 variants but only three options per product. A sofa described internally by size, fabric grade, fabric color, arm style and leg finish will need a deliberate storefront structure.
That is a commercial and merchandising choice, not a last-minute import fix.
Use stable identifiers
Give every product and sellable variant a stable internal SKU. Keep other identifiers in their own fields rather than substituting one for another.
The SKU should join the product to its price, assets, stock and channel records. Changing or reusing it casually makes updates harder to distinguish from new products.
If you use GTINs, maintain a separate policy based on GS1's current management rules. GS1's non-reuse rule means a GTIN assigned to one trade item should not later be reassigned to another.
Do not assume every corrected description or measurement needs a new identifier. Decide whether the commercial item has changed, then follow the applicable identifier rules.
Name an owner for each specification group
The person entering the value is not necessarily the person qualified to decide it.
A practical split might be:
- Product development owns construction and approved options.
- Operations confirms production and packaging measurements.
- Commercial owns prices and pricing rules.
- Compliance specialists own applicable evidence and labeling decisions.
- Marketing owns the expression of approved facts, not the facts themselves.
When sources disagree, keep the issue open until the accountable owner resolves it. Do not select the newest file automatically.
Control changes after launch
Every approved change should record:
- The product, variants and materials affected
- The old and new value
- The source and approver
- The effective date
- The assets, documents and channels that need updating
- Confirmation that the change reached them
Update the authoritative source first: the base record for shared specifications, or the relevant variant, material or channel record for changes specific to that level. A corrected retailer page with an unchanged source record is waiting to become wrong again.
Where Furniture Connect fits
Furniture Connect keeps products, variants, materials and assets connected. Furniture Connect supports formulas on eligible base-catalog fields and channel-specific customizations for supported content fields. Teams can search and filter the catalog, then apply supported bulk updates to selected products.
Complex ranges need an agreed catalog structure before import. Furniture Connect's current variant model supports up to two variant axes per product; additional choices need to be represented through separate products, supporting attributes or documented order-time selections, as appropriate.
CSV import suggests header mappings for review. Rows whose SKU matches an existing catalog product update that product, so the team must confirm that the identifiers represent the intended items before importing. SKU matching does not verify commercial identity or establish whether an unknown specification is correct.
For the underlying fields, see the furniture product data model. For the process around later changes, see furniture product change management.
The test is simple: when one dimension changes, can the team find every place that depends on it without searching old email attachments? If not, the range does not yet have a managed specification. It has several copies.
