Post purchase email

Use post-purchase emails to invite customers to leave a review after they receive their order.

Typical flow

1. Customer places an order.
2. The app schedules a review request email based on your delay settings.
3. Customer opens the review link in the email.
4. Customer submits the review on your hosted Post Purchase Form.
5. Review is stored with request context and can be treated as verified-style feedback.

Why use it

• Higher review collection rate than relying on product-page forms only
• Better timing control (for example days after purchase)
• Stronger trust signals through request-based context

What to configure

• Enable review collection by email in app settings
• Set the send delay in days after the order was placed (1–30 days)
• Customize subject and body templates using the placeholders below
• Optionally enable discount rewards (see section below)

Email template placeholders

Use these in the email subject, text, and HTML fields:

• {first_name} - customer’s first name
• {last_name} - customer’s last name
• {full_name} - customer’s full name
• {review_link} - the unique link to the Post Purchase Form page - must be present for the email to work

Discount rewards

You can automatically send a discount code to customers after they submit a post-purchase review.

Enable Issue a discount code after post-purchase review submission in app settings, then configure:

• Discount type - percentage off or fixed amount off the full order
• Discount amount - the value (e.g. 10 for 10% or $10)
• Combinable discount classes - which other discounts this code can stack with: product discounts, order discounts, shipping discounts

The reward email uses its own separate subject/text/HTML templates with these placeholders:

• {first_name}, {last_name}, {full_name} - same as above
• {discount_code} - the generated discount code - must be present for the reward to be delivered

Best practices

• Send after delivery window, not immediately after purchase.
• Keep the email short with one clear call to action.
• Test the full flow with a real order before launching broadly.
• Pair with storefront app blocks so new reviews are visible quickly.

Quick links

Troubleshooting

• If emails are not sent, verify email collection is enabled and delay settings are valid.
• If customers land on invalid request pages, confirm the {review_link} placeholder is in the template.
• If reviews are unverified, test with a fresh order and link generated from a new request.
• If discount codes are not delivered, confirm {discount_code} is present in the reward email template.