Skip to content

Supplemental feed: what it is and when to use it without breaking your catalog

A beginner-friendly guide to enriching existing products in Google Merchant Center and other catalog workflows without rebuilding your primary source.

J

Julia Villegas

· 9 min read · 247 views
Supplemental feed with products and catalog data layers

A supplemental feed is a secondary product data source that adds or updates information for items already present in your primary product feed. It is useful when you need to complete attributes, fix titles, add campaign labels, or enrich data for Google Shopping without changing your store, ERP, or original catalog every time.

What is a supplemental feed?

A supplemental feed does not replace your main product catalog. It adds a layer of information on top of it. In Google Merchant Center, the primary data source is the one that contributes the products, while a supplemental source can help complete or modify data for products that already exist.

Google’s documentation on product data sources separates the role of sources that provide products from sources used to support or complete product data. For beginners, the easiest way to understand it is this: a supplemental feed is not a second catalog. It is a matching table that enriches your base catalog.

For that matching to work, the system needs to know which row belongs to which product. That is why the product identifier must match the one used in the primary feed. In practice, this means the same ID, the same product context, and consistent language or country settings when they apply.

Source type What it does What it is useful for What it should not do
Primary feed Provides or creates products Sending the base catalog with ID, title, image, price, availability, and required attributes Depending on another source for the product to exist
Supplemental feed Enriches existing products Adding labels, correcting attributes, completing fields, or overriding selected data Creating new products that are not in the primary feed

If a product appears only in the supplemental feed but does not exist in the primary feed, you should not expect it to be created as a new item. The supplemental source needs an existing product to match against.

When a supplemental feed makes sense

A supplemental feed is useful when your primary catalog works, but it is missing information that marketing, merchandising, or performance teams need. Instead of requesting changes in the ecommerce platform, ERP, PIM, or original export, you can maintain a more flexible enrichment layer.

Common use cases include:

  • Adding custom labels for margin, seasonality, campaign priority, or merchandising focus.
  • Completing attributes that do not exist in your store, such as promotion type, collection, material, style, or an internal price range.
  • Adjusting titles or descriptions for selected products without changing the ecommerce product page.
  • Creating product segments that can later be used in campaigns, rules, or exports.
  • Adapting data for a specific channel without changing the catalog used by every other destination.

Imagine your online store has thousands of products. Your primary feed already includes product ID, title, price, image, link, and availability. It works, but the marketing team wants to distinguish between “gifts under 30,” “high-priority items,” and “clearance products.” Those fields do not exist in the store, but they are useful for campaign structure.

A supplemental feed might include columns like this:

id campaign_label priority gift_price_range
SKU-001 holiday high under_30
SKU-002 clearance medium under_50
SKU-003 evergreen low over_50

The product SKU-001 already exists in the primary feed. The supplemental feed does not create it. It only adds extra information that can later help you filter products, create sets, or apply export rules.

What a supplemental feed cannot do

The most common mistake is thinking that a supplemental feed is a quick way to “upload a few extra products.” It is not. If you need to add new products, they should come from the primary feed or from another source configured to provide products, depending on the platform you use.

It also does not fix structural problems by itself. If the products in your primary feed have inconsistent IDs, invalid images, missing required attributes, or the wrong language, the supplemental feed does not remove the need to clean the base catalog.

Keep these limits in mind:

  1. It does not create new products when there is no match in the primary source.
  2. It does not fix a broken ID strategy; it depends on exact matching.
  3. It does not replace a clean primary product feed.
  4. It does not guarantee instant updates in the ad channel, because your import frequency and the channel’s own reading or validation frequency are separate processes.
  5. It should not mix languages carelessly, because the content language must match the product and destination context.

The last point matters a lot for international catalogs. If your primary source is in English for the US, do not enrich it with titles or descriptions in another language unless your setup and channel configuration are designed for that. As a beginner rule: same product, same ID, same operating language.

Supplemental feed: how to prepare it step by step

Before creating a supplemental feed, define the business problem you want to solve. Do not start with the file. Start with the question.

For example: “I want to identify products for a holiday gifting campaign and group them by price range.” That is a clearer goal than “I need to upload another CSV.”

Step 1: review your primary feed

Check that the primary feed contains the products you want to enrich. At minimum, review:

  • Product ID.
  • Product title.
  • Product URL.
  • Main image.
  • Price.
  • Availability.
  • Language and target country, if relevant.

If the product is not in the primary source, do not treat it as supplemental enrichment. It first needs to exist in the base catalog.

Step 2: decide which attributes you want to add

Avoid adding columns “just in case.” Every field should have a clear use. Examples include:

  • campaign: black_friday, holiday, sale, back_to_school.
  • priority: high, medium, low.
  • margin_band: high, medium, low.
  • price_range: under_30, 30_60, over_60.
  • gift_type: kids, home, tech, fashion.

If you work with Google Shopping, some columns may map to attributes supported by Merchant Center, while others may be internal fields that you transform or use in rules before exporting.

Step 3: use the exact same ID as the primary feed

This is the critical point. If the primary feed uses SKU-001, do not use 001, sku001, or a barcode if that is not the expected matching key.

Uppercase and lowercase differences, spaces, prefixes, suffixes, and alternative formats can prevent the enrichment from applying. To reduce mistakes, export a sample of your primary feed and copy the ID pattern exactly.

Step 4: keep language and context consistent

If the primary feed is built for the United States in English, keep text fields in English. If you have separate versions by market or language, avoid mixing data without a clear strategy.

This applies to titles, descriptions, colors, categories, visible labels, and any attribute whose value depends on language or local merchandising.

Step 5: test with a small product set

Before enriching thousands of products, test with a smaller group, such as 20 products from one category. Check whether the data matches correctly and whether the channel or export workflow interprets the attributes as expected.

Your test should answer:

  • Is the product ID recognized?
  • Is the right attribute updated or added?
  • Does the product still exist and remain active in the primary feed?
  • Is the language consistent?
  • Does the added data help you filter, segment, or build campaigns?

Example: a home decor retailer

Example: a home decor retailer sells lamps, cushions, rugs, and small furniture. Its primary product feed comes from the ecommerce store and includes all active products. The marketing team wants to prepare campaigns by purchase intent, but the store does not have a field that says whether a product is a “gift,” “home basic,” or “premium item.”

Instead of rebuilding the catalog source, the team creates a supplemental enrichment file with these fields:

id marketing_use price_range season
LAMP-1001 gift 30_60 holiday
CUSH-2044 home_basic under_30 evergreen
RUG-3309 premium over_100 sale

The primary feed still defines that LAMP-1001 exists, what it costs, whether it is available, and which image should be used. The supplemental feed adds commercial context.

With this extra data, the team can build more useful product sets: holiday gifts, premium sale items, or lower-price discovery products. This does not mean every channel will accept every custom attribute in the same way. The important principle is to separate responsibilities: the base catalog keeps operational product data, while the supplemental layer adds marketing or normalization data.

How to do it with AdMotion

In AdMotion, the goal is to work with your product catalog as a base that can be cleaned, enriched, segmented, and published by channel. The Feed Manager connects your store or any product file, maps fields, normalizes data with rules, filters product sets, and generates feeds through a URL at each download.

A practical workflow would look like this:

  1. Connect the primary source. You can start from Shopify, BigCommerce, Tiendanube, or any existing file or feed.
  2. Map the catalog fields. Match source fields with the fields you need, such as ID, title, price, image, stock, category, or other available product data.
  3. Add or import enrichment data. If you have a table with labels, commercial priority, internal classification, or campaign fields, use it as an enrichment layer for existing products and make sure IDs match.
  4. Normalize with rules. Clean values, transform fields, or build segmentation rules. AdMotion can also help write rules in natural language, with the result reviewed in the editor before applying it.
  5. Filter product sets. Build sets by campaign, category, availability, price, or internal labels.
  6. Create the feed for the channel. With Export Channels, you can prepare feeds for Google Shopping and other destinations, and use the analyzer to review the feed against the channel specification.
  7. Copy the feed URL into the channel. The feed is published through a URL generated at each download. Remember that importing data into your tool and the channel reading that data are not the same process, so you should not rely on instant synchronization for critical changes.

This workflow helps keep your primary source stable while giving marketing teams a manageable enrichment layer. If you also need to turn catalog fields into product creatives, the Templates Editor can generate one image per product using fields such as photo, title, price, or brand in 1:1, 4:5, 9:16, and 16:9 formats.

If you are setting up your first enrichment workflow, start with the Feed Manager and test it with your own catalog before redesigning your entire feed architecture.

Checklist before publishing a supplemental feed

Before pushing changes into a channel, review this checklist:

  • The primary feed contains every product you want to enrich.
  • The supplemental feed does not include products missing from the primary source.
  • Product IDs match exactly across both sources.
  • Text fields use the right language for the destination.
  • Every added column has a clear purpose.
  • You tested first with a small product sample.
  • You know which fields override existing data and which only add context.
  • You reviewed warnings or errors before using the feed in campaigns.
  • You are not depending on instant channel updates for urgent price, stock, or promotion changes.

That last point is especially important for time-sensitive promotions. Even if your feed is generated correctly, each advertising or commerce platform has its own reading, validation, and application cycle. Plan changes with enough time.

Common mistakes and how to avoid them

Using similar IDs instead of identical IDs

SKU-123, sku-123, and 123 may look like the same product to a person, but not necessarily to a system. Use one convention and keep it consistent.

Trying to create new products

If the product does not exist in the primary source, do not solve it with a supplemental feed. Add it correctly to the base catalog first.

Adding too many unused columns

A feed full of unnecessary fields becomes harder to maintain. Start with a few attributes and expand only when you know how each field will be used.

Mixing market data without control

Do not combine titles, categories, or labels from different languages or countries without a clear setup. If you work across markets, document which source feeds each destination.

What to do this week

  1. Export a sample of your primary feed and check which product ID format it uses. Save that pattern as your reference.
  2. Choose one use case for your first supplemental feed: campaign labels, commercial priority, margin bands, or price ranges.
  3. Create a small test table with 20 or 30 existing products and two or three new columns.
  4. Check matching and language before uploading anything: same ID, same context, and understandable field values.
  5. Document which field wins when two sources contain related data, so your team knows what comes from the base catalog and what comes from the enrichment layer.

A supplemental feed works best when you treat it as an enrichment layer, not as a second catalog. Start with a clean primary feed, consistent IDs, and clear rules, and you can complete product data without rebuilding the original source every time.

Frequently asked questions

Can a supplemental feed create new products?

No. A supplemental feed is used to add or update information for products that already exist in the primary feed. If an item is not present in the base catalog, the supplemental source should not be used to create it. Add the product to the primary source first.

What is the most important field in a supplemental feed?

The product ID is the key field. It must match the ID used in the primary feed so the system knows which product should receive the extra data. Differences in formatting, spaces, prefixes, or capitalization can prevent the enrichment from being applied correctly.

Can I use a supplemental feed for Google Shopping campaigns?

Yes. A supplemental feed can help complete attributes, add labels, or adjust data for existing products before using them in Google Shopping. You still need to follow the channel’s specifications and review Merchant Center warnings. The primary feed remains the foundation of the catalog.

Sources

  1. Crear una fuente de datos de productos — Google
  2. Feed Manager de AdMotion — AdMotion
Share:
J

Written by

Julia Villegas

Performance Marketing

Julia Villegas works in performance marketing at AdMotion.

Related posts