When Should You Actually Send a Review Request Email? (Hint: Not When You Think)

Most review plugins send requests based on when the order was placed, not when it shipped. That gap is quietly killing your review collection rate — here's why shipping-based timing gets dramatically better results.

Every review plugin on the market gives you the same setting: “Send review request X days after purchase.” You pick a number — seven days, ten days, fourteen days — and off it goes.

There’s just one problem with this approach. It’s based on when the order was placed, not when the product is actually on its way to the customer.

And that gap — between purchase and shipping — is where most review strategies quietly fall apart.

The “Days After Purchase” Problem

Let’s walk through what actually happens with a standard “send review request 7 days after purchase” setup.

Your customer orders on Monday. The email is scheduled for next Monday. Straightforward, right?

Except you didn’t ship until Wednesday because you were waiting on stock. Shipping took five business days because they chose standard delivery. The package arrived the following Wednesday — two days after the review request landed in their inbox.

So your carefully crafted “How did you like your purchase?” email arrived before the purchase itself did. Your customer either ignores it (most likely), gets mildly annoyed (probable), or — worst case — starts wondering if their order is even coming.

Now multiply this across every order with variable shipping times, delays, backorders, or international delivery. That tidy “7 days after purchase” rule starts looking less like a strategy and more like a guess.

It Gets Worse When Shipping Times Vary

If you sell domestically with a reliable two-day courier, the “days after purchase” model might work okay. The timing is predictable enough that you can pick a number that lines up roughly with delivery for most orders.

But most WooCommerce stores don’t live in that tidy world. You’ve got:

  • Standard vs express shipping options (different delivery windows)
  • Regional vs interstate vs international orders (wildly different timelines)
  • Products that ship from different warehouses or suppliers (variable dispatch times)
  • Pre-orders or made-to-order items (could be weeks before they ship)
  • Peak season delays (hello, December)

With all those variables, no single “X days after purchase” number works for every order. Set it too short and you’re emailing people before their parcel arrives. Set it too long and you’ve missed the window where they actually care about giving feedback.

Research from Northwestern University’s Spiegel Research Center found that up to 80% of reviews originate from follow-up emails — not from customers spontaneously leaving feedback. That means your email timing isn’t a minor detail. It’s the mechanism that drives the vast majority of your reviews. Getting it wrong doesn’t just reduce your collection rate — it undermines the whole strategy.

The Smarter Trigger: Shipping Status, Not Purchase Date

The fix isn’t complicated once you think about it: instead of counting days from when the order was placed, start counting from when the order was shipped.

Shipping-based timing means:

  • The countdown doesn’t start until the product is actually on its way
  • Orders that sit in processing for a few days don’t skew the timing
  • Variable dispatch times don’t matter because the trigger is the actual shipping event
  • Pre-orders and backorders don’t send embarrassingly premature emails
  • International and domestic orders can use the same delay setting, because the clock starts from the same logical point

It’s not rocket science. When you mark an order as shipped in WooCommerce — whether that’s manually or via your shipping provider — that status change becomes the trigger for your review request timer. Three days after shipped. Five days after shipped. Whatever makes sense for your product and your typical delivery windows.

The psychology here isn’t complicated either. You want to ask someone how they liked something after they’ve had a chance to experience it. Tying that ask to the point when the product left your hands — rather than the point when they clicked “buy” — gets you dramatically closer to the right moment.

It’s not perfect. You still don’t know the exact moment it lands on their doorstep. But you know it’s in transit, and you can make a reasonable estimate based on your typical shipping times. That’s a world better than counting from purchase date, which tells you nothing about where the product actually is.

The Sweet Spot: How Long After Shipping?

So if shipping status is the trigger, how long after shipping should you send the email?

There’s no universal magic number, but you can get close by thinking about two things: your typical delivery window and your product type.

Start with your delivery time. If most of your orders arrive within 3-5 days of shipping, setting your review request for 5-7 days after shipping means most customers will have had the product for a couple of days. That’s usually enough time to open it, try it, and form an impression.

Then adjust for your product type:

Immediately usable products (clothing, accessories, homewares, food): 5-7 days after shipping. They know pretty quickly if they like it.

Products that need time (skincare, supplements, tools, equipment): 10-14 days after shipping. They need to actually use it before they can review it meaningfully.

Gifts: This one’s tricky. The buyer might not even see the product. Consider keeping the standard window but adjusting the messaging — “We hope your gift arrived safely” rather than “How did you like it?”

Digital products or services: Shipping-based timing doesn’t apply the same way, but the principle does — trigger based on access or completion, not purchase date.

The Reminder Strategy (Without Being Annoying)

BrightLocal’s Consumer Review Survey found that 83% of people who were asked to leave a review went on to do so. That’s an extraordinary number — but it assumes the ask actually reaches them at the right moment.

A single well-timed email will get you a solid response rate. But people are busy, inboxes are chaos, and even willing reviewers forget. A reminder helps.

Here’s what works without crossing into “please stop emailing me” territory:

Email 1 (5-7 days after shipping): The initial ask. Friendly, personal, one clear call to action. Keep it short. Don’t make them click through three pages to leave a review — the fewer steps, the better.

Email 2 (5-7 days after Email 1): A gentle reminder. Acknowledge that they’re busy. Make it even easier than the first email if possible. This is your last shot — don’t waste it with a generic “Just checking in!”

And that’s it. Two emails. Maybe three if you’ve got a strong reason and the right tone, but two is the sweet spot for most stores. Beyond that, you’re trading potential reviews for guaranteed annoyance.

The key thing most stores miss: if someone doesn’t respond to two well-timed, well-written emails, a third one isn’t going to change their mind. What will change their mind is better timing, better messaging, or a better experience next time around.

What Happens When You Get the Timing Wrong

Getting review request timing wrong isn’t just a missed opportunity — it actively works against you.

Too early (before the product arrives):

  • Customer confusion (“I haven’t received it yet?”)
  • Signals that you don’t know where their order is — not a great look
  • May prompt a “where’s my order?” support ticket instead of a review
  • Customer mentally dismisses the review request; they won’t circle back when it arrives

Too late (weeks after they’ve had the product):

  • The product excitement has faded
  • They’ve moved on to other purchases and priorities
  • The experience details are fuzzy — you get vaguer, less useful reviews
  • Response rates drop significantly as time passes

Mismatched timing (varies randomly because dispatch times vary):

  • Some customers get a great experience, others don’t
  • Inconsistent data — hard to optimise what you can’t control
  • Your “review program” is actually a lottery

The frustrating thing is that most store owners never realise this is happening. They set up their review request timing once, notice they’re getting some reviews, and assume it’s working. They never see the reviews they’re not getting because the email arrived at the wrong moment.

Why Most Review Plugins Can’t Do This

Here’s why most WooCommerce review plugins use “days after purchase” instead of “days after shipped”: they don’t pay attention to order status changes.

Your review plugin and your fulfilment process are typically separate systems. The review plugin knows when an order was placed (WooCommerce tells it that). But does it actually watch for when you update the order status to “Shipped” or “Completed”?

Most don’t — or if they do, they don’t use it as the trigger for review request timing. They were designed as standalone review collection tools, not as part of an integrated order workflow. The review plugin doesn’t know (or care) what’s happening on the fulfilment side.

This is one of those problems where the technical solution isn’t complicated, but it requires the tools to be built as a connected system rather than separate plugins bolted together. When your order management and review collection share the same data layer and both understand your order statuses, shipping-based timing becomes a simple settings toggle. When they’re separate plugins from separate developers? You’re stuck with “X days after purchase” and a prayer.

What to Do Right Now (Even Without Shipping-Based Triggers)

If your current review plugin only supports “days after purchase” timing, here are practical ways to get closer to good timing:

Use your average total time-to-delivery as the baseline. Add up your typical processing time plus shipping time. If it’s usually 7-8 days from purchase to doorstep, set your review request to 10-11 days after purchase. It won’t be perfect, but it’s better than an arbitrary number.

Set different delays for different shipping methods. If your review plugin supports it, create separate timing rules for express (shorter delay) and standard (longer delay) shipping. Some plugins let you do this; many don’t.

Actually update your order statuses consistently. If you mark orders as “Completed” when they ship, some review plugins can trigger off that status change. It’s not quite shipping-based timing, but it’s closer than counting from purchase date. The catch: you have to actually do it for every order, which means building the habit.

Segment by location. If you ship domestically and internationally, set different timing for each. International orders need a longer delay — sometimes significantly longer.

Monitor your review request performance. Track your open rates, click rates, and actual review submission rates. If they’re declining or low, your timing might be off. A sudden drop often correlates with a change in shipping patterns you haven’t accounted for.

None of these are perfect substitutes for proper shipping-based timing, but they’ll get you meaningfully closer than the default “pick a number and hope” approach.

Why This Matters More Than You Think

Review timing feels like a minor operational detail — a setting you configure once and forget about. But the downstream effects are significant.

Better timing means higher response rates. Higher response rates mean more reviews, faster. More reviews mean better social proof, better SEO (structured review data is gold for search engines), better conversion rates, and better customer intelligence.

The Spiegel Research Center found that products with just five reviews are nearly four times more likely to be purchased than products with none. Every review you don’t collect because your timing was off is a tangible hit to your conversion rate.

And here’s the bit that connects to everything else: when your review collection is aware of your fulfilment workflow — when it knows an order has been shipped rather than just placed — you’re not just collecting more reviews. You’re running a smarter operation where the different parts of your store actually talk to each other.

That’s the difference between a review plugin and a review strategy. And it starts with getting the timing right.


The best review request email in the world doesn’t work if it arrives before the product does.

Quick Fire Questions!

For most physical products, five to seven days after the order ships is a solid starting point — that gives enough buffer for delivery plus a day or two to open and experience the product. Products that need extended use, like skincare or supplements, benefit from a longer window of ten to fourteen days after shipping. The key principle: ask after they’ve had a chance to experience it, but while the experience is still fresh. If your plugin only supports “days after purchase,” add your average processing time to these numbers.

Two emails total is the sweet spot for most stores — one initial request and one reminder about five to seven days later. You can push to three if your brand tone supports it and you’ve got something genuinely new to say in the third email (not just “hey, we noticed you haven’t reviewed yet”). Beyond that, you’re burning goodwill faster than you’re collecting reviews. If two well-timed emails don’t get a response, a third probably won’t either. Focus on improving timing and messaging instead.

This is exactly where “X days after purchase” timing breaks down. If your review plugin can trigger off a shipping status change, that solves the dispatch-time variability entirely — the countdown starts when the product actually leaves. If it can’t, set different timing rules for different shipping methods (express vs standard) and different destinations (domestic vs international). Use your longest common total delivery time as the baseline rather than the average — it’s better to email slightly late than before the parcel arrives.

Keep it short, personal, and focused on one action. Use their first name. Reference the specific product they bought. Make the review mechanism as frictionless as possible — ideally they can start the review directly from the email without logging in or navigating your site. Avoid long preambles, multiple calls to action, or anything that feels templated. The tone should match your brand, not sound like a corporate form letter. And never, ever include a sales pitch in your review request email. It’s not the time.

They can, if you’re doing it badly. Sending review requests before the product arrives (prompting confused replies or spam reports), sending too many reminders, or emailing customers who’ve unsubscribed are all ways to tank your sender reputation. Best practices: use a reputable email sending service, honour unsubscribes immediately, keep your list clean, and — most importantly — only email people when they’ve actually had a chance to use the product. Well-timed, relevant review requests get opened, not reported.

Generally yes, but with exceptions. You might want to skip: orders that were fully refunded or returned (asking for a review feels tone-deaf), orders from customers who’ve already reviewed that specific product, and orders where the customer has opted out of marketing communications (depending on your region’s privacy laws, review requests may count as marketing). Some stores also exclude very small orders or wholesale/trade orders. The goal is to ask everyone who had a genuine customer experience, and skip everyone who didn’t.

Still have questions?

We love a curious cookie. If you’ve got a burning question we haven’t covered here, get in touch—we’re real humans, we don’t bite, and we’d love to help you figure out if we’re the right fit.

Contact Us Now

Not quite ready to hit “go”?

No stress. If you’re still wrapping your head around what your website needs (or if you just want to not mess it up), grab our No-Regrets Website Guide.

It walks you through the five things you need to get clear on before you start a website project—so you can stop second-guessing and start making smart moves.
[gravityform id="13" title="false"]

Leave the first comment

More, you say?