Four numbers, for one product. Run it again for others.
Retain
Days your customer spends without the product
17 days
One purchase lasts 47 days. Allowing 4 days to arrive, the reminder wants to land on day 40.
Show me where the revenue isWhat those days actually cost
You send on day 60. With 4 days of shipping, the replacement arrives on day 64, and the supply ran out on day 47.
That is 17 days where your customer has none of your product and every reason to try somebody else’s. Reorder reminders do not fail because the message is wrong. They fail because they are late.
- One purchase lasts
- 47 days
- Measured from your own numbers, not rounded to thirty or sixty.
- Possible orders a year
- 7.8 times
- If every reorder happened on time.
Everything here runs in your browser. Your numbers are never sent anywhere, not to me and not to anyone else.
How this is calculated, and what to put in
Why thirty, sixty and ninety are the problem
Almost every reorder reminder goes out on one of those days. They are round numbers, not measured ones. No product runs out on a round number.
Say a product lasts forty seven days and the reminder goes at sixty. The customer ran out two weeks earlier. They spent those two weeks without your product and able to buy someone else’s.
How this is calculated
Units in a purchase divided by units used in a week gives weeks of supply. Times seven gives days.
The reminder has to land early enough for a replacement to arrive first. So delivery time comes off, plus three days. Nobody orders the moment they are asked.
What to put in
- Units used in a week
- What a typical customer actually gets through, not what the label recommends. Those two differ, and the label is optimistic.
- Day you send the reminder now
- Leave it at zero if nothing goes out. That is a common answer. The tool treats it as its own case rather than an error.
What to do with the answer
Move the date. This is the cheapest fix on this site. It changes a delay rather than rewriting anything.
Then run it again for your other products. One reminder schedule across products of different lengths is the same mistake again.