WooCommerce Product Sync to Google Merchant Center

WooCommerce product synchronization with Google Merchant Center: Complete guide

Synchronising WooCommerce products with Google Merchant Center is more than transferring a product title, price and image from one platform to another. A reliable product synchronisation system must understand how products are structured in WooCommerce, convert that information into valid Google product data, send it through an appropriate data source and continue updating it whenever the store changes.

Prices change. Stock quantities move throughout the day. Sale periods begin and end. Product images are replaced. New variations are created. Old products are removed. Google Merchant Center must receive these changes accurately if shoppers are expected to see information that matches the WooCommerce store.

PW Merchant API is a WooCommerce Google Merchant Center plugin designed to help merchants establish and manage this connection directly from WordPress. Instead of depending only on a traditional XML product file, the PW Merchant API plugin uses the Google Merchant API workflow to submit WooCommerce product information, update changing data and retrieve processing results.

The central principle of reliable synchronisation is:

WooCommerce should remain the controlled source of product information, while PW Merchant API manages the transfer of that information to Google Merchant Center.

This structure gives merchants a clearer workflow. Product information is maintained in WooCommerce, PW Merchant API prepares and submits it, and Google Merchant Center processes it for eligible Google destinations.

What is WooCommerce product synchronisation?

WooCommerce product synchronisation is the process of transferring product information from a WooCommerce store to another system and keeping both systems aligned as the catalogue changes.

For Google Merchant Center, synchronised information can include:

Product IDs
Product titles
Product descriptions
Product links
Main and additional images
Regular prices
Sale prices
Availability
Stock-related information
Brand
GTIN
MPN
Condition
Product categories
Shipping information
Product variations
Colour
Size
Material
Pattern
Target country
Content language

A one-time product upload is not complete synchronisation. It creates an initial copy of the product data, but it does not guarantee that later WooCommerce changes will reach Merchant Center.

True synchronisation needs to handle the full product lifecycle:

A WooCommerce product is created.
Its data is reviewed and prepared.
PW Merchant API submits it to Google Merchant Center.
Google processes the submitted product.
The submission result or product issue is retrieved.
A price, stock value or product detail changes in WooCommerce.
PW Merchant API updates the existing Merchant Center item.
A discontinued product or obsolete variation is removed or excluded safely.

PW Merchant API is intended to bring these stages into a manageable WooCommerce workflow instead of requiring merchants to maintain an unrelated catalogue manually inside Merchant Center.

Why synchronise WooCommerce with Google Merchant Center?

Google Merchant Center needs structured product information to understand what an online store sells. This information can support free listings, Shopping ads and other eligible Google surfaces, depending on the account, market and programme configuration.

Manually entering products may be practical for a very small catalogue, but it becomes increasingly difficult as the store grows. A merchant with hundreds or thousands of WooCommerce products cannot reliably update every price, stock status and variation manually.

Without an automated or controlled synchronisation method, common problems include:

Google displays an old price.
An out-of-stock product remains available.
A newly published product never reaches Merchant Center.
A discontinued item remains in the catalogue.
Sale prices do not end at the correct time.
Product variations use incorrect availability.
WooCommerce and Google display different images.
Merchant Center contains products that no longer exist.
Errors remain unnoticed after submission.
Multiple product sources create duplicates.

The PW Merchant API plugin is designed to reduce this operational gap. It connects WooCommerce product management with Merchant Center submission so that merchants can manage their store data from its natural source.

How PW Merchant API connects WooCommerce to Google Merchant Center

PW Merchant API functions as a WooCommerce Merchant API integration. The merchant connects an authorised Google account, selects the accessible Merchant Center account and uses the plugin’s WordPress interface to manage product submission operations.

The general workflow is:

Install and activate PW Merchant API in WordPress.
Connect the merchant’s Google account securely.
Select the correct Google Merchant Center account.
Review the WooCommerce catalogue.
identify suitable products and product-data problems.
Configure the required submission details.
Send products through Merchant API.
Retrieve and display processing results.
Correct source data in WooCommerce when necessary.
Resubmit or update the affected products.

Google’s Merchant API requires product inputs to be submitted to a primary data source. Google then processes those inputs and creates the resulting product representation visible in Merchant Center. Submission and processing are therefore related but separate stages. A successful API operation does not automatically mean that a product has been approved or is immediately visible.

PW Merchant API helps make this distinction clearer by providing a WooCommerce-oriented management process for submission and result tracking.

PW Merchant API is more than a basic product exporter

A simple exporter creates a file or sends a fixed set of values. A practical WooCommerce Google Merchant Center plugin must deal with changing catalogue conditions.

PW Merchant API is intended to support a broader workflow that includes:

Reviewing WooCommerce products
Identifying products that require attention
Processing simple and variable products
Preparing product data for Merchant API
Sending new products
Updating existing product information
Synchronising changing prices
Synchronising availability
Following submitted operations
Displaying Google-side results and issues
Retrying failed processes when appropriate
Managing larger catalogues through planned operations

This makes PW Merchant API relevant not only during the first connection but throughout the ongoing management of a WooCommerce catalogue.

Prepare WooCommerce before the first synchronisation

The quality of Merchant Center data begins in WooCommerce. PW Merchant API can read, organise and transmit product information, but missing or inaccurate source data still needs to be corrected.

Before starting the first full synchronisation, inspect the catalogue for:

Products without prices
Products without main images
Empty or extremely short titles
Incomplete descriptions
Incorrect stock status
Duplicate SKUs
Missing variation attributes
Disabled variations
Broken product URLs
Products that cannot be purchased
Missing brand information
Missing or invalid GTIN values
Inaccurate sale prices
Placeholder images
Draft or private products
Products not intended for Google

PW Merchant API can help merchants review their catalogue and organise the synchronisation process, but Google evaluates the final product information according to its own requirements.

Google’s product data specification explains that inaccurate, conflicting or missing information may cause disapprovals, limited eligibility or incorrect product presentation. Google specifically identifies problems such as invalid identifiers, missing variation attributes, poor-quality images and conflicts between submitted data and landing pages. Google product data specification

For this reason, the best first step is not “send everything immediately.” The better approach is to review the catalogue, correct critical source problems and then begin a controlled PW Merchant API synchronisation.

Connect the correct Merchant Center account

A Google account may have access to more than one Merchant Center account. Selecting the wrong account can send products into an unrelated or test environment.

During the PW Merchant API connection process, confirm:

The Google account belongs to or is authorised by the merchant.
The intended Merchant Center account is accessible.
The correct account is selected in PW Merchant API.
The account represents the correct business.
The verified website matches the WooCommerce store.
The target country and language plan is understood.
No staging website is connected to the production account.
Old credentials or unrelated integrations are not being reused.

The PW Merchant API plugin should be connected deliberately. The connection is not merely a technical permission; it determines which Merchant Center account receives product operations and from which WooCommerce store those operations originate.

Understand data sources before synchronising

Google Merchant Center can receive products from several types of sources, including API calls, uploaded or fetched files, ecommerce platform connections and automatically discovered website products.

Merchant API supports API-based product data sources, but at least one appropriate primary source must exist before product details can be submitted. Google’s current Merchant API documentation also explains that API data sources can be created and managed separately, providing greater control over product-data pipelines. Google Merchant API data-source guide

Before making PW Merchant API the main WooCommerce synchronisation method, inspect the existing Merchant Center sources.

Look for:

An old XML feed
A scheduled product file
A former Content API connection
Another WooCommerce Google plugin
An ecommerce platform connection
Manually added products
Automatically discovered products
Test data sources
Staging-site connections

PW Merchant API should have a clearly defined role. If it becomes the primary WooCommerce product synchronisation system, an old integration should not continue submitting the same complete catalogue without a specific plan.

Running PW Merchant API and an old XML feed together can produce duplicate records when the systems use different product IDs. It can also create uncertainty about which source controls a product.

How PW Merchant API submits a new product

When a valid WooCommerce product is selected for submission, PW Merchant API prepares the information required for the Merchant API product input.

The prepared product may contain:

A stable offer ID
Content language
Feed label
Title
Description
Product-page link
Image link
Availability
Price
Sale price
Condition
Brand
GTIN
MPN
Product type
Google product category
Variation attributes
Shipping-related information

PW Merchant API then sends the product input to the relevant primary Merchant Center data source.

Google’s documentation states that inserting a ProductInput creates the product input and starts Google’s processing stage. The submitted attributes must conform to the Merchant Center product data specification. Add and manage products with Merchant API

The product is therefore not necessarily approved at the moment PW Merchant API completes the submission. Google still needs to process the information, compare relevant data and determine the product’s status.

Use stable product IDs

A stable product ID is essential for synchronisation.

Google uses the submitted ID to recognise an existing offer. When PW Merchant API updates a price, stock status or description, it must address the same product identity instead of creating a new record.

A good WooCommerce Merchant API identifier strategy should ensure that:

Every product has a unique ID.
Every variation has a unique ID.
IDs remain stable during normal updates.
A price change does not create a new ID.
A stock change does not create a new ID.
The same ID is not reused for unrelated products.
A deleted product’s identity is handled safely.
Domain or plugin changes do not alter IDs unnecessarily.

PW Merchant API should preserve the identity of products that already exist within its synchronisation structure.

Changing identifiers without a migration plan can create duplicates. Google may see the new identifier as a different offer while the former item remains in the old source.

Synchronise simple WooCommerce products

A simple WooCommerce product normally represents one purchasable item. Its price, availability, image and product page can usually be submitted as one Merchant Center offer.

Before PW Merchant API sends a simple product, verify that:

The product is published.
It has a valid regular or sale price.
It is purchasable.
Stock information is accurate.
The main image is accessible.
The product page is publicly available.
The title describes the product.
The description is useful and accurate.
Required identifiers are available when applicable.
The landing page displays the submitted price and availability.

When any of these values change, PW Merchant API should update the existing Merchant Center item rather than creating another product.

Synchronise WooCommerce variable products

Variable products need more detailed processing.

A WooCommerce parent product may contain many purchasable variations. Each colour, size, material or configuration can have its own:

Variation ID
SKU
Price
Stock status
Image
Weight
Dimensions
GTIN
MPN
Landing-page selection

PW Merchant API must treat each real purchasable variation as an individual product offer while preserving its relationship with the other variations.

For example:

WooCommerce item	Product ID	Item group ID	Colour	Size
Black, small	shirt-400-black-s	shirt-400	Black	S
Black, medium	shirt-400-black-m	shirt-400	Black	M
Blue, small	shirt-400-blue-s	shirt-400	Blue	S
Blue, medium	shirt-400-blue-m	shirt-400	Blue	M

PW Merchant API should submit the exact price and availability of each variation. It should not apply the parent product’s general stock condition to every option.

The plugin should also avoid submitting an unnecessary generic parent offer when the parent cannot be purchased without selecting a variation.

Synchronise WooCommerce prices accurately

Price mismatch is one of the most important catalogue risks.

The price sent by PW Merchant API should match the price displayed on the corresponding WooCommerce landing page. This includes:

Regular price
Active sale price
Currency
Variation-specific price
Tax presentation when applicable
Any price that becomes visible after selecting the variation

A variable product may display a range such as $40–$65, but each submitted variation needs its own exact price.

If a WooCommerce store changes a price, PW Merchant API should update the same Merchant Center item. It should not wait for a completely unrelated catalogue rebuild when a controlled product update is available.

Google’s Merchant API documentation supports partial updates for frequently changing information such as price and availability through product-input update methods. Google also advises integrations to avoid using conflicting update strategies for the same data. Frequent product updates with Merchant API

PW Merchant API can use this API-oriented structure to create a more direct WooCommerce price-management workflow.

Synchronise stock and availability

Availability should represent what the customer can actually purchase.

A WooCommerce product can be:

In stock
Out of stock
Available on backorder
Disabled
Unpurchasable
Available only through a specific variation

PW Merchant API should read the appropriate product or variation-level condition and send the corresponding availability information.

For a variable product, one option may be in stock while another is unavailable:

Variation	WooCommerce condition	Merchant Center availability
Black, small	Available	In stock
Black, medium	No stock	Out of stock
Blue, small	Available	In stock
Blue, medium	No stock	Out of stock

Sending the parent product’s general “in stock” state to all four variations would be inaccurate.

Accurate PW Merchant API availability synchronisation helps reduce the chance that a shopper clicks a Google listing for an option that cannot be purchased on the WooCommerce store.

Synchronise product images

The main image sent by PW Merchant API should represent the exact advertised product.

For simple products, this is generally the WooCommerce featured image. For colour or pattern variations, a dedicated variation image is preferable because shoppers should see the same visual option after opening the product page.

Before synchronisation, confirm that:

The image URL is public.
Google can crawl it.
The image is not blocked by security rules.
The image is not a placeholder.
The displayed product is clear.
Promotional overlays do not dominate the image.
The variation image matches the submitted colour or pattern.
Deleted images are not still referenced.
HTTPS works correctly.

PW Merchant API can transmit the image URL, but the server must allow Google to retrieve the file.

Keep landing pages consistent

Every product submitted by PW Merchant API should lead to a valid WooCommerce landing page.

The page should display information consistent with the submitted product, particularly:

Title
Price
Currency
Availability
Condition
Selected variation
Main image
Brand
Product identifiers when displayed

Variation links should help customers identify or select the advertised option. If PW Merchant API submits a blue, medium product but the landing page opens with an unrelated default option, price and availability comparisons may become unreliable.

Structured data on the WooCommerce page is also important. Google identifies price, price currency, availability and condition as relevant structured-data properties for automatic item updates. Google Merchant Center structured-data guidance

PW Merchant API synchronisation and valid WooCommerce structured data should support each other. Structured data does not replace the PW Merchant API workflow; it helps Google compare submitted information with the landing page.

Plan automatic synchronisation carefully

Not every store needs the same synchronisation frequency.

A store with a small, rarely changing catalogue may need fewer updates. A store with thousands of products, frequent stock movements and changing prices needs a more structured schedule.

PW Merchant API can help organise operations around practical timing choices. Depending on the store and configured workflow, synchronisation may be run:

Immediately
At planned intervals
During quieter server hours
Through controlled scheduled processes
After significant catalogue changes

Scheduling should consider:

Catalogue size
Number of variations
Server capacity
WooCommerce activity
Price-update frequency
Stock-update frequency
API limits
Background processing
Retry behaviour
Maintenance periods

Large synchronisation jobs should be divided into manageable operations rather than placing unnecessary pressure on WordPress, WooCommerce or the hosting server.

PW Merchant API is especially useful for stores that need to organise larger catalogues and recurring operations from within WordPress.

Understand submission, processing and approval

These three stages should not be confused:

Submission: PW Merchant API successfully sends the product operation.
Processing: Google reads and evaluates the product input.
Status or eligibility: Google determines issues, approval and possible destinations.

A successful submission means the operation reached Google for processing. It does not guarantee:

Product approval
Immediate visibility
Shopping ad eligibility
Free listing eligibility
Absence of product-data issues
Absence of account-level issues

After inserting, updating or deleting product input, Google notes that the processed product may take several seconds or minutes to become retrievable. Insert a product with Merchant API

PW Merchant API should therefore track results beyond the initial request. Merchants should review both the plugin’s reported outcome and the final product status in Merchant Center.

Use PW Merchant API to identify and correct problems

When Google reports an issue, the most reliable correction is usually made in WooCommerce or the PW Merchant API mapping that produced the data.

Common issues can include:

Missing price
Price mismatch
Availability mismatch
Missing image
Image crawl failure
Missing brand
Invalid GTIN
Missing MPN
Incorrect identifier use
Missing variation attributes
Invalid landing page
Incorrect currency
Duplicate products
Unsupported or malformed values
Policy-related restrictions

PW Merchant API can make the response process more manageable by displaying submission and Google-side results within the WordPress workflow.

The merchant can then:

Open the affected WooCommerce product.
Correct the source information.
Save the product.
Resubmit or update it through PW Merchant API.
Wait for Google’s processing stage.
Review the new status.

This is more reliable than repeatedly editing synchronised products manually inside Merchant Center, because manual changes can be overwritten by the next update from the primary source.

Retry failed synchronisation operations

API operations can fail temporarily because of:

Network interruptions
Request timeouts
Temporary Google service conditions
Invalid authentication
Expired authorisation
Incorrect Merchant Center account selection
Invalid product data
Server resource limits
A failed background task

PW Merchant API should distinguish between errors that may be retried and errors requiring a product-data correction.

For example, a temporary connection timeout may justify a later retry. An invalid price or missing required value should be corrected before sending the same operation again.

Blindly retrying every failed product without understanding the cause can create unnecessary workload. PW Merchant API’s result and issue information should guide the next action.

Synchronise new and changed products without recreating everything

Efficient synchronisation does not always require resending the complete catalogue.

The PW Merchant API workflow should distinguish among:

New products that need to be inserted
Existing products that need to be updated
Unchanged products that require no immediate action
Failed products that require correction
Deleted or obsolete products that need removal
Out-of-stock products that need an availability update

This reduces unnecessary processing and helps merchants understand what has changed.

A product whose stock changes from 5 to 0 should remain the same product identity. PW Merchant API should update its availability instead of creating a second listing.

A product with a revised description should also remain the same item. Stable IDs allow PW Merchant API to update the correct record.

Handle removed WooCommerce products safely

When a product is permanently deleted or excluded from the store, its Merchant Center record should not remain active indefinitely.

Google states that products expire 30 days after their last refresh, although merchants should not depend on expiration as their primary removal strategy when an active synchronisation system can manage product changes. Manage products in Merchant Center

PW Merchant API should support a controlled approach to obsolete products:

Identify the existing Merchant Center item.
Confirm that the WooCommerce product is genuinely obsolete.
Avoid deleting a temporary out-of-stock item unnecessarily.
Remove or stop refreshing permanently discontinued products.
Handle deleted variations separately.
Confirm the result after Google processes the operation.

An out-of-stock product may remain valid with accurate availability. A permanently removed product requires a different action.

Migrate from an XML feed to PW Merchant API

Many WooCommerce stores already have an XML product feed before adopting PW Merchant API.

The transition should be controlled:

List the current Merchant Center data sources.
Identify the old XML source.
Record the existing product ID structure.
Connect PW Merchant API.
Select the correct Merchant Center account.
Configure the Merchant API data source.
Test a representative product group.
Compare price, stock, images, links and variations.
Verify that PW Merchant API results are processed correctly.
Stop the old feed from submitting the same catalogue.
Remove obsolete duplicate records safely.
Monitor the account after the next update cycle.

Do not keep the old XML feed and PW Merchant API active for the same full catalogue without a clear reason. Different identifiers can cause the same WooCommerce products to appear twice.

Google’s Merchant API migration guidance explains that the newer API provides explicit data-source creation and allows multiple API data sources. It also recommends migrating products carefully and removing former sources after the migration is complete when that matches the chosen structure. Google Merchant API data-source migration

PW Merchant API can become the primary WooCommerce Merchant API integration, but the old submission method must be retired deliberately.

Prevent staging websites from synchronising

A staging copy of a WooCommerce site should not submit products to the live Merchant Center account.

When a website is cloned, it may copy:

PW Merchant API settings
Google account information
Merchant Center account references
Scheduled synchronisation tasks
Product mappings
Stored identifiers
Background jobs

If synchronisation runs from both environments, the production catalogue may receive unexpected updates.

After cloning a website:

Disable PW Merchant API synchronisation on staging.
Do not run production schedules.
Do not send test products to the live account.
Use a dedicated test structure when testing is necessary.
Confirm that only the production site controls the real catalogue.

Common WooCommerce synchronisation mistakes

Frequent mistakes include:

Sending products before reviewing WooCommerce data
Selecting the wrong Merchant Center account
Running PW Merchant API and an old feed simultaneously
Changing product IDs during routine updates
Using duplicate SKUs
Sending variable-product parents incorrectly
Applying parent stock to every variation
Sending a price range instead of an exact variation price
Failing to update sale prices
Linking every variation to an unclear default page
Using inaccessible images
Treating a successful API request as product approval
Ignoring Google processing results
Retrying invalid products without correcting them
Deleting products instead of updating availability
Allowing a staging website to use production settings
Correcting data only in Merchant Center
Failing to remove obsolete integrations
Synchronising the complete catalogue during peak server usage
Assuming every product needs the same update frequency

PW Merchant API provides the technical connection and management workflow, but merchants should still maintain accurate WooCommerce data and monitor Merchant Center results.

Why choose PW Merchant API for WooCommerce?

PW Merchant API is built around the needs of WooCommerce merchants who want a more manageable Google Merchant Center connection.

Its role is to help merchants:

Connect WooCommerce with Google Merchant Center
Use the current Merchant API workflow
Review WooCommerce product data
Submit simple products
Process product variations
Synchronise prices and availability
Manage larger catalogues
Schedule product operations
Follow processing results
See product or account issues
Correct failed products
Retry suitable operations
Reduce dependence on manually maintained feeds
Manage the connection from WordPress

For a store with frequent price changes, many product variations or continuously changing stock, PW Merchant API provides a more direct management model than periodically creating an unrelated product file and waiting for the next scheduled retrieval.

PW Merchant API does not replace the need for accurate product data, a compliant ecommerce website or Merchant Center review. It gives WooCommerce merchants a structured way to connect, submit, update and monitor their catalogue.

Frequently asked questions

What is PW Merchant API?

PW Merchant API is a WooCommerce Google Merchant Center plugin that connects WooCommerce product data with Google Merchant Center through the Google Merchant API workflow.

It helps merchants review products, submit catalogue information, update prices and availability, follow processing results and manage Google Merchant operations from WordPress.

Does PW Merchant API use an XML feed?

PW Merchant API is designed around API-based product submission rather than depending solely on a traditional XML feed.

If an old XML feed already exists, it should be reviewed during setup to prevent the same products from being submitted through multiple uncontrolled sources.

Can PW Merchant API synchronise WooCommerce variations?

Yes. A suitable variation workflow submits each purchasable variation with a stable unique ID and uses shared grouping information for related options.

Variation prices, availability, attributes and images should be evaluated separately.

Does PW Merchant API update prices automatically?

PW Merchant API can support planned product synchronisation and price-update operations. The final behaviour depends on the configured synchronisation settings and schedule.

The price sent to Google must match the price visible on the WooCommerce landing page.

Can PW Merchant API update stock information?

Yes. PW Merchant API can transmit availability changes from WooCommerce to Merchant Center. Variable products should be evaluated at variation level so that one out-of-stock option does not incorrectly change all related variations.

Does a successful PW Merchant API submission mean that the product is approved?

No. A successful submission means that Google accepted the API operation for processing. Google then processes the product and determines its issues, status and possible eligibility.

Can PW Merchant API fix every Merchant Center issue automatically?

No integration can guarantee automatic correction of every issue. Some problems originate from missing WooCommerce data, landing-page inconsistencies, account configuration or Google policies.

PW Merchant API can help identify and manage issues, but the source information must still be accurate.

Should I remove my old XML feed before using PW Merchant API?

First test and verify the PW Merchant API connection. Once the new source is confirmed to contain accurate and complete products, retire the obsolete feed in a controlled way.

Leaving both systems active for the same catalogue can create duplicates.

Can I use PW Merchant API on a large WooCommerce store?

PW Merchant API is particularly useful for catalogues that need planned processing, product review and recurring updates. Large jobs should be scheduled and divided into manageable operations according to server capacity.

Where should product errors be corrected?

Errors should usually be corrected in WooCommerce or in the PW Merchant API configuration responsible for mapping the product data. Manual Merchant Center edits can be overwritten during later synchronisation.

Can an out-of-stock product remain in Merchant Center?

Yes, when it remains a valid product and its availability is updated accurately. A temporary stock shortage does not always require deletion.

What happens when a WooCommerce product is deleted?

A permanently removed product should no longer be refreshed and may need to be removed through the synchronisation workflow. Obsolete variations should also be handled individually.

Does PW Merchant API guarantee visibility on Google?

No. PW Merchant API manages the product-data connection and submission workflow. Visibility depends on Google processing, product quality, account configuration, programme eligibility and applicable policies.

Final PW Merchant API synchronisation checklist

Before starting WooCommerce product synchronisation, confirm that:

PW Merchant API is connected to the correct Google account.
The correct Merchant Center account is selected.
The website matches the Merchant Center business.
The primary API data source is configured.
Old XML feeds and integrations have been reviewed.
WooCommerce remains the source of product information.
Product IDs are stable and unique.
SKUs are not duplicated.
Product titles and descriptions are accurate.
Every submitted product has a valid price.
Sale prices are current.
Stock status is accurate.
Product images are accessible.
Landing pages work correctly.
Brand, GTIN and MPN information is handled properly.
Variable products are processed at variation level.
Related variations use valid grouping data.
Variation prices are exact.
Variation availability is accurate.
The parent product does not create an unnecessary duplicate.
Synchronisation timing suits the catalogue and server.
Staging websites cannot send production data.
Submission results are reviewed.
Google processing issues are monitored.
Corrections are made in WooCommerce or PW Merchant API.
Failed operations are retried only when appropriate.
Permanently obsolete products can be removed safely.
The catalogue is checked again after synchronisation.

Build a reliable WooCommerce Merchant Center connection

Reliable product synchronisation depends on accurate source data, stable product identity, controlled data sources and continuous monitoring.

PW Merchant API brings these requirements together in a WooCommerce-focused workflow. It allows merchants to manage product submission without treating Merchant Center as an entirely separate catalogue.

WooCommerce remains the place where products, prices, stock, variations and images are managed. PW Merchant API acts as the connection that prepares and sends this information through Merchant API. Google Merchant Center processes the submitted data and reports the resulting product status.

When this relationship is configured correctly, merchants gain a clearer way to manage:

New product submission
Existing product updates
Price synchronisation
Stock synchronisation
Variation management
Product issue tracking
Failed-operation handling
Obsolete product removal
Migration from older feeds

PW Merchant API is therefore not only a tool for sending WooCommerce products to Google Merchant Center. It is a product synchronisation and management system designed to help merchants maintain a cleaner, more current and more understandable connection between their WooCommerce store and Google.