PrestaShop reviews: collection, Google ratings and complaint handling

What we would do

We would keep a working review system until you can name the gap: missing product feedback, requests that never arrive, features your buyers need or independent store reputation. Diagnose collection before replacing the display. A new badge does not repair a broken invitation sender, and a paid account does not turn store feedback into product reviews.

The right route depends on your existing PrestaShop and PHP versions, theme, checkout, order-status and carrier integrations, review history, product identifiers, languages and markets. Include the people who will moderate reviews and answer complaints. A system your team cannot maintain is a poor fit even when its demonstration looks right.

For an integration change or migration, we would work on a private staging copy with customer emails, live invitations and external synchronisation disabled. Rehearse collection, display and permitted data migration there, then make a planned switch with backups, the previous configuration and clear reversal steps. Do not enable a second invitation system until you have decided which orders each sender owns.

If you have chosen a module and want its settings and customer journey checked, the PrestaShop Module Installation & Configuration Service covers that agreed setup; licences and custom integration work are separate.

Choose the review type you need

A product rating is not a store rating. Do not apply a shop-wide service score to every product. Google Customer Reviews can collect optional product feedback, but it does not automatically add review widgets to your product pages.

Choose based on the features you need: purchase verification, photos, merchant replies, request delivery, moderation, export rights and search integration. Compare the actual installed release or current plan. A paid platform can include automated collection; a local module does not necessarily include a working sender.

Business Profile eligibility is separate from ecommerce review collection. An online-only shop cannot create a profile solely to collect reviews if it does not meet Google's in-person customer-contact requirements.

Decide whether to keep, extend or add a system

Compare ongoing work as well as the licence: request delivery, moderation, backups, provider access and future theme changes. Local storage gives you operational control but also responsibility for maintaining the records. A hosted profile can complement on-site product reviews; assign each a purpose rather than displaying competing totals as though they measure the same thing.

Check Product Comments by version

Product Comments is a first-party module, not an inseparable core feature. It may need to be installed separately. Select a release compatible with your PrestaShop and PHP versions and test your theme's review hooks.

Product Comments supports star ratings and configurable criteria. Open Modules > Module Manager, find Product Comments and select Configure to inspect the criteria and the moderation queue; where the installed release supports it, assign criteria to relevant categories, such as fit for clothing. In releases exposing these settings, check PRODUCT_COMMENTS_MODERATE for moderation, PRODUCT_COMMENTS_ALLOW_GUESTS for optional guest submissions, PRODUCT_COMMENTS_MINIMAL_TIME for the minimum submission interval and PRODUCT_COMMENTS_USEFULNESS for helpfulness voting. Record the installed values rather than assuming installation defaults. It also exposes GDPR-related integration hooks. Those hooks do not by themselves establish your shop's legal compliance.

Do not assume the basic module verifies purchases, sends post-purchase requests, accepts photos or provides a hosted platform's moderation and import features. Check each requirement in the release you intend to use.

These release-specific distinctions are documented in the 9.0.0 source and 7.0.0 list template. They do not mean that every theme outputs valid review markup.

For local reviews, back up the database tables, including your prefix followed by product_comment, product_comment_criterion and product_comment_grade, plus any module-specific tables and uploaded media. Check the schema before migrating between releases.

For a local route with photos, verified-purchase badges and public replies, Product and Store Reviews keeps review records in your PrestaShop database. It queues reminder records when an order enters a state with the delivery flag. That flag is not confirmation of parcel delivery, and queueing a record does not send an email. Arrange and test a working reminder sender before relying on requests.

Understand Google Customer Reviews and its order data

Google Customer Reviews is a free Google programme with an order-confirmation opt-in and a survey sent by Google after the supplied estimated delivery date. Integration work or a third-party extension can still cost money.

Enable the programme in Merchant Center and follow Google's survey opt-in specification. It requires the opt-in on confirmation pages, HTTPS and accurate transaction data. A third-party payment flow must return customers to the appropriate confirmation page.

In PrestaShop, use a confirmation integration that reads the actual order. The displayOrderConfirmation hook receives order context; a theme's presented order array is not a legacy Order object. Do not assume an arbitrary payment-return hook runs for every payment method.

A missing required date can invalidate the payload. An inaccurate date can schedule a survey too early or too late. A carrier's delivery-time label is not automatically an order-specific calendar date. Test cutoffs, weekends, stock delays, countries and split deliveries in the date calculation you use.

The Google Customer Reviews module calculates today plus a configured day offset, rather than reading an order-specific date from Estimated Delivery Date. Check its supported configuration before choosing the survey timing.

The Estimated Delivery Date module displays estimates on product pages, in the cart and at checkout, and saves the accepted estimate with the order. Passing that saved date to the Google survey requires a separate integration; check the actual confirmation payload.

Test the actual confirmation payload for each payment path, language and destination. Keep the opt-in visible on mobile and desktop. An order-confirmation opt-in for a Google survey is not newsletter consent.

Worked example: different payment and delivery journeys

Suppose your shop sells stocked accessories alongside made-to-order products. A card customer returns to confirmation, while another customer closes the payment provider's page after paying. The paid order alone does not prove that either customer saw the survey opt-in. Record the actual return journey and where the prompt appears; do not fabricate consent for the customer who never saw it.

For a mixed order sent in separate parcels, agree which realistic date represents the experience the survey asks about, then compare that date with the submitted payload. A fixed day offset that suits the accessory may be too early for the made-to-order item. If that cannot be represented by the chosen module's settings, scope the missing integration rather than assuming the product-page estimate is already connected.

Keep the order reference, expected country and date, captured payload and observed opt-in together as test evidence. That makes a later complaint about an early survey traceable to the calculation or return path, rather than to a guess about Google's email delivery.

Evaluate Trustpilot invitations and widgets

Separate service-review collection from product-review collection when comparing Trustpilot plans. Confirm invitation limits, reminders, product widgets, exports and supported PrestaShop/PHP versions. Stable product identifiers matter: a base-product reference and a combination reference are separate fields. Match reviews to the intended product or variant using the identifiers required by the integration.

For example, a shirt's size combinations may have different references while the provider groups feedback under the parent product. Record that mapping explicitly. Trace a purchased combination from the order line to the invitation identifier and the displayed product, including a combination with a blank reference. Resolve missing or reused identifiers before importing historical reviews or changing catalogue references.

The official Trustpilot integration has confirmation-page and order-status paths governed by the configured invitation trigger. Check that trigger in your installed release. Select timing based on when the customer can reasonably evaluate the experience, and test a real invitation through the complete delivery path.

Do not confuse a state named Shipped, the state's delivery flag and a carrier-confirmed delivery event. If you need delivered-only requests, require a reliable delivery signal and an explicit matching condition.

A service badge, an ordinary product widget and a Product Review SEO widget have different jobs. Trustpilot's widget guidance states that Product Review SEO widgets include structured data. Inspect the selected widget before adding another rating block.

Place a compact service badge where it helps establish shop identity, and product reviews near the information used to choose that product. Keep the review content accessible on small screens. Measure the selected widget's requests, loading behaviour and reserved space; third-party code is not inherently render-blocking or layout-shifting. On staging, block its external requests and confirm that product selection, the buy button and the route to checkout still work when the badge cannot load.

The separate Trustpilot Review Widget extension displays your store reputation in its supported placements. It sends no customer or order details, so displaying it does not establish an invitation integration or product-review collection.

Validate product markup and store-rating eligibility

Product review snippets

Use ratings and review text about the product shown on the page. Keep the visible average, count and structured data consistent. Permission to import reviews does not by itself make them eligible for review snippets: check Google's restrictions on ratings aggregated from other websites before including imported feedback in structured data. Follow Google's review snippet requirements and Product snippet documentation.

JSON-LD can be in the head or body; it is not the only supported format. JavaScript-generated markup can be processed. Multiple Product blocks do not automatically invalidate each other, but contradictory prices, ratings or identities need investigation. Assign responsibility for the Product entity and remove conflicting output deliberately.

Automatic SEO Schema Rich Snippets emits its own schema, can remove existing markup and reads local product-comment ratings or configured overrides, rather than automatically fetching or merging Trustpilot ratings.

View Source shows only the initial HTML. Use Search Console URL Inspection to check rendered content and the Rich Results Test to check structured data. Google can render JavaScript, but blocked resources, errors and delayed content can cause problems. Check whether reviews appear in the rendered page and whether the page is indexed, even when reviews are stored locally.

Self-serving LocalBusiness or Organization review markup is not a route to Google review-snippet stars for your own business. Store ratings use a separate system. Valid Product markup establishes eligibility, never guaranteed stars or a conversion increase.

Google store ratings

Do not use one review threshold for every surface. Google Ads store-rating guidance describes enough eligible country-specific reviews within 24 months, commonly 100 or more, or a qualifying research evaluation. Text ads require at least 3.5 stars, matching domain information and other eligibility conditions.

The Customer Reviews badge guidance separately describes ratings based on the past year; the badge can show "Rating not available". Check Merchant Center and the current guidance for the surface you use. A review count, country total or valid feed does not guarantee display with every ad or listing.

Record a baseline and compare impressions, clicks, conversions and actual rating display for the affected pages or campaigns. Use comparable traffic and enough data for a useful comparison. Account for other changes before attributing a change in score or click-through rate to the widget.

Collect fairly and protect review data

Use a working request system or a direct review-form link after customers have had time to experience the product. A permitted packaging insert or QR code can offer another route. Select timing and recipients consistently, without filtering by predicted sentiment.

Do not buy fake reviews, ask only happy customers, or route unhappy customers away from the public review opportunity. Trustpilot prohibits incentives, including discounts and loyalty points, under its business guidelines. Google Product Ratings permits certain neutral incentives only under its disclosure and other programme policies. An offer for any rating is not automatically allowed everywhere.

Review the FTC's solicitation guidance and applicable local rules; UK businesses can consult the CMA fake-review guidance. Disclose relevant connections and incentives where required. Never condition a remedy on changing or deleting a review.

Moderate against a published policy, not the score. Remove or report spam, personal data, abuse and other policy breaches through the proper process. A genuine negative review may still need a public response. Distinguish a service complaint from product feedback without hiding criticism because it is inconvenient.

Before moving to another review system

1. Check the source provider's export and redistribution terms and the reviewer's rights before importing anything.
2. Export and back up only what you are permitted to retain, including dates, product mapping, rating scale and verification provenance.
3. Keep product and service reviews separate. Do not turn a service review into a product rating.
4. Map identifiers and media in staging, check duplicates and compare counts and averages. Quarantine unmapped products and unexplained rating differences; do not guess a product match or invent verified-purchase status to complete an import.
5. Test visible output, rendered content and structured data before retiring the old display.
6. Update your privacy, retention and data-request processes for the new storage location.

Trustpilot's service-review export guidance expressly restricts exporting reviews for display on other platforms. A downloadable CSV is not permission to republish it. Cancellation and free-plan display rights vary; do not assume all hosted reviews disappear when payment stops.

Rehearse the review journey and plan the switch

1. Inventory every collector, sender and display: local modules, provider connectors, template snippets, tag-manager scripts and scheduled jobs. Record which system supplies the visible count and which supplies Product markup.
2. Use approved test accounts and test recipients. Keep copied customer details out of provider submissions, exports and reminder jobs. Follow the provider's permitted testing process before sending anything to its live service.
3. Submit a test review and follow it through moderation to the intended product page. Check guest and signed-in journeys where enabled, a rejected policy breach, a legitimate negative review and a merchant reply where supported.
4. Trace an eligible test order through the invitation trigger, queue, scheduled worker, provider hand-off and received message, whichever stages your integration uses. Check the review link on mobile and confirm that a repeated event or retry does not create unintended duplicate requests.
5. Check the review summary after publication, moderation changes and deletion. Compare the visible average and count with structured data, then refresh caches and repeat the check. Keep evidence for a reviewed product and a product without reviews.
6. Set the cutover boundary before enabling live collection: which historical orders remain with the old sender, which start in the new one and what happens to pending reminders. Save the settings and queue position so reversal does not replay requests to customers already invited.

A staging copy cannot prove delivery through the live provider account by itself. After the planned switch, make the agreed live check using a permitted recipient, watch the next eligible order and retain the evidence. If you reverse the change, reconcile invitations already sent and reviews collected since the switch before restoring data; an old database backup can discard those new records.

What to ask your developer or agency

• Which installed releases, theme templates and custom integrations did you test, and which requirements remain unsupported?
• What exact event schedules a request, what process sends it, and where can staff see a failed or repeated attempt?
• Which identifier connects an order line, review and product variant, and who resolves an unmatched import?
• Which component owns Product markup, and can you show the visible review summary alongside the rendered test result?
• What export and display rights have been confirmed, who handles moderation and data requests, and how will collection continue through the switch?

Reply to negative reviews with a concrete next step

Read the complaint and check the facts before replying. Write for the reviewer and future customers. Acknowledge the concern, state the action you can take, move account details into a private channel and sign with a real name. Give each promised remedy an owner and due date. Link the review URL to an internal support ticket and check the existing conversation before asking the customer to repeat it. Keep the order connection and proof of completion private.

As background, BrightLocal's 2026 survey of 1,002 US adults reported that 80% were likely to use a business responding to every review, 42% were unlikely to use one that never replies, 89% expected a response and 81% expected one within a week. These are stated preferences about local businesses, not measured ecommerce conversion effects.

The following are example reply patterns, not customer histories. Adapt them to the actual facts and remedies you can actually provide.

Do not publish contact details, order references, purchase histories or private account actions. Correct material facts calmly and avoid accusations of dishonesty. For safety, injury, fraud, discrimination, security or legal allegations, preserve the report and escalate to the responsible specialist before making substantive claims.

Report a review only for a valid policy violation. A low score alone is not grounds for removal, and the platform decides whether to remove it. Trustpilot's 2025 Trust Report reports 4.5 million fake reviews removed in 2024. Assess each review on its own content and evidence before reporting it.

For Business Profile reviews, owners and managers of a verified profile can reply. Google checks replies before publication; approved replies appear publicly as the business and the reviewer is notified. Reporting is a separate action. Trustpilot business accounts have their own reply, private-information request and flagging tools. Enable notifications and assign a responsible person on each platform.

Handle a surge of complaints as an operational incident

1. Contain the underlying failure. Pause inaccurate delivery promises and identify affected orders.
2. Assign an incident owner. Publish one accurate status update and contact affected customers with realistic options and update times.
3. Triage reviews individually. Reply to legitimate complaints and report actual policy violations.
4. Use a consistent incident explanation, adapted to each review. Do not claim the backlog is cleared until you have confirmed it.
5. Keep invitation rules neutral. Define the cohort and triggers independently of expected rating, including appropriate handling of cancelled, refunded and delayed experiences.
6. Close promised refunds, replacements and investigations. Do not ask for a review change in return.
7. Record the root cause, failed control, corrective action, owner and results of the follow-up check.

Google's published rating and Trustpilot's age-sensitive TrustScore are different measures. Do not combine them or claim that replies alone caused a recovery. Genuine new feedback can reflect improved service, but there is no guaranteed score or recovery time.

Worked example: a fulfilment partner stops dispatching

If a partner disruption stalls orders, separate the operational backlog from the review inbox. A replied-to review stays linked to an open customer case until the promised refund, replacement or delivery action is complete. Conversely, an affected order needs an update even if its buyer has posted no review. Reconcile both lists against the incident owner's order list so vocal customers are not the only ones receiving help.

Use the pattern in complaints to check the repair: if customers still report missing tracking after dispatch resumes, test the tracking hand-off and notifications before declaring recovery. Give the review inbox a backup owner during staff absence. Close the incident against completed remedies and checked controls, rather than against a target star rating.

Questions owners ask

Can we keep on-site reviews and a public Trustpilot profile?

Yes, if you assign each a clear purpose. Keep product and service totals labelled separately, and agree invitation coverage so customers do not receive accidental overlapping requests.

We already pay for a review platform. Should we replace it?

Ask what requirement it meets and what would survive cancellation: public profile, display rights, permitted exports and pending invitations. Compare that evidence with the system decision table before changing a working setup.

Why did our average change after an import?

Compare the source and destination by product, published status, rating scale and duplicate handling. Check whether variants were regrouped or service reviews were mixed in. Resolve the difference before publishing the replacement summary.

Does an empty review inbox mean customers received no requests?

No. Trace the journey from the eligible order to the received message and review-form submission. A provider dashboard or queued reminder proves only that stage; it does not prove delivery or a usable form.

Will changing modules remove old criticism?

A module change does not resolve a complaint or justify suppressing it. Preserve permitted history, finish the remedy and keep the response process assigned during the change.

When should we expect stars in Google?

Do not set a promised launch date for stars. Ask for evidence that the intended surface's requirements have been met, then track actual display separately from configuration and collection; the eligibility checks explain the distinction.