Product feed validator: what to check

A product feed validator checks whether each row has the format and facts a receiving specification expects. The best validators do more than count empty cells: they make it obvious which errors prevent an item being understood, which fixes belong in the source shop and which issues repeat across the catalogue.

Why this matters now

A catalogue with 300 products can hide one missing seller name in every row, 12 broken images and a handful of duplicate IDs. Looking line by line is a slog. Validation turns that into a prioritised list, so the merchant can repair the shared cause before polishing exceptions.

What to check first

A practical way to do it

1. Run a sample or public-store check before setting up a full connection.
2. Sort failures by frequency and severity, not by the order they appear.
3. Fix global data such as seller name or default brand once where possible.
4. Open a handful of flagged URLs and images in a normal browser session.
5. Re-run the same checks after the source has refreshed.

Common mistakes

• Calling every warning a blocker and delaying a useful launch.
• Ignoring a small set of duplicate IDs because most rows passed.
• Fixing the exported file rather than the product source that will regenerate it.

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.