feedsmerchant-centerproduct-data

Supplemental feeds: enrich product data without forking the primary feed

Add labels, titles and identifiers through supplemental feeds without replacing the primary catalog—and protect every link during API migrations.

The short version

Keep your commerce platform or feed tool in charge of the primary feed. Add campaign labels, improved titles, verified identifiers and other targeted corrections through a supplemental source keyed to the same processed product IDs.

Treat a new primary data source as a migration event, not a harmless replacement. Snapshot source IDs, rules, labels and joins before a cutover; then prove that every dependency still works.

Use a supplemental source for enrichment, not reinvention

A primary feed carries the complete offer: identity, title, description, price, availability, URLs, images and market context. Rebuilding it just to add a few attributes means taking ownership of every field, refresh and platform rule the original generator already handles.

Use a supplemental source when you need to:

  • add custom_label_0–custom_label_4 for campaign segmentation;
  • fill verified GTINs, MPNs or brands;
  • test titles on a controlled product set;
  • add promotion or seasonal attributes with an expiry date;
  • apply a reversible merchandising experiment.

Do not use one to hide a broken primary feed, invent availability or publish a price that differs from the product page or checkout.

Keep the primary feed owned by its generator

A fork creates three avoidable risks:

  1. Large blast radius. One malformed replacement can remove or corrupt the catalog.
  2. Silent drift. The fork falls behind new variants, markets, fields or plugin behavior.
  3. Unclear ownership. Operations fixes the store, marketing fixes the fork, and neither reliably matches the other.

Leave the primary in place. Make the smallest possible supplemental change and keep the rule that generated it beside the feed pipeline.

Protect source identity during API and app migrations

Google's Merchant API can continue using existing Content API-created data sources. The danger appears when an app or migration path creates a new primary source instead of preserving the old source identity.

Source-scoped configuration may stay attached to the old source. Attribute rules can stop applying, supplemental sources can stop enriching products, feed-label-bound campaigns can lose inventory, and changed item IDs can break exclusions, remarketing or cart-data joins.

Before a cutover, snapshot:

  • primary data-source ID;
  • feed label and language;
  • attribute rules;
  • supplemental-source links;
  • processed item-ID format;
  • label-bound campaign selection;
  • item-ID exclusions;
  • remarketing and cart-data IDs.

After the cutover, diff the snapshot. If a new primary source appeared, rebuild or relink every source-scoped dependency and verify the processed products before trusting campaign coverage.

Design the supplemental source at offer-ID grain

The join key is the contract. Use the exact processed product ID expected by the destination, including channel, language, country or feed-label context where those fields form the identity.

Before upload:

  1. Export the destination's current processed product IDs.
  2. Match the proposed enrichment to those IDs.
  3. Count matched, unmatched and duplicate rows.
  4. Stop if the match rate is lower than expected.
  5. Keep the pre-change extract as the rollback baseline.

A row with the wrong ID does nothing. A row matched to the wrong variant can confidently publish the wrong title, label or identifier.

Split changes by purpose and owner

Do not turn one supplemental file into an ungoverned patch drawer.

Source Carries Refresh Owner Rollback trigger
Campaign labels Margin, season, experiment labels Daily Paid media Segment membership is wrong
Identifier fills Verified GTIN, MPN, brand Weekly Catalog ops Identifier mismatch appears
Title test Controlled title overrides Daily Merchandising Eligibility or conversion degrades
Promotion layer Sale labels and dates Hourly or daily Trading Promotion ends or prices diverge

Each source needs a field allowlist. Reject a campaign-label file that unexpectedly contains price or availability.

Make every change reversible

Record the product population and exact IDs, original and replacement values, calculation rule, owner, effective date, verification condition, rollback condition and expiry date.

Start with a small but commercially meaningful sample. File acceptance is not the result: inspect processed products, item issues, eligibility and serving after the platform applies the source.

Protect parity after every override

Compare a value-weighted sample across:

  1. the processed feed instance after primary and supplemental sources combine;
  2. the rendered page and structured data for the exact variant;
  3. checkout.

Price, currency, availability, identifiers and variant identity must agree. A campaign label may be invisible to shoppers, but its source rule still needs a reproducible business definition.

Deploy in a controlled sequence

  1. Inventory every primary, supplemental and API-written source.
  2. Define the target products, fields and expected match count.
  3. Build a file containing only the ID and approved enrichment fields.
  4. Validate IDs, duplicates, lengths, formats and allowed values.
  5. Upload a limited sample where possible.
  6. Confirm the platform combined the sources as expected.
  7. Inspect item diagnostics and the exact products used by campaigns.
  8. Compare feed, page and checkout for high-value variants.
  9. Expand only after the acceptance checks pass.
  10. Save the successful extract and membership counts as the baseline.

Run the free product feed scanner before upload. Then verify processed products inside the destination platform; a valid file proves syntax, not correct matching or serving.

Know when to fix the source instead

Move a change into the primary source when it becomes universal, stable and owned by catalog operations. Keep destination-specific campaign labels and short-lived experiments supplemental. Promote durable product truth upstream so every channel receives the same fact.

Sources