A product feed is a structured file or data stream that lists a store’s products with their attributes, such as identifier, title, price, availability, image and brand, in a format that an external channel can read automatically. In product catalogs within e-commerce, the feed is the bridge between the internal catalog and the outside world: shopping ads, marketplaces, price comparison sites, affiliate networks and social commerce catalogs all build their listings from it.
A feed is not a copy of the store database. It is a channel-specific projection of the catalog, filtered, renamed and transformed so that each receiving system gets exactly the fields, values and formats its specification requires.
How a product feed moves catalog data
A feed pipeline has three stages. First, the export reads products from the store platform or product information management system. Second, transformation rules map internal fields to channel attributes, clean text, convert units and exclude unsuitable items. Third, the delivery step publishes the result where the channel can fetch it, or pushes it through an API.
Delivery methods differ mainly in freshness and complexity. A scheduled file is simple and robust but only as current as its last fetch, while an API connection can update a single price within minutes. The table below compares the common formats and delivery methods.
| Format or method | Structure | Typical refresh | Best suited for |
|---|---|---|---|
| XML (RSS or Atom) | Nested elements with namespaced attributes | Daily to several times a day | Shopping ads and comparison sites |
| CSV or TSV | One row per product, one column per attribute | Daily | Simple catalogs and spreadsheet editing |
| JSON | Objects with nested arrays | Hourly to daily | Modern marketplace and social catalogs |
| API push | Individual product updates sent on change | Minutes | Fast-changing prices and stock |
| Supplemental feed | Partial file keyed by product ID | As needed | Overriding or adding selected attributes |
Most channels identify every item by a stable product ID, usually the SKU or variant identifier. Changing IDs between exports resets the history of each item, so performance data and approval status are lost.
Key attributes and their requirements
Every channel publishes its own specification, but a core set of attributes appears almost everywhere. Missing or inconsistent values in these fields are the most common reason for rejected or disapproved items.
| Attribute | Content | Typical requirement |
|---|---|---|
| id | Unique, stable identifier | Required, unchanged across exports |
| title | Product name with key attributes | Required, often up to 150 characters |
| price | Amount with currency code | Required, must match the landing page |
| availability | In stock, out of stock, preorder or backorder | Required, must match the landing page |
| image link | URL of the main product image | Required, no watermarks or promotional text |
| GTIN | Global trade item number such as EAN or UPC | Required for branded goods on many channels |
| item group ID | Shared ID linking variants of one product | Required when variants exist |
Variants deserve particular care. Each size or color usually becomes its own feed item with its own ID, price and availability, while the shared item group identifier tells the channel that they belong to one product. This is where the feed reflects the catalog model of product variants and product attributes most directly.
Product feed compared with related catalog concepts
A product feed is easy to confuse with the systems around it. The distinction matters because each one has a different owner and purpose: the catalog is the master, while the feed is a derived output.
| Concept | What it is | Relationship to the feed |
|---|---|---|
| Product catalog | Master set of products in the store | Source of almost all feed data |
| SKU | Internal stock-keeping identifier | Often reused as the feed item ID |
| Product attribute | Single property such as color or material | Mapped to channel-specific fields |
| Sitemap | List of page URLs for search crawlers | Contains pages, not structured product data |
| Structured data markup | Product data embedded in the page code | Used by channels to verify feed values |
Optimizing a product feed for performance
Feed optimization improves how products are matched to searches and how attractive the listings look, without changing the products themselves. On shopping channels without keyword bidding, the title and category fields act as the targeting, so they deserve the most attention.
- Front-load important words in titles: brand, product type and the decisive attribute such as size or capacity.
- Assign the most specific category from the channel taxonomy instead of a broad parent category.
- Use custom labels to segment campaigns by margin, season or best-seller status.
- Exclude items with low margin or no stock instead of paying for clicks that cannot convert.
- Provide additional images and shipping data where the channel supports them.
Large catalogs are usually handled with a feed management tool or rule engine rather than manual edits. Rules such as appending the color to every apparel title scale across thousands of items and survive the next export.
Common feed errors and how to fix them
Channels compare feed values with the landing page and with each other, and mismatches lead to warnings, disapprovals or account suspension. The following table lists frequent problems and their usual remedies.
| Symptom | Likely cause | Fix |
|---|---|---|
| Price mismatch disapprovals | Feed refreshed less often than prices change | Increase refresh frequency or push price updates by API |
| Items shown in stock but sold out | Availability exported from a stale cache | Export live stock or add a safety threshold |
| Missing identifier warnings | GTIN not stored in the catalog | Add manufacturer barcodes to product data |
| Variants shown as separate products | Item group ID missing or inconsistent | Use the parent product ID for all variants |
| Sudden drop in active items | Changed IDs or broken image URLs | Keep IDs stable and validate links before export |
The idea in brief
A product feed is a list of everything a shop sells, written in a format that other websites can read automatically. Each line or entry describes one product: its name, price, picture, and whether it is in stock.
Google, marketplaces and comparison sites use this list to show the shop’s products to their own visitors. If the list is wrong or outdated, the ads and listings are wrong too, so keeping the feed accurate matters as much as keeping the shop itself accurate.
A practical scenario
An online retailer of outdoor equipment sells about 4,000 products, many of them in several sizes. It sends one XML feed to a shopping ads platform, a CSV feed to a regional price comparison site and a JSON catalog to a social commerce channel, all generated from the same catalog.
After seeing frequent price mismatch disapprovals during weekend sales, the team moves from one daily file to an hourly export plus API updates for price changes. It also rewrites jacket titles from the internal model code to a pattern of brand, product type, gender, material and size.
Within the following weeks, disapprovals fall to a handful of items with missing barcodes, and the rewritten titles start matching more specific searches. The catalog did not change, but its presentation to each channel did, which is the core purpose of feed management.