Furniture SKU Naming Conventions for Configurable Ranges

Your business controls its SKU format. The essential job is simple: each SKU must identify one sellable item unambiguously within the catalog scope where that code is used.

The code does not need to carry the item's complete specification. It needs to stay unique, stable and connected to the structured product data that explains what the item is.

SKU is not the same kind of identifier as GTIN

A SKU is an internal identifier. A GTIN is standardized and governed by GS1. GS1's general rule is that a GTIN assigned to one trade item must not later be reassigned to another, apart from narrow exceptions. A SKU follows the business's own rules, but it should remain stable wherever orders, warranties, retailer records or integrations depend on it.

Do not make the SKU do a GTIN's job. Design the SKU for your own operations and use a GTIN where standardized identification is required.

Make identifiers easy to handle and difficult to confuse

Readable segments can help warehouse, service and catalog teams, but uniqueness and stability matter more than encoding every specification. Avoid characters that are easy to confuse, undocumented abbreviations and patterns that depend on one person's memory.

What a configurable-range SKU needs to identify

A SKU must uniquely identify the sellable item within the business's agreed catalog scope. It does not need to spell out every configuration choice. Descriptive, sequential and hybrid formats can all work, provided each SKU resolves unambiguously to the correct model and approved options.

For teams that benefit from readable codes, one possible pattern is model, size, upholstery and leg finish in a fixed order. For example, AMR-3S-OAT-WAL could represent the Amara three-seat sofa in an approved oatmeal fabric with walnut legs. That is an illustrative convention, not a required architecture.

Keep the complete specification in structured product and variant fields rather than relying on the SKU as the only record of those choices.

Give every material an exact identity

A material code should resolve to one approved material record, not merely a color description. Two unrelated fabrics called "Oatmeal" need distinct identities even if their appearance is similar.

Use shared codes consistently where the exact same material appears across ranges. Existing supplier codes may need supplier, collection or brand context rather than being forced into one global shorthand that creates collisions.

Platform constraints worth checking before you finalize a format

Shopify recommends keeping SKUs short, giving no more than 16 characters as an example, and using a unique SKU for every variant. Treat that length as design guidance, not a documented technical ceiling.

Before finalizing the format, check the mandatory length, character and uniqueness rules in every ERP, ecommerce platform, retailer template and warehouse workflow that will receive the SKU. Keep preferred lengths separate from genuine system limits.

How Furniture Connect uses the SKU during import

In Furniture Connect's flat CSV and spreadsheet import, a row whose SKU matches an existing catalog product updates that product. This matching does not verify commercial identity or automatically create parent–variant relationships. Confirm that each incoming SKU still refers to the intended item before importing.

Changing the SKU in an import file is not a reliable way to rename an existing record. An unmatched SKU can create a new product instead. Handle identifier changes as a controlled update, then verify the result.

An existing variant's SKU can be updated explicitly. That does not establish automatic updates to historical orders, retailer records or other connected systems.

For the wider structure the SKU identifies items within, see the configurable furniture product data guide.

What to do when a code needs to change

Prefer to keep established SKUs stable once orders, warranties, retailer records or integrations depend on them. A supplier's marketing-name change does not automatically require a new SKU.

If an identifier must change, document the old-to-new mapping, coordinate the affected systems and retain traceability for historical orders and warranties. A change in the actual sellable specification may require a new commercial identifier under the business's rules; do not treat it as merely a naming correction.

This internal policy is separate from GS1's rule for GTINs. GS1 generally prohibits reallocating a GTIN from one trade item to another, apart from narrow exceptions.

A naming convention checklist

Before finalizing a SKU format for a configurable range, confirm:

• Uniqueness: No unintended duplicate SKU exists within the agreed catalog scope.
• Identity: Each SKU resolves to the intended model and approved options in the structured catalog.
• Non-reuse: Retired SKUs are not recycled for different items where historical records depend on them.
• Text preservation: Leading zeros survive, and imports do not trim the code or change its case.
• Identifier mapping: Internal SKU, supplier article number and GTIN remain distinct.
• Platform fit: The code meets mandatory receiving-system limits as well as the team's preferred length.
• Ownership: One named team or role allocates new codes and checks for collisions.
• Change control: The convention explains how old-to-new mappings and legacy identifiers are retained.

A well-formatted SKU can still identify the wrong item. Test the identity as well as the pattern.

Why this pays off earlier than expected

The value becomes clear once several configurable ranges are live. Warehouse staff need to match stock, customer service needs to identify an item from an invoice, and new catalog staff need to understand the code without asking its original author. A written convention removes that daily guesswork.

A step you can take this week

Pull the SKUs for your most complex configurable range. Check for duplicates, spreadsheet damage, collisions between internal and supplier codes, and records whose SKU resolves to the wrong product or options.

Then check the format. A code can look perfectly consistent and still point to the wrong sellable item.