Feature · Replenishment

Due to reorder, by their own clock

Replenishment is customer replenishment analytics that finds which customers are due to reorder a specific product right now — by that customer's own cadence for that exact product, not a shop-wide interval that flattens everyone to the same number. There's no date range to set: it's evaluated against current purchase history, not a reporting window, because changing the window wouldn't change who's due.

app.amicited.com/reports/replenishment
Due to reorder table ranking customer-product pairs by expected value and days overdue
How due-to-reorder is calculated
Cadence basisnot shop-wide per-customer, per-product
Minimum historyof the same product 2+ orders
Rankingnot just days overdue expected value (EUR)
Evidence — the purchase count the interval was measured over — is shown beside every row.
One row, one customer, one product

Late is relative to the customer, not the shop

The interval that says somebody is due is the mean of their own gaps for that product — so the purchases it was measured over are stated right beside it. A customer needs at least two orders of the same product before there's a cadence to be late against, and a row only turns 'due' once time since the last purchase reaches that mean — it's flagged 'overdue' only past 1.5 times it.

  • Due to reorder — a reorder reminder worklist, one row per customer and product, ranked by what contacting them could be worth, amounts in EUR.
  • Per-customer, per-product cadence — the interval is the mean of that customer's own gaps for that exact product, never a shop-wide average.
  • Due, then overdue — a row turns due once elapsed time reaches the customer's own mean interval, and overdue only past 1.5 times it, flagged in red so a mildly late pair isn't confused with a genuinely stale one.
  • Evidence shown, not hidden — the number of purchases the interval was measured over sits right beside it.
  • Minimum two orders — a customer needs at least two orders of the same product before there's a cadence to be late against at all.
  • Ranked by value — sorted by what reaching that customer about that product could be worth, not just by how overdue they are.
  • No date picker — due-to-reorder is judged against current history, not a window, so there's nothing to set.
Ranked by what it's worth

Not just a reorder reminder — who's worth reaching

Due to Reorder doesn't just flag lateness, it ranks rows by what contacting that customer about that product could be worth, in EUR — so a slightly overdue high-value pair can outrank a badly overdue low-value one.

Row ranking
customer × product
Unit
expected value (EUR)
Sort
customer's own mean gap
Interval source
purchase count shown
Evidence
A pair with fewer purchases behind its interval is a weaker signal than one with many — and the count says which is which.
What the list won't do
Duenormal color elapsed ≥ their own mean interval
Overdueflagged in red elapsed ≥ 1.5× their own mean interval
Over the capnever shown as complete count of omitted pairs is stated
No email exportpseudonymous customer keys only not on this page
No row filter, sort, or CSV export lives on this page — it's a worklist to click into, not a campaign builder.
Built to be worked, not skimmed

A capped list says so, instead of pretending to be complete

When more eligible pairs exist than the list shows, the page states how many lower-value pairs were left off rather than letting a capped table pass as the whole workload. An empty list means nobody currently has enough same-product history and elapsed time to qualify — not that the shop has no repeat customers.

From history to cadence
Same-item purchase frequency how many times a pair repurchased
Time between orders gap length, bucketed
Due to reorder mean gap, per customer per product
One report measures the rhythm; the other acts on it.
Where the cadence comes from

The same history Repeat Purchase already tracks

Replenishment's per-product cadence draws on the same order history that Repeat Purchase breaks down by gap length and order sequence — so a customer's own rhythm, once established there, is exactly what decides when they're due here.

2+ orders of the same product before a cadence exists One order gives no gap to measure — Replenishment only surfaces a customer once there's at least one real interval of their own to compare against. See Repeat Purchase

Know who's due to reorder, before they forget

One row per customer and product, ranked by expected value, using each customer's own reorder cadence for that exact product.

app.amicited.com/reports/replenishment
Due to reorder table ranking customer-product pairs by expected value and days overdue

Ready to know who's due to reorder?

Free check · 7-day trial · no credit card