Skip to content

How to Automate Ecommerce Review Requests: Timing, Triggers, and Order Exclusions

A review request sent before an order arrives feels premature. One sent weeks after the customer has used the product may be easy to ignore. And one sent while they are trying to resolve a damaged delivery can make a bad experience worse.

To automate ecommerce review requests well, you need more than a scheduled email. You need a workflow that starts from the right order event, waits long enough for the customer to form an opinion, and skips orders where a request would be inappropriate. Here is how to set up that workflow without adding another task to your team’s daily list.

Start with the experience you want customers to review

Before choosing a delay, decide what you are asking about. A customer can review a product only after they have received and had a reasonable chance to use it. They may be able to review the buying or delivery experience sooner.

That distinction matters if you sell products with different usage patterns. Someone can assess a phone case shortly after fitting it, but may need several weeks to form a useful opinion about skincare or a piece of fitness equipment. If your store collects both product and store reviews, consider separate requests rather than sending two links in one crowded message.

A simple starting rule is: trigger the request from delivery when possible, then add a product-appropriate waiting period. Treat the first timing you choose as a test, not a universal best practice.

Choose a reliable trigger for your review request automation

An automation trigger is the event that starts the countdown to your request. The strongest available trigger depends on the order data your store receives.

TriggerWhen it works wellWhat to watch for
DeliveredYou receive dependable delivery updates from your shipping providers.Delivery scans can be late or missing, so you may need an exception process.
Fulfilled or shippedDelivery data is unavailable, but dispatch status is reliable.Add estimated transit time before the product-use delay.
Order placedThe product is digital or available to use immediately.For physical goods, shipping delays can cause premature requests.
Pickup completedYou offer local pickup and record when the customer collects the order.An order marked “ready for pickup” is not necessarily in the customer’s hands.

For physical products, avoid starting the timer when payment is captured unless you have no better event. An order can be paid but unfulfilled, delayed, or split into several shipments. If you must use an earlier trigger, build in enough buffer and suppress the request when the order is still unfulfilled.

Handle split shipments and mixed-product orders

Multi-item orders make timing harder. If one item arrives today and another arrives next week, an order-level email sent today could ask the customer to review a product they have not received.

Where your systems support it, use item-level delivery events and send a request only for delivered items. Otherwise, wait until the full order is delivered. For mixed carts—such as an everyday consumable and a product that takes weeks to evaluate—consider asking about the store experience first and requesting product feedback later, if your setup can prevent excessive messaging.

Set the delay based on delivery and product use

There is no single best time to send a review request. The useful question is: when will this customer have enough experience to say something meaningful?

Use these ranges as starting points for testing, not fixed rules:

  • Immediately usable products: Try a few days after confirmed delivery for items such as accessories or home décor.
  • Products used repeatedly: Consider a week or more after delivery for items such as kitchen tools or apparel, depending on typical use.
  • Products with a longer evaluation period: Allow several weeks where customers need time to assess the product.
  • Digital products: Start from access or activation when that event is available, rather than the payment date.

If you trigger from shipment rather than delivery, your total delay must account for both transit and product use. For example, a store that typically sees several days between dispatch and arrival should not apply a “three days after delivery” rule as “three days after dispatch.”

Send at a reasonable local time when your system supports time-zone scheduling. If you add a reminder, send it only to customers who have not already reviewed, and keep the sequence short. More messages are not automatically more useful.

Build order exclusions before you switch on the automation

Exclusions are rules that stop or pause a review request when the customer’s experience is unresolved or the message would be irrelevant. Set these up before activating your sequence—not after the first awkward email goes out.

Exclude orders that cannot produce a useful review

  • Cancelled or fully refunded orders: The customer may never have received the product.
  • Unfulfilled, undelivered, or lost shipments: Do not ask for a product review while receipt is uncertain.
  • Fraudulent, test, and internal orders: These should not enter a customer review workflow.
  • Orders already reviewed: Avoid asking for the same product review twice.

Pause requests while a problem is being resolved

Consider temporarily suppressing orders with an open return, replacement, chargeback, or support case. The goal is not to hide negative feedback. It is to avoid asking for a product assessment in the middle of an unresolved process.

Once the issue is closed, decide whether a later, neutral request still makes sense. Do not permanently exclude customers merely because they contacted support, received a refund, or might leave a critical review. Selectively asking only likely-happy customers can distort your reviews and may conflict with the rules of the review platform you use.

Account for product and customer exceptions

Preorders, made-to-order products, subscriptions, gifts, and exchanges may need their own timing rules. A preorder should follow fulfillment rather than the original order date. A subscription request may be more useful after the customer has received and used the first delivery. For gifts, the buyer may be able to rate the purchase experience but not the product itself.

Also check your contact preferences and applicable messaging rules before sending. Whether a review request is treated as a service message or marketing can depend on its content and the jurisdiction. If you add a discount, cross-sell, or promotional language, review the requirements that apply to your store and customers. Follow unsubscribe and suppression settings where required.

Put the workflow together step by step

  1. Choose the review destination. Decide whether you want product reviews, store reviews, or both. Check the destination’s policies before designing incentives or message wording.
  2. Map your order events. Identify which delivery, shipment, pickup, or access events your store and review tool can reliably use.
  3. Create timing rules. Group products by how long customers typically need to use them. Start with a small number of groups you can maintain.
  4. Add exclusions and pauses. Cover cancellations, non-delivery, open issues, existing reviews, and your store’s unusual order types.
  5. Write a short, neutral request. Name the item where appropriate, ask for an honest review, and make the action clear. Do not imply that only positive feedback is welcome.
  6. Test realistic order scenarios. Check a normal delivery, a delayed shipment, a partial refund, a split shipment, a return, and an already-reviewed order before turning the workflow on.
  7. Monitor and adjust. Review what was sent, what was suppressed, customer complaints, and the quality of the feedback you receive.

Your first version does not need dozens of branches. A dependable delivery trigger, a sensible delay, and clear exclusions are more valuable than a complicated workflow your team cannot audit.

Write a request customers can act on

The message should explain why the customer is hearing from you and make the next step easy. A straightforward version could read: “You’ve had some time with your order. Would you share an honest review of your

  • Sale! Placeholder

    Webshop Toolbox

    Original price was: € 199,00.Current price is: € 99,00.
? Your feedback helps other shoppers understand what to expect.” Add a direct review link only when you have the real destination for that customer and item.

Avoid “Tell us if you loved it” or a flow that sends satisfied customers to a public review page while directing unhappy customers elsewhere. You can offer a separate route to customer support, but it should not replace a fair opportunity to leave an honest review.

If you offer an incentive, check the policies of the platform where the review will appear and any applicable disclosure requirements. The incentive should not depend on a positive rating.

Measure whether the automation is working

Look beyond the number of requests sent. Track how many eligible orders enter the workflow, how many are excluded, whether messages arrive after delivery, and how many customers submit a review. Read the reviews and support replies, too: they can reveal whether your timing is sensible or whether customers are being asked to evaluate products too early.

If requests are going out before delivery, fix the trigger or delay before changing the copy. If customers say they have not used the product yet, lengthen the product-use window. If very few orders qualify, inspect your exclusion rules for mistakes rather than removing protections indiscriminately.

Make every request timely and appropriate

Effective review request automation is a small set of well-chosen decisions: start from a reliable event, give customers time to use what they bought, and pause or exclude orders where a request does not yet make sense. Begin with one product group and a few test orders, then expand once you can see that the workflow behaves as intended.

Review your current post-purchase emails this week. If any request can reach a customer before delivery—or during an unresolved order issue—fix that rule first.

Frequently asked questions

How long after delivery should you ask for a product review?

It depends on how quickly the customer can evaluate the product. Start with a few days for immediately usable items and a longer period for products that require repeated use. Check customer responses and adjust by product group.

Should you send review requests for refunded orders?

Do not automatically treat every refund alike. A cancelled order that was never delivered should generally be excluded from product review requests. For a delivered product with a later refund, consider whether the issue is resolved and follow the policies of your review platform. Do not suppress reviews solely because they may be negative.

What if your store does not have delivery confirmation?

Use a reliable shipment or fulfillment event, add estimated transit time and a product-use delay, and check that the order has not been cancelled or marked as undelivered before sending. Revisit the timing if customers report receiving requests too early.

Should you send more than one review request?

A single well-timed request is a sensible starting point. If you add a reminder, send it only when no review has been submitted, leave a reasonable gap, and respect contact preferences and applicable messaging rules.

Leave a Reply

Your email address will not be published. Required fields are marked *

Secret Link