Automate pre-order and backorder delay notices before the promised ship date passes
Updated · By Ecomsellertool editorial team
To automate pre-order and backorder delay notices, store the ship date you promised on every open order line, compare it daily with the inbound ETA for that SKU, and send a delay notice before the promise passes. Under the US FTC rule the notice gives a revised date or says you cannot give one, offers a free way to cancel, and leads to a prompt refund if the customer cancels.
- The FTC's mail and internet order rule (16 CFR Part 435) requires a reasonable basis to ship within the time you state, or within 30 days of a properly completed order if you state none.
- If you cannot ship on time, the rule requires an offer to consent to the delay or cancel for a prompt refund, made no later than the original shipping time.
- A definite revised date up to 30 days after the original time lets silence count as consent; a later date or no date means the order is cancelled unless the customer says yes or you ship within those 30 days.
- A prompt refund under the rule is sent within 7 working days, or within one billing cycle when you are the creditor; the FTC's guide says store credit cannot replace it.
- Shopify pre-orders run through a third-party app, need Shopify Payments or PayPal Express, and can collect full, partial or no payment at checkout (checked October 23, 2026).
- This recipe covers the customer side between order and shipment; it is not legal advice and describes the US federal rule only.
The step map: who runs each step
Trigger: A daily check of every open pre-order and backorder line against the latest inbound ETA for its SKU, plus any ETA change from purchasing and every customer reply to a delay notice.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | At checkout, each pre-order or backorder line is saved with the ship date promised on the product page, or the order date plus 30 days when no date was shown, and its place in the queue for that SKU. | Rule |
| 2 | Every day, and whenever purchasing changes an ETA, the workflow matches queued lines to inbound units in order-date order and computes a projected ship date for each line. | Rule |
| 3 | Lines whose projected ship date falls after the promised date go to the decision table, which picks the notice type and the send-by date with a safety buffer before the deadline. | Rule |
| 4 | A person confirms the revised date has a real basis, such as a supplier confirmation or a ship notice, or chooses an indefinite notice that states the reason for the delay. | Person |
| 5 | The workflow sends the notice from your template with the revised date or the no-date wording, the reason, the right to cancel for a full refund, and one-click links to wait or cancel. | Rule |
| 6 | An AI model reads free-text replies and suggests wait, cancel or question. Clicks are recorded directly; a suggested consent or cancellation from text is confirmed by a person before it counts. | AI model |
| 7 | Cancellations, and orders that lapse without the consent the rule needs, are cancelled with the refund prepared and a deadline 7 working days out; a person approves the refund batch every day. | Person |
| 8 | Before a consented revised date passes, the workflow flags lines that will miss it again for a renewed notice, and a morning report lists every open line by deadline. | Rule |
5 rule steps · 1 AI model step · 2 person steps. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Approving each revised ship date before it is promised to customers
- Choosing an indefinite notice and writing the reason for the delay
- Approving the daily refund batch, and any decision to cancel a product instead of waiting
- Free-text replies the model could not classify with confidence
- Changes to the notice templates, the buffers and the decision table, after advice from your own counsel
Which tools can run it
- Your pre-order app plus a spreadsheet and your email tool, for a few SKUs on pre-order at a time
- Zapier, Make or n8n reading open orders and the ETA sheet, with an AI model step for customer replies
- Custom code on your accounts, for queue allocation across several POs, per-line deadlines, consent records and refunds
Systems it connects
- Shopify orders and fulfillment holds
- Pre-order app or selling plans
- Purchasing system or ETA sheet
- Email or SMS tool for customer messages
- Helpdesk
- Slack or email for the approval queue
Build size: Medium
Each rule is plain date math; the work is a reliable ETA per SKU, allocating inbound units to queued lines and keeping consent and refund records per line.
A launch sells out in a day, so you open pre-orders with "ships by December 1." Purchasing hears in mid-November that the container is two weeks late. Support finds out on December 4, when the first customer asks where the order is. By then the date you promised has passed, nobody has offered the customer anything, and in the US you may already be outside the federal mail and internet order rule. This recipe makes the delay notice a scheduled job instead of a scramble: every open line carries its own deadline, and the notice goes out before it. It is one page of our automation library.
What must a delay notice say, and when must it go out?
The rule is short. 16 CFR Part 435 says you need a reasonable basis to ship within the time you clearly state, or within 30 days of receiving a properly completed order if you state no time (50 days when no time is stated and the buyer applies to you for credit to pay). If you cannot make that time, you must offer the buyer, without being asked, the choice to consent to the delay or cancel for a prompt refund. The offer goes out within a reasonable time after you learn of the problem and no later than the original shipping time (checked October 23, 2026).
The notice gives a definite revised shipping date, or, when you have no reasonable basis for one, says you cannot say how long the delay will last and gives the reason. It must give the buyer a way to cancel at your expense. The FTC's business guide to the rule confirms email is an acceptable way to send it and names a website as one free way to cancel. It also says you are not required to keep records, but without them you bear the burden of showing you followed the rule (checked October 23, 2026). An automated log of every notice, click and refund is that record.
Which delay situations need which notice? The decision table
Write this table with your counsel before you build anything. "T" is the applicable shipping time: the date you stated, or 30 days after a properly completed order when you stated none. Every row comes from Part 435 or the FTC guide; the buffers and the approvers are design choices for your brand.
| # | Situation | Deadline | What the customer must be told or offered | What the workflow does | Who approves |
|---|---|---|---|---|---|
| 1 | Projected ship date is on or before T | None | Nothing required | Logs the projection; re-checks daily | The rule |
| 2 | Projected ship date is after T; the revised date is T + 30 days or earlier | Notice by T | Definite revised date; right to cancel for a prompt refund; a free way to cancel; no reply means consent to ship by the revised date | Sends the notice by T minus your buffer; the revised date becomes the line's new deadline | Ops lead confirms the revised date first |
| 3 | Revised date is more than 30 days after T | Notice by T; consent by T + 30 days | Definite revised date; right to cancel; the order is cancelled automatically unless the customer agrees within 30 days of T or you ship within that window | Sends the notice with a one-click "I'll wait" link; sends reminders; at T + 30 with no yes and no shipment, cancels and prepares the refund | Ops lead confirms the date; a person approves the refund |
| 4 | No reasonable basis for any revised date | Notice by T; consent by T + 30 days | That you cannot say how long the delay will last, and why; right to cancel; automatic cancellation without consent; if they agree, they can still cancel any time before shipment | Same as row 3; consented lines keep a live cancel link until shipment | Ops lead writes the reason |
| 5 | Customer cancels before shipment, under any option | Refund within 7 working days (one billing cycle if you are the creditor) | A prompt refund | Cancels the line, releases its place in the queue, prepares the refund with its deadline | Daily refund batch approved by a person |
| 6 | Customer agrees to the delay | None new | Nothing further for now | Records the consent with its time and the revised date it covers | The rule |
| 7 | A consented revised date will be missed | Renewed notice before the revised date expires | A renewed option: new definite date or no-date wording; no reply now means the order is cancelled if you have not shipped by the old revised date | Flags the line early; sends the renewed notice; cancels unanswered lines at the old revised date | Ops lead confirms the new date |
| 8 | Customer agreed to an indefinite delay | None, until shipment | No further notices required; the right to cancel continues | Keeps the cancel link live; courtesy updates are your choice | The rule |
| 9 | You decide not to ship the item at all | Within the time a delay notice would have been due | Notice that the order is cancelled, with a prompt refund | Cancels every queued line for the SKU and prepares refunds | Founder or ops lead |
| 10 | Order is outside the rule (cash on delivery, seeds or growing plants) | None under this rule | Your own policy | Routes to a person instead of the table | Support lead |
Three things make it work. The deadline belongs to each line, not to the product, because two customers who ordered three weeks apart without a stated date have different T dates. Row 2 is the cheap path: a definite date within 30 days of T, sent on time, keeps the order unless the customer cancels. Rows 3, 4 and 7 cancel by default when the customer stays silent, so the workflow must chase a yes and, failing that, refund on time.
How do you calculate the dates for each order line?
Five formulas, run every morning. Receiving and handling days come from your own warehouse history.
T = promised ship date shown at checkout, or order date + 30 days if none was shown
Projected ship date = inbound ETA of the PO that covers the line + receiving days + pick-and-pack days
Notice send-by date = T − your safety buffer
Consent window ends = T + 30 days
Notice type = row 2 if revised date ≤ T + 30 days; row 3 if later; row 4 if no reasonable basis for a date
Which PO covers a line depends on its place in the queue. Queued lines take inbound units in order-date order, so if 300 units arrive on one PO and 340 lines are waiting, lines 301 to 340 wait for the next PO and get its ETA. Here is how it reads for an illustrative launch; the dates and quantities are examples, not client data.
| Line (illustrative) | Ordered | Promise shown | T | Covering PO and projected ship date | Result |
|---|---|---|---|---|---|
| A | Oct 20 | "Ships by Dec 1" | Dec 1 | PO 1, Nov 26 | Row 1: no notice |
| B | Nov 3 | "Ships by Dec 1" | Dec 1 | PO 1 slips, Dec 20 | Row 2: notice by Dec 1; Dec 20 is within T + 30 (Dec 31) |
| C | Nov 3 | None shown | Dec 3 | PO 2, Jan 15 | Row 3: notice by Dec 3; needs a yes by Jan 2 or the order is cancelled |
| D | Nov 10 | "Ships by Dec 1" | Dec 1 | PO 2, supplier has not confirmed a date | Row 4: no-date notice by Dec 1 with the reason; needs a yes by Dec 31 |
With a five-business-day buffer, the notices for lines B and D go out in the week of November 23. The buffer is a design choice: it covers a supplier who misses a confirmation and a weekend. Our supplier PO and ETA tracking recipe is where the ETAs come from; this recipe only reads them. Keep the two apart, because a buyer accepting a new date is not the same decision as promising that date to a customer.
What does Shopify give you to build this?
Pre-orders run through an app. Shopify's pre-orders help page says pre-orders need a third-party app, are available only with Shopify Payments or PayPal Express, and can collect full, partial or no payment at checkout, storing the customer's payment method for later (checked October 23, 2026). Backorders usually come from the Continue selling when out of stock setting on a product or variant, which works only when inventory is tracked (checked October 23, 2026). That setting sells the item; it tells the customer nothing about a ship date, so the promise has to be shown and stored by you.
Shopify's guide to managing pre-orders covers the actions the workflow calls: placing an unfulfilled order on hold, changing a deferred payment's due date, cancelling a partially paid pre-order that is not fulfilled, and refunding (checked October 23, 2026). It also warns that after a refund in Shopify you may need to cancel the order in the pre-order app as well, so the workflow does both. Shopify leaves telling the customer about pre-order status to you.
For a custom build, Shopify's developer guide to deferred purchase options says pre-orders are modeled as selling plans, an order can have only one deferred payment due date, and fulfillment can be set to as soon as possible, a specific date or unknown (checked October 23, 2026). The SellingPlanFixedDeliveryPolicy object holds that setting as ANCHOR, ASAP, EXACT_TIME or UNKNOWN, with an exact fulfillment time when one is set (checked October 23, 2026). An exact time is a useful default for T, but the date shown on the product page is the one that counts.
What stays with a person?
The promise and the money. The rule requires a reasonable basis for any revised date, so a person confirms each date against a supplier confirmation or ship notice before the notice goes out; an ETA guessed from last year's lead time is not enough. The same person writes the reason for any no-date notice. Refunds are required, not optional, but a person still approves the daily batch so a mistaken cancellation does not refund the wrong order. Cancelling a product outright is a founder or ops lead decision.
Customer replies split two ways. A click on "I'll wait" or "Cancel my order" is recorded directly with its time. A reply that says "fine, but can you ship the other item first?" is a question, and the AI model only suggests a reading; a person decides. Customers who write in through support should land next to the order's delay history, which is what our support-ticket triage recipe does. Once the parcel ships, this recipe hands over to shipping exception alerts, which watch the carrier instead of the supplier.
Where does a custom build earn its cost?
When several POs feed one queue. A single pre-order SKU with one supplier date fits a spreadsheet and an email tool. A launch with three variants, two POs per variant and orders placed both with and without a stated date needs queue allocation, a T per line, consent records and refund deadlines that survive an ETA moving twice. That is where custom code on your accounts beats a long chain of Zapier, Make or n8n steps. The same queue tells purchasing how much demand is waiting, which feeds our low-stock alerts and draft purchase orders recipe and the stockouts gap, and it can run on Ecomsellertool Growth OS beside your other order flows.
Who builds pre-order and backorder delay notices?
Ecomsellertool builds workflow automation on your own Shopify store, purchasing data and email accounts. We have built software on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. For delay notices we write your decision table and templates with you and your counsel first, then connect the ETAs, the per-line dates, the customer messages and the refund queue. Send a project brief or read how our workflow automation service works.
The building blocks are work we have shipped:
- Orders and alerts on one screen. For Seller7, a multi-marketplace seller OS we built, order volume, cancel rates, fulfillment health, pending shipments and alerts sit on one dashboard, with orders from Amazon, Walmart, Target Plus, Shopify and Mirakl in one list.
- Inbound shipments tracked. For Little Owl, a 3PL and FBA prep center, we built software that tracks inventory and inbound shipments for the center and its clients.
Get your delay notices built
Send us your pre-order rules and your supplier dates
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
Do I have to email customers if a pre-order is delayed?
In the US, if you cannot ship within the time you stated, or within 30 days when you stated no time, the FTC rule requires you to offer the customer the choice to accept the delay or cancel for a prompt refund, no later than the original shipping time. Email is an accepted way to send it. This is not legal advice; ask your counsel about your orders.
Does the 30-day rule apply to pre-orders?
The rule covers merchandise ordered by mail, internet or telephone and does not exempt pre-orders. If your product page shows a ship date, that date is your deadline; if it shows none, the default is 30 days from a properly completed order. How deferred-payment pre-orders fit that definition is a question for your counsel.
What if a customer does not reply to a delay email?
It depends on the revised date. If it is 30 days or less after the original shipping time, silence counts as consent to that date. If it is later, or you could not give a date, the order is cancelled unless the customer agrees within 30 days of the original time or you ship within that window.
Can I give store credit instead of a refund for a cancelled backorder?
Not for a refund the rule requires. The FTC's business guide says you cannot substitute store credit, vouchers or scrip for a required refund. You can offer credit as an extra option the customer chooses, as long as the refund stays available.
How fast must the refund go out after a cancellation?
The rule defines a prompt refund as one sent within 7 working days of the customer's right to a refund, or within one billing cycle when you extend the credit yourself. The workflow sets that deadline on every cancelled line.
Can this workflow send delay notices without anyone checking?
The sending can be automatic, but the revised date should not be. The rule requires a reasonable basis for any revised date, so a person confirms it from a supplier confirmation or ship notice before customers see it. Refunds and cancelling a product also stay with a person.
