Keep your existing feed
Import an HTTPS source or an XML, CSV, TSV or JSON file. Map once, then work from a saved source.
THE FEEDAPTOR WORKSPACE
From source to release.
With a paper trail.
A practical workspace for the decisions between importing a merchant feed and releasing a new catalog artifact.
merchant-feed.xmlYour existing source
f Enrichment Review
ILLUSTRATIVE DEMOSTUDIO / TEE-001
Organic cotton tee
3 proposed field changes
ATTRIBUTEBEFORE → AFTER
MaterialMissingOrganic cotton✓
ColorMissingBlack✓
TitleStudio teeStudio organic cotton tee — black○
↳ Evidence: original product description
Try the review workflow ✓
Approved. Versioned. Traceable.ACP discovery · UCP snapshot · Google supplement
Approve the actual changes
Compare original and proposed values, inspect the supporting evidence, and decide field by field.
Make the next update easier
Carry relevant approvals forward. Changed supporting facts return to review instead of silently keeping an old decision.
Ship a release you can explain
Prepare versioned artifacts with a record of the source, rules, approvals and checks behind them.
APPROVAL MEMORY
Keep the decision.
Recheck the reason.
Approvals carry forward across refreshes for the same product identity when their supporting fields are unchanged. Unrelated price and availability changes can preserve a descriptive-field approval.
A changed dependency, ambiguous identity or expired captured page evidence returns the field to review. The reviewer and the reason travel with the decision.
This reduces repeat work while keeping changed facts visible. It is not a blanket “approve forever” switch.
FEED CENTER
One action.
A controlled batch.
Preview selected feeds before importing, refreshing, auditing, pausing or resuming them. Track child jobs, recover failures and respect the workspace allowance.
01Preview affected sources↗
02Start a durable batch↗
03Track each feed separately↗
04Retry failed jobs only↗
05Keep a record of the result↗
EVIDENCE & IMPACT
A release you
can account for.
Compare source and approved completeness for the same product cohort. Keep source versions, rules, review decisions and artifact checksums together in a release evidence manifest.
Use Catalog Lab to save deterministic product-matching scenarios. A scenario can explain whether the catalog contains particular facts. It does not predict AI rankings or prove commercial uplift.
Try a review