Structured product records supplied through a file or supported data connection, using the receiving platform’s required attributes and format.
A product feed is a structured collection of product records supplied to a platform or system. It is often a file, but modern workflows can also use connected data sources and supported integrations. The important concept is the agreed structure and meaning of the fields, not a single mandatory file extension.
Each record must identify the correct item and variant. A color, size or model difference can change the offer, so avoid combining incompatible variants under misleading details. The receiving platform’s specification determines which fields are required or supported. A valid file format does not guarantee that the values are accurate.
Updates need a reliable source of truth. Prices, availability and landing-page details can change, and a stale feed may keep describing an offer that no longer exists. Decide how changes reach the destination and how errors are detected. Preserve stable identifiers where appropriate so that updates modify the intended records rather than creating avoidable duplicates.
Takeaway: Maintain structured product information as carefully as the storefront itself. Validate both the format and the real-world accuracy of the offer, especially after catalog or pricing changes.
Example
A retailer sells a chair in three sizes. Its data source keeps the variants distinguishable and sends each to the appropriate offer details. A price change is checked against the website so that shoppers do not see a small-chair price attached to the larger model.
What to check
Use the current destination specification and inspect rejected or inconsistent records. Do not assume that a successful upload means all products are eligible, displayed or synchronized with current stock.
For more detail, see Google product data specification.