Ecommerce & Omnichannel Commerce

What Is a Product Feed?

Definition

A product feed is a structured data file or API stream that delivers product information to a channel such as a marketplace, advertising platform, or comparison service. It contains one row or record per sellable item, with the fields, formats, and identifiers the receiving system specifies.

Last updated November 10, 2026

Key takeaways

  • Feeds are schema-bound: fields, order, and formats are dictated by the destination.
  • One source record usually produces several feeds with different mappings.
  • Most feed rejections come from missing required fields, invalid option values, or identifier problems.
  • Feed health requires monitoring acknowledgements, not just transmission.

A contract with a channel

A feed is not an export; it is an agreement. The destination defines which fields exist, what values are allowed, and how items are identified. Anything outside that contract is rejected or silently ignored.

Anatomy of a feed

  • Identifiers. SKU, GTIN, brand, and sometimes a category-specific identifier.
  • Core attributes. Title, description, dimensions, material, and channel-specific fields.
  • Commercial fields. Price and availability where the channel requires them.
  • Media references. Image URLs meeting size and background rules.

Why one record becomes several feeds

A marketplace feed for electronics, an advertising feed, and a retailer portal template share facts but differ in field names, mandatory attributes, and structure. Maintaining those as separate manual exports guarantees drift; generating them from one record with per-channel mappings does not.

Feed hygiene

Validate before sending, monitor acknowledgements after sending, and keep a record of per-item errors. A feed that transmits successfully can still have most of its items rejected.

Example

A distributor generates a marketplace feed from its PIM. Items missing a required material attribute are excluded rather than sent and rejected, and the exclusion list becomes the next enrichment queue.

Frequently asked questions

CSV, TSV, XML, and JSON over API are the common ones. Each channel specifies its own schema, field names, allowed values, and file size limits.

Further reading