Quick answer: The Trustpilot Shopify integration should trigger company review invitations after fulfillment or delivery, not at purchase. Product review invitations should be delayed until the customer has used the item. Bad timing is the most common reason Shopify stores collect fewer reviews and more negative feedback than expected.
What the Shopify integration does
The Trustpilot Shopify integration connects order data to Trustpilot so review invitations can be sent automatically. Instead of manually uploading customer emails, Shopify order events trigger company review requests, product review requests, or both depending on plan and configuration.
The integration can also help place TrustBox widgets on storefront pages and connect product review data to SKUs. Used correctly, it turns review collection into a background workflow. Used carelessly, it asks customers for reviews before the order arrives and turns preventable operations issues into public complaints.
Start with the trigger event
Do not trigger a review invitation when the order is created. Purchase-time invitations are too early because the customer has not experienced shipping, packaging, product quality, or support. For Shopify stores, the trigger should usually be fulfillment, delivery confirmation, or a post-fulfillment delay.
If delivery tracking is reliable, trigger after delivery. If delivery data is messy, trigger from fulfillment with a delay that matches your average shipping window. Domestic stores often use 5-7 days after fulfillment. International stores may need 12-21 days.
The best review invitation is sent after the customer can honestly judge the experience.
Company reviews vs product reviews
Company review invitations ask about the overall shopping experience. Product review invitations ask about a specific SKU. For most Shopify stores, company reviews should come first because they feed the Trustpilot company profile, TrustScore, widgets, and Google Seller Ratings eligibility.
Product reviews are valuable once the company profile is already healthy and the store has enough product-page traffic to use the proof. Do not ask for a product review the day a package arrives if the item needs weeks of use, assembly, washing, skincare results, or testing.
Recommended timing by store type
Apparel and accessories: company review 3-5 days after delivery, product review 7-10 days after delivery. Beauty, skincare, supplements, and wellness: company review 5-7 days after delivery, product review 21-35 days later. Furniture, home improvement, and electronics: company review 7-14 days after delivery, product review after setup or meaningful use.
Digital products and subscriptions are different. Trigger after activation, onboarding completion, or the first successful usage milestone rather than after payment. A subscription customer who paid but never activated cannot give a useful review yet.
Product mapping matters
If product reviews are enabled, Shopify product IDs, variants, handles, and canonical URLs need to map cleanly to Trustpilot product records. Variant chaos is the most common product review problem: reviews for the same item fragment across colors, sizes, bundles, or retired URLs.
Before turning product review invitations on, audit your top revenue SKUs. Decide whether variants should share reviews or keep separate reviews. A black medium shirt and a white medium shirt may share one product family; a replacement part and the main device should not.
Widget placement on Shopify
Use lightweight TrustBox widgets near high-friction decisions: below the add-to-cart area, near checkout reassurance, and on the homepage hero only if your review count is strong. Do not load multiple heavy carousels across every page. Widget bloat can hurt performance and conversion more than it helps trust.
Reserve fixed space for widgets so they do not shift the page after loading. Below-fold widgets should lazy-load. The review proof should support the purchase decision without making the storefront feel slower.
Invitation copy that works
Keep the email plain and specific. Mention the product or order context, ask one clear question, and avoid language that implies only positive reviews are welcome. Incentives, discounts, or loyalty points tied to leaving a review can create compliance problems and should be avoided unless carefully structured around neutral participation rules.
The highest-performing subject lines usually include the customer first name and a simple experience question. Overdesigned emails often underperform because they feel like marketing instead of a genuine review request.
Segments to exclude
Do not invite orders that were canceled, fully refunded, marked fraudulent, test orders, wholesale/internal orders, employee purchases, or orders currently in an unresolved support escalation. These exclusions are not cherry-picking happy customers; they prevent invalid or premature review requests.
Be careful with partial refunds and replacement orders. A customer who had a problem can still be invited, but timing should wait until the issue is resolved. Inviting during the dispute increases negative review risk and produces less accurate feedback.
Common setup mistakes
The first mistake is sending invitations from order creation. The second is enabling product reviews before product mapping is clean. The third is placing TrustBox widgets everywhere instead of where they influence decisions. The fourth is collecting too few company reviews to support Seller Ratings while spending time on low-traffic product SKUs.
The fifth mistake is turning off invitations after a wave of negative reviews. That creates selective collection risk and makes the profile look less credible. Fix the operational cause, respond to the reviews, and keep the invitation program consistent.
Metrics to watch
Track invitation send volume, open rate, conversion rate, review rating, review lag, and review count by country. For product reviews, track review density on top SKUs, not total product review count across the catalog. A thousand reviews scattered across 800 products may be less useful than 200 reviews concentrated on the 20 SKUs that drive revenue.
For Shopify brands running paid traffic, compare conversion rate on product pages with product review widgets against similar pages without review density. The goal is not to collect reviews for the dashboard; the goal is to reduce buyer hesitation where it matters.
What to do this week
Open your Shopify fulfillment and delivery timing data. Set the company review invitation to fire only after the customer realistically received the order. Exclude canceled, refunded, fraudulent, internal, and unresolved support orders. If product reviews are enabled, audit your top 20 SKUs for clean IDs, variant rules, and canonical URLs before asking for another review.
Frequently asked
Q.When should Shopify send Trustpilot review invitations?
Usually after fulfillment plus a realistic shipping delay, or after delivery confirmation if delivery data is reliable. Do not send at order creation because the customer has not experienced the product or fulfillment yet.
Q.Does the Trustpilot Shopify app collect product reviews?
It can, depending on your Trustpilot plan and setup. Product reviews require clean product mapping between Shopify product or variant data and Trustpilot product records.
Q.Should I ask for company and product reviews in the same email?
Usually no. Ask for the company review first, then send a separate product review request later when the customer has used the item. Two requests in one email often lowers completion.
Q.Can I exclude refunded Shopify orders from Trustpilot invitations?
Yes, canceled, fully refunded, fraudulent, test, internal, and unresolved support orders should be excluded to prevent invalid or premature invitations. Do not use exclusions to avoid unhappy but valid customers.
Q.Where should Trustpilot widgets go on a Shopify store?
Place lightweight widgets near purchase decisions: product pages, checkout reassurance areas, and homepage proof if review count is strong. Avoid loading heavy widgets on every page.
Q.Why are my Shopify product reviews split across variants?
Variant fragmentation usually comes from inconsistent product IDs, handles, canonical URLs, or feed rules. Decide which variants should share reviews before enabling product review requests at scale.
