Backorder emails: telling customers a line slipped before they ask
Your ERP already knows when a promise date moves. The gap is the email nobody had time to write. How to catch slipped lines every morning, draft the notice automatically, and have a person approve it before it goes out.

In brief
Most ERPs already link a customer's order line to the purchase or production order that will fill it, and they recalculate the ship date when supply moves. So the signal that a line slipped is already in your system. What's missing is the step that turns it into an email. Run a daily check that compares each open line's current ship date to the date you promised, draft a short notice for every line that moved, and have a person review and send it. Tell the customer what slipped, the new date or when you'll know, and what they can do (wait, split, substitute or cancel). If you sell to consumers by mail, phone or online, the FTC's mail order rule already requires a notice like this.
- Your ERP already recalculates ship dates when supply slips; the missing step is the email.
- Run a daily check: compare each open line to the original promise date, flag real slips, and skip lines you already told the customer about.
- A good notice says what slipped, the new date or when you'll know, what's still on time, and the customer's options.
- Keep a person approving sends at first; some dates are wrong and some customers need a call.
- For consumer orders, the FTC's mail order rule already requires a delay notice with a cancel option.
The worst way to find out
A customer calls on Thursday to ask where their order is. Your rep looks it up and finds that one line has been waiting on a vendor for a week. The purchase order slipped, the ERP moved the ship date, and nobody told the customer. Now the call is about trust, not dates.
It usually isn't because people don't care. It's because writing "line 3 is late" emails is nobody's job, and on a busy day it loses to everything else.
Buyers notice. In a 2024 survey by Sana Commerce, as reported by Digital Commerce 360, 31% of B2B buyers named a lack of accurate delivery time information as a reason they hold back from ordering online. And 87% said a bad buying experience would affect their relationship with the supplier at least to some extent. Sana sells B2B ecommerce software, so read it as a vendor survey, but the point matches what order desks hear on the phone.
What holds B2B buyers back from ordering online
Share of B2B buyers naming each reason, Sana Commerce survey, 2024.
Source: Sana Commerce survey, as reported by Digital Commerce 360, March 11, 2024. A vendor survey.
Your ERP already knows
The good news is that the hard part, knowing a line will be late, is usually done already. Take Microsoft Dynamics 365 Business Central as an example. Its order promising feature calculates shipment and delivery dates from what's in stock and what's on planned receipts. If a requested date can't be met, it calculates the earliest date the items will be available and puts that date on the line. Its order tracking shows how sales orders, production orders and purchase orders are linked.
Other ERPs have the same idea under different names: a promise date or requested ship date on the sales line, an expected receipt date on the purchase order, and some way to tie the two together. The names change. The logic doesn't.
So when a vendor pushes a receipt date, the sales line that depends on it is affected inside the ERP. The problem is that the ERP shows it on a screen. It doesn't write to the customer.
The ERP already knows the date moved. What's missing is the email.
The daily check
The fix is one check that runs every morning before the order desk starts. It looks at every open sales line and asks three questions:
- Did the date move? Compare the line's current ship date to the date you first promised. Store the original promise date once, at order entry, so you always have something to compare against. Many ERPs overwrite the date, so keep your own copy.
- By how much? A one-day slip on a line due in three weeks may not need an email. A three-day slip on a line due Friday does. Set a threshold, for example any move of two or more business days, or any line that will now miss the customer's requested date.
- Have we already told them? Keep a log of notices sent, per line and per date, so the same customer doesn't get the same email twice. If the date moves again, that's a new notice.
The output is a short list: these lines slipped since yesterday, by this much, for these customers. Your first week's count (below) tells you how long that list really is.
What the email should say
Keep it short. A customer reading a delay notice wants four things, in this order:
The four parts of a backorder notice
| Part | Example | Where it comes from |
|---|---|---|
| What slipped | "Line 3 on your PO 48192, 40 pcs of part 1180-B" | The sales line, with the customer's own PO number and part number if you store them |
| The new date, or when you'll know | "Now shipping Dec. 9" or "We'll have a firm date by Tuesday" | The recalculated ship date, or the date the buyer expects to hear from the vendor |
| What else is fine | "Lines 1, 2 and 4 ship on time Friday" | The other open lines on the same order |
| Their options | "We can ship what's ready now, hold it all, offer 1180-C, or cancel line 3" | Your rules: partial shipments allowed, approved substitutes, cancel terms |
Don't explain your supply chain. "Our vendor is late" is enough. Don't promise a date you can't back. If the new date is a guess, say when you'll know instead.
Use the customer's PO number and, if you have it, their part number. It's the first thing their buyer will search for in their own inbox. Our guide on automating order-status emails covers where those answers live in the ERP.
Where a person stays in the loop
The software can do the checking and the drafting. A person should approve the send, at least at first. Here's why:
- Some dates are wrong. A purchasing agent may already know the vendor will ship early, or that stock is coming from another branch. The ERP doesn't know what's in their head or their inbox.
- Some customers need a call, not an email. If a line is holding up a customer's production run or a job site, a rep should pick up the phone. The draft can flag big orders or key accounts for a call instead.
- Options need judgment. Offering a substitute part or free freight on a split shipment is a business decision. The draft can suggest it; a person decides.
A good setup puts every draft in one review queue: the line, the old and new dates, the reason if known, and the email ready to send. The reviewer approves, edits or skips. After a few weeks you'll know which kinds of notices never get edited. Those are the ones you can let go out on their own.
If you sell to consumers, it's the law
For orders from consumers by mail, phone or online, this isn't optional. The Federal Trade Commission's Mail, Internet, or Telephone Order Merchandise Rule (16 CFR 435.2) says that if you can't ship within the time you stated, or within 30 days if you didn't state one, you must offer the buyer the choice to accept the delay or cancel and get a prompt refund. You have to offer that choice without waiting for them to ask, and the notice must give a definite revised shipping date. If you don't have a reasonable basis for a date, you have to say you don't know.
The rule covers orders placed by mail, online or by phone, however they're paid for. If you sell to other businesses under signed terms, your contract and your terms of sale set the rules; check with your lawyer. Either way, the FTC's rule is a good model for a notice any customer would want: tell them early, give a real date or say you don't have one, and offer a way out.
How to start in two weeks
- Week 1: run the report by hand. Pull open sales lines with their current ship dates every morning and compare them to yesterday's pull in a spreadsheet. Count how many lines move each day. That number tells you whether this is a five-minute job or a one-hour job.
- Week 1: write three templates. One for "new date," one for "date unknown, we'll know by X," one for "partial shipment available." Have your best customer service rep write them in their own voice.
- Week 2: automate the compare and the draft. A script or automation reads the ERP, keeps the original promise dates, finds slipped lines, fills in the template and puts each draft in a review queue. Nothing sends on its own.
- Week 2: measure. Track how many "where's my order?" calls and emails come in about late lines. If notices are working, that number should drop.
Where the other side has a point
Some owners worry that sending more delay emails makes the company look worse. That's fair. A customer who gets three notices a week may start to think you can't keep a date. Two answers. First, the problem is the late lines, not the email; the notice just makes it visible earlier. Second, the daily list is also a report card for purchasing. If the same vendor shows up every week, that's a purchasing conversation worth having.
Others say their reps already know which customers to call. Often they do, for the top accounts. The automated check isn't there to replace that. It's there for the orders nobody is watching closely, where the first sign of trouble is still the customer's phone call.
And if your dates are wrong in the ERP to begin with, because receipts aren't entered on time or vendor confirmations live in someone's inbox, fix that first. A notice built on a bad date is worse than no notice.
Common questions
How do you tell customers an order is backordered?
Send a short notice as soon as the ship date moves: what line slipped (with their PO and part number), the new date or when you'll know it, which lines are still on time, and their options such as wait, ship partial, substitute or cancel.
Can an ERP send backorder emails automatically?
Most ERPs recalculate ship dates when supply moves, but few write to the customer on their own. A daily check can compare each open line's date to the original promise date and draft a notice for each slipped line for a person to review.
Where does the backorder signal come from?
From the link between the sales line and the purchase or production order that fills it. In Business Central, order promising calculates dates from stock and planned receipts, and order tracking shows how sales, purchase and production orders are linked.
Is there a law about telling customers about shipping delays?
For consumer orders placed by mail, phone or online, the FTC's rule (16 CFR 435.2) requires sellers who can't ship on time to offer the buyer the choice to accept the delay or cancel for a prompt refund, with a revised shipping date. Business sales are usually governed by your terms and contracts.
Should a person review backorder emails before they go out?
Yes, at least at first. Purchasing may know the date is wrong, some customers need a call, and offering substitutes is a business decision. Once a kind of notice never gets edited, it can go out on its own.
What should a backorder email not say?
Don't explain your supply chain or promise a date you can't back. If you don't have a firm date, say when you will have one.
How do you know if delay notices are working?
Track how many 'where's my order?' calls and emails come in about late lines before and after. If notices work, that number drops.
Sources
- Digital Commerce 360, Many B2B sellers lose online buyers with error-prone order processing (Sana Commerce survey, Mar. 11, 2024)
- Microsoft Learn, Calculate order promising dates (Business Central)
- Microsoft Learn, Track relations between demand and supply (Business Central)
- 16 CFR 435.2, Mail, Internet, or telephone order merchandise (Cornell LII)
- 16 CFR 435.1, Definitions (Cornell LII)
Automating lead-time and order-status emails
Automating revised POs and change orders
Signs your order desk needs automation