How Furniture Product Content Reaches Retailers and Marketplaces
How furniture data, imagery, prices and inventory move from manufacturers to retailers and marketplaces, and why one clean source matters.
F
Furniture Connect Team24 sierpnia 2026
“We sent the data weeks ago.”
The retailer may still be waiting for the images. Or the product file arrived, but its dimensions don't match the portal's fields. The inventory feed works while an old price remains on the product page.
All three can be true because furniture content rarely moves as one package. Product facts, assets, commercial terms and stock follow different routes. A range is ready to distribute only when those routes meet at the destination.
What actually moves between trading partners?
There are four separate flows:
| Flow | Typical contents | Common route | Usual cadence |
|---|---|---|---|
| Transactions | Orders, acknowledgements, dispatch and invoices | EDI or API | Hours or daily |
| Product data | Names, identifiers, dimensions, materials and descriptions | Portal, spreadsheet, feed or product-content platform | At launch and when facts change |
| Assets | Product shots, lifestyle images, swatches, diagrams and documents | Portal, file transfer, DAM link or platform export | At launch and when assets change |
| Commercial data | Cost, retail price and advertised-price policies | Portal, feed, price list or email | According to the trading agreement |
Treating these as one “syndication” task hides the handoffs. A successful EDI order flow doesn't prove that the retailer has the current product photography. An accepted image upload doesn't prove that every sellable variant has a price.
Does EDI distribute the whole product record?
No. Electronic data interchange is valuable, but its job depends on the message being used.
UN/EDIFACT PRICAT is a price and sales catalog message. PRODAT is for product master data. Both can identify external files through the EFI segment, but that is a reference to a file rather than a modern image library with product, variant and usage context.[1][2]
In practice, furniture imagery still tends to travel separately from orders and inventory. That separation is why the data team can believe a range has been delivered while the retailer's content team is still chasing swatches.
Is there one furniture data standard?
Not across every market and retailer.
GS1's Global Data Synchronisation Network gives trading partners a common way to exchange standardized product data through certified data pools.[3] Whether it fits your business depends on the retailers, markets and attributes involved. It shouldn't be adopted speculatively because it exists.
IDM Living is much closer to the structure of configurable furniture. The Daten Competence Center publishes the current IDM Living schema, media documentation and related multi-manufacturer formats. At the time of review, the current listed version is IDM Living 4.1.1.[4]
That still doesn't remove retailer-specific work. If a customer supplies its own template or portal specification, that specification governs the submission.
The useful question isn't “Which standard wins?” It is: Which destinations do we need to serve, and what does each one require?
Why retailer portals still matter
Most large retailers control what enters their own product pages. They may ask suppliers to upload files and assets to a vendor portal, follow a named image specification and provide fields that another retailer never requests.
Nebraska Furniture Mart's public vendor guide is a good example. It asks for crated and uncrated dimensions, multiple product images, lifestyle photography, swatch close-ups and supporting documents.[5] That isn't a universal furniture template. It is an example of how specific one retailer's requirements can be.
The destination also controls publication. In a marketplace relationship, a seller may manage its own listing within the marketplace rules. In a first-party vendor relationship, the retailer often controls the live page. The supplier submits content, but may not control how quickly it appears or how it is formatted.
That makes the first submission more important. Fixing a missing field in your own catalog takes minutes. Correcting a retailer-controlled listing may require another upload, another review and another queue.
Why updates don't appear everywhere at once
“Connected” does not mean every destination updates on the same schedule.
Inventory may refresh several times a day. Orders can move within hours. Product photography may wait for a merchandising review. Price changes may be subject to a contractual notice period. The NFM guide, for example, requires 60 days' notice for specified cost and price changes.[5]
Build the operating calendar around the slowest required route, not the fastest integration.
For a new range, that means working backward from the retailer's submission date. Data, assets and commercial approval must be complete before that date. Uploading an incomplete range simply creates a second submission cycle.
A workable distribution model
The strongest setup has one complete internal record and a defined view for each destination.
1. Hold the complete product once
Keep identifiers, dimensions, materials, variant relationships, commercial fields and assets connected. Don't maintain a different master spreadsheet for every retailer. The furniture product data model covers what that record has to hold.
2. Record destination requirements
For each website, marketplace or retail customer, capture its required fields, accepted values, image specifications, document requirements and commercial notice periods.
3. Map from the master record
Translate your field names and values into the destination's structure. If one retailer calls a field “packaged depth” and another calls it “carton D,” both should come from the same approved fact.
4. Review the output
Check the actual export or submission, including several complicated products. Configurable sofas, handed corner units and products sold as sets expose mapping errors quickly. The furniture ecommerce readiness checklist is the go/no-go review for that step.
5. Keep evidence of what was sent
Record the export date, destination and version. When a retailer reports a problem, the team should be able to see whether the error existed in the source, the export or the live listing.
Where Furniture Connect fits
Furniture Connect's Agentic Catalog brings supplier data into a product structure that can hold SKUs, dimensions, prices and variants. CSV imports include a column-mapping step that the team can check before the import runs.[6]
Studio and DAM keep imagery connected to the relevant product context. Teams can also generate a batch of product-and-material combinations, with outputs tagged by product, material and angle.[7]
That prepares a range for distribution. It does not remove the retailer's portal, agreement or approval process. Product data and generated imagery still need human review, exact variant linking requires confirmation, and channel-specific image requirements must be stated.
The value is a bigger share of the catalog ready to list across the destinations that matter, without rebuilding the range from the supplier files each time.
Distributors carry an extra layer of this problem, because the content arrives from many suppliers before it leaves for many customers. Why distributors struggle with product content covers that case. If AI shopping services are one of your destinations, catalog readiness for AI shopping covers what those services need to read.
Frequently asked questions
What actually moves between a furniture supplier and a retailer?
Four separate flows, on four different routes and cadences: transactions (orders, acknowledgements, dispatch, invoices) over EDI or API; product data (names, identifiers, dimensions, materials, descriptions) through a portal, spreadsheet, feed or product-content platform; assets (product shots, lifestyle images, swatches, diagrams, documents); and commercial data (cost, retail price, advertised-price policies). Treating them as one syndication task hides the handoffs.
Does EDI distribute the whole product record?
No. UN/EDIFACT PRICAT is a price and sales catalog message and PRODAT is for product master data. Both can reference an external file through the EFI segment, but that is a file pointer rather than an image library with product, variant and usage context. Furniture imagery still tends to travel separately from orders and inventory.
Is there one furniture product data standard?
Not across every market and retailer. GS1's Global Data Synchronisation Network gives trading partners a common way to exchange standardized data through certified data pools, and IDM Living is much closer to the structure of configurable furniture. Neither removes retailer-specific work: where a customer supplies its own template or portal specification, that specification governs the submission.
Why don't product updates appear everywhere at once?
Because each route has its own cadence. Inventory may refresh several times a day and orders move within hours, while product photography waits for a merchandising review and price changes may be subject to a contractual notice period. Build the operating calendar around the slowest required route, not the fastest integration.
Sources
- UNECE: UN/EDIFACT PRICAT message
- UNECE: External File Link Identification segment
- GS1: Global Data Synchronisation Network
- Daten Competence Center: IDM downloads and current versions
- Nebraska Furniture Mart: Vendor Guide
- Furniture Connect Help Center: Upload products by CSV
- Furniture Connect Help Center: Generate imagery across products and materials
Want to test the route before rebuilding the whole catalog? Book a Furniture Connect demo with one supplier file and one retailer specification.
Gotowi pokazywać i sprzedawać?
Daj każdemu zespołowi dane produktowe, obrazy i zasoby, by szybciej wprowadzać produkty, lepiej ofertować i zamieniać więcej katalogu w przychód.