Merchant API vs Content API for Shopping: What WooCommerce stores need to know
WooCommerce store owners who send products to Google may encounter two similar names: Content API for Shopping and Merchant API.
Both technologies are connected with Google Merchant Center, but they belong to different generations of Google’s product-management infrastructure.
Content API for Shopping has supported automated product and account management for many years. Merchant API is its redesigned successor and is now the platform Google expects integrations to adopt.
This change matters even when a merchant does not write code.
A WooCommerce store may rely on:
- A Google Merchant Center plugin
- A Google Shopping plugin
- A custom API connection
- An external feed-management service
- An agency-developed integration
- An older product-synchronization system
If any of these systems uses Content API for Shopping, its provider must migrate the integration to Merchant API.
Google states that Content API for Shopping is deprecated and is scheduled to shut down in August 2026. Merchant API v1 became generally available in July 2025 as its official successor. Google Merchant API updates
For WooCommerce store owners, the essential question is therefore no longer whether Merchant API will replace Content API.
The practical questions are:
- Does the current WooCommerce integration already use Merchant API?
- Will the existing plugin continue working after Content API is shut down?
- Does the merchant need to change anything?
- Will product IDs and Merchant Center data sources remain consistent?
- Could migration create duplicate products?
- How should the new workflow be tested?
- What advantages can Merchant API provide?
This guide explains those questions from the perspective of a WooCommerce merchant rather than an API developer.
What is Content API for Shopping?
Content API for Shopping is the older Google interface used by software applications to manage information in Merchant Center.
It has allowed approved systems to perform operations such as:
- Adding products
- Updating products
- Deleting products
- Managing inventory
- Reading product status information
- Managing Merchant Center accounts
- Configuring selected account settings
- Accessing reports
- Managing promotions and related resources
A WooCommerce plugin using Content API could take product information from the store and send it programmatically to Merchant Center.
For example, when a merchant changed a product’s price or stock status in WooCommerce, the integration could send the revised information without requiring the merchant to upload a complete XML file manually.
Content API therefore helped establish an important workflow:
WooCommerce product → API integration → Google Merchant Center → Google product experiences.
Although that general workflow remains useful, the underlying Google technology is changing.
Content API is now a legacy platform. Existing integrations must move to Merchant API before the old service becomes unavailable.
What is Merchant API?
Merchant API is Google’s newer interface for managing Merchant Center resources.
Google describes it as a redesign of Content API for Shopping. It separates different areas of Merchant Center into more clearly structured sub-APIs and follows newer Google API design standards. Merchant API overview
Merchant API can support tasks such as:
- Managing Merchant Center accounts
- Creating and managing product data sources
- Adding and updating products
- Managing product inventory
- Retrieving processed product information
- Reviewing account and product issues
- Managing promotions
- Accessing performance reports
- Receiving selected notifications
- Managing business-related resources
For a store owner, the visible purpose remains familiar: keeping WooCommerce and Merchant Center product information connected.
The main changes occur inside the integration.
A well-designed WooCommerce Google Merchant Center plugin should handle those technical differences while giving the merchant a clear WordPress interface.
Is Merchant API simply a renamed Content API?
No.
Merchant API replaces the same general category of integration, but it is not merely Content API with a different name.
Google redesigned the structure, resources, request methods and data-management model.
Some important differences include:
- Merchant API is divided into specialised sub-APIs.
- Resource names follow newer Google API conventions.
- Product inputs and processed products are treated as distinct resources.
- API data sources can be created and managed more explicitly.
- Multiple API data sources can be supported.
- Some fields and methods have different names.
- Some data types have changed.
- Some Content API methods do not have identical replacements.
- Content API custom batch requests are not used in the same way.
- Account and product issues have more structured resources.
- Google Cloud projects must be registered appropriately with Merchant Center.
These differences mean that replacing an endpoint address is not always enough.
A genuine migration requires the integration provider to review product management, account access, data sources, errors, identifiers, batching, reporting and other supported operations.
Google’s official migration guide warns that complete backward compatibility cannot be guaranteed because Merchant API has an improved design and may use different fields or methods for similar functions. Google’s Content API migration overview
The most important difference for WooCommerce merchants
The most important difference is the future availability of the integration.
Content API is scheduled for shutdown in August 2026. An integration that remains dependent on it may stop completing affected operations after Google disables the service.
Possible consequences could include:
- New products no longer being added
- Price changes not reaching Merchant Center
- Stock changes not being synchronized
- Product deletions failing
- Product-status information no longer being retrieved
- Account information not loading inside the plugin
- Scheduled synchronization jobs returning errors
- Merchant Center reports no longer appearing in WordPress
The exact effect depends on which Content API resources the plugin uses.
The WooCommerce store itself will not disappear. Product pages, checkout and customer orders can continue to operate because those belong to WooCommerce.
The risk concerns the connection between the store and Google Merchant Center.
Do store owners need to perform the migration themselves?
Usually, no.
If a merchant uses a third-party WooCommerce plugin or managed integration, the plugin developer is normally responsible for updating the underlying connection.
Google similarly explains that merchants using a third-party technology provider to synchronize products generally do not need to perform the code migration themselves. The provider should handle it. Google’s migration guidance
However, “the developer handles the code” does not mean the store owner should ignore the transition.
The merchant should still confirm:
- Which plugin or service sends products
- Whether it uses Content API or Merchant API
- Whether a migration update is available
- Whether the installed plugin version is current
- Whether Google authorization must be renewed
- Whether the Merchant Center account must be selected again
- Whether a new API data source will be created
- Whether product IDs will remain stable
- Whether scheduled operations are working
- Whether duplicate products appear after migration
A merchant should not edit API code without the necessary technical knowledge, but should verify that the selected provider has a documented transition plan.
How Merchant API changes product data sources
Data-source management is one of the most relevant changes.
With Content API for Shopping, an API product source could be created automatically when the first product was inserted. The account generally used a Content API source for these submissions.
Merchant API provides more explicit control.
An integration can create and manage API data sources, and an account can use multiple API sources. Google also allows compatible Content API data sources to remain available during migration. Merchant API data-source migration
This additional flexibility can be useful, but it requires careful management.
For example, a Merchant Center account might contain:
- An old XML feed
- A Content API source
- A newly created Merchant API source
- Automatically found products
- Manually entered products
- Another WooCommerce integration
- An agency-managed source
Multiple sources are not automatically a problem.
The problem begins when several sources submit the same commercial products without a deliberate plan.
Can migration create duplicate products?
Yes, an uncontrolled migration can contribute to duplicate products.
Suppose an old WooCommerce plugin submitted an item with this ID:
online:en:US:SKU-104
A new Merchant API integration might submit the same physical item using:
woocommerce-2841
If the old source remains active and both offers are processed as separate identities, the merchant may see two product records representing the same item.
Duplicates can also occur when:
- The old plugin continues its scheduled synchronization.
- The new system creates another API data source.
- Automatic website discovery adds overlapping products.
- Product identifiers change during migration.
- Parent and variation products are mapped differently.
- A staging website connects to the live Merchant Center account.
- Products remain in an old feed while being sent through Merchant API.
- An agency connection is still active.
A safer migration keeps the identity strategy predictable.
Before switching systems, document:
- Existing data sources
- Active WooCommerce plugins
- Current product IDs
- Feed labels
- Content languages
- Target countries
- Variation IDs
- Existing scheduled jobs
- Products owned by each source
Then test a small group before processing the complete catalogue.
What happens to existing Content API data sources?
Existing Content API sources do not necessarily have to be deleted immediately.
Google explains that data sources created through Content API can be used compatibly with Merchant API. Such a source may still appear in Merchant Center as a “Content API” source even when Merchant API inserts products into it. Merchant API data-source compatibility
This is important because merchants may assume that seeing the words “Content API” automatically means the new integration is still calling the deprecated service.
The displayed source name alone may not prove which API currently performs the operation.
The plugin developer or integration provider should confirm the actual implementation.
Do not delete an existing source merely because of its label.
Deleting a source can remove the product information associated with that source. First determine:
- Whether it still receives updates
- Whether the new integration uses it
- Which products belong to it
- Whether another source has replaced those products
- Whether IDs remain consistent
- What will disappear if it is removed
Product inputs and processed products
Merchant API makes an important distinction between product inputs and processed products.
A product input represents the information submitted by the merchant or integration.
A processed product represents the result Google creates after processing that information.
This distinction helps explain why an API operation can succeed while the product is still not eligible to appear.
The general process is:
- WooCommerce contains the source product.
- The plugin prepares the product information.
- Merchant API receives the product input.
- Google processes the submitted information.
- Google evaluates the product and landing page.
- Merchant Center reports product issues or status.
- An eligible product may appear in applicable Google experiences.
A successful submission confirms that Google received the technical request.
It does not guarantee:
- Product approval
- Free-listing visibility
- Shopping ad eligibility
- Impressions
- Clicks
- Search position
- Conversions
- Sales
This distinction is particularly useful in a WooCommerce plugin interface.
The plugin should communicate whether an operation failed technically, succeeded technically or produced a product that Google later limited or disapproved.
How product management differs
Both APIs can support product operations, but their product models and request structures differ.
Merchant API introduces updated resources for submitted product information and processed product results.
The migration may involve changes to:
- Product insertion
- Product updates
- Product deletion
- Product retrieval
- Product-status retrieval
- Supplemental product information
- Local inventory
- Regional inventory
- Product attributes
- Data-source selection
- Error processing
- Batch operations
Google provides a separate product migration guide because product operations cannot always be converted through a simple one-to-one replacement. Google’s product migration guide
For merchants, this means a plugin update should be tested with more than one simple product.
The test group should include:
- A simple product
- A variable product
- An in-stock product
- An out-of-stock product
- A sale product
- A product with a GTIN
- A product without a standard identifier
- A product with several images
- A permanently discontinued product
- A product requiring an update after initial submission
This provides a more realistic test of the migration.
How batch processing changes
Content API supported custombatch, which allowed several product operations to be included in one request.
Merchant API does not support the same customBatch model. Google instead provides guidance for sending multiple individual requests and processing operations asynchronously or in parallel where appropriate.
This is mainly a developer concern, but it can affect merchant-facing behaviour.
An updated plugin may need to reconsider:
- Batch size
- Worker processes
- Retry logic
- Request queues
- Server resource consumption
- Rate-limit handling
- Progress reporting
- Failed-product isolation
- Scheduled operation duration
A responsible migration should not simply convert a large Content API batch into uncontrolled simultaneous requests.
The provider should preserve a stable workflow suitable for WordPress hosting environments.
For the merchant, useful interface elements include:
- Products waiting to be processed
- Products currently being processed
- Successful operations
- Failed operations
- Retry controls
- Clear error information
- Progress indicators
- Scheduled synchronization status
- Last successful operation time
Does Merchant API improve issue reporting?
Merchant API introduces more structured account-issue management.
For example, account issues can be retrieved as dedicated resources with information about affected destinations, regions and severity.
Google’s newer model uses severity values such as critical, error and suggestion, allowing integrations to organise findings more consistently. Merchant API account-issue migration
This can help a WooCommerce integration present findings more clearly.
However, the plugin should not translate every Google message into a guaranteed diagnosis.
A useful interface should distinguish between:
- A WooCommerce source-data problem
- A technical API error
- A Merchant Center account issue
- A product issue
- A policy-related limitation
- A temporary processing state
- An informational recommendation
The correction should usually be made at the real source.
If the price is wrong in WooCommerce, changing it temporarily in Merchant Center does not create a dependable long-term solution.
WooCommerce should remain the principal product source
For most stores, WooCommerce should remain the principal source of product information.
That includes:
- Product title
- Description
- Price
- Sale price
- Currency
- Stock status
- Product URL
- Main image
- Additional images
- Brand
- GTIN
- MPN
- Product category
- Variation information
When a problem appears in Merchant Center, follow this workflow:
- Identify the affected product.
- Review the reported value.
- Find the original WooCommerce product or variation.
- Correct the source information.
- Confirm that the landing page shows the correction.
- Process the product again.
- Review the API operation result.
- Wait for Google to process the new input.
- Check the resulting Merchant Center status.
This prevents temporary edits from being overwritten during the next synchronization.
Will Google authorization change?
Merchant API still requires an authorized relationship with the merchant’s Google account and Merchant Center resources.
Depending on how the existing integration was designed, migration may require:
- Updating the Google Cloud project
- Enabling Merchant API
- Registering the developer
- Updating the application’s internal API calls
- Renewing user authorization
- Reconnecting the Google account
- Selecting the Merchant Center account again
The exact steps depend on the provider.
A WooCommerce plugin should use Google’s authorization process. The user should not enter a normal Google password into the plugin.
Before reconnecting, verify:
- The application name
- The Google account being used
- The requested permission
- The selected Merchant Center account
- The website connected with that account
- The plugin’s official origin
- The connection result
Successful authorization to the wrong Merchant Center account is still an incorrect setup.
How to check whether a plugin is ready
Ask the plugin provider clear questions:
- Does the current version use Merchant API?
- Does any important feature still depend on Content API for Shopping?
- Which plugin version contains the migration?
- Will existing product IDs remain unchanged?
- Will the integration use the existing data source or create another one?
- Is renewed Google authorization required?
- Are variable products supported after migration?
- How are price and stock updates processed?
- How are failed operations retried?
- Can the merchant review API operation results?
- Has the migration been tested with large catalogues?
- What happens to the old scheduled tasks?
- Is there a documented rollback or recovery procedure?
Avoid relying only on a general statement such as “Google compatible.”
The provider should be able to identify Merchant API specifically.
A safe WooCommerce migration checklist
Before migration:
- Back up the WooCommerce database and files.
- Record the installed plugin version.
- List all Merchant Center data sources.
- Identify every plugin sending products to Google.
- Record current product IDs.
- Check scheduled synchronization tasks.
- Select representative test products.
- Note current Merchant Center product counts.
- Record critical account and product issues.
- Confirm the intended Google and Merchant Center accounts.
During migration:
- Install the provider’s verified Merchant API version.
- Complete any required Google authorization.
- Select the correct Merchant Center account.
- Review the intended data source.
- Keep automatic large-scale synchronization disabled initially.
- Run WooCommerce product checks.
- Process only the selected test group.
- Review technical results.
- Compare the products in Merchant Center.
- Confirm that no duplicates were created.
After migration:
- Update a test product’s price.
- Update its stock status.
- Synchronize the change.
- Confirm the new values in Merchant Center.
- Test a variable product.
- Test a product deletion or discontinuation workflow.
- Review failed-product handling.
- Check scheduled operations.
- Monitor the catalogue over several cycles.
- Retire the old workflow only after verification.
How PW Merchant approaches the new workflow
PW Merchant for WooCommerce is designed around an authorized Merchant API connection.
Its purpose is to help WooCommerce store owners:
- Examine products before processing
- Identify products requiring attention
- Separate critical findings from suggestions
- Connect the intended Google account
- Select the correct Merchant Center account
- Process suitable WooCommerce products
- Update product information
- Review operation results
- Manage recurring product workflows from WordPress
PW Merchant does not replace WooCommerce or Merchant Center.
WooCommerce remains responsible for the online store and source product information. Merchant Center remains Google’s platform for processing business and product data.
PW Merchant provides the operational connection between them.
It does not bypass Google policies and does not guarantee product approval, visibility, clicks or sales.
Frequently asked questions
Is Content API for Shopping still working?
It may still work during the transition period, but Google has deprecated it and scheduled its shutdown for August 2026. Integrations should move to Merchant API before the shutdown.
Is Merchant API the replacement for Content API?
Yes. Google identifies Merchant API as the official successor to Content API for Shopping.
Do I need to change my WooCommerce store?
The store itself may not require structural changes. The plugin or service connecting WooCommerce to Merchant Center must use the supported API. Product information should still be reviewed for accuracy.
Must I write API code myself?
Not when using a maintained third-party plugin. The integration provider should perform the technical migration.
How can I know which API my plugin uses?
Check the plugin documentation, version notes or provider statement. Ask specifically whether all required product and account operations use Merchant API.
Should I delete my Content API data source?
Not merely because of its name. Merchant API can work with compatible Content API sources. Determine how the integration uses the source and which products belong to it before deleting anything.
Will Merchant API create another data source?
It can create and manage explicit API data sources. Whether your plugin creates a new one or uses an existing compatible source depends on its design.
Can the migration duplicate products?
Yes, if the old and new sources submit the same items with different identifiers. Test a small group and compare product IDs before processing the full catalogue.
Will my existing products disappear?
Not automatically. However, deleting a data source or changing the product identity strategy without planning can remove or recreate products. Review the source configuration first.
Does a successful Merchant API operation mean that Google approved the product?
No. Technical acceptance and Google eligibility are separate stages. Google still evaluates the product, landing page, account and applicable policies.
Does Merchant API guarantee better Google Shopping performance?
No. It provides a newer and more structured integration foundation. Product visibility and performance still depend on product quality, demand, competition, pricing, account status, website quality and Google’s systems.
Can PW Merchant migrate products from an old feed automatically?
PW Merchant can process suitable WooCommerce products through Merchant API, but an old source should first be reviewed. Product IDs, overlapping sources and existing Merchant Center records must be considered before a transition.
What should I do first?
Identify the plugin or service currently sending WooCommerce products to Merchant Center. Confirm whether it uses Merchant API and review all existing data sources before changing anything.
Conclusion
The difference between Merchant API and Content API for Shopping is more than a new product name.
Content API belongs to Google’s older Merchant Center integration infrastructure. Merchant API is its redesigned and officially supported successor.
For WooCommerce store owners, this transition means:
- The current product plugin must be reviewed.
- Legacy Content API dependencies must be removed.
- Existing data sources must be understood.
- Product IDs should remain stable.
- Duplicate products must be prevented.
- Google authorization may need to be renewed.
- Product and variation operations should be tested.
- Price and stock changes must continue reliably.
- Failed operations should be visible and recoverable.
- The old workflow should not be removed before the new one is verified.
Merchants using a maintained third-party integration do not normally need to rewrite API code.
They do need confidence that the provider has completed the migration correctly.
A careful transition begins with a small representative product group. It verifies IDs, prices, availability, variations, data-source ownership and Merchant Center results before extending the new process to the complete catalogue.
PW Merchant API is designed to provide a controlled Merchant API workflow for WooCommerce.
It helps store owners examine source products, connect the appropriate Merchant Center account, process suitable products and monitor operations from WordPress.
If your current Google Shopping connection still depends on legacy technology, discover PW Merchant for WooCommerce and prepare your store for the Merchant API generation.
A successful migration preserves more than technical connectivity.
It protects product continuity, reduces duplicate risks and helps WooCommerce remain a dependable source of current product information for Google Merchant Center.