Data Source Types in Merchant Center Next (2026)

Managing a product feed in Google Merchant Center starts with understanding which type of data source you are working with. In Merchant Center Next, "feeds" are now called data sources. Three types exist: primary, supplemental, and automatic website crawl. Most merchants only use the first. The other two unlock significant data-management capabilities — but both are hidden behind an add-on that is not in the default UI, which is why most feed managers have never encountered them. The definitional foundation — required vs optional attributes, unique identifiers, and what a data source actually contains — lives in what is a product feed in Google Merchant Center. This pillar covers the operational layer: how you manage, refresh, automate, layer, and migrate data sources at scale.

Primary data sources support 5 input methods: file upload (SFTP or Google Cloud Storage), Google Sheets, scheduled fetch, Merchant API v1, and automatic website crawl. Supplemental data sources support 4 of those 5 — automatic website crawl is not available for supplemental sources. Both supplemental data sources and attribute rules require the Advanced data source management add-on, which is not visible in the default Merchant Center Next interface. Enable it under Settings → Add-ons before you look for either feature.

Key Takeaways: Managing and Automating Product Feeds

The Three-Layer Feed Stack Most Merchants Never Use

Feed management in Merchant Center Next operates on three layers — and most merchants are only running the bottom one. The bottom layer is the primary data source: the main upload or API push that defines every product in your catalog. This is what most teams build, export, and call "the feed." Above it, two additional layers exist that the vast majority of merchants have never touched, because both are hidden behind the Advanced data source management add-on: supplemental data sources (a separate input file that overrides or adds specific attributes on a per-product basis) and attribute rules (a transformation layer within a source that remaps fields, standardizes values, sets conditional logic, and derives new attributes from existing ones).

The key operational insight: you do not need to rebuild your ERP export every time you want to augment product data. Supplemental data sources and attribute rules provide a separation-of-concerns layer, letting a feed manager fix, enrich, or segment data above the primary source without touching the underlying system. For ecommerce teams that manage both the platform export and the campaign data, this architecture is the difference between a fragile monolithic feed and a modular pipeline that survives platform migrations, promotional campaigns, and attribute spec changes without a full rebuild.

The Shopping feed management team at MB Adv Agency starts every GMC audit by confirming which layers are active. In most accounts the answer is: primary only. The Advanced data source management add-on is almost universally not enabled, even in accounts with large catalogs where the supplemental-source and attribute-rules layer would deliver immediate value — correcting title spec violations, adding custom label segmentation from an internal pricing sheet, or overriding Google product category assignments for specific SKU ranges. The first step: Settings → Add-ons → Advanced data source management. For deeper work on what attributes actually belong in the primary feed, see what is a product feed in Google Merchant Center. For our full Shopping feed management service, see Google Shopping feed management.

Attribute Rules (Formerly Feed Rules): The Rename That Confuses Most Merchants

If you have searched "feed rules google merchant center" and found nothing in the Merchant Center Next UI, you are not looking in the wrong place — you are using the wrong vocabulary. Feed rules were renamed to attribute rules in Merchant Center Next. The feature persists; the name and location both changed. Attribute rules are now part of the Advanced data source management add-on (Settings → Add-ons), and they share that add-on gate with supplemental data sources. Neither feature is in the default navigation. According to the official attribute rules help page, merchants must "add the Advanced data source management add-on" to enable this feature.

What attribute rules do: they transform data within a data source at the attribute level — remapping fields (your ERP exports "Colour" but Merchant Center expects "color"), standardizing values (normalizing size formats across product lines), setting conditional logic (apply a specific google_product_category when a title contains "running shoe"), stripping prohibited text (promotional language in a title column before it reaches the spec check), or deriving new attributes from existing ones (concatenate brand + product type to build a cleaner title). Attribute rules do not add products to the catalog — they only transform attributes for products already in the data source.

What supplemental data sources do (and why they are different): a supplemental data source is a separate input file that Google merges with the primary source on a per-product basis, matched by product ID. It overrides or adds specific attributes without replacing or rebuilding the primary. The typical use case: adding custom_label_0 margin-tier values from an internal pricing sheet, or injecting promotional override titles during a sale period, without touching the ERP export that drives the primary source. The supplemental source is an input file — it does not transform data that is already there.

Feed Freshness: The 30-Day Expiry Clock and Update Cadence

Products in Merchant Center Next expire 30 days after the last refresh. This is the hard ceiling that every feed pipeline must clear — products do not vanish instantly at day 30, but they move to an "Expiring" status, then get disapproved, and then stop serving in Shopping results. The result is a silent traffic drop: impressions fall, revenue drops, and the cause is not visible in campaign dashboards until someone checks the Merchant Center Products tab and sees a wave of disapprovals. This is the most common feed-pipeline failure the team at MB Adv Agency encounters in new account audits. See our ecommerce PPC audit for the full feed pipeline checklist.

Beyond the 30-day ceiling, Google recommends daily updates as the baseline for price and availability accuracy. For promotions — flash sales, time-limited discounts, live inventory changes — Google states "multiple times a day." The table below shows the three cadence tiers and what happens at each boundary. The chart above this section visualizes the maximum safe interval in hours at each tier: 720h (30 days hard ceiling), 24h (daily recommended baseline), 12h (the minimum of "multiple times a day" — i.e., at least 2 times per day).

For the full disapproval workflow — what happens after a price mismatch triggers a PID, how to diagnose availability discrepancies, and how to clear account-level warnings — see debugging feed disapprovals and errors in Merchant Center.

Scheduled Fetch: How Google Pulls Your Feed Automatically

A scheduled fetch is one of the five input methods for a primary data source — and one of four available for supplemental data sources. Instead of pushing a file to Merchant Center manually or via SFTP, you give Google a URL and a schedule; Google fetches the file from that URL automatically. According to the scheduled fetches help page, the default frequency is every 24 hours, and the schedule can be adjusted for more frequent pulls. This makes scheduled fetch the simplest automation path for merchants whose platform exports a static file to a predictable URL on a nightly job — the most common setup for Shopify, WooCommerce, and BigCommerce stores that have not installed a native Google integration app.

The scheduled fetch workflow: set up a data source in Merchant Center Next → choose "Scheduled fetch" as the input method → enter the URL where your platform exports the feed file (must be publicly accessible or password-protected with credentials Google can use) → set the fetch schedule. Google fetches on its own schedule after that. For stores with real-time price or inventory changes, the scheduled fetch default of 24h is sufficient for the 30-day expiry requirement but not sufficient for flash sales — for promotional periods, supplement with Merchant API event-driven pushes on price/stock change events.

Automatic Item Updates: The Safety Net, Not the Solution

Automatic item updates are on by default in Merchant Center Next. They work by reading schema.org structured data and visible page content on your product landing pages — using advanced extractors that combine schema.org annotations with statistical models and machine learning — to update price, sale price, availability, and condition in the feed automatically. The toggle is under Products → Automations. They are a safety net: they catch drift between your submitted feed and your landing page. They are not a data source. The official documentation states this explicitly: "Automations are not a replacement for regular updates of your product data. They're designed to fix temporary problems with your price, availability, and condition accuracy for a small percentage of your products."

The most common misconfiguration: a merchant enables automatic item updates, lets the primary feed go stale over several weeks, and assumes the automations are keeping the feed current. They are not. Automatic item updates handle small drift for a small percentage of products. If the primary feed is significantly stale or the landing-page markup is absent or JavaScript-rendered (which reduces detection accuracy), the safety net fails silently. The correct architecture: primary data source (refreshed daily or more often) → schema.org Offer markup on landing pages (server-rendered for highest accuracy) → automatic item updates catching residual drift as a background supplement.

Merchant API v1 Migration: The August 18, 2026 Deadline

The Content API for Shopping shuts down on August 18, 2026. This is a hard deadline — there is no grace period. The Merchant API v1 went generally available in July 2025 and is the current developer standard for all programmatic product data submission. Any Merchant Center data source that shows "Content API" as its input method will stop working on August 18, 2026. The v1beta was already shut down on February 28, 2026 — any integration that had not migrated from v1beta to v1 by that date is already broken.

For merchants on Shopify, WooCommerce, or BigCommerce, the migration is handled by the platform's integration app — it is the app vendor's responsibility, provided the merchant is on the current app version. For any merchant with a custom integration, a third-party PIM, or an agency-built API push that shows "Content API" in their Merchant Center data sources, the migration to Merchant API v1 is a developer task. The endpoint structure changed and authentication works differently — this is not a drop-in swap. Scope the migration now. Our PPC campaign management team handles Merchant API migration engagements as part of feed infrastructure work. See also ecommerce PPC audit to identify whether your account still uses Content API.

Connecting Shopify, WooCommerce, and BigCommerce to Merchant Center

Each major ecommerce platform has a free, official integration app for Google Merchant Center. App names in this ecosystem have changed more than once — and integration guides that reference "Google channel" (old Shopify name) or "Google Listings & Ads" (old WooCommerce name) are outdated. The current names as of 2026-06-30:

Shopify: the app is called "Google & YouTube" (available in the Shopify App Store — also confirmed in official Google Merchant Center documentation). The old name "Google channel" is deprecated. The old name "Google Shopping" is even older. Always search the Shopify App Store for the current name before following any integration guide.

WooCommerce: the plugin is called "Google for WooCommerce" (plugin slug: google-listings-and-ads on the WordPress Plugin Directory, but display name updated to "Google for WooCommerce"). The old display name "Google Listings & Ads" is outdated. Version 3.7.2 was released June 29, 2026. Merchants must be on the current version as of August 1, 2026. 800,000+ active installations as of June 2026.

BigCommerce: the native integration is "Ads and Listings on Google" (free, available in the BigCommerce App Marketplace). Once your platform connection is live, the next step is connecting Merchant Center to Google Ads to run Shopping campaigns and Performance Max. That integration is covered in linking Merchant Center with Google Ads. And for Shopping campaign setup and PPC management once the feed is connected, see PPC campaign management.

AI in Product Feed Management: Google Native vs Third-Party Tools

Google's own AI tools in Merchant Center Next restructure the feed management layer in four distinct ways: automatic item updates (background price/availability sync via schema.org and advanced extractors), AI-generated title and description suggestions via the structured_title and structured_description attributes (merchant reviews before publishing), Product Studio (image generation, background removal, video animation, AI text — free in AU/CA/IN/JP/UK/US), and Conversational Attributes (shipped January 2026, optimizes product descriptions for AI Overviews, AI Mode, and Gemini Shopping surfaces — the official help page confirms the January 2026 ship date).

Third-party AI feed optimization tools — DataFeedWatch, Feedonomics, Channable, and others — build optimization layers on top of the primary data source, treating product title, category, and attribute signals as the primary Shopping ranking mechanism. The phrase "the feed is the new keyword" — meaning that attribute optimization drives the same targeting outcomes in Shopping that keyword selection drives in Search — is attributed to third-party practitioners including Optmyzr, Store Growers, and ZATO. It is a useful frame; it is not an official Google formulation and should not be attributed to Google. Third-party tools sync into Merchant Center via Merchant API v1 or scheduled fetch.

For the optimization work that happens once the feed pipeline is live and accurate — title structure, image specifications, and listing quality improvements that move the needle in Shopping auctions — see best practices for optimizing product feeds. For the full Merchant Center programs that benefit from a clean feed — free listings, Shopping ads, Local Inventory Ads — see overview of Merchant Center programs.

How to Manage and Automate Your Product Feed: Step-by-Step

The eight steps below represent the operational checklist for building a well-managed, automated, and migration-ready feed pipeline in Merchant Center Next. Steps 1 and 5 are the minimum viable baseline; steps 2–4 unlock the Advanced layer; steps 7–8 cover integrations and API migration.

Common Misconceptions About Merchant Center Feed Management

Misconception 1: "Feed rules disappeared from Merchant Center." They did not. Attribute rules are the renamed version of feed rules. The rename happened as part of the Merchant Center Next migration. In classic Merchant Center, feed rules were a prominent feature accessible from the main feed navigation. In Merchant Center Next, the feature persists as attribute rules — but the name changed, the location changed (now under the Advanced data source management add-on in Settings → Add-ons), and the framing changed (attribute rules are unified with supplemental data sources under the same add-on gate). Merchants searching "feed rules google merchant center" in the Merchant Center Next UI find nothing — because the name is now "attribute rules" and the path is Settings → Add-ons → Advanced data source management → [your data source] → Attribute rules. The capability is the same. The path changed.

Misconception 2: "Supplemental data sources are in the default Merchant Center Next UI." They are not. Both supplemental data sources and attribute rules require the Advanced data source management add-on. If you open Merchant Center Next and do not see a way to add a supplemental data source or configure attribute rules, you have not enabled the add-on. This is the most consistent source of confusion for merchants who used supplemental feeds in classic Merchant Center and upgraded to Merchant Center Next — the feature did not disappear, it moved behind an add-on gate. Enable the add-on first.

Misconception 3: "Automatic item updates handle feed freshness." They do not — not at scale, not as a substitute for active feed management. Automatic item updates are a safety net for small drift in a small percentage of products. They are not a data source. Running automatic item updates as your only freshness mechanism while letting the primary feed go stale produces price-mismatch disapprovals and account-level warnings. The correct mental model: primary data source keeps the catalog current; automatic item updates catch the residual drift that slips through. The official documentation is explicit on this point.

Misconception 4: "The Shopify app is called Google channel." "Google channel" is the old Shopify app name. The current app is "Google & YouTube", available in the Shopify App Store. Any integration guide referencing "Google channel" is outdated. Similarly, any guide referencing "Google Listings & Ads" for WooCommerce is outdated — the current name is "Google for WooCommerce." App names in this ecosystem have changed multiple times; always verify in the relevant app marketplace before following an integration guide.

Supplemental Data Sources: Override Attributes Without Rebuilding the Primary

The supplemental data source pattern solves a specific operational problem: your primary data source is a nightly export from your ERP or ecommerce platform, and you need to enrich, correct, or segment specific attributes without touching that export — because the export is automated, shared with other systems, or managed by a separate team. A supplemental data source is the answer: it is a second input file (in the same format as your primary — TSV, XML, or Google Sheets) that contains only the products and attributes you want to override or add, matched by product ID.

Practical use cases for supplemental data sources: (1) Custom label injection — add custom_label_0 through custom_label_4 values from an internal margin-tier or promotional-priority sheet that does not exist in the ERP. These labels drive campaign segmentation in Shopping and Performance Max without any change to the primary feed. (2) Title correction — override specific product titles that violate the spec or perform poorly in Shopping, without rebuilding the full catalog export. (3) Google product category override — correct the category assignment for specific product ranges where the auto-assignment from the ERP is wrong, without touching the ERP schema. (4) Promotional attribute injection — add sale_price or sale_price_effective_date for promotional periods via a supplemental source that is active only during the sale window.

The supplemental data source requires the Advanced data source management add-on. Once enabled, you add a supplemental source the same way you add a primary source — file upload, Google Sheets, scheduled fetch, or Merchant API v1. The supplemental source merges with the primary at the product ID level; attributes in the supplemental source override the same attribute in the primary for the matched products. Products in the supplemental source with no match in the primary are ignored. For campaign strategy once your feed is clean and optimized, our Google Shopping feed management team handles the full pipeline — from supplemental source configuration to PPC services for ecommerce accounts.

Product Feed Management FAQ

Methodology

This pillar consolidates six absorbed Google Merchant Center pages: using-feed-rules-in-google-merchant-center (15 GSC impressions, avg pos 26.07); how-to-use-supplemental-feeds-for-advanced-optimization (0 impressions); automating-feeds-with-scheduled-fetches (0 impressions); how-often-should-i-update-my-product-feed (0 impressions); the-role-of-ai-in-feed-management-and-optimization (121 impressions, avg pos 11.8 — top keyword "ai feed optimization"); integrating-merchant-center-with-e-commerce-platforms (0 impressions). Combined GSC footprint: 136 impressions across 90 days (2026-04-01 through 2026-06-30). Source: data/google-merchant-center/managing-and-automating-product-feeds.json.

All platform-mechanic claims (add-on gate, input methods, freshness intervals, API migration dates, platform app names) were web-verified on 2026-06-30 against official Google Merchant Center Help (support.google.com/merchants) and Merchant API developer documentation (developers.google.com/merchant). Key corrections from web verification: (1) WooCommerce plugin display name is "Google for WooCommerce" (formerly "Google Listings & Ads" — rebranded); (2) Merchant API v1 GA date is July 2025 (not August 2025 as stated in some earlier documentation). No mbadv client metrics are used — per anti-fabrication policy, the MB Adv Agency POV stays qualitative. Platform market share data sourced from StoreLeads (13.6M stores tracked, August 2025) via redstagfulfillment.com — the relative ranking (WooCommerce > Shopify > BigCommerce) is consistent across all major sources.