Marketplace Feed Validator
Paste a feed, pick the destination, and see what breaks. The interesting failures are not typos — they are values that are perfectly correct on the platform you copied the feed from.
🔒 Your data never leaves your browser.
Google writes in_stock. Meta writes in stock.
An underscore against a space. Copy a working Google Shopping feed into a Meta catalogue and
every row has an availability field, and every row's value is rejected. What Meta
reports back is usually just that the product is not live — so people go looking for a problem
with the product.
| Meaning | Google Shopping | Meta |
|---|
That is what this page is for. When a value is wrong here but right somewhere else, it says which platform's spelling you used and what this one wants — rather than reporting an invalid value and sending you to check a spelling that was never wrong.
A duplicate id does not overwrite. It deletes both.
Meta's documentation is explicit: where a content ID appears more than once, all instances are ignored. Not last-wins, not first-wins — both products vanish from the catalogue. It is the one feed error where the damage is larger than the row it is on.
Which of these profiles is actually verified
Meta catalog — the field list, character limits, accepted values, price form and URL rules all come from Meta's own published catalog fields reference, which is publicly readable.
TikTok Shop, Walmart Marketplace, Amazon flat file — these carry only constraints that can be checked without their documentation: a unique id, core fields present, a numeric price, absolute URLs. Their field references sit behind a seller login or change with each release, so this project has not verified a field-by-field list and does not present one. A clean result on those is not a statement that your feed will upload; check the current template in your seller account.
Saying that plainly costs a feature and buys the only thing that matters here — you can tell which parts of this page to trust.
Every check this tool runs (11 rules)
PFD-X01 Value is valid on another platform but not this one
The value is one the field accepts somewhere else. The clearest case is stock status: Google Shopping wants in_stock with an underscore and Meta wants "in stock" with a space. A feed that works on one and is copied to the other has the field present on every row and the value rejected on every row — and the error the platform reports is usually just that the product is not live.
Fix: Use the value this platform expects; the equivalent on each is shown.
Source: Meta — Catalog Fields
PFD-R01 Required field missing or empty
The platform will not accept the item without it.
Source: Meta — Catalog Fields
PFD-V01 Value not in the accepted set
The field takes a fixed vocabulary and this is not one of the words. Close synonyms fail exactly like nonsense does.
Source: Meta — Catalog Fields
PFD-L01 Over the field’s character limit
The value is longer than the platform accepts, and the row is rejected rather than truncated.
Source: Meta — Catalog Fields
PFD-L02 Within the limit but past the recommended length
Accepted, but cut off in display — the tail is written for nobody.
Source: Meta — Catalog Fields
PFD-P01 Price in the wrong form for this platform
Some platforms want the value and an ISO 4217 code separated by a space (9.99 USD); others want a bare decimal with the currency set elsewhere. Sending the wrong one makes the price unreadable rather than wrong by a bit.
Source: Meta — Catalog Fields
PFD-U01 URL is relative, or points at the platform
Feed URLs must be absolute and on your own domain. A link to the platform’s own site is specifically rejected — it is not a product page.
Source: Meta — Catalog Fields
PFD-D01 Duplicate id
Each id must appear once. Meta states that where an id repeats, ALL instances are ignored — so a duplicate does not overwrite, it removes both products.
Source: Meta — Catalog Fields
PFD-H01 HTML or all capitals in the description
Descriptions are plain-text fields. Tags are shown literally or stripped, and text in capitals is explicitly discouraged.
Source: Meta — Catalog Fields
PFD-N01 This platform profile is not field-verified
Only Meta’s field reference could be retrieved and checked in full. For the others this tool carries generic constraints — unique id, core fields present, numeric price, absolute URLs — and does not claim a complete field list. A clean result here is not a statement that the feed will upload.
Source: This platform profile carries only constraints that can be checked without its documentation — a unique id, the presence of core fields, a numeric price, absolute URLs. The platform’s own field reference is behind a login or changes with each release, so this project has NOT verified a field-by-field list for it and does not present one. Check the current template in your seller account before relying on a pass.
PFD-V02 Row passes the checks this profile carries
Every constraint this profile knows about is satisfied.
Field-verified for Meta catalog. Generic constraints only for TikTok Shop, Walmart Marketplace, Amazon flat file — their references are login-gated or version-unstable, and this page does not invent one.