What is supplemental feed?
A supplemental feed is a secondary data file that adds or overwrites specific attributes on products already present in your primary feed, matched by product id.
Worked example, not a result
Adding data your store platform cannot send
Say a primary feed carries 9,700 products straight from the store platform. It sends titles, prices, images and availability correctly, but it has nowhere to store a margin band, and the platform does not export a field for it.
A supplemental file solves that without touching the store. It contains 680 rows, each one a product id and a custom label naming that product's margin band. Merchant Center matches on the id and attaches the label to the existing item. The primary feed keeps updating price and stock as usual, and the extra field rides alongside it.
The same approach works for seasonal groupings, corrected titles on a handful of products, promotion ids, or filling in identifiers on a subset. It is the tidy way to fix a small set of products without asking a developer to change how the whole catalogue exports.
The counts here are an example.
Why it matters
Supplemental feeds are how a store gets campaign structure without rebuilding its product data. Custom labels for margin bands, seasonality or stock depth are what let a shopping account bid differently on products that deserve different treatment, and most store platforms have no natural place to store them.
That matters for the visitors lever because bidding the same way on a high margin best seller and a low margin clearance item wastes money on both. It also matters for speed. A supplemental file is a spreadsheet a marketer can maintain, so a change that would otherwise wait for a development cycle can happen the same day.
For a store owner it is a practical rule: keep the primary feed automatic and honest about price and stock, and use a supplemental file for the marketing layer on top. Mixing the two invites a manual value to override the truth.
Common mistakes
- Overriding price or availability from a supplemental file. Those two must come from the live store, and a static override quickly produces a mismatch with the landing page.
- Matching on the wrong id. The product id in the supplemental file must be exactly the id in the primary feed, including case, or the rows attach to nothing and fail silently.
- Building a supplemental file for something the primary feed could carry. If the store platform can hold the value, put it there once rather than maintaining a second file forever.
- Letting the file go stale. Rows for products that no longer exist do no harm, but missing rows for new products mean your newest items are the ones excluded from your campaign structure.
Related terms and answers
Your plan is free.
A person reads it. You keep the plan. No logins, no call first.