Notice repeat customers who have gone quiet

Define the repeat pattern before calling it late

A buyer ordering consumables every month has a different rhythm from a contractor buying for occasional projects. Record what the business actually supplies and why the customer buys. A single average across both groups will flag the wrong people.

Use a reasonable history window and comparable periods. If the customer ordered twice, you have little basis for a precise reorder prediction. Keep a confidence note such as regular monthly pattern or project-driven and irregular.

Shopify’s customer reports show how cohorts and repeat purchases can be examined. The general idea is useful outside ecommerce, but the business must define its own order data and intervals.

An illustrative reorder review

A workshop-supply customer usually buys a particular consumable every four to six weeks. Eight weeks pass without an order. The account owner checks the latest interaction and sees that the customer mentioned a planned production shutdown.

The appropriate action may be to confirm the restart date, not offer a discount.

Another customer has no known explanation and had an unresolved delivery complaint. That calls for a service conversation before a sales message. The same missing-order signal has a different meaning because the context differs.

Keep customer cohorts separate from website cohorts

A website visitor returning next month is different from a customer placing another paid order. Google Analytics explains cohort analysis in an app or website setting. Do not substitute visitor retention for customer purchasing retention.

For order review, group customers by first purchase period and comparable buying situation. Measure how many place another order within a defined interval and how much contribution those orders produce. State the interval so a six-month repeat rate is not compared with a one-month rate.

Exclude cancelled or duplicate orders consistently. If the same customer has two names in different systems, resolve that identity issue before interpreting the pattern.

Run a small account-review routine

Start with a manageable list rather than messaging everyone who has not bought recently. The account owner should be able to explain why each person is on the list.

1. Identify customers with enough history to show a buying pattern.
2. Separate recurring consumables from project and seasonal orders.
3. Check recent complaints, closures and known changes.
4. Make a relevant, permission-appropriate contact where useful.
5. Record the explanation, next action and any actual order outcome.
6. Review contribution and relationship feedback, not only messages sent.

Avoid turning a signal into a false promise

Use the pattern to prioritize a conversation with the customer. Evaluate follow-up using a defined period, actual orders and a sensible comparison. Record what happened before deciding why it happened.

Prepare a short list using the customer's normal buying pattern, open service issues and last meaningful contact. Let the account owner check the context before reaching out. Record what the customer actually says rather than inferring a reason from silence.

If the follow-up leads to an order, distinguish that observed result from an assumption that the reminder caused it.

If follow-ups repeatedly find normal seasonality, improve the review rule. A useful process becomes more selective as the team learns, rather than generating a growing list of false alarms.