Galeria

PrestaShop Google Customer Reviews: Opt-in & Seller Ratings

The gcroptin PrestaShop module seamlessly integrates Google Customer Reviews opt-in on the order confirmation page. It dynamically injects accurate order data, including language, email, country, and an intelligently calculated estimated delivery date, ensuring optimal survey timing. With a clean Smarty template, it avoids fragile manual snippet pasting. Merchants can conditionally include product GTINs (EAN-13/MPN) for product-level reviews, enhancing data quality. This professional solution ensures robust, maintainable integration, requiring only a valid Merchant ID. It’s designed for predictable upgrades, helping e-commerce stores build trust with Google's seller ratings efficiently and reliably.

Module version: 1.1.1

Shop versions:

9.x8.x1.7.x

Works with ThirtyBees: No

Translations:

google reviews survey

Google Customer Reviews for PrestaShop -
opt-in, surveys, and trust signals done right

gcroptin injects the official Google Customer Reviews opt-in on the order confirmation page. No pasted snippets in themes: one Merchant ID , a clean Smarty template for the JavaScript, and real order data (language, email, country, estimated delivery, optional product GTINs). Turn product matching on or off with a switch-the products field is only sent when you want it.

displayOrderConfirmation - right moment, right customer

Smarty-driven JS + json_encode for safe values

Smart estimated delivery date logic

[Insert screenshot: module configuration - Merchant ID, include GTIN switch, fallback delivery offset + order confirmation with GCR opt-in]

Why “just paste the Google snippet” is a bad idea

Google’s documentation shows static JavaScript. In a real PrestaShop store you need dynamic values: the buyer’s email, the order reference, the delivery country, a believable estimated delivery date , and optionally GTINs so reviews can attach to products- not only to the shop.

Hard-coding that into a theme or a generic HTML block means fragile copy-paste, editors that strip tags, and no clean separation between what Google expects and what your shop knows . When Google changes a field or you multishop, you chase regressions.

gcroptin keeps the contract with Google in one versioned Smarty template , feeds it with computed PHP data , and exposes only what merchants need in configuration: Merchant ID, whether to include the product payload, and a fallback offset when the shop cannot infer a better delivery horizon.

Paste-in snippets vs gcroptin

Manual JS in CMS blocks: WYSIWYG editors and cache layers love to break script tags. One save and your opt-in vanishes.
Guesswork delivery dates: Sending “today + 2” for every carrier and country trains bad data and unhappy reviewers.
Always-on product arrays: Forcing products when your catalog lacks EAN-13 can weaken signal quality.
gcroptin? Template-owned markup, guarded output, conditional products , delivery date resolved from order + carrier + shop settings, then fallback. Merchant ID required - no silent half-broken installs.

What you get

Smarty template for the GCR script

Front-office output lives in views/templates/hook/gcroptin-order-confirmation.tpl . Override it in your theme under modules/gcroptin/… when you need markup tweaks-without forking PHP.

Conditional `products` payload

Toggle Include product GTIN list . When off, the products key is omitted from gapi.surveyoptin.render -cleaner than sending empty arrays. When on, each line uses EAN-13 with MPN fallback for the gtin field.

Estimated delivery date, calculated

The date sent to Google is built in layers: use the order’s delivery date when set; otherwise order date + N days where N comes from the carrier ( max_delivery_time / max_delay when present), then shop PS_SHIPPING_DELAY , then your configured fallback offset .

Merchant ID gate + safe JSON

Nothing renders until a valid numeric Merchant ID is saved-no accidental blank surveys on production. Strings passed into the template are prepared with json_encode so quotes and special characters in emails do not break the opt-in.

Template-first architecture

One hook, one tpl, predictable upgrades.

Maintainable by design

The module resolves the current order , builds an array of variables (merchant id, language ISO, order id, customer email, delivery country, estimated delivery date, include-products flag, and the pre-built products JSON when enabled), then renders the template.

That separation means your team can audit the exact payload Google receives by reading one template file. PHP stays focused on data integrity and business rules -not on hand-maintained script blobs in the database.

Theme override path

Copy gcroptin-order-confirmation.tpl into your theme’s modules/gcroptin/views/templates/hook/ folder to customize markup while keeping module updates safe.

Delivery date that respects reality

Order, carrier, shop-then your fallback.

Better data for Google’s survey timing

Google uses the estimated delivery window to decide when to ask for a review. Flat “+3 days for everyone” ignores carriers, cut-off times, and country-specific logistics.

gcroptin prefers structured signals from PrestaShop: a real order delivery date when your workflow sets it; otherwise it walks a short priority list (carrier max delivery, global shipping delay, module fallback) so the submitted date tracks your shop configuration instead of a single hard-coded constant.

Fallback offset remains configurable-ideal when carriers do not expose numeric delays in your PS version.
ISO date output ( YYYY-MM-DD ) matches Google’s expected format.

GTINs when you are ready

EAN-13 first, MPN fallback-documented in config.

Product-level reviews need clean identifiers

When you enable the GTIN list, each ordered product becomes a small JSON object {"gtin":"…"} . The module reads EAN-13 from the order line; if it is empty, it falls back to MPN . The include switch description in the Back Office reminds you that rich EAN data improves match quality in Google’s ecosystem.

If your catalog is not ready yet, turn the switch off: the opt-in still runs for the order, but without the products block-no invalid or half-empty arrays sent “because the tutorial said so.”

Back Office: only what merchants need

No giant script textarea. Set your Merchant ID , decide whether to send product GTINs , and tune the fallback delivery offset . The module explains how delivery is computed and where the template lives.

Trust & safety

No opt-in output until Merchant ID is valid
JSON-encoded strings for JavaScript embedding
Official Google loader URL for the survey opt-in API

Merchant outcomes

Collect eligible post-purchase reviews
Support Google’s seller rating ecosystem with less engineering risk
Keep upgrades predictable-logic in PHP + tpl, not in CMS HTML

Technical specification & compatibility

Native PrestaShop module: registers displayOrderConfirmation , ships a hook template, and uses configuration keys for Merchant ID, include-products flag, and fallback delivery offset. Compatible with PrestaShop 1.7 through 9.x per module metadata-verify on your staging theme before production.

Hook: displayOrderConfirmation - runs after a successful order, ideal moment for opt-in.

Template: gcroptin-order-confirmation.tpl - GCR language block + platform script + render callback.

Configuration: Merchant ID (required), include GTIN list (yes/no), fallback delivery offset (days).

MyPresta: Update checker integration in module configuration (where enabled in your distribution).

Module Gallery

Why choose our module
Google Customer Reviews for PrestaShop - opt-in & survey (GCR)?

Optimization and Automation

This module automates the Google Customer Reviews opt-in on the order confirmation page. It optimizes data quality by dynamically providing accurate customer details, smart estimated delivery dates, and conditional product GTINs, eliminating manual snippets and reducing engineering risks for reliable review collection.

Increased Sales

This module directly increases sales by injecting official Google Customer Reviews opt-ins, building crucial trust signals. It leverages real order data to enhance Google's seller ratings, inspiring buyer confidence and boosting conversion rates through authentic post-purchase reviews.

15 years of experience

With 15 years of PrestaShop expertise, we crafted this module to bypass common integration pitfalls. It dynamically injects Google Customer Reviews opt-ins using Smarty, providing precise estimated delivery dates, conditional GTINs, and secure JSON. This robust, template-first approach ensures upgrade-safe integration and reliable data for Google's survey timing.

Extensive Customization

The module provides extensive customization with its theme-overridable Smarty template for the Google opt-in script. Merchants can toggle product GTIN inclusion and fine-tune the delivery date logic with a configurable fallback offset, adapting to specific store requirements.

Open Source Code

This module boasts a template-first architecture, providing full access to its Smarty template for the GCR script. This enables safe theme overrides and markup customization without forking PHP, ensuring complete auditability, flexible modifications, and predictable upgrades.

License and Updates

Designed for predictable upgrades, this module ensures future enhancements are seamless by separating logic from templates. It integrates an update checker, making it easy to keep current with Google and PrestaShop requirements without manual script changes.

Modules

Services

Your cart