Feedonomics
Product feed management and channel-specific catalog distribution.
Product feed management and channel-specific catalog distribution. Vendor describes transforming and distributing enriched catalog exports. Distribution cannot correct an incorrect source price without a source-data workflow. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.
What this establishes
The documented role and version scope in the source ledger.
What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
Claim-to-source mapping
- description: Product feed management and channel-specific catalog distribution. · verified · Checked 2026-09-28 · Sources: feedonomics, amazon-feeds
- role: Vendor describes transforming and distributing enriched catalog exports. · vendor-claim · Checked 2026-09-28 · Sources: feedonomics, amazon-feeds
What is documented today.
Each state applies to a named capability and scope. Native describes the product’s own role; it does not mean your merchant account has a live integration.
Shipped / publicly documented
Channel-ready catalog distribution native / live
Feedonomics: catalog-distribution in the documented product role only. Not proof of a live merchant account, connector or AI-surface deployment. Confirm plan, market and onboarding.
Announced / roadmap
Cannot verify
What it does not solve: Distribution cannot correct an incorrect source price without a source-data workflow.
What it helps with
Vendor describes transforming and distributing enriched catalog exports.
What it does not solve
Distribution cannot correct an incorrect source price without a source-data workflow.
The merchant work
- Identify which existing capability this would replace or complement.
- Confirm region, plan, data access and integration effort.
- Request a scoped proof of fit before purchasing.
Merchant fit: Catalogs with multiple destinations or mapping complexity.
Individual merchant eligibility and deployed configuration require confirmation.
| Onboarding | Confirm destination and connector scope. |
|---|---|
| Surfaces | Destination-specific; Amazon Shop Direct feed route documented |
| Protocols | Unknown |
| Pricing | Unknown |
| Regions | Unknown |
| Integrations | Confirm exact platform and connector; no blanket support inferred |
| History | First observed September 2026 |
What we observed, and when.
First house observation: 28 September 2026. Earlier dates, where known, are effective dates researched retrospectively.
First observed 28 September 2026. One baseline snapshot; no subsequent change is recorded.
Go to the source.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: Catalog transformation and distribution
Vendor performance and ROI claims are not independently measured here.
Claim scope: External merchant product feeds
Names Feedonomics, Salsify and CEDCommerce; Shop Direct and Buy for Me are different purchase paths.