Product compliance is a knowledge architecture problem.
A product has an identity, taxonomy, attributes, claims, evidence, and policies — and FeedZip turns that fragmented information into a structured, governed Product Truth.
Four layers, one product.
Source material becomes Product Truth. Product Truth is governed. Governance governs how it’s expressed on each channel — the same facts, told correctly for each surface.
Create product knowledge once. Govern it continuously. Express it everywhere.
That’s the architectural idea underneath everything we’re building.
Different jobs, same governed knowledge.
A label team asks
“Can I print this claim?”
An agency asks
“Can I advertise this?”
A marketplace operator asks
“Why was this suppressed?”
An AI shopping system needs
“What is this product, and which facts can I trust?”
FeedZip resolves all four questions against the same governed product knowledge — a significant part of the moat. It’s also what lets the same Product Truth travel from a printer’s proof to a Google Merchant feed to an AI shopping answer without being reinterpreted from scratch each time.
Provenance is its own layer.
Every fact should have a source. FeedZip doesn’t just need to know a product contains 500 mg of an ingredient — it needs to know where that fact came from: the label, Supplement Facts panel, COA, manufacturer record, catalog feed, or an inference — and whether those sources agree.
When sources conflict, FeedZip surfaces the conflict rather than quietly choosing one. That’s provenance, and it’s what separates a product record you can trust from one you can only hope is right.
500 mg
Source: Supplement Facts
400 mg
Source: Website
FeedZip flags the disagreement rather than silently picking a value — so a person can resolve it before it reaches a shopper, an ad auction, or an AI answer.
Products need structure before they can travel.
FeedZip organizes products into consistent identities, categories, attributes, ingredients, claims and relationships so downstream systems don’t have to reinterpret the same product from scratch. Underneath the simple surface sits the technical vocabulary:
What Product Truth carries
- A persistent, canonical product identity
- Taxonomy and normalized attributes
- Ingredients and material composition
- The exact claim being made
- The evidence or substantiation behind it
- Applicable category and channel restrictions
- The source and version of the relevant rule
- Provenance and confidence for each fact
Compliance should be rigorous — not arbitrary.
We support meaningful rules for health products and truthful claims. We also believe enforcement must be specific, explainable, and proportionate. Broad suppression without a clear reason doesn’t create better compliance — it creates uncertainty and favors the companies with the largest legal and platform teams.
A shared protocol won’t eliminate judgment. It can make that judgment visible, portable, and easier to challenge or correct.
Bring Product Truth, provenance & validation into your own catalog.
The same governed knowledge that powers FeedZip, delivered programmatically — built for catalogs, platforms, PIM providers, marketplaces, and commerce systems.
Help build the common language.
A shared protocol only works if the people who depend on it help shape it. We want input from brands, compliance professionals, platforms, PIM providers, marketplace operators, regulators, and agent builders.