How a supplemental feed works
A supplemental feed sits on top of the catalogue rather than forming it. It contains a product identifier and whichever attributes you want to add or change, and Merchant Center joins it to the main catalogue by matching that identifier exactly. Where a match is found, your values are applied; where none is found, the row is ignored.
The boundary is worth stating plainly: it cannot create a product and it cannot delete one. Only the primary feed decides what exists. A supplemental feed edits, enriches and excludes from destinations, which covers most of the day-to-day corrections a shop needs.
It can come from a Google Sheet, a scheduled file fetch, an upload or the API, and it has to be applied to the specific primary feeds you want it to affect. Applying it to the wrong one is the reason a perfectly good supplemental feed sometimes appears to do nothing at all.
Why supplemental feeds matter
They let you improve product data without waiting for a developer. Titles that read like internal stock names can be rewritten for the way customers actually search, missing brand or category values can be filled in, and a promotion can be attached to a set of products for as long as it runs.
Their most useful job is segmentation. Custom labels added by supplemental feed — margin band, season, bestseller, clearance — give campaigns something meaningful to bid on, and none of that information usually exists inside a shop platform’s default export.
Common mistakes with supplemental feeds
Identifier mismatches account for most failures. A stray space, a different letter case, a prefix the export adds, and the join silently finds nothing while the feed still reports as processed. Always test with a handful of known products before trusting a whole file.
The larger mistake is strategic: using a supplemental feed as a permanent patch for data that is wrong at source. If your shop stores bad titles, every channel you ever sell on inherits them, and only Google gets the corrected version. Fix the shop where you can and let the supplemental feed handle the things the shop genuinely cannot express.
Then there is staleness. Sale prices and promotion tags left in place after a campaign ends create mismatches with the website, which is a disapproval rather than an oversight. Give every temporary override an end date and an owner.
How to use one well
Keep each supplemental feed to a single purpose — one for custom labels, one for title improvements, one for a promotion — so you can see at a glance what is overriding what. Confirm it is applied to the right primary feeds and to the right countries.
Test the join on known products, check the final values in the product view rather than in your source file, and review the overrides on a schedule so nothing outlives its purpose. Treat it as ongoing feed management, not a one-time fix: the products change, the promotions end, and an override nobody remembers is the hardest kind of problem to diagnose later.
