Migrate from v2 inventory service to supplemental feeds
Stay organized with collections
Save and categorize content based on your preferences.
The supplemental feeds feature introduced in Content API version 2.1 provides
similar functionality to the legacy (v2) inventory service.
Both services let you to make partial updates of online (non-local) products
without replacing all product data. When migrating to supplemental feeds,
keep the following points in mind:
With supplemental feeds, calling Products.insert with the feedId as a
query parameter is equivalent to using Inventory.set with the legacy inventory
service to perform partial updates on a product.
You can update any product data field with supplemental feeds, except
local inventory-specific
fields.
To add and update store-level product data with Content API v2.1, use the
local inventory service
instead of supplemental feeds.
You can create separate supplemental feeds for separate product data updates.
For example, you can create a supplemental feed for price updates and a separate
supplemental feed for availability updates. This helps with debugging product
data issues by making it easier to track down the feed responsible for updating
that attribute.
Request quotas
In addition, one major difference between supplemental feeds and the legacy
inventory service is that supplemental feeds have a lower request quota. Unlike
the inventory service, requests made via supplemental feeds count towards the
same quota as the
Products resource.
If you need a higher request quota, please
contact us and include the following
information:
Your Merchant Center ID
The methods you are hitting your quota on
An estimate of how many extra calls per day you need for those methods
A business justification for why you need these extra method calls
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-13 UTC."],[[["\u003cp\u003eThe Merchant API is the new version of the Content API for Shopping and is now in beta.\u003c/p\u003e\n"],["\u003cp\u003eSupplemental feeds in Content API v2.1 offer similar functionality to the legacy inventory service for partial product updates, but with a lower request quota.\u003c/p\u003e\n"],["\u003cp\u003eYou can update any online product data field using supplemental feeds, except for local inventory fields.\u003c/p\u003e\n"],["\u003cp\u003eSeparate supplemental feeds can be created for different product data updates (e.g., price, availability) to streamline debugging.\u003c/p\u003e\n"],["\u003cp\u003eContact Google Merchant Center support if you require a higher request quota for supplemental feeds, providing necessary information for evaluation.\u003c/p\u003e\n"]]],["The Merchant API beta, a new version of the Content API for Shopping, is introduced. Supplemental feeds in Content API v2.1 allow partial updates to online product data, similar to the legacy inventory service, using `Products.insert` with `feedId`. Supplemental feeds can update any non-local inventory field and allow for creating multiple feeds for different attributes. Unlike the legacy system, requests using these feeds count against the Products resource quota. Increased quota requests require providing the Merchant Center ID, quota details, and a business justification.\n"],null,["# Migrate from v2 inventory service to supplemental feeds\n\nThe supplemental feeds feature introduced in Content API version 2.1 provides\nsimilar functionality to the legacy (v2) inventory service.\nBoth services let you to make partial updates of online (non-local) products\nwithout replacing all product data. When migrating to supplemental feeds,\nkeep the following points in mind:\n\n- With supplemental feeds, calling `Products.insert` with the `feedId` as a query parameter is equivalent to using `Inventory.set` with the legacy inventory service to perform partial updates on a product.\n- You can update any product data field with supplemental feeds, except [local inventory](/shopping-content/reference/rest/v2.1/localinventory)-specific fields.\n - To add and update store-level product data with Content API v2.1, use the [local inventory service](/shopping-content/reference/rest/v2.1/localinventory) instead of supplemental feeds.\n- You can create separate supplemental feeds for separate product data updates. For example, you can create a supplemental feed for price updates and a separate supplemental feed for availability updates. This helps with debugging product data issues by making it easier to track down the feed responsible for updating that attribute.\n\n| **Note:** For more information on updating your application for v2.1, see [Migrating from Content API v2 to v2.1](/shopping-content/guides/migration).\n\nRequest quotas\n--------------\n\nIn addition, one major difference between supplemental feeds and the legacy\ninventory service is that supplemental feeds have a lower request quota. Unlike\nthe inventory service, requests made via supplemental feeds count towards the\nsame quota as the\n[Products resource](/shopping-content/v2/limits#method_call_quotas).\nIf you need a higher request quota, please\n[contact us](/shopping-content/support/contact-us) and include the following\ninformation:\n\n- Your Merchant Center ID\n- The methods you are hitting your quota on\n- An estimate of how many extra calls per day you need for those methods\n- A business justification for why you need these extra method calls"]]