Google for WooCommerce: is “SHOPPING_PLUS” blocking product sync?

Are your products set to “Sync and show” but still pending? Does the log contain [primaryProductDataSource.destinations] Destinations of the data source are invalid: SHOPPING_PLUS.? Start by checking the Merchant Center data source and its destinations. Individual product titles, images or GTINs are not the first useful place to investigate this particular error.

A public report describes the error after reconnecting an account and switching Merchant Center accounts with Google for WooCommerce 3.10.0. The store owner reported running background jobs but no data source created by the plugin. A confirmed final resolution is not documented publicly in the thread. Q1

Four states to check separately

A simple breakdown helps with diagnosis:

1. Account connection: Is the intended Merchant Center account connected?
2. Data source: Does the data source associated with the plugin exist, with the correct input type and intended destinations?
3. Transfer: Has the specific product been sent to that data source?
4. Product assessment: Is the submitted product accepted for the intended destination?

This sequence is a diagnostic model. Success at one stage does not prove success at the next. In particular, a completed background job is not evidence that a specific product reached the expected destination.

What the error reveals about the data source

Google’s documentation describes destinations as the programmes targeted by a primary product data source. A data source can only enable destinations that are already available or enabled for the account. When destinations are explicitly specified, the data source is restricted to that selection. Q2

Preserve the exact string SHOPPING_PLUS in your diagnostic notes. It does not, by itself, identify which account setting is wrong in your installation. A vendor reply in the original thread discusses the relationship between account programmes and the requested destination; investigation of the final cause moved to private support. Q1

Do not replace the value experimentally with a programme name that sounds similar. First establish which request was actually sent and which destinations the connected account is allowed to use.

Safe first steps without deleting existing feeds

1. Preserve the exact error and timestamp. Record the full message, plugin version and affected period. Note whether it occurs during data source creation, product submission or a status query. Remove access tokens and private account information before sharing an excerpt.

2. Check the identity of the connection. Compare the Merchant Center connection selected in the plugin with the intended account. Use unambiguous IDs internally and placeholders in public material. Document any recent account switch so that old and new data sources are not accidentally mixed up.

3. Record the destinations available to the account. Note which marketing methods are enabled in the actual account and which ones the plugin requests. Google’s guide distinguishes, for example, between free listings and Shopping ads. Creating an advertising campaign is therefore not a universally valid repair step for an invalid data source configuration. Q3

4. Inspect the existing data sources. Record the name, input type, language, target market and association with the plugin. Distinguish API sources from file feeds and products found automatically. Initially leave existing, functioning sources untouched so that the current state remains traceable.

5. Trace one product attempt. Choose a suitable test product or a limited routine update. Connect the product reference, timestamp, job and specific API response. “Job completed” without its corresponding response is not a sufficient diagnostic result.

6. Identify the error category before running another full sync. WooCommerce documents full synchronisation for certain other issues, such as when the corresponding record for a previously synced product is missing. That does not establish that a full sync repairs an invalid destination. Q4

7. Change only the part shown to be at fault. If the data source or destinations remain unclear, prepare a focused support case with the configuration and sanitised response. Do not delete working feeds or all products, and do not repeatedly connect arbitrary accounts simply to produce a different state.

Is this already fixed in version 3.10.0?

The sources reviewed do not confirm that for SHOPPING_PLUS. Version 3.10.0, released on 20 October 2026, does include fixes for unsuitable data source types and an error in status processing. Those changes concern other, specifically documented messages. Q5 Q6

The report covered here already identifies version 3.10.0. Any version advice therefore needs to name the exact error: a resolved file/API conflict must not be presented as a confirmed solution for an invalid destination. Q1

Check the latest release information before making changes. When checked on 4 November 2026, the official directory still listed 3.10.0. Even a newer version would only provide reliable evidence of a solution if its changes address the specific error and your own flow passes verification. Q5

Frequently asked questions

Do I have to connect Google Ads for free listings to work?

This error does not establish such a requirement. Google’s API guide distinguishes free listings and Shopping ads as separate destination configurations. Check which option you actually want to use and what the data source is requesting. Q3

My products already appear under “Found by Google”. Is that enough?

To check the plugin’s synchronisation, identify the actual source used by the specific product. A product’s presence in Merchant Center does not tell you whether the current API attempt succeeded. Compare the source, product reference and time of the change.

Has a multi-client account been proven to be the cause?

No. This point was checked in the original thread, and the store owner confirmed a standalone account. The discussion therefore does not establish that a multi-client account caused this incident. Q1

Should I delete all products and sync them again?

That is not a justified first step for an error at data source level. First preserve a record of the existing products and their source associations. Consider resubmission only after a clearly documented correction and a successful, limited test.

Why can a background job finish even though nothing arrives?

Treat completion of the job and the outcome of the individual product attempt separately. Document the actual response instead of only the job status. Without that link, it remains unclear which part of the process succeeded.

What makes a support request useful?

Include the plugin version, exact error, timestamp, target market and language, most recent account switch, and a sanitised overview of the data source and destinations. Add the result of one traceable product attempt. Access tokens, complete customer lists and private keys are not required.

Describe your issue

Explain how long the products have been pending, which connection was changed most recently and where SHOPPING_PLUS appears. A sanitised example helps establish whether the data source, destination or another submission step needs investigation.