Definition
A supplemental feed is a secondary data source in Merchant Center that adds attributes to, or overrides attributes on, products that already exist in a primary feed. It is joined to the primary data by the id attribute, so every row has to carry an id that already appears there. It cannot create products, and it cannot serve on its own, which is exactly what makes it safe to experiment with.
A spreadsheet that fixes three problems without touching the app feed
- Column 1
- id, matching the identifier the primary feed already sends for each item
- Column 2
- custom_label_0, carrying the margin band the store calculates outside the platform
- Column 3
- gtin, filled in for a run of products whose barcodes were only ever recorded in a supplier spreadsheet
- Column 4
- title, rewritten for two hundred items being tested against the app generated titles
- Rows included
- Only the products being changed, since anything absent from the sheet keeps its primary feed values
- Connection
- A Google Sheet on a daily schedule, or a hosted file fetched on a set frequency
- Result in Merchant Center
- The primary feed still supplies everything else, with these four fields taking precedence where the sheet has a value
An illustrative sheet. The value of this pattern is that the platform integration keeps doing its job untouched, and a change can be reversed by clearing a cell rather than by rebuilding an export.
Why it matters
Supplemental feeds matter because the feed a store gets from its platform is rarely the feed the store needs, and rewriting the source is slow and risky. A supplemental data source lets you improve titles, add custom labels for campaign structure, fill in identifiers, correct a category, or exclude a group of products from one destination, all without asking a developer to change the export or waiting for an app update. They are also the practical way to bring in data that only exists elsewhere: cost of goods from an accounting system, sales rank from a reporting tool, or shipping weights from a warehouse. Because a row is only applied when the id matches, mistakes stay contained.
Where it goes wrong
- Sending ids that do not match the primary feed, usually a SKU on one side and a platform id on the other, so the sheet appears to be working while nothing is joined
- Trying to add products that the primary feed never included, which a supplemental source cannot do no matter how complete the row is
- Including a column with blank cells where the intention was to leave the value alone, since an empty value can clear an attribute rather than skip it
- Letting the sheet drift out of date, so a title test from last season is still overriding the live titles months after anyone remembered it existed
- Scheduling the supplemental fetch before the primary feed refreshes, which applies yesterday's overrides to today's products and produces mismatches that look like feed errors
Questions about supplemental feed
Can a supplemental feed remove products from Merchant Center?
Not by deleting them, but it can exclude them from destinations. Submitting the excluded destination attribute for a set of ids stops those products appearing in Shopping ads or free listings while leaving them in the account. That is the usual way to hold back items with poor margin, unreliable stock or a policy question, without changing anything in the store.
How is a supplemental feed different from a feed rule?
A feed rule transforms data that is already in the account, such as combining two attributes or mapping one value to another. A supplemental feed brings in data the account does not have. Use rules for logic you can express from existing fields, and a supplemental source when the information lives outside the platform entirely, such as cost of goods or a curated list of ids.
Do Shopify and WooCommerce stores need supplemental feeds?
Often yes, and for the same reason. The native integration on either platform sends a serviceable feed built from the fields the platform holds, which rarely includes margin bands, seasonal codes or hand-written titles for the products that matter most. A supplemental source lets you layer those on while leaving the integration to handle price, availability and the day-to-day sync.