Two different jobs
Feed management is the discipline of producing, enriching, and distributing product data — titles, prices, availability, GTINs, variants, and images — across the channels where you sell. Its tools exist to make a catalog machine-readable and synchronized.
Preflight is the discipline of reviewing a product's language, claims, and supporting evidence before that product is published or before spend begins. It asks a different question: not 'is the data well-formed?' but 'will a human reviewer, a policy engine, or an AI shopping model treat this product as fair, substantiated, and consistent?'
A feed can be pristine and the product can still be suppressed — because the suppression came from a claim on the PDP, a banned phrase in the title, or a restricted-category flag the feed never carried.
Where they overlap (and where they don't)
Both disciplines touch the same attributes, but for different reasons. Confusing the two is how teams fix the feed and still get suppressed.
- Both care about identifiers — feed tools enrich GTIN/MPN; preflight checks that the identifier matches the actual product and the landing page.
- Both care about the title — feed tools optimize it for match and CTR; preflight checks it for claim and policy language that triggers review.
- Both care about consistency — feed tools enforce feed-to-store sync; preflight enforces feed-to-PDP-to-label-to-schema agreement.
- Neither replaces the other: feed management won't read your claim copy; preflight won't run your nightly price sync.
The correct sequence
For a new or relaunched product, run preflight first. Once the content is clean, the feed can carry it honestly. Reversing the order — sending a polished feed of risky copy — scales the problem instead of solving it.
For an existing catalog, feed management runs continuously; preflight runs at the moments of risk: new-SKU onboarding, claim or creative change, category expansion, and post-suppression resubmission.
The expensive failure is not a bad feed. It's a perfect feed of products a channel will not serve.
How FeedZip fits
FeedZip is preflight, not feed management. It reads the language, attributes, and sources you supply, surfaces the claim and data risks a channel or AI system is likely to flag, and produces lower-risk alternatives and a structured record.
FeedZip is designed to sit alongside your feed tool — you keep your feed pipeline and add a content gate before risky products are submitted or resubmitted.
Frequently asked questions
Should I replace my feed tool with FeedZip?
No. FeedZip complements feed management tools. Keep your feed pipeline for distribution and sync; add FeedZip for the content and claim review feeds don't do.
Does a clean feed prevent suppression?
It reduces data-driven suppressions (price mismatch, missing identifiers) but not content-driven ones (claims, restricted-category language). Those require preflight.
When in the workflow do I run preflight?
Before first submission, before spend, on claim or creative changes, on category expansion, and before resubmission after a suppression.