Google Merchant Center supplemental feed: a practical setup guide

Your primary product source is doing most of the work. Then one attribute needs a separate owner, faster update cycle, or Google-specific value. Rebuilding the whole source adds risk. A Google Merchant Center supplemental feed gives you a second input for products already in Merchant Center.

Google calls feeds data sources. The UI label is supplemental data source. It adds or updates selected product data after a primary source creates the product record. Choose between a new input, a transformation, or a durable primary-source fix.

What a supplemental data source does#

A supplemental data source is a linked, secondary input. It can add details to an existing product or update details that Merchant Center already receives from a primary source. It cannot add products, remove products, or work by itself.

The default join key is the product ID, [id]. Each row in the supplemental source must use the exact ID that Merchant Center has for the product or variant. A supplemental row with an unknown ID has nothing to update.

For example, a merchandising team can keep a campaign label in a small source rather than regenerate a large primary file:

id,custom_label_0
SKU-COAT-BLU-M,holiday
SKU-COAT-BLU-L,holiday

Those rows can add custom_label_0 to matching products. They do not create the two products. The primary source must already contain them.

A supplemental source is useful when:

• a separate team owns a small set of attributes;
• a field needs a different update cadence from the main catalog;
• a Google-only label or classification should stay out of the core product record;
• a temporary, controlled correction needs to go live before the upstream system is changed;
• price or availability needs a focused update path, with the correct rule configuration.

Treat the last two as operational exceptions. If a title, price, availability value, or product fact is wrong everywhere, fix the system of record. A channel-side patch will otherwise be overwritten by the next primary refresh.

Supplemental source vs. primary source vs. attribute rules#

These features are related. They solve different problems.

Use a supplemental source when the data itself deserves a separate input. Use attribute rules when the value can be derived from data you already have.

For example, a separate sheet with campaign labels is a supplemental source. A rule that combines brand and product_type into a title is an attribute rule. A missing product variant belongs in the primary source.

How precedence works#

Do not assume that a supplemental source always wins. Merchant Center combines connected sources through its default and custom rules. The source order and the rule for the target attribute determine which value is used.

Google's Take latest option is designed for price and availability-related attributes. It is not a universal instruction to prefer every value in a supplemental source. For any other attribute, define the intended value with an attribute rule or leave the primary value in control.

If you connect more than one supplemental source, document the owner and precedence of every overlapping field. Two sources that both publish price, availability, or title create a troubleshooting problem before they create a data solution.

How to set up a Google Merchant Center supplemental feed#

The current setup follows this sequence.

1. Enable Advanced data source management#

In Merchant Center, open Settings, then Add-ons, and activate Advanced data source management. The Supplemental sources tab is available only after this add-on is enabled. The same add-on enables attribute rules.

Older instructions may send you to Products > Feeds. That is legacy navigation. Use Settings > Data sources in the current Merchant Center interface.

2. Start a supplemental source#

Go to Settings > Data sources, open the Supplemental sources tab, and select Add supplemental product data.

Choose the input that matches how the data is maintained:

• File for a scheduled or manually uploaded file source;
• Google Sheets for a small, collaborative dataset;
• Merchant API for a programmatic source with frequent updates.

A sheet is convenient for a short-lived campaign label. An API is a better fit when the same change is generated from an inventory or merchandising system. The input method does not change the matching requirement. The source still has to identify existing products correctly.

3. Prepare the rows and headers#

Include [id] and only the attributes you intend to add or update. In a file or sheet, the column is normally named id; [id] is Google's attribute notation. Keep the IDs stable. Use the product or variant ID that Merchant Center actually stores, including the exact variant-level value when the primary source submits variants separately.

A minimal title correction looks like this:

id,title
SKU-COAT-BLU-M,"Waterproof commuter jacket, navy, medium"

Use the current product data specification for the target attribute's format, length, accepted values, and country-specific requirements. A supplemental source does not relax those requirements.

For file and UI-based sources, the data source label and language need to align with the primary source you are linking. In particular, the feed label must match the primary source's label. For Merchant API sources, Google supports broader label and language configurations, so apply the Merchant API data-source guidance rather than copying the UI rule into API code.

4. Choose the match and link the primary source#

During setup, select [id] as the matching product ID unless you have a documented reason to use another attribute. Then select the primary data source that owns the products.

Custom matching can join on an attribute such as brand instead of [id]. Google makes that feature available to only a limited number of merchants, and its custom matching documentation sets a 30,000-row limit for a supplemental source using that join. It is an advanced exception. Stable product IDs are safer for most catalogs.

Select Create data source after choosing the primary source. The supplemental source cannot be useful until that link exists.

5. Add an attribute rule only when the merge needs one#

If the supplemental data should be selected conditionally, combined with another value, or given explicit precedence, open the linked product source and its Attribute rules tab.

The practical sequence is:

1. Select the target attribute.
2. Add the source, static value, condition, or modification that should define it.
3. Save the rule as a draft.
4. Select Test rules and inspect the sample output.
5. Select Apply changes only after the result is correct.

Rules run in a cascade. A later rule can change the value produced by an earlier one. Keep each rule narrow and record why it exists. This makes a temporary campaign patch easy to remove and makes a permanent mapping easier to move upstream.

6. Use the current API for programmatic setup#

For a programmatic workflow, use the Merchant API data-sources guide. It shows how to create a supplementalProductDataSource and link it to a primary source through the primary source's default rule.

Do not build a new integration from the old Content API supplemental-feed examples. Google says the Content API for Shopping reached its sunset on August 18, 2026, and its replacement is the Merchant API. Existing integrations should follow Google's migration and sunset guidance.

When updating an API default rule, preserve the primary source reference as well as the supplemental references. The API documentation warns that a patch replaces the complete default-rule configuration. Omitting the primary reference can cause the primary source's attributes to be ignored.

Validate the result before relying on it#

Uploading a file is only the first checkpoint. Validate the join, the resulting attribute, and the customer-facing offer.

Check the source configuration#

• The supplemental source is linked to the intended primary source.
• The [id] header is mapped correctly.
• Every ID exactly matches an existing product or variant in Merchant Center.
• The data source label and language match the intended primary source when using the UI flow.
• The file, sheet, or API payload contains valid headers and values for each changed attribute.
• The source contains updates for existing products only.

Check the processed product#

After Merchant Center processes the source, inspect a changed item and its issue details. Confirm that the expected attribute appears in the resulting product data. If you used a rule, inspect the tested output before applying it, then check the item after reprocessing.

A successful API response or an accepted upload means Google accepted the data for processing. It does not mean the item is approved for every destination or eligible to show. Review the item-level issues and the relevant destination status.

Check the offer against the storefront#

For price and availability changes, compare all customer-facing representations:

• the value in Merchant Center;
• the product landing page;
• the page's structured data;
• the value at checkout.

Google's product data specification treats these as connected requirements. A supplemental value that disagrees with the page can create a mismatch even when the source processed successfully.

Troubleshoot common supplemental-feed failures#

The Supplemental sources tab is missing#

The Advanced data source management add-on is not enabled, or your account does not have access to the feature. Check Settings > Add-ons first. If you work in a multi-client account, confirm whether the source is being managed at the parent or sub-account level. Google can apply sources and rules across associated accounts, but an override at one level can prevent a source from being linked at another.

The source processed, but zero products changed#

Start with the join. Compare a supplemental [id] with the exact ID on the corresponding Merchant Center item. Look for a variant mismatch, a stale export, a wrong delimiter, or a header that was not mapped to [id].

If the IDs match, inspect the source link and the rule output. A source that is created but not linked cannot enrich the primary records. A rule may also be selecting the primary value, or a later rule may be replacing the supplemental value.

The wrong value appears after the update#

Check which source and rule provide the target attribute. Merchant Center's default rule takes values according to its configured source order, and custom attribute rules can change that result. Do not add another supplemental source until you know which existing rule is winning.

For price or availability, confirm that you used the intended latest-value behavior and that the page, structured data, and checkout all show the same offer. If the primary source refreshes more often, it may replace a temporary patch unless the rule configuration explicitly supports the update.

Products are disapproved after a supplemental update#

A supplemental source can add or change data, but it cannot bypass product-data requirements or policies. Open the issue details for the affected item. Check the changed attribute against the product specification, then check the landing page, identifiers, images, variants, shipping, and policy requirements that apply to the product and country.

Fix a recurring error in the upstream product record. Use the supplemental source for a bounded channel update, not as a permanent hiding place for bad data.

API requests fail or old examples stop working#

Check that the integration uses the Merchant API rather than the sunset Content API. Then inspect the data-source name, account ID, OAuth scope, default-rule payload, and label or language configuration. A newly created source can also take a short time to become available for subsequent API operations.

Where Catalog fits#

A supplemental source is a Google-side patch layer. It is useful for a narrow exception. Repeated patches usually point to a product-data governance problem upstream.

We help teams structure, normalize, and enrich live product data before it is sent to channels and AI shopping surfaces. Our product feed management perspective explains that upstream layer in more detail. We complement Merchant Center. We are not a primary or supplemental Merchant Center source, and we do not replace Google's validation or approval workflow.

If the same title, variant, material, or compatibility fact must be repaired for Google, marketplaces, and AI surfaces, keep that fact in a shared product-data layer. Then map the approved record into each destination and reserve a Google supplemental source for the exceptions that belong only in Google.

FAQs#

Can a supplemental source add products to Merchant Center?#

No. A supplemental source can update or enrich products that already exist in a linked primary source. Add or remove products through a primary data source.

Do I need a primary source before creating a supplemental source?#

Yes. A supplemental source cannot run standalone. It must be linked to a primary source that contains the products it will update.

What is the difference between a supplemental feed and attribute rules?#

A supplemental feed, now called a supplemental data source, is a separate input. Attribute rules transform, combine, filter, or select values from connected sources. You can use both when a separate dataset also needs conditional logic.

Does the supplemental source always override the primary source?#

No. The configured default rule and any attribute rules determine the result. Take latest is for price and availability-related attributes, so it should not be treated as a global override switch.

What should I use to match products?#

Use the exact [id] value that Merchant Center has for each product or variant. Custom matching on another attribute is limited to eligible merchants and has a documented 30,000-row limit.

Is the old Content API still the right way to create a supplemental feed?#

No. Use the current Merchant API for new programmatic work and migrate existing Content API integrations. The Content API for Shopping reached sunset on August 18, 2026.

If recurring Google patches are exposing gaps in your shared product data, explore Catalog as the product-data layer behind cleaner channel and AI-commerce outputs.