How to Track Repeat Orders in Your CRM

Short answer

You track repeat orders in your CRM by storing an expected next order date for every recurring customer. That date comes from the customer's own order history. When the date passes without an order, your CRM or ERP creates a task for the sales rep, so you catch the drop the week it starts, not months later.

What is repeat order tracking?

Repeat order tracking means knowing when a regular customer's next order should arrive and acting when it doesn't. In B2B sales, most revenue comes from existing customers ordering again, not from new logos.

In most companies this knowledge lives in the rep's head. The rep knows "Mr. Ahmet calls at the start of every month." When the rep goes on leave, gets busy or leaves the company, that knowledge goes too.

Why do repeat orders disappear unnoticed?

Because the CRM is set up to follow new deals, not orders that never came. If there is no open deal, there is no alert. Order records sit in the ERP, while reps look at the CRM.

So a customer skips a month and nobody notices. The next month passes too. In month three the sales manager sees the dip in a report, and the "why did they stop buying" meetings begin. By then the customer is already buying from a competitor.

How do you calculate the expected order date?

The expected order date is the last order date plus the customer's average order interval. Six to twelve months of order dates is enough.

Example: a customer ordered on January 5, February 3, March 6, April 4 and May 7. The gaps are roughly 29 to 32 days, averaging 30. With the last order on May 7, the next one is expected around June 6.

Don't treat the interval as fixed. For seasonal customers, last year's order in the same month is a better guide.

How late is too late?

A delay becomes a warning once it passes roughly half of the customer's normal interval. For a monthly buyer that is about 15 days; for a weekly buyer, 3 to 4 days.

Set the threshold by customer type rather than one number for everyone. Test it against your own data: look at customers you lost and check how many days after their last order they went quiet.

Which fields should your CRM hold?

Four fields on the customer record are enough:

• Last order date: synced from the ERP, never typed by hand.
• Average order interval (days): calculated from recent orders.
• Expected next order date: last order date plus average interval.
• Average order value: shows what a delay is worth.

Once these are filled, your CRM or ERP can open a task for every customer past the expected date. The task should not just say "call the customer". It should say "the June order hasn't arrived; last time they bought these items."

How do you set up the process step by step?

The process takes five steps:

1. Separate your recurring buyers. Customers with at least 4 orders in the last 12 months are a good starting filter.
2. Calculate each customer's average order interval.
3. Store the expected order date as its own CRM field.
4. Create automatic tasks and a weekly list for customers past the threshold.
5. Log the outcome of every call: stock on hand, budget frozen, switched to a competitor, product issue. These reasons tell you whom to prioritize next month.

How do you calculate the cost of a delay?

The cost of delays is the sum of the average order values of all late customers. That figure tells your sales team where to look this week.

Example: you have 120 recurring customers. This month, 14 of them are past the threshold. If their average order is 40,000 TL, 560,000 TL is at risk. Win back half of them and the month closes 280,000 TL better. This is an illustrative calculation; plug in your own numbers.

What do you have, what are you losing, what do you gain?

You already have the order history. Your ERP records every order with a date, but that data is only used for invoicing.

What you are giving up, often without noticing, is customers who quietly buy less. While reps chase new deals, existing orders slip and nobody sees it. With this tracking in place, you see the loss in the first week of the delay, not in a report months later.

Related reading: Predicting customer churn from CRM data and How to calculate customer lifetime value from CRM data.

Closync AI is a decision partner that connects to your CRM and ERP: it points out missing and inconsistent records, tells you which deals are at risk and turns your team's call notes into the right CRM fields.

FAQ

Do I need separate software to track repeat orders?

No. If your CRM or ERP stores the last order date, an expected date field and a simple reminder rule are enough.

How do I track customers who order irregularly?

Compare with the same period last year instead of an average interval. For project-based buyers, track new deals rather than repeat orders.

Should I also track falling order values?

Yes. A customer who orders on time but spends less each time may be moving part of their purchases to another supplier.

Whose job is this?

The account's sales rep. The sales manager checks the weekly list to see whether late customers were actually called.

How much history do I need?

At least 4 to 5 orders to calculate a reliable interval. With fewer orders, the estimate won't hold.

Last updated: November 7, 2026