Why Furniture Supplier Product Data Arrives Incomplete

The retailer says the supplier file is incomplete. The supplier says it contains everything needed to order the range.

Both can be right.

Most furniture supplier data was built to support manufacturing, wholesale orders and stock control. An ecommerce team is trying to use the same file to answer customer questions, build variants, meet channel rules and support a purchase. Those are different jobs.

The recurring gaps are not usually carelessness. They are a mismatch between the system that produced the data and the job the retailer needs it to do.

1. The source system was built for trade orders

A supplier can process an order with a model code, size, cover grade and price. The customer needs rather more:

• Will it fit through the door?
• How high is the seat?
• What is inside the cushion?
• Does it require assembly?
• What does this exact colorway look like?

Those facts may exist in technical drawings, factory systems or someone's inbox, but not in the wholesale spreadsheet. The file is complete for the supplier's transaction and incomplete for the retailer's product page.

2. Furniture variants do not fit neatly into rows

A sofa can vary by size, configuration, orientation, fabric, colorway, leg finish and filling. Suppliers often express that logic through codes and price bands because listing every combination would make the file unwieldy.

Retail and marketplace systems need explicit relationships. They need to know which combinations are actually purchasable, which SKU belongs to each one and which image, price and availability record should appear when the customer changes an option.

Google's product data rules illustrate the gap: each variant is submitted separately, while a shared item_group_id groups the variants together.[1] A supplier's single row containing “available in all fabrics” cannot do that job on its own.

3. Materials live in a different library

Fabric composition, rub count, care guidance, finish details and swatch images are often managed separately from the product range. The range file carries a material code; the useful information sits in a fabric book or another database.

That split is sensible for the supplier. The same fabric may be available across hundreds of products. It becomes a problem when the retailer imports the code but not the library behind it.

The answer is not to type the same material details into every SKU. Link products to a reusable material record, then update the composition, care information and swatch once.

4. Compliance evidence is held as documents, not product data

Test reports and certificates tend to be organized by factory, batch, component or test date. The ecommerce team needs to know which sellable products they cover.

That relationship cannot be reduced to a generic compliant = yes column. A useful record identifies the regime, document, issuer, date, covered SKUs or batches and the source file.

The required evidence also changes by product and market. UK upholstered furniture, US clothing storage units and furniture containing composite wood do not follow the same rules.[2][3][4] The catalog needs a way to say “not applicable” as well as “missing” and “verified.”

5. Imagery is supplied by product family, not by sellable option

A supplier may provide strong images for the launch fabric and little or nothing for the rest of the range. From a brochure perspective, the product has been photographed. From a catalog perspective, most variants remain unseen.

This is why image count is a weak measure. The better question is: what percentage of purchasable colorways and configurations has an accurate image?

Furniture Connect can create colorway, packshot and lifestyle outputs from approved product photography and run the same job across hundreds of SKUs.[5] The output still needs a person to compare it with the reference product and approve or reject it. Once approved, it can be linked to the precise variant rather than left in an unstructured image folder.

6. Every retailer asks for a different version

One retailer wants millimeters; another wants centimeters. One treats left-hand and right-hand configurations as variants; another separates them into products. Marketplace titles, required fields and image rules differ again.

There is no single supplier export that can anticipate every downstream model. The practical solution is a stable internal product record plus a repeatable mapping for each supplier and each sales channel.

What should a catalog team do with an incomplete file?

Start by deciding what must be known before publication. Do not begin with every field the business might ever want.

For each product type, define:

• The facts required to identify and sell each variant.
• The questions a buyer needs answered before purchase.
• The images required to represent the range honestly.
• The evidence required for the market and product.
• The attributes required by each intended channel.

Then compare the supplier's file with that standard.

Map what is already there

Normalize headings, units, values and codes before asking the supplier for new data. Furniture Connect's CSV importer can detect likely header matches and lets the team adjust the mapping before import.[6] A reusable map prevents the same clean-up job on the next range.

Keep missing facts visible

Do not bury gaps inside polished copy. Mark dimensions, materials or documents as missing and assign an owner. AI can draft a description from verified inputs; it should not invent a seat height, material composition or safety claim.

Join the separate libraries

Connect product records to the fabric, finish, media and compliance records that support them. That is usually where the “missing” information is hiding.

Feed the result back to the supplier

Send a short exception report: which fields are missing, which values failed validation and which documents cannot be matched. A supplier is more likely to improve a specific recurring gap than respond to a request for “better data.”

The aim is not a perfect supplier spreadsheet

The aim is a catalog that can turn a supplier's information into accurate, approved product records repeatedly.

Some suppliers will improve their exports. Some will continue to send price lists and PDFs. Your process needs to work in both cases.

That means keeping supplier mappings, separating verified facts from generated content, connecting variants to the right assets and checking completeness before the range reaches the publish queue. The supplier catalog onboarding process sets out that workflow; the data quality scorecard gives you a quick way to find the weakest part of a range.

Frequently asked questions

Sources

1. Google Merchant Center: Item group ID for product variants
2. UK legislation: Furniture and Furnishings (Fire) (Safety) Regulations 1988
3. US CPSC: Clothing storage unit requirements
4. US EPA: Formaldehyde standards for composite wood products
5. Furniture Connect: AI for furniture at catalog scale
6. Furniture Connect Help Center: How to upload products by CSV

---

Bring us the supplier file you are actually working with. We will show you how Furniture Connect can structure the products and variants, surface the gaps and keep the approved data and imagery together. Book a demo.