What is the difference between a product feed and a catalog?

A product feed is the file or stream used to transport data, while a catalog is the final representation of that data inside an advertising platform like Meta or Google.

Why is my product correct in Shopify but wrong in Google Merchant Center?

This usually indicates a break in the data flow. Either the product feed hasn't updated yet, or there is a transformation rule (either in your feed tool or GMC) modifying the data during transit.

Do I need a CMS to have a product feed?

Technically, no. You can create a feed from a Google Sheet or a manual CSV, but for most ecommerce businesses, the CMS (like Shopify) acts as the primary source of truth for the feed.

What is a 'State 1' data error?

A State 1 error occurs during the 'Vehicle' phase. This means your source data is correct, but the process of translating it into a feed has introduced a mistake or formatting issue.

Product Feed vs Catalog vs CMS: Data Flow Guide

In the world of ecommerce advertising, terms like "CMS," "Product Feed," and "Catalog" are often used interchangeably. You might hear a marketer say, "The product is wrong in the catalog," while the developer insists, "The CMS data is correct."

This terminological overlap isn't just a matter of semantics—it's a primary source of friction when debugging performance issues or scaling to new channels. To build a reliable data pipeline, you must distinguish between the source, the vehicle, and the destination.

Understanding the nuances of the data flow allows you to identify exactly where a desync occurs, saving hours of guesswork and preventing wasted ad spend.

1. The CMS: The Source of Truth (State 0)

Your CMS (Content Management System)—such as Shopify, WooCommerce, Magento, or a headless setup—is your internal database. It is where you manage your business: inventory, prices, product descriptions, and shipping weights.

In the data flow, the CMS represents State 0: Raw Data.

Purpose: Internal management and website rendering.
Scope: Includes all data, even stuff that shouldn't be in an ad (e.g., internal SKU notes, raw HTML, or low-margin items).
Control: You have 100% control over this data.

The Pitfall: Many teams assume that if the data looks "correct" on their Shopify product page, it is ready for Google Shopping. This is rarely true. CMS data is built for humans and web browsers, not for advertising algorithms.

2. The Product Feed: The Vehicle (State 1)

The Product Feed is the bridge. It is a structured file (XML, CSV, JSON) or a real-time API stream that transports a snapshot of your CMS data to an external platform.

In the data flow, the feed represents State 1: Transport & Transformation.

Purpose: Communication between systems.
Scope: A filtered and formatted subset of your CMS data.
Control: Managed via plugins, custom scripts, or a dedicated feed layer.

Think of the feed as a translation layer. It takes the "Midnight Blue" from your CMS and translates it to "Blue" for the platform's requirements. If you are wondering if you've reached the point where manual exports aren't enough, read our guide on do you really need a feed management tool?.

3. The Catalog: The Representation (State 2)

The Catalog (Meta Catalog, Google Merchant Center Catalog, TikTok Catalog) is the end-user's view of your data inside the advertising platform. It is what the ad algorithm actually "sees" and uses to target users.

In the data flow, the catalog represents State 2: Interpreted Data.

Purpose: Ad generation and algorithmic matching.
Scope: The final, processed version of the data after the platform's own validation and "feed rules" have been applied.
Control: Limited by the platform's interface and policies.

The Distinction: A product can exist in your feed but be missing from your catalog because it was rejected during the platform's ingestion phase.

The Data Flow: From SKU to Impression

Visualizing the flow is essential for feed management fundamentals. The journey usually looks like this:

CMS Update: You change a price in Shopify.
Extraction: A plugin or tool (like 42feeds) reads the change from the CMS via API or import feed.
Transformation: Rules are applied (e.g., "Add Brand to Title").
Feed Generation: The data is rendered into a format the channel understands.
Ingestion: The ad platform (GMC/Meta) fetches the feed.
Processing/Validation: The platform checks the data against its policies.
Catalog Update: The product status is updated in the ad account.

Why the Difference Matters for Debugging

When a price mismatch occurs, most people start clicking buttons randomly. A structured approach asks: Where did the flow break?

Is the price wrong in the CMS? If yes, fix your source data.
Is the price correct in the CMS but wrong in the Feed? Your transformation rules or plugin logic are broken.
Is the price correct in the Feed but wrong in the Catalog? The platform hasn't fetched the latest feed yet, or there is a "Feed Rule" inside the platform (like Google Merchant Center) overwriting your data.

By decoupling these three entities, you can treat your feed as a system rather than a file.

Decoupling for Scale

The most successful ecommerce operations decouple their CMS from their Catalogs using a dedicated feed layer (e.g., 42feeds). This allows you to:

Optimize for the Channel: Change titles for Google without changing them on your website.
Filter Early: Keep low-stock or low-margin items out of the feed entirely, before they even reach the ad platform.
Multi-Channel Consistency: Send the same high-quality data to Meta, Google, and TikTok from a single source of truth.

Summary

CMS: Where the product lives (Database).
Product Feed: How the product travels (Bridge).
Catalog: Where the product is shown (End-point).

If you treat these as three distinct stages of a pipeline, you move from reactive firefighting to intentional product feed management.

Product Feed vs. Catalog vs. CMS: Understanding the Ecommerce Data Flow