Backorder Notification Email: What to Say and When

A customer orders three items. Two ship today. The third is sitting in a warehouse in another state, with a delivery window your supplier describes as "should be early next month." Should you write "arrives by October 3"? Or "we expect it in early October, though we'll confirm once the supplier updates us"?

That one sentence is the whole game with a backorder notification email. Get it right and you retain the customer's trust across a messy situation. Get it wrong — by either going silent or making a promise your supplier hasn't made — and you create a support problem that costs more to fix than the original order was worth.

This guide gives you four copyable messages, an item-level state table for mixed orders, and a worked timeline you can adapt to your own fulfilment process.

Your turn · A one-minute experiment

Which version of this backorder update is safe to send?

Fictional one-minute exercise. All names, order numbers, items, dates, and supplier details below are invented for practice.

The situation

FICTIONAL BACKORDER SCENARIO Shop: Crestfield Goods (fictional) Operator: fictional character Ines Park Customer: fictional character Dom Saurel Order #: CFG-8821 ORDER CONTENTS: — Slate coaster set (qty 2): in stock, shipped Day 1, tracking sent. — Copper pour-over kettle (qty 1): backordered. SUPPLIER COMMUNICATION (received Day 6): Email from fictional supplier Harwell Supply reads: 'Stock expected mid-to-late November, though we're still confirming with our manufacturer.' PREVIOUS CUSTOMER MESSAGE (sent Day 1): Ines told Dom the kettle was backordered and that she would follow up by Day 7. INES'S TWO DRAFT OPTIONS: DRAFT A — Subject: Your kettle arrives November 18 Body: 'Hi Dom, quick update — your copper pour-over kettle will arrive by November 18. We'll send tracking once it ships.' DRAFT B — Subject: Update on order #CFG-8821 — copper pour-over kettle Body: 'Hi Dom, following up as promised. Our supplier's current estimate is mid-to-late November — that's their language, not a confirmed date on our end. We'll update you again by November 14 unless it ships sooner.'

Choose what you would do, then open it to see the reasoning. You can explore every option.

A · Send Draft A — gives the customer a clear, specific delivery date.

Wrong. Harwell Supply said 'mid-to-late November' and explicitly flagged uncertainty with their own manufacturer. The article states directly: 'Your supplier said around three weeks. That is not a delivery date. If you write arrives in three weeks, you own that commitment whether or not the supplier delivers on it.' November 18 is a date Ines invented — Harwell Supply never confirmed it. Sending Draft A converts a supplier estimate into a personal promise, which is the exact failure the article's review checklist is designed to catch.

B · Send Draft B — quotes the supplier's language and sets a next-update date.

Correct. Draft B applies the article's three obligations precisely: it names the affected item, it uses the supplier's own words rather than a committed date, and it gives Dom a specific next-update window (November 14). The article's checklist asks: 'Does the ETA use the supplier's own language, not a date you've committed to?' and 'Is there a next-update date in the email?' Draft B passes both tests. It also honours the follow-up promise Ines made in her Day 1 message.

C · Hold both drafts — wait until Harwell Supply confirms a firm date before sending anything.

Wrong. The article's worked timeline shows that a 'no confirmed date' update (Message 4) is itself a valid and expected message — the honest answer is sometimes 'we don't know, and we're not going to guess.' Ines also promised Dom an update by Day 7. Holding the email breaks that promise and leaves the customer without the follow-up window they were told to expect. Draft B communicates the current state accurately without requiring a confirmed date first.

A supplier's estimate is not your promise. Quote their words, set the next update date, and send — even when the honest answer is that no firm date exists yet.

What Makes a Backorder Email Different From a Standard Delay Message

A standard shipping delay says "your order is taking a bit longer." A backorder notification is more specific: one or more items are not currently in stock, the order may ship in parts, and the timeline depends on a supplier rather than your own warehouse.

That specificity creates three obligations that a generic delay message doesn't:

Name the affected item. "Part of your order is delayed" can leave customers opening every other email wondering which part. Name the product.

Separate the supplier's estimate from your promise. Your supplier said "around three weeks." That is not a delivery date. If you write "arrives in three weeks," you own that commitment whether or not the supplier delivers on it.

Tell the customer when they'll hear from you next. A single update without a follow-up window leaves the customer wondering whether to keep waiting or contact you. Setting a next-update time — even if it's "we'll check in by Friday" — closes that loop.

Item-Level State Table for Mixed Orders

This is the structure you need when an order contains both in-stock and backordered items. Keep it updated as state changes.

Item	Qty	Current state	Supplier estimate	Committed to customer	Next update due
Blue ceramic mug (12 oz)	2	In stock — shipped	—	Tracking sent	—
Blue ceramic mug (16 oz)	1	Backordered	"Early October" (supplier, 22 Sep)	Not committed	29 Sep
Bamboo lid set	1	In stock — shipped	—	Tracking sent	—

A table like this lives in your order management system or a shared doc. The email the customer receives is derived from it — you don't paste the table, you translate the current state into plain language.

One field matters most: "Committed to customer." When that says "Not committed," your email uses the supplier's words, not a date you've invented.

Four Copyable Messages

Every template below uses [brackets] for fields you fill in. Each includes an opt-out line because you should treat commercial messages conservatively regardless of their purpose; check your own compliance obligations before sending.

1 — Initial backorder notice (full order held or item separated)

Subject: Update on your order #[ORDER NUMBER] — [ITEM NAME]

Hi [FIRST NAME],

Thank you for your order. I want to let you know that [ITEM NAME] is currently on backorder, which means we don't have it in stock right now.

What's happening: [ITEM NAME] (qty: [QTY]) is waiting on a restock from our supplier. The rest of your order — [LIST IN-STOCK ITEMS] — [has already shipped / will ship today] with tracking number [TRACKING NUMBER].

What we know: Our supplier estimates restock in [SUPPLIER'S LANGUAGE, e.g. "early October"]. That's their current estimate, not a confirmed date on our end.

Next update: We'll check in with you by [DATE — typically 5–7 days out] with whatever we know at that point.

If you have questions in the meantime, reply to this email or reach us at [CONTACT].

[UNSUBSCRIBE LINK] · [BUSINESS NAME] · [ADDRESS]

2 — Partial-order confirmation (in-stock items shipped, backordered item still pending)

Subject: Part of your order #[ORDER NUMBER] is on its way

Hi [FIRST NAME],

Good news: [IN-STOCK ITEM(S)] shipped today. You'll find tracking details below.

[TRACKING NUMBER / LINK]

Still to come: [BACKORDERED ITEM] (qty: [QTY]) remains on backorder. Our supplier's current estimate is [SUPPLIER'S LANGUAGE]. We're monitoring stock daily and will update you by [DATE].

You don't need to do anything right now. We'll be back in touch as soon as we have a firm update.

Questions? Reply here or contact us at [CONTACT].

[UNSUBSCRIBE LINK] · [BUSINESS NAME] · [ADDRESS]

3 — ETA has changed

This is the one people dread writing. Write it anyway, quickly, and don't bury the change.

Subject: Updated timeline for [ITEM NAME] on order #[ORDER NUMBER]

Hi [FIRST NAME],

I'm writing to update you on [ITEM NAME], which we told you in our last message was expected [PREVIOUS ESTIMATE].

Our supplier has revised their timeline. Their current estimate is now [NEW SUPPLIER LANGUAGE, e.g. "mid-to-late October"]. We understand this is frustrating, and we're sorry for the extended wait.

What this means for your order: [ITEM NAME] will ship as soon as stock arrives. We'll send tracking the same day it leaves our facility.

Next update: We'll contact you again by [DATE] unless stock arrives sooner.

If you'd like to discuss your options, please reply to this email and a member of our team will respond. We don't want to assume what works best for you.

[UNSUBSCRIBE LINK] · [BUSINESS NAME] · [ADDRESS]

Note the last paragraph. When alternatives or adjustments are on the table, the email invites a conversation rather than listing options your team hasn't confirmed are available. A person should review those conversations before commitments are made.

4 — No confirmed date yet

Sometimes the honest answer is "we don't know, and we're not going to guess."

Subject: [ITEM NAME] — order #[ORDER NUMBER] status

Hi [FIRST NAME],

We're following up on [ITEM NAME] from your order #[ORDER NUMBER]. Our supplier has not yet confirmed a restock date, and we don't want to give you an estimate that turns out to be wrong again.

Where things stand: The item remains on backorder. We're in contact with our supplier and will update you as soon as we have reliable information.

Next update: By [DATE].

We know this isn't the news you were hoping for. If you'd like to talk through your order, reply to this email and we'll be in touch within [TIMEFRAME, e.g. one business day].

[UNSUBSCRIBE LINK] · [BUSINESS NAME] · [ADDRESS]

Worked Timeline: What Happens When the ETA Shifts

Here's how the four messages fit together in a real sequence. The dates are illustrative — yours will follow your own fulfilment calendar.

Day 0 — Order placed. Two of three items in stock. Third is backordered.

Day 1 — Send Message 1 (initial notice). Name the backordered item. Cite the supplier's estimate in their words. Set next update: Day 7.

Day 5 — In-stock items ship. Send Message 2 (partial-order confirmation). Reiterate backorder status. Next update still Day 7.

Day 7 — Supplier revises estimate. Previously "late September," now "mid-to-late October." Send Message 3 (changed ETA). Acknowledge the change directly. Set next update: Day 21.

Day 21 — No confirmed date. Supplier hasn't confirmed stock. Send Message 4 (no confirmed date). Keep next-update promise: Day 28.

Day 26 — Item ships. Send tracking. No further backorder notifications needed — stop the sequence here. A stopped sequence is just as important as a started one. Running a "backordered" update after an item has shipped creates its own confusion.

The Customer Apology Section (and When It Belongs)

A customer apology email is often woven into the backorder messages above — you saw it in Message 3, where the ETA shift warranted a direct acknowledgment. The apology isn't a separate document; it's a paragraph or sentence in the update where something has changed for the worse.

What a useful apology does: names what happened, doesn't over-explain or shift blame to the supplier, and tells the customer what you're doing next.

What it doesn't do: promise a specific compensation or refund that your team hasn't approved. If your policy allows order adjustments, the email invites the customer to get in touch — it doesn't commit to an outcome a person hasn't reviewed.

Where the Review Step Actually Sits

One significant failure in a backorder email sequence isn't bad writing — it's the review step happening too late or not at all. Someone schedules an automated follow-up for Day 7, the supplier revises their estimate on Day 5, and the Day 7 email goes out with the wrong date because nobody caught the change.

Zapier documents a structural pattern for this kind of workflow: monitor order state, filter for qualifying conditions, create a draft, have a person review it before it sends. For pre-order items, Zapier's documented automation creates a draft in Microsoft Outlook for a person to review before it reaches the customer. That draft-then-approve step is where stale supplier dates and incorrect commitments get caught.

A related Zapier automation shows the same monitor-filter-notify-log structure applied to backorder status using Neto Commerce and touchSMS — a different platform and channel, but the same logic: detect a qualifying order state, act, and record the result. The principle transfers even when the tools don't.

The tension between a convincing draft and an unverified fact is the subject of Splice Work's guide to AI email replies: when to send, edit, or escalate — worth reading if you're thinking about automating any part of this sequence.

What a Custom Integration Could Handle

If your order volume makes this sequence hard to manage manually — or if your inventory data lives in one system while your emails go out through another — the gap between those two systems is where errors happen.

Shopify's built-in notification system doesn't include a backorder state. Its fulfilment status values are shipped, partial, unshipped, or any — none is "backorder." That means triggering a properly timed, item-specific backorder notification requires custom automation or a third-party app, not a native Shopify setting.

Splice Work's Custom AI Solutions service covers exactly this kind of problem: building a connector between your inventory or order data and an email workflow, with an approval step before anything customer-facing sends. Their confirmed connectors include Gmail, Salesforce, QuickBooks Online, BILL, Stripe, Airtable, Slack and Twilio. A Shopify-native inventory connector isn't a published off-the-shelf offering, so that scope would need to be defined as part of a custom build — which is what the Custom AI Solutions service is for.

The approval model is worth noting: every agent drafts, a person approves, then it acts. That's the pattern that catches a stale supplier estimate before it becomes a promise in your customer's inbox.

If your team is writing and sending these emails manually and the volume is becoming unmanageable, it's worth describing the workflow to them. The first conversation is a walkthrough, not a commitment. Book one here.

Quick Review Checklist Before You Send

Does the email name the specific backordered item and quantity?
Does the ETA use the supplier's own language, not a date you've committed to?
Is there a next-update date in the email?
If alternatives or adjustments are mentioned, has a person approved what can be offered?
Is there an opt-out line? (Treat all commercial messages conservatively.)
If the item has shipped since this was drafted, has the email been cancelled?

That last one catches more mistakes than any of the others.