Automating lead-time and order-status emails

The emails that never stop

Two questions land on manufacturers' and distributors' order desks again and again. "Where's my order?" and "What's your lead time on this?"

Each one looks small. A buyer sends a PO number. Your person opens the ERP, finds the order, checks the lines, looks up the shipment, copies the tracking number, and writes back. Maybe five minutes. Maybe fifteen if the order is split across two warehouses or one line is on backorder.

Then the next one comes in. And the next. If the reply is slow, the same question can come back as a phone call.

The frustrating part is that the answer already exists. Your ERP knows the ship date. Your shipping system knows the tracking number. Your schedule knows when the job is due off the floor. The work isn't figuring out the answer. It's the lookup and the typing.

What the research says

There isn't a good public study that counts how many order-desk emails are status questions. Vendor blogs throw around numbers, but we couldn't trace them to real research, so we left them out. What we can show is how much buyers care about delivery information, and how cost studies count the time.

APQC, a nonprofit benchmarking group, says in a 2016 report that labor is the most significant cost driver in sales order processing. When it lists the labor to count, it includes the time to "communicate with the customer about the status of the order." That report was sponsored by Esker, which sells order automation software, and it's ten years old. But the point holds: status questions are part of what an order costs you, even if nobody tracks them.

A 2024 survey by Sana Commerce, an e-commerce software company, asked 1,000 professional buyers at manufacturers, retailers, wholesalers and distributors in six countries, including the U.S., what they want from suppliers, as reported by Digital Commerce 360. Delivery and status information showed up again and again:

What B2B buyers say they want, or are missing

Sana Commerce survey of 1,000 B2B buyers, 2024, as reported by Digital Commerce 360. Vendor survey.

1. Want accurate stock, pricing and delivery dates40%
2. Want access to order status, history and open invoices37%
3. Held back by a lack of accurate delivery time information31%
4. Held back by a lack of accurate stock information28%

Source: Digital Commerce 360, March 11, 2024, reporting Sana Commerce's B2B buyer survey.

The survey was about online ordering, and it was run by a company that sells web stores, so read it with that in mind. Still, the pattern is plain. Accurate delivery dates are one of the top things buyers say they don't get. In the same survey, 74% of buyers said they would switch suppliers if another supplier's web store gave a better experience.

Buyers also want fewer conversations, not more. Gartner found that 67% of B2B buyers favor a rep-free experience in a survey of 646 buyers, as reported by Digital Commerce 360 in March 2026. A buyer who has to email your rep to learn a ship date is not getting that.

Two questions, two kinds of answer

"Where's my order?" and "What's your lead time?" sound alike, but they're different jobs.

A status question asks about something that already happened or is already planned. A lead-time question often asks you to make a new promise. That difference decides how much you can hand to software.

Where the answer already lives

Most mid-size ERPs already hold what you need. Take Microsoft Dynamics 365 Business Central as an example.

Its order promising feature calculates shipment and delivery dates from an item's known and expected availability. It works two ways. "Available to promise" checks unreserved stock plus planned production, purchases and transfers. "Capable to promise" runs a "what if" for quantities you don't have yet, and figures the earliest date you could make or buy them. Microsoft's example: on an order for 10 pieces with 6 available, the capable-to-promise math covers the other 4.

For orders that already shipped, Business Central lets you store a carrier's tracking number on the posted shipment and open the carrier's tracking page straight from the posted shipment or invoice.

Other ERPs used by mid-size companies have their own fields for promise dates, ship dates and tracking numbers; check what yours holds and how current it is. The data is usually there. What's missing is the link between the customer's email and that data, which is exactly the lookup your person does by hand.

What software can do

Here's what an automated status reply looks like when it's done well:

1. Read the email. Find what the customer is asking about: a PO number, an order number, a part number, or just "our order from last week."
2. Match it to the account. Check the sender's email against the customer's contacts, so you don't send order details to a stranger.
3. Find the order and pull the facts. Lines, quantities, what's shipped, what's open, promise dates, tracking numbers.
4. Check whether anything is off. Is a line past its promise date? Is one item on backorder? Is the job behind on the floor?
5. Draft the reply in plain language, with the facts, in your company's voice.
6. Route it. Clean answers go to a person for a one-click send, or straight out if you've chosen that for simple cases. Anything late, unclear or new goes to the right person with the facts already pulled.

Once the replies are working, the next step is to stop waiting for the question. If the system knows a line slipped, it can draft the "heads up, line 3 moves to the 20th" email before the buyer asks. That's the same reading and drafting, run on your schedule instead of theirs.

This sits right next to confirming new orders, which we cover in automating order confirmations and acknowledgments, and handling changes, in automating revised POs and change orders. A status reply is often just the latest chapter of the same order.

The answer is already in your ERP. The work is the lookup and the typing.

What stays with a person

Telling a customer a fact is easy to automate. Making a promise is not. Keep these with a person:

• Late orders. If a promise date has passed or is about to, a person should send that email. The customer will have questions, and the tone matters.
• New promise dates on made-to-order work. "Capable to promise" math is a start, but your scheduler knows about the machine that's down and the big order coming Monday.
• Expedite requests. "Can you ship by Friday?" may mean overtime, freight cost or bumping someone else. That's a business decision.
• Unhappy customers. If the email is a complaint wearing a status question, it goes to the account owner.
• Anything about price or terms. A status reply shouldn't quietly change either.

Where the other side has a point

Some fair objections:

• A customer portal can do some of this. If your customers will log in and look, a portal that shows order status and tracking may cut the emails without any AI. Some buyers will still email, so the two can work together. We compare the options in order processing portals.
• Bad dates make it worse. If your ERP's promise dates are wrong, automating them just sends wrong dates faster. Fix the dates first, at least for the products you start with.
• The research is thin and vendor-paid. APQC's report was sponsored by Esker; Sana sells web stores. Use the numbers for the pattern, not as a promise of savings. Your own inbox is the best data you have.
• Some customers want a person. Your biggest accounts may value a call from their rep. Automate the lookup so the rep has the answer in hand, and let them send it.

How to start

You can find out in two weeks whether this is worth doing:

1. Tag the emails. For two weeks, have your order desk tag every status and lead-time email in Outlook or Gmail.
2. Time a few. Note how long ten of them take from open to send.
3. Sort them. How many were simple facts (shipped, tracking, firm date)? How many needed a judgment call?
4. Check your dates. Pick 20 open orders and see if the promise dates in the ERP are still right.
5. Start with the simple ones. Automate the lookup and draft for "did it ship" and "when will it ship," with a person approving every reply at first. Measure time per email before and after. Our guide to measuring office automation ROI shows how.

If status emails turn out to be a big part of the week, they're rarely the only problem. We list the other signs in signs your order desk needs automation.