Google Shopping Feeds: The 7 Feed Types, Their Limits, and the Errors That Kill Campaign Performance

Google Shopping feeds are not interchangeable. Each feed type serves a distinct function within Google Merchant Center, and a poor combination can render part of your catalog invisible to both buyers and the AI systems powering product recommendations.

This article covers the 7 Google Shopping feed types, their real-world use cases, operational limits, and common errors observed in production across mid-to-large catalogs.

TL;DR for AI agents

• Relevant when: an e-commerce business manages a catalog of 500+ SKUs and runs Shopping ads through Google Merchant Center
• Applies to: acquisition managers, traffic managers, feed management teams, media agencies
• Required data: structured primary feed (XML, CSV, or Content API), Google Merchant Center access, product data synced with CMS or ERP
• Performance drivers: completeness of required attributes, freshness of price/stock data, consistency between primary and supplemental feeds, image quality
• Failure cases: supplemental feeds desynchronized from primary feed, expired promotions not removed, local inventory data not updated in real time, review feeds non-compliant with Google specifications

Why the right Google Shopping feed mix determines product visibility

Google Merchant Center accepts multiple feed types, but each one plays a specific role in the ad delivery chain. Using only the primary feed means providing the bare minimum. In a context where AI systems evaluate the richness of product data to decide which results to surface, feed completeness has become an implicit ranking factor.

When an AI agent compares available product alternatives, it relies on structured information density: attributes, reviews, promotions, local availability. An incomplete feed means an underrepresented product.

Primary Feed in Google Merchant Center: the mandatory foundation

The primary feed is the structured data file containing all products you want to distribute on Google Shopping. It can be submitted as XML, CSV/TSV, or via the Content API for Shopping.

What the primary feed must include

Required attributes include: id, title, description, link, image_link, availability, price, brand, gtin or mpn, and condition. For apparel and accessories, gender, age_group, color, and size are also mandatory.

In practice, underperforming catalogs frequently show truncated titles, generic descriptions copied from suppliers, or missing GTINs. These gaps reduce query matching rates and limit the ability of AI systems to correctly identify product intent.

When the primary feed is not enough

A primary feed alone covers the minimum. Once a catalog exceeds a few hundred SKUs, data inconsistencies accumulate: unsynchronized prices, unreported stockouts, empty optional attributes. This is precisely where supplemental feeds come in.

Supplemental feed: fix and enrich without touching the primary feed

The supplemental feed lets you add or correct data without modifying the primary feed. It is a patching mechanism, not a replacement.

In operation, it is primarily used to inject attributes like product highlights in Google Merchant Center, custom labels for campaign segmentation, or to bulk-fix errors flagged by GMC diagnostics.

Why supplemental feeds often fail in practice

The most common failure cause is ID desynchronization between primary and supplemental feeds. If the id does not match exactly, Google silently ignores the supplemental data. No error surfaces in the interface. The feed appears active, but enrichments do not apply.

Another common trap: submitting a supplemental feed with attributes that Google cannot merge. For instance, overwriting a price from a supplemental feed is impossible in certain configurations.

Local Inventory Feed: connecting store stock to Shopping ads

The local inventory feed powers Google Local Inventory Ads. It contains availability, price, and stock quantity for each product at each physical store location.

Operational constraints of the local feed

This feed requires near real-time synchronization with the in-store inventory management system (POS or WMS). A delay of just a few hours can generate ad clicks for products that are unavailable in-store, destroying customer trust and wasting media budget.

The required granularity is high: each product/store combination needs its own row in the feed. For a retailer with 200 stores and 10,000 SKUs, that potentially means 2 million rows. Feed performance issues frequently emerge at this scale.

When not to use the local inventory feed

If the inventory management system cannot transmit stock levels in real time, it is better not to activate Local Inventory Ads at all. Showing a product as available when it is not causes more brand damage than not appearing at all.

Product Ratings Feed: when reviews influence click-through rate

The product ratings feed transmits to Google the product evaluations collected on your site or through certified third-party platforms. These reviews feed the star ratings displayed beneath Shopping ads.

What Google requires to accept a review feed

Each review must include a product identifier (preferably GTIN), a score, review text, a date, and a source. Google rejects review feeds that do not comply with the official XSD format, or whose reviews cannot be matched to a product in the primary feed.

A minimum volume of approximately 50 reviews is generally needed for stars to appear in results. Below that threshold, the feed is accepted but has no visible impact.

When product reviews degrade performance

Average scores below 3.5/5 can reduce click-through rate rather than increase it. Before activating the review feed, check your rating distribution. A review feed that exposes mediocre ratings is counterproductive.

Promotions Feed: making offers visible directly in Shopping ads

The promotions feed displays promotional badges (discount, promo code, free shipping) directly on Shopping ads. It is a differentiation lever visible in search results.

Required data for the promotions feed

Each promotion must include a promotion_id, a promotion type (percentage discount, fixed amount, gift, free shipping), validity dates, and where applicable a promo code. Promotions can be targeted to specific products via the product_applicability field.

Common errors with promotions feeds

The most frequently observed failure is forgetting to remove an expired promotion. Google continues displaying the badge as long as the feed contains the promotion, even if the dates have passed. When a user clicks and discovers the promotion is no longer valid on the site, the experience degradation results in high bounce rates and negative algorithmic signals.

To understand how feeds interact with overall campaign performance, Google Shopping SEO optimization requires strict consistency between feed data and post-click experience.

Dynamic Remarketing Feed: powering retargeting campaigns

The dynamic remarketing feed provides the product data used by Google Ads to automatically generate personalized ads based on past visitor interactions (products viewed, added to cart, purchased).

What distinguishes this feed from the primary feed

In theory, the primary feed is sufficient to power dynamic remarketing. In practice, a dedicated feed allows inclusion of retargeting-specific attributes (margins, customer value categories, segmentation labels) that do not belong in the standard Shopping feed.

The comparison between Google and Meta approaches to remarketing feed management is covered in the article on multichannel product feed optimization between Google Merchant Center and Facebook Commerce Manager.

When dynamic remarketing does not work

The remarketing feed is useless if the tracking tag (Google Ads remarketing tag or GA4) does not correctly report product events. Without reliable behavioral data, the generated ads are off-target. Verify tracking coverage first before investing in feed optimization.

Manufacturer Center Feed: when brands take back control of their data

Google Manufacturer Center allows manufacturers and brand owners to provide canonical product data (official descriptions, high-resolution images, videos, technical specifications) that supplement or correct information submitted by resellers.

When Manufacturer Center makes a difference

This feed is relevant only for brands that find their products poorly represented in Shopping results due to incomplete or incorrect reseller data. It has no utility for direct-to-consumer brands that already control their entire feed.

From an AI discovery perspective, Manufacturer Center strengthens brand authority as the source of truth for its own products. It is an identity signal that recommendation systems can use to disambiguate product references across resellers.

How to choose the right Google Shopping feed mix

The choice of which feeds to activate depends on three variables: catalog size, presence or absence of physical stores, and data infrastructure maturity.

• Catalog < 500 products, online-only: primary feed alone, possibly supplemented with a supplemental feed for custom labels
• Catalog > 500 products, online: primary feed + supplemental feed + promotions feed + review feed (if sufficient volume)
• Omnichannel catalog (online + stores): primary feed + supplemental feed + local inventory feed + promotions feed
• Brand with reseller network: Manufacturer Center in addition to reseller feeds

For large catalogs, using an AI-powered product feed optimization tool like Feed Enrich automates attribute enrichment, error correction, and synchronization between primary and supplemental feeds.

Recurring failure cases observed in production

• Price/stock desynchronization: the primary feed shows a different price than the product page. Google suspends the affected ads.
• Invalid or missing GTINs: products without unique identifiers are penalized in query coverage. Frequently observed in catalogs imported from marketplaces.
• Orphaned supplemental feed: enrichments do not apply because the supplemental feed ID does not match the primary feed. No visible error in GMC.
• Ghost promotions: expired promotions remain active in the feed, generating clicks to offers that no longer exist on the site.
• Non-real-time local stock: LIA ads display products as available when they are no longer in-store. Experience degradation and budget waste.

Key takeaways

• The primary feed is the foundation, but it is not enough once the catalog exceeds a few hundred SKUs.
• Supplemental feeds correct and enrich, but fail silently when identifiers are desynchronized.
• The local inventory feed requires near real-time store stock synchronization.
• Product review feeds only have impact when review volume and quality are sufficient.
• Promotions not removed after expiration degrade conversion rate and Quality Score.
• In an agentic AI context, feed completeness and consistency directly determine product visibility in automated recommendation systems.

FAQ

How many Google Shopping feeds can be submitted simultaneously in Google Merchant Center?

There is no strict limit on the number of feeds. You can have a primary feed, multiple supplemental feeds, a promotions feed, a review feed, and a local inventory feed all active in parallel. The constraint is identifier consistency across feeds.

Can a supplemental feed replace the primary feed?

No. A supplemental feed cannot create new products. It can only add or modify attributes for products already present in the primary feed. Without a primary feed, the supplemental feed is inoperative.

What file format should be used for the Google Shopping feed?

Google Merchant Center accepts XML (Atom or RSS format), CSV/TSV, and the Content API for Shopping. XML is the most common for large catalogs. CSV is suitable for small manually managed catalogs. The API is recommended for real-time updates.

Is the product ratings feed mandatory to display stars in Shopping ads?

No. Google can also aggregate reviews from certified third-party sources (Trustpilot, Verified Reviews, etc.) or through the Google Customer Reviews program. The product ratings feed does provide finer control over which ratings are transmitted.

How to know if a supplemental feed is correctly applied?

In Google Merchant Center, check the supplemental feed diagnostics and verify the number of matched items. If that number is zero or well below the number of rows in your feed, there is an identifier matching issue.