What Is a Catalog Feed?
A catalog feed is a structured data file that transmits product information from a retailer’s database to advertising platforms, marketplaces, and comparison shopping engines. It acts as the machine-readable backbone of any product advertising campaign, telling platforms like Google, Meta, and Amazon exactly what a brand sells, at what price, and whether items are in stock.
Without an accurate catalog feed, product ads cannot run. The feed is the source of truth that platforms use to populate dynamic product ads, shopping listings, and retargeting campaigns automatically.
How a Catalog Feed Works
Catalog feeds come in three standard formats: XML, CSV, or TSV. The retailer generates the file from their e-commerce platform (Shopify, WooCommerce, Magento). From there, they submit it to a feed management system such as Google Merchant Center or Meta Commerce Manager. The platform ingests the feed, validates each product entry against its requirements, and then uses the data to serve ads.
Most platforms require scheduled feed refreshes. Google Merchant Center, for example, flags products as “expiring” after 30 days without an update. High-volume retailers typically push feed updates every 4 to 24 hours to reflect live inventory and price changes.
Core Feed Attributes
Every catalog feed contains a set of required and optional attributes. The required fields vary by platform, but the following appear across virtually all major channels:
| Attribute | Description | Example |
|---|---|---|
| id | Unique product identifier | SKU-7842 |
| title | Product name shown in the ad | Men’s Trail Running Shoe, Size 10 |
| description | Product details for matching and display | Lightweight mesh upper, 4mm drop… |
| link | URL of the product page | https://example.com/products/trail-shoe |
| image_link | URL of the primary product image | https://cdn.example.com/shoe-main.jpg |
| price | Current selling price with currency | 89.99 USD |
| availability | Stock status | in_stock / out_of_stock / preorder |
| brand | Manufacturer or brand name | Brooks |
| gtin | Global Trade Item Number (barcode) | 00012345678905 |
| google_product_category | Standardized category taxonomy | Apparel & Accessories > Shoes |
Where Catalog Feeds Are Used
Catalog feeds power product discovery across every major paid channel. Retailers adapt the same underlying data file for different destinations, each with its own specification:
- Google Shopping / Performance Max: Submitted via Google Merchant Center. Feeds fuel Shopping ads and are required for Performance Max campaigns with product goals.
- Meta Advantage+ Catalog Ads: Uploaded to Meta Commerce Manager. Meta uses the feed to serve dynamic product ads based on browsing behavior and purchase signals.
- TikTok Shopping: TikTok’s catalog system accepts direct feed uploads or integrations via Shopify and WooCommerce plugins.
- Amazon Seller Central: Amazon’s flat-file feed format controls product listings, pricing, and inventory across its marketplace.
- Pinterest Shopping: Catalog feeds enable shoppable Pins and collection ads.
Feed Quality and Campaign Performance
Feed quality directly affects ad auction eligibility, click-through rate, and return on ad spend. Poorly structured titles, missing GTINs, or stale prices cause platform disapprovals and reduce impression share.
A benchmark study by Feedonomics found that optimized product titles can increase Google Shopping click-through rates by up to 18%. Retailers who include GTINs on eligible products typically see lower cost-per-click because Google can better match queries to products.
Title Optimization Formula
Google and Meta both weight product titles heavily for query matching. A reliable title structure for most product categories follows this pattern:
[Brand] + [Product Type] + [Key Attribute 1] + [Key Attribute 2] + [Variant]
Example: Nike Air Zoom Pegasus Running Shoe Men’s Black Size 11
Apparel categories benefit from leading with gender, while electronics often perform better with brand first. The optimal sequence depends on how buyers search within the category.
Feed Management and Supplemental Feeds
Most mid-to-large retailers use a primary feed combined with one or more supplemental feeds. The primary feed contains the full product catalog. Supplemental feeds override or append specific attributes, such as promotional labels, custom labels for campaign segmentation, or corrected titles, without touching the primary source data.
This separation matters operationally. A merchandising team can update promotional labels in a lightweight supplemental feed on a daily cadence without triggering a full catalog reprocessing cycle.
Custom Labels for Segmentation
Custom labels (custom_label_0 through custom_label_4) are five free-form fields that let advertisers tag products with campaign-specific data. Common uses include:
- Margin tier: high-margin / mid-margin / low-margin
- Seasonality: summer-2026 / clearance
- Bestseller status: top-100 / new-arrival
- ROAS target bucket: target-roas-8x / target-roas-3x
Smart Bidding strategies and manual bid adjustments in Google Ads can apply different targets to each label group. This lets advertisers push budget toward high-margin products without creating separate campaigns for every SKU.
Common Feed Errors and Fixes
Google Merchant Center and Meta both generate diagnostic reports identifying disapproved or limited products. The most frequent errors and their remedies include:
- Price mismatch: The feed price does not match the landing page price. Fix by ensuring the feed updates within minutes of any on-site price change, or by using the Automatic Item Updates feature in Merchant Center.
- Missing GTIN: Products with a known barcode require the GTIN field. Fix by pulling GTINs from the brand or distributor’s product data.
- Unclear or generic image: Lifestyle images with text overlays are often disapproved. Fix by using clean, white-background product images for the primary image_link.
- Incorrect availability: Out-of-stock products submitted as “in_stock” lead to disapprovals and wasted spend. Fix with real-time inventory sync via API or hourly feed fetches.
Catalog Feed vs. Product Data Sheet
A product data sheet is a human-readable document summarizing a product’s specifications for buyers or sales teams. A catalog feed is its machine-readable counterpart, structured specifically for automated ingestion by ad platforms. The two serve different audiences: one informs people, the other instructs algorithms.
Retailers that manage both typically maintain a master product information management (PIM) system as the single source of truth, then export formatted versions to each destination.
Frequently Asked Questions About Catalog Feeds
What is a catalog feed?
A catalog feed is a structured data file that transmits product information from a retailer’s database to advertising platforms, marketplaces, and comparison shopping engines. It contains attributes like product ID, title, price, availability, and images, and serves as the data source that platforms use to generate and target product ads automatically.
What file formats does a catalog feed use?
Catalog feeds are most commonly formatted as XML, CSV, or TSV files. XML is the most widely supported format across major platforms. Some platforms also accept direct API connections or scheduled URL fetches as an alternative to manual file uploads.
How often should a catalog feed be updated?
Most retailers should update their catalog feed every 4 to 24 hours to keep inventory and pricing accurate. Google Merchant Center marks products as expiring after 30 days without a refresh, so monthly updates are the absolute minimum. Retailers with frequent price changes should aim for hourly or near-real-time syncs.
What causes catalog feed errors?
The most common catalog feed errors are price mismatches between the feed and the product landing page, missing GTINs on branded products, disapproved images such as lifestyle photos with text overlays, and incorrect availability data. Both Google Merchant Center and Meta provide diagnostic reports that identify and prioritize these issues.
What is the difference between a primary feed and a supplemental feed?
A primary feed contains the full product catalog and serves as the base data source. A supplemental feed overrides or adds specific attributes, such as promotional labels or custom segmentation tags, without modifying the primary feed. This structure lets teams make targeted updates on a faster cadence without triggering a full catalog reprocessing cycle.
Key Takeaways
- A catalog feed is a structured data file that pushes product attributes to advertising platforms for automated ad generation.
- Feed quality (title structure, GTIN coverage, image quality, price accuracy) directly influences ad eligibility and campaign conversion rate.
- Supplemental feeds and custom labels allow granular campaign segmentation without rebuilding the primary feed.
- Regular feed refreshes, ideally every 4 to 24 hours, keep inventory and pricing data accurate across channels.