Product data feed: the merchant's guide

A product data feed is a structured export of the product information a receiving channel needs. It turns a catalogue into rows and fields that can be checked consistently: product identity, copy, links, images, price, availability and seller context.

Why this matters now

A catalogue is built for the shop that owns it. A feed is built for a channel that did not. That difference matters when a shop stores a beautiful product name in one place, availability in another and images behind a private content delivery service. The feed makes the hand-off explicit, which is exactly where hidden gaps surface.

What to check first

A practical way to do it

1. List the facts a receiving channel requires before choosing a format.
2. Map each field to a maintained source, rather than filling gaps with guesses.
3. Use UTF-8, stable column or key names and publicly accessible product assets.
4. Keep variants as separate sellable rows when their price, availability or image differs.
5. Test a small export before publishing the whole catalogue.

Common mistakes

• Calling a spreadsheet a feed before checking whether the target accepts its format.
• Using stock codes that change whenever the merchandising team changes a title.
• Treating a product category as a substitute for a real product description.

What this does not mean

A clean product feed makes your catalogue understandable to a receiving platform. It does not guarantee approval, inclusion, ranking, sales or a particular checkout experience. Those decisions and customer-facing flows remain with the platform and the merchant.

The useful habit is simple: correct the source data, then validate the exported feed. Do not patch a one-off file and assume the next shop sync will remember your fix. That is how a tidy launch turns into a slow drift a fortnight later.