Problem with not being able to send products to Google Merchant Center
Hello,
I have a PrestaShop based e-commerce site. A few months ago, I created a Google merchant account and started sending my products to Google via “product feed”. However, I noticed that the products could not be sent for a while.
A warning message as follows appears in the “Product Feed” section under the Prestashop –> Marketing –> Google –> Configure menu;
“You can’t send your products data to Google right now. Try again later.”
There is a “Refresh Page” button under this warning. Even though I pressed this button at different times, there was no change.
I wonder what is the reason for this problem? Can you help me?
My e-commerce site: www.morcuval.com
Best regards.
The short answer is:
The error “You can’t send your products data to Google right now.Try again later.” almost always indicates a temporary or persistent connection failure between the PrestaShop module and the Google Merchant Center (GMC) service.
The most common causes are a simple timeout, a firewall/server configuration issue blocking the connection, or an expired/invalid authentication token or API key.
The long-term solution is to move away from the traditional “product feed” file upload to a direct, real-time integration using the Google Merchant API (formerly Content API for Shopping) which offers far superior reliability and speed.
The long answer is:
The warning message you are seeing suggests a problem with the communication layer, not necessarily with your product data itself.
Since refreshing the page hasn’t helped, the issue is likely rooted in one of three areas: the PrestaShop module’s configuration, your server’s environment, or the Google Merchant Center account’s connection status.
For immediate troubleshooting, first check your Google Merchant Center account directly to see the status of your product feed.
If the feed is expired or has an unfixable error, the PrestaShop module may be failing to connect to an account it deems “broken.”
Second, ensure your PrestaShop module has the correct, non-expired API credentials (token/key) and that your server’s PHP settings, like memory and execution limits, are not timing out the feed generation process, as this is a common cause of generic errors.
Finally, check your server’s error logs, as they may contain a specific connection error code that the module is failing to display.
However, the file-based product feed method is inherently prone to these kinds of generic failure messages and delays.
The superior, highly reliable, and relatively cheap long-term solution involves implementing an automated, server-to-server connection using the Google Merchant API (which is the official successor to the Content API for Shopping).
Here is how a Content API solution works with your PrestaShop site:
Instead of generating a static XML file and waiting for Google to fetch
it, you would use a dedicated module or custom development to interact directly with the Google Merchant API.
The API allows your PrestaShop store to send product data updates (price change, stock change) instantly.
This eliminates the “can’t send” problem entirely because the product data is pushed immediately upon change, instead of relying on a batch job.
To trigger this real-time push, you can leverage the built-in PrestaShop Webservice API or use custom webhooks tied to events like a product’s price or stock being updated.
This is the mechanism that tells your integration, “A product just changed, push the update to Google now!”
By implementing this level of server-side data control, you can also drastically improve your conversion tracking quality.
You would use Google Tag Manager (GTM) on your store’s frontend to capture anonymized customer data (like a hashed email address) at the point of purchase.
Then, the same system that pushes products can be extended to utilize the Google Ads API to send Enhanced Conversions data server-to-server.
This ensures that every conversion is accurately tracked, even if the customer’s browser or ad-blockers prevent client-side tracking, providing your smart bidding campaigns with the best possible data.
Hosting: This whole system requires minimal hosting resources, making it very cheap to run on a service like Stape or Google Cloud Platform (GCP).
The reliability, speed, and accuracy gained from this direct API-to-API approach far outweigh the small cost of hosting.