Build cached Google Merchant XML feeds for PrestaShop with variants, images and market settings
Google Merchant XML & API Integration is a module for PrestaShop stores that sends the product catalogue to Google Merchant Center as XML and through a direct connection, then keeps prices, stock and product details aligned. Setup is short: install the module, connect the Merchant account and create the first feed profile.
Google Merchant Center is Google’s free product-listing service. Its account holds product data, shows approval issues and performance, and places eligible offers in free listings across Search, Shopping, Images, Maps, YouTube, Lens and Gemini. Paid product advertising is optional and billed separately by Google.
The module gives each shop, country, language and currency its own profile. You choose products, categories and brands, include variants, map shop categories to Google’s official classification, set shipping rules and filter the catalogue by image, stock, identifiers, condition, price, quantity or discount. Automatic updates follow catalogue changes, while a local hour and timezone control the full scheduled refresh.
Merchant titles, descriptions, product types, official attributes, campaign labels and tracking links remain separate from the storefront text, with values for each product and language. Loyalty-group prices, promotions, reviews and local stock travel in their proper feeds. Priorities prevent overlap between profiles, a deletion limit stops an unexpected mass removal, and the diagnostics area isolates failed products and retries them without holding back the rest.
The result is accurate product visibility, fewer rejected offers, safer international catalogue work and less manual maintenance.
What does Google Merchant XML & API Integration take care of?
Google Merchant XML & API Integration turns a PrestaShop catalogue into controlled product sources for Google Merchant Center. One profile publishes XML and updates the Merchant account directly, while the same workspace controls markets, product selection, data enrichment, safety and daily supervision.
- The first section explains the two delivery routes and the product sources managed by the module.
- The market section covers shops, countries, languages, currencies and update timing.
- The selection section defines which products and official details reach Google.
- The enrichment section separates Merchant content, campaign data and loyalty prices from the storefront.
- The safety section protects against duplicate offers, mass deletion and invalid publication.
- The operating section brings setup, progress, errors, history and recovery into one place.
How does each market receive the right catalogue?
Every profile belongs to a selected shop and carries its own target countries, content language, currency, feed label and priority. Product links open in the currency advertised by that profile, so the landing page and submitted price describe the same offer. A single account therefore stays orderly across several storefronts and markets.
The profile publishes XML and updates Merchant Center directly in the same run. Catalogue changes to price, stock, title, translation, image or variant trigger an immediate refresh of the affected offers. The complete catalogue refresh follows the local hour and timezone set for that market, and unchanged products are left untouched.
This structure turns a new country into another repeatable profile, rather than another manually repaired file.
Which products and product details reach Google?
Selection starts with the whole catalogue or chosen products, category trees and brands. Include and exclude groups combine with limits, while filters remove products without an image or identifier, unavailable items, selected conditions, prices outside the chosen range, low stock and offers below the required discount. A preview shows the resulting set before publication.
Variants arrive as separate offers with their own price, availability, identifiers, image and shared product group. A searchable official classification links each shop category with the right Google category for each country and reports anything still unmapped. Dedicated fields cover material, gender, age group, size, adult status, highlights, certifications and energy labels. Shipping costs follow country and carrier rules.
Separate sources carry promotions with their effective dates, product reviews and stock held by physical locations, so each type of information follows the structure Google expects.
How does Merchant data stay independent from the storefront?
A feed profile has its own title, description, product type, Google category and five campaign labels. Each product receives a different value for each shop language when needed, without changing the product page read by shoppers. Campaign tracking details are merged safely into product links, including links that already contain parameters.
Merchant-specific fields use simple text, longer text, number or selection controls, with a default for the profile and an exception for a single product. Loyalty settings map PrestaShop customer groups to programme tiers and submit the real group price only when it is lower than the public feed price. Promotions carry their identifier and sale period.
For teams that need complete file control, the XML opening, product block and closing remain editable. Ready fields and official validation handle the everyday work, while the full template remains available for a specialised catalogue.
What protects the catalogue from costly mistakes?
Feeds assigned to one Merchant account have an explicit priority. The overlap report shows products claimed by more than one profile, and automatic separation removes them from the lower-priority profile before publication. Two simultaneous runs never alter the same feed at once.
Before products disappear from Merchant Center, the module compares the removal set with the known catalogue. An adjustable percentage limit blocks an unexpectedly large deletion. Direct writes also verify that the current shop, its address, product links and image links all belong to the declared live store, so a development copy or clone never changes the live Merchant account.
XML is validated before it replaces the previous valid file, dynamic text is escaped correctly, and shared-stock shops submit the availability that PrestaShop actually uses. One malformed value therefore never turns into an empty feed or a false stock promise.
How does daily operation stay simple?
Installation adds dedicated areas for Merchant accounts, feeds, custom values, settings, diagnostics and integrity. The first working profile needs the account connection, market, product selection and delivery choice. Sensible defaults fill the remaining fields, including the standard refresh lifetime.
The diagnostics workspace shows each run, affected offers, completed and remaining work, retry state and practical error details. Long jobs continue in safe batches with live progress and remaining-time estimates. Failed products wait for an automatic retry while successful products finish normally, and run history is exportable and removes old entries according to the selected retention period.
That makes the module quick to launch for one market and deep enough for several shops, loyalty tiers, specialised product data and tightly governed catalogue operations.
-
Referencemprgooglemerchantfeedmanager
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.7 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront & Back-office
-
GDPR RelevantYes
-
Business GoalIncrease Traffic
-
External Account NeededYes
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageAttract Visitors
-
Works With PlatformGoogle Services
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Automatically generate Google Merchant XML feeds from your PrestaShop catalogue, or sync product inputs directly to Google Merchant Center through the Merchant Products API. Smart Google Merchant Feed Manager helps you control product selection, feed fields, variants, Merchant Center accounts, custom labels, and scheduled feed refreshes from the Back Office.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1301
questions
9
categories
2013
building modules since
1.6–9
PrestaShop versions
v1.4.62026-05-27
- AddedAdd Merchant Products API sync
- AddedImprove feed quality — strip empty tags, fix availability, add identifier_exists
- Addedcomplete FR/DE/ES/IT/PL translations
Loading full changelog...
Works Well With Google Merchant XML & API Integration
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
A store running Smart Google Merchant Feed Manager shapes catalogue data into protected XML feeds or Content API syncs for Google Shopping, with profiles for markets, languages, currencies and countries. A clean feed gets products into Shopping, but the same products also appear in organic search, where Google reads the page itself rather than the feed to understand them.
Automatic SEO Schema Rich Snippets covers that on-page side by adding structured data so search engines can understand products, categories, CMS pages, breadcrumbs and site identity, with Organization and WebSite output. It works on the storefront markup, a separate channel from the Merchant feed.
Running both, your product data is well-formed in two places that matter: the feed Google Shopping consumes and the schema on the live pages organic search reads. Each operates independently, but together they give Google consistent, structured product information across both paid Shopping listings and organic results.
Measurement
With Smart Google Merchant Feed Manager, a store publishes product data so Shopping campaigns have something to advertise. Getting products listed is one half of paid acquisition, but it tells you nothing about what shoppers do after the click, whether they view, add to cart, start checkout or actually buy.
Google Analytics GA4 covers that measurement side, sending ecommerce activity, product views, cart activity, checkout starts, purchases, searches, logins and account creation, built from PrestaShop actions, with Measurement Protocol purchase support. It validates the GA4 ID before tracking and is a separate analytics tool, not part of the feed.
Together, the feed gets products in front of shoppers and GA4 shows how that traffic behaves once it lands. You can see which product interest turns into carts and orders, so feed and campaign decisions rest on real on-site behaviour rather than only on whether listings are live.
Governance
A store using Smart Google Merchant Feed Manager depends on its feed staying current, since Shopping listings go stale or wrong when a scheduled sync quietly stops running. The feed module does the syncing, but knowing whether those routine jobs actually fired is a separate operational concern.
Cron Manager covers that by giving one Back Office place to check whether routine module tasks are running, centralising MPR module tasks, protected scheduling links, manual runs and task status, helping protect feeds, cleanups and synchronisations from silent failure. It oversees scheduled work rather than building feeds itself.
Running both, your feed keeps doing its job while Cron Manager gives your team visibility that the underlying scheduled runs are happening on time. If a sync stalls, you find out from the task status screen instead of from disapproved Shopping listings, so the feed stays trustworthy and problems surface where they can be acted on.
Measurement
A store running Smart Google Merchant Feed Manager lists products for Google Shopping, but listings only become worthwhile if the paid orders they drive are credited back to the campaigns. The feed gets products advertised, yet it does not report a purchase conversion to Google Ads when an order completes.
Google Ads covers that focused need, sending purchase signals directly from order confirmation into Google Ads using the Conversion ID and purchase conversion label, giving campaigns clearer revenue feedback from paid orders. It is a separate conversion-tracking module, not a function of the feed.
With both, your products reach Shopping through the feed and your completed orders report back to Google Ads as conversions. Campaigns get revenue feedback from real purchases rather than clicks alone, and the two work as independent pieces of the same paid-Shopping setup, one supplying the listings and the other measuring what they earn.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
