Skip to content
Article 2 of 8 — part of the AI-Ready Commerce Feeds™ series.
NSOLVIA Intelligence

My Products Keep Getting Disapproved. Is It the Format or the Data?

Your feed validates, and products still get disapproved or misclassified. Here is the difference between format problems and data problems in commerce feeds.

google shopping disapprovalsproduct feed disapprovedfeed format vs data
Illustration of a validated product feed that still carries ambiguous data

It's one of the most frustrating loops in multi-channel selling. You fix the feed. It validates. Products upload. And then: disapprovals, warnings, items misclassified into categories you never chose, listings that seem to exist but never quite perform.

So you fix the feed again. Same loop.

Here's the pattern worth naming: there are two different kinds of problems that surface at the platform's door, and they have different cures. One is a format problem. The other is a data problem. Most merchants keep treating the second as if it were the first.


Format problems: loud, visible, fixable

Format problems are the ones your feed tool was built for: a required field missing, a value in the wrong shape, an encoding issue, an image URL that doesn't resolve. Platforms reject these loudly and specifically — the error message usually tells you what to fix.

These problems are real, and they're also the solved part of the discipline. Any decent feed setup catches them. If your feed validates cleanly, format is mostly behind you.

Which is exactly why the remaining trouble is so confusing: everything passes, and things still go wrong.


Data problems: quiet, structural, recurring

A data problem is different in kind. The values are valid — they're just not meaningful enough for the machine on the other end.

The most common one we see is the category. A product filed under a generic or home-made label — "Accessories," "New Arrivals," a house-invented type — arrives in perfectly correct syntax and gives the platform almost nothing to classify with. So the platform's systems do what they do with ambiguity: misfile it, flag it, or quietly rank it below products whose category actually resolves. The consistent pattern in our research is that category is one of the strongest signals of whether a machine can interpret a product at all — and one of the most common failure points in traditional feeds.

The same applies to purpose and audience. If what the product is for lives only in your marketing copy, the machine reading structured fields finds silence where meaning should be. No validator flags that. There's no error message for "technically valid, semantically empty."

That's why the loop never closes: you keep fixing format, and format was never the disease.


The tell: which problem do you have?

A rough but useful test. If the platform tells you specifically what's wrong — missing field, bad value, broken link — it's format. Fix it once, it stays fixed.

If products pass validation but get misclassified, disapproved for vague "policy" or "misrepresentation" style reasons, or simply underperform in surfacing — and it keeps happening across batches — you're likely looking at data. The entries are clean containers with ambiguous contents.


Fixing the second problem

Data problems don't close at the feed level; they close at the data level — resolving categories into structured values, making use cases and intent explicit, structuring the attributes the platform's systems actually reason with. Then the feed carries that clarity everywhere, in whatever format each channel demands.

That's the whole architecture of an AI-Ready Commerce Feed™: enrichment first, formatting second. The Pillar below walks through it — including what it honestly can't promise about any platform's decisions.

(And if you sell on several platforms, there's a related headache: the same product telling a different story on each channel. That's Article 3.)


Find out where your catalog stands

Run the free Agentic Catalog Readiness Audit™ — see, on a real product from your catalog, whether your trouble is format or data.

→ Read the complete PillarAI-Ready Commerce Feeds™, the full picture behind this series.


Continue the series

Previous: What Is an "AI-Ready" Feed — and Isn't That What I Already Have? · AI-Ready Commerce Feeds™ (Pillar) · Next: I Sell on Three Platforms and My Product Data Never Matches. Does It Matter?


Series: AI-Ready Commerce Feeds™ (PI-PL002) · Knowledge Domain: Product Intelligence

NSOLVIA Intelligence — Products generate knowledge. Knowledge generates authority.