What is a Merchant Center supplemental feed?

A supplemental feed is a data source that modifies products already in your primary feed. It works by matching on the item id, so every row in the supplemental file has to correspond to a product that already exists in the main one.

That matching rule is the whole mechanic. A supplemental row with an id that does not exist in the primary feed does nothing at all, silently. This is the first thing to check when a supplemental feed appears to have had no effect.

What it can do to a matched product is add an attribute that was missing, or replace one that was present with a different value. So a primary feed generated automatically by your ecommerce platform can be corrected without touching the platform or the integration.

This is why it exists. Most stores have a primary feed produced automatically from the catalogue, and no easy way to change what it contains. A supplemental feed sits on top and lets you fix specific attributes on specific products, which is much faster than rebuilding the catalogue data or replacing the integration.

It is a layer, not a replacement. The primary feed remains the source of which products exist and what most of their data says.

The limits are worth knowing before you plan work around it, because two of them catch people out.

It cannot add products. If an item is not in the primary feed, no supplemental feed will bring it into the account. New products have to come from the primary source.

It cannot work alone. There has to be a primary feed for it to attach to.

It is applied per feed, so if you have several primary feeds, you need to be deliberate about which one the supplemental applies to. Attaching it to the wrong one is another silent failure.

What it can do is broad. Add or replace titles, descriptions, images, identifiers, categories, custom labels, sale prices, promotion associations, availability and most other attributes. It can also exclude specific products from particular destinations, which is a useful way to hold products out of shopping ads while leaving them in the account.

The practical consequence is that a supplemental feed is a correction tool. It is excellent for fixing what a generated feed gets wrong, and it is not a way to build a catalogue.

Four uses cover most of what stores actually need, and each of them is hard to do any other way.

Rewriting titles. This is the highest-value use. A generated feed usually carries your internal product names, which do not match what shoppers type. A supplemental sheet with two columns, item id and a rewritten title, fixes an entire catalogue's worth of titles without touching the store.

Adding identifiers. Missing trade item numbers or part numbers are a common source of disapprovals and reduced visibility, and they often live in a spreadsheet from a supplier rather than in the ecommerce platform. A supplemental feed puts them into the account directly.

Adding custom labels for campaign structure. Tagging products by margin band, seasonality, bestseller status or stock depth lets you build campaigns around commercial reality rather than around category names. Those labels rarely exist in the catalogue, and this is the clean way to add them.

Excluding products. Items you sell but do not want in shopping ads, such as very low margin lines or items with unreliable stock, can be held out without deleting them.

All four are cases where the correct data exists somewhere in your business, just not in the ecommerce platform.

The simplest workable version is a spreadsheet with the item id in the first column and one column per attribute you are overriding, connected as a scheduled fetch so changes propagate without a manual upload.

Only include the attributes you are changing. Blank columns and unnecessary attributes create more ways for the file to go wrong. A title-fixing feed should be two columns.

Get the item ids exactly right, including case and any prefixes your platform adds. Most supplemental feeds that appear to do nothing are failing on the id, and the diagnostic is to check how many items were matched after processing rather than assuming.

Set the fetch frequency to match how often the data changes. A title override sheet can update weekly. A sale price override needs to keep pace with the promotion.

The biggest ongoing risk is drift. New products added to the store are not in your supplemental sheet, so they keep the generated title while everything else has a corrected one. Build a routine that checks for products in the primary feed with no supplemental row, and add them, or the benefit erodes month by month.

A supplemental feed is one of three ways to change feed data, and choosing the wrong one creates work.

Feed rules apply logic inside Merchant Center: take this attribute from that field, append a value, set a default when empty, find and replace. They suit changes that follow a pattern across many products, such as prefixing every title with the brand name or mapping your categories to the standard taxonomy. They need no external file and they apply automatically to new products, which is a real advantage.

A supplemental feed suits changes that are specific per product and cannot be derived by a rule. A rewritten title, a supplier's identifier, a hand-chosen label.

Fixing the source is the third option and often the right long-term answer. If your product titles are wrong in the feed because they are wrong in the catalogue, changing them in the ecommerce platform improves the feed, the product page, the search listing and the shopper's experience at the same time. A supplemental feed only fixes one of those.

So the rule of thumb is: fix the source where the data should have been right anyway, use a rule where the change follows a pattern, and use a supplemental feed for the per-product corrections that neither of the others can reach.