Fixing Product Sync: PrestaShop Sending Fewer Products to Google Merchant Center

Merchant not receiving all products from PrestaShop store

Hi, I’m using Prestashop and the module “PrestaShop Marketing with Google” (latest version) to send information to my Merchant account.

In the PrestaShop it shows that will send 337 products to sync, but in Google Merchant only shows 124. Is it possible to understand it Google Merchant is blocking some products? 

I have deleted the feed and recreated again and I always get the same behavior.

Thank you!

The short answer is:

Why is the PrestaShop “Marketing with Google” module showing a higher product count than what appears in Google Merchant Center?

Yes, it is very possible that Google Merchant Center is blocking or rejecting the majority of your products, or your PrestaShop module is incorrectly filtering them before sending the feed.

The discrepancy between 337 products ready to sync and 124 products in Merchant Center points directly to two common issues: products violating Google Shopping policies or missing crucial attributes like gtin, mpn, or brand.

To diagnose, you must check the “Diagnostics” section within Google Merchant Center, which will explicitly list the rejected items and the exact reason for the block.

For a highly reliable, real-time feed solution that bypasses common module limitations, you should look into a server-side implementation using the Content API for Shopping, rather than relying solely on the module’s feed generation.

The long answer is:

Your experience with the “PrestaShop Marketing with Google” module is a classic indicator of a synchronization failure that happens in two stages: filtering on the store side, and rejection on the Merchant Center side.

The initial drop from 337 to 124 items is too drastic to be a simple delay, especially after recreating the feed.

First, you need to address the immediate problem by using the tools Google provides.

Log into Google Merchant Center, navigate to the Products section, and then click on the Diagnostics tab.

This is your single source of truth.

It will show a dashboard of product issues, categorized as “Critical” (rejected and not showing in ads), “Warning” (issues that may limit performance), and “Pending.”

You should see an exact count of the 213 missing products, along with the precise violation, such as “Missing required attribute: gtin” or “Inaccurate product price.”

This is the only way to confirm why Google is blocking them.

Common reasons include missing unique product identifiers (gtin, mpn, and brand), products listed as unavailable in stock, or policy violations like misleading images or poor landing page quality.

Second, for a robust and long-term solution, you should stop relying on the PrestaShop module to build the XML feed file.

These modules often have performance issues and limited control over data fields.

The most advanced and reliable method for product synchronization is using the Content API for Shopping.

This allows your store to send product data to Google Merchant Center in real-time, one product at a time, rather than relying on a slow, scheduled feed file upload.

A scalable and cost-effective way to achieve this server-side integration is by combining the PrestaShop Webservice API/webhooks with a server-side tagging environment.

You would use a system like Google Tag Manager (GTM) Server Container, hosted cheaply on a service like Stape or Google Cloud Platform (GCP).

The process works like this: when a product is created or updated in PrestaShop (a confirmed event via webhook), that event is captured by your server container.

The server container then uses a Content API for Shopping tag to push the product data directly to Merchant Center.

This ensures that the data is clean, sent immediately upon change, and can be enriched with the highest quality information for better ad performance.

Furthermore, you can use the same server-side structure, leveraging the Google Ads API, to send crucial offline conversion data, such as a final sale confirmation, back to Google Ads, creating a single, powerful, and reliable data pipeline that entirely bypasses the unreliable feed module.

About The Author