Google Customer Reviews: setup and help

1. Upload and install the mprgooglereviews ZIP in Modules > Module Manager.
2. Click Configure, or open Google Reviews > Settings > Configuration.
3. Select the intended shop context if you use multistore.
4. Enter your numeric Merchant ID from Google Merchant Center.
5. Set Estimated Delivery Days, Badge Position and Badge Language.
6. Turn on Enable Google Customer Reviews and save.
7. Test in a fresh customer browser session with marketing consent. Complete a test order and check its native order confirmation page.

Your Google account must be configured to use the Customer Reviews programme. The module starts disabled with an empty Merchant ID. It does not create or administer your Google account.

Settings inherit from all shops to shop group to shop. Save in the correct context. Use inherited settings removes local overrides where available. Back-office read permission is required to view settings; saving also requires the appropriate edit permission and a valid request.

The module loads its browser scripts through displayHeader and supplies order survey data through displayOrderConfirmation. It displays the badge through displayBeforeBodyClosingTag, with a displayFooter fallback on PrestaShop versions below 1.7.

The Google script loads only when marketing consent, internal-traffic rules, data-sending policy and module ownership allow it. Test as a customer rather than a marked back-office employee. If another supported module owns Google Customer Reviews for the same Merchant ID, this module shows an ownership notice and leaves the badge and survey to that module. Its Product Review Feed remains separate.

On the shop's standard order confirmation page, the survey data contains:

• Merchant ID and order ID.
• Customer email and delivery country ISO code.
• Estimated delivery date calculated from Estimated Delivery Days.
• Distinct numeric GTIN values of 8, 12, 13 or 14 digits from the EAN-13 fields saved with the purchased items, when present. No GTIN checksum is checked.

The confirmation response is made private and non-cacheable. A delivery ledger prevents repeated admission for the same shop, Google destination and order. Reloading an old confirmation is not a reliable way to repeat a test. Use a new test order.

Google controls the opt-in UI, subsequent review invitations, badge availability and rating eligibility. There is no separate switch to hide the badge while keeping the survey enabled.

Open Google Reviews > Product Review Feed. This screen generates public Google Product Reviews XML schema 2.4 files from your existing product reviews. It is independent of post-purchase seller-rating collection.

Save your settings, then click Generate now. The status panel lists public XML URLs, written reviews and skipped reviews. Files use this pattern:

https://example.com/modules/mprgooglereviews/feeds/reviews_1_en.xml

You get one file per enabled active shop and active language. Product mapping includes available names, URLs, GTIN, brand and SKU. MPN is available where the PrestaShop product schema supports it. Submit the public XML URLs to Google, not the generation endpoint.

Map a Generic table

Use a dedicated public review table. Table and column identifiers must contain only letters, digits and underscores. You can include or omit the shop database prefix in Generic table.

For a table with id_review, id_product, rating, customer_name, title, comment, date_add and active, map those fields. Keep scale values 1 and 5 for a five-star source. This release does not hold generic mappings for public-column authorization or reject private fields by their purpose. Check every mapped column before publishing the XML.

The External cron URL panel displays a separate token-bearing URL for each shop, rather than a separate Cron token field. You need edit permission and a verified back-office browser session to view it. Treat the complete URL as a secret.

Send an HTTPS POST request. The displayed URL includes the token in its query string, which this release accepts. To keep it out of scheduler URLs, remove the token parameter from the URL and send that same value in the POST body as token. The X-MPR-Review-Feed-Token header is not supported.

curl --request POST \
  --data-urlencode 'token=YOUR_SHOP_TOKEN' \
  'https://example.com/index.php?fc=module&module=mprgooglereviews&controller=reviewfeed&id_shop=1'

The endpoint returns JSON for that shop. GET returns 405. An invalid token or mismatched shop is refused. Schedule a separate request for each shop you use.

The PHP process needs write access to modules/mprgooglereviews/feeds/. The module writes access rules that allow XML while denying PHP, temporary and lock files on servers honoring those rules. Confirm the equivalent protection if your server ignores .htaccess.

• Missing badge or survey: check enabled state, Merchant ID, marketing consent, employee markers and any ownership notice. Check browser console and Network errors.
• Survey missing on a custom checkout: confirm that the native order confirmation hook receives a valid order. Do not cache or prerender the confirmation response.
• Invalid settings: use numeric Merchant ID, delivery days 0 to 365, a listed position and a valid language code.
• Empty feed: check source availability, approval state, review text, dates, ratings, active products and product URLs. Inspect skipped counts.
• Generic feed fails: check the table, mapped column names, required fields and a stable review ID or primary key. There is no public-column authorization workflow in this release.
• Generation fails: check directory write access, employee shop permissions and whether another generation is already running.
• Cron fails: use POST, the correct shop endpoint and that shop's token query or POST parameter; header-only authentication is not supported.
• Configuration cannot be read: open Google Reviews > Settings > Integrity.

Configure the badge and survey in the module settings. Overrides of order-confirmation.tpl and badge.tpl do not control these settings.

Turn off Enable Google Customer Reviews to stop badge and survey output. Disable Enable product review XML feed separately to stop new feed generation. Existing XML files stay public; remove them from the feed directory when withdrawing a feed.

Uninstall through Module Manager to remove the module menu and configuration. Generated XML feeds remain in the feed directory if you keep the module files on disk. Check and remove any remaining public XML files. Ratings already held by Google are outside the module's local storage.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.