Templates

Template library

Shipping delay email templates for Shopify merchants

A legally careful template library for Shopify merchants covering shipping delay notices, revised ship-date emails, carrier-delay updates, preorder delays, and cancellation-ready communication.

Updated March 11, 2026
19 min read
Editorial note: This page is an operational and legal drafting guide, not legal advice. Consumer-rights rules vary by jurisdiction, product type, and contract terms. Use these templates as a safer baseline, then have counsel review the versions you automate at scale.

Why delay emails matter more than most merchants think

Most merchants treat a shipping delay email like a courtesy note. "Sorry, running late, thanks for your patience." That is usually not enough. A delay email is quietly doing three jobs at once:

  • it resets the operational promise you previously made,
  • it reduces support volume caused by silence and uncertainty, and
  • it can help you comply with consumer-protection rules when timing commitments slip.

On Shopify, this matters for a structural reason too. The order status page becomes useful once tracking exists. Before that, the customer has almost nothing to go on except your policy pages and whatever you proactively tell them. That gap is where trust starts to erode.

A customer who gets a clear revised timeline is disappointed. A customer who gets silence starts wondering if the store is even real.

“The order status page is the final page of your store's checkout where customers can track their orders and view shipping updates.”

A delay email is a promise-management tool

The point is not to sound apologetic. The point is to make the customer’s next decision easy: wait, change course, accept a split shipment, or cancel.

The legal baseline merchants should understand

Here is the legal mistake that trips up the most merchants: assuming a polite apology covers them. In some jurisdictions, it does not even come close.

In the United States, the FTC’s Mail, Internet, or Telephone Order Merchandise Rule says merchants must have a reasonable basis for shipment promises. If you cannot ship within the promised time, or within 30 days when no time was promised, you generally need to notify the customer, seek consent to the delay, or refund promptly if consent is not obtained.

“you must seek the customer’s consent to the delayed shipment”

The FTC also draws a sharper line for longer delays. For a first definite delay under 30 days, silence can sometimes count as consent. For anything longer, anything indefinite, or any second delay, express consent is the safer path. Many merchants do not realize the rules get stricter each time the timeline slips.

In the EU, the baseline is different. Unless you agreed otherwise, goods generally must be delivered without undue delay and no later than 30 days from conclusion of the contract. If delivery is late, the consumer normally gives the trader an additional reasonable period to perform. If the trader still does not deliver, the consumer can terminate and be reimbursed. If the date was essential or the trader refused delivery, termination can happen immediately.

In the UK, the baseline is broadly similar for distance sales: goods should generally be delivered within 30 days unless another delivery period was agreed with the customer.

The takeaway is the same in every market: a proactive delay email helps, but it does not erase statutory rights. Your template has to match the legal logic of where you actually sell.

Do not collapse all markets into one template

A single “sorry for the delay” email is usually too weak. Your app should support at least a U.S. delay-consent pattern and an EU/UK delay-notice pattern.

What a safer delay email includes

The safest delay email is the one where the customer can read it once and know exactly what happened, what changed, and what to do next. In practice, that usually means including:

  • Order reference so the customer instantly knows what this is about
  • What changed, stated plainly, not buried in soft language
  • The original expectation and the revised expectation
  • A real date or range if you have one, not invented certainty
  • The customer’s options, such as wait, split shipment, or cancel
  • A direct reply path or support route
  • A next update promise if the revised date is still unknown

For Shopify stores, the delay email should not contradict anything the store already said. If checkout showed a delivery date, if the shipping policy explains processing time, if the order status page says something after tracking exists, the delay email has to be consistent with all of those. When surfaces disagree, support tickets follow.

“A service message is for information only, it can’t contain anything promotional.”

This is worth saying clearly: keep your default delay emails free of promo blocks, discounts, recommendations, and campaign banners. General branding is fine. But the moment you add a product carousel or a coupon code, you have turned a service update into marketing. That has compliance implications.

What not to say

Bad delay emails tend to fail in the same five ways, and most merchants hit at least two of them:

  • they apologize without stating the new timeline,
  • they imply certainty the merchant does not actually have,
  • they hide the cancellation or refund path,
  • they use vague blame language instead of concrete facts, or
  • they bolt on marketing copy and muddy the email’s primary purpose.

Do not write "your order should go out very soon" unless you can actually defend that. The FTC does not ask whether the wording sounds reasonable. It asks whether you had a reasonable basis for the claim when you made it. "We hoped for the best" is not a basis.

Also keep the subject line honest. If the email is about a delay, the subject should say so. A "good news!" subject line that opens into a delay notification is the kind of thing that makes customers trust you less, not more.

Template 1: short operational delay

Use this when the delay is short and you actually have a revised ship date you can stand behind. This is the most common scenario: warehouse congestion, batch processing slippage, a stock transfer that took longer than expected.

Copy block

Template 1: short operational delay

Best for

1 to 5 business-day delay with a credible revised ship date

Subject line

Update on your order {{ order_number }}

Email body

Hi {{ customer_first_name }},

We’re writing to let you know that your order {{ order_number }} is running slightly behind our original shipping estimate.

Original estimate: {{ original_ship_window }}
Updated ship date: {{ revised_ship_date }}

The delay is due to {{ delay_reason_short }}.

We expect to hand your order to the carrier by {{ revised_ship_date }}. As soon as that happens, we’ll send your tracking details automatically.

If this updated timing no longer works for you, reply to this email and we’ll help with the next step.

Thanks for your patience,
{{ store_name }}
{{ support_email }}

Why this works

It says what changed, gives a real date, and avoids legal overreach. It does not add a discount, upsell, or vague reassurance that could weaken the message.

Template 2: definite revised ship date

Use this when the revised date is later and materially changes the promise. This is often the best default template for made-to-order items, inbound restock slippage, or supplier delays where you still have a reliable ETA.

Copy block

Template 2: definite revised ship date

Best for

definite revised date that materially changes the original expectation

Subject line

Your order {{ order_number }} will ship on {{ revised_ship_date }}

Email body

Hi {{ customer_first_name }},

We need to update you on your order {{ order_number }}.

We originally expected this order to ship by {{ original_ship_date_or_window }}, but we now expect it to ship on {{ revised_ship_date }}.

Reason for delay:
{{ delay_reason_long }}

What happens next:
- We will ship your order on or before {{ revised_ship_date }}
- You will receive tracking as soon as the shipment is created
- If you prefer not to wait, contact us at {{ support_email }} or {{ support_phone }}

We’re sorry for the change and appreciate your patience.

{{ store_name }}

This version is intentionally plain. A revised-date email should read like what it is: an operational update. Not brand copy trying to make a delay sound like a gift.

Template 3: revised delivery window after carrier disruption

This one is different. The parcel already left your warehouse. You are not explaining why you have not shipped. You are explaining why the carrier has not delivered. That is a different posture and usually a simpler message.

On Shopify, this is also where the order status page and tracking links become more useful, because customers can often follow shipment progress after tracking exists.

Copy block

Template 3: revised delivery window after carrier disruption

Best for

weather events, hub congestion, customs review, carrier backlog

Subject line

Delivery update for order {{ order_number }}

Email body

Hi {{ customer_first_name }},

Your order {{ order_number }} has already shipped, but the carrier is currently reporting a delay.

Tracking number: {{ tracking_number }}
Carrier: {{ carrier_name }}
Updated delivery estimate: {{ revised_delivery_window }}

Current carrier note:
{{ carrier_delay_note }}

You can track the shipment here:
{{ tracking_url }}

If the package status does not change by {{ escalation_date }}, reply to this email and we’ll investigate further.

Thank you,
{{ store_name }}

Important distinction

A post-dispatch carrier delay is usually a service update, not a shipment-delay consent scenario. The tone should be informative and specific, not defensive.

Template 4: indefinite or uncertain delay

This is the template most merchants avoid, because admitting "we don't know" feels worse than guessing. But a fake precise date that you miss again is always worse. If you do not have a real date, say that, then give the customer their options and a promise for when you will update them next.

This is also where your app should push back. If the merchant marks the delay as unknown, the UI should strongly encourage cancellation language and actively suppress overconfident ETA phrasing. Do not let a merchant type "ships next week" when the honest answer is "we have no idea."

Copy block

Template 4: indefinite or uncertain delay

Best for

supplier disruption, customs hold, manufacturing uncertainty, unconfirmed inbound date

Subject line

Important update on order {{ order_number }}

Email body

Hi {{ customer_first_name }},

We’re contacting you because we can’t currently confirm the shipping date for order {{ order_number }}.

Reason:
{{ delay_reason_long }}

At the moment, we do not have a reliable revised ship date. We know that uncertainty is frustrating, so we want to be clear rather than guess.

Your options:
- Wait for our next update
- Contact us to discuss alternatives
- Request cancellation if you do not want to keep the order open

We will send you another update no later than {{ next_update_date }}.

If you would prefer not to wait, reply to this email at {{ support_email }} and we’ll help right away.

{{ store_name }}

If you serve U.S. customers and the delay falls under the FTC shipment-delay rule, this general template is not enough by itself. Use the more explicit delay-option version later on this page.

Template 5: split shipment or partial fulfillment

Use this when part of the order is ready and part is not. Instead of making the customer wait for everything or email support to ask, you give them a choice. That turns a support problem into a clean operational decision.

Copy block

Template 5: split shipment or partial fulfillment

Best for

mixed-stock orders, partial restock delays, multi-line orders

Subject line

One item in your order is delayed

Email body

Hi {{ customer_first_name }},

We have an update on order {{ order_number }}.

These items are ready now:
{{ ready_items_summary }}

This item is delayed:
{{ delayed_items_summary }}

Updated ship estimate for the delayed item:
{{ revised_ship_date_or_window }}

You can choose one of the following:
1. Wait and receive everything together
2. Ship the available items now and the delayed item later
3. Cancel the delayed item

To choose an option, reply to this email by {{ response_deadline }}. If we don’t hear from you, we will {{ default_action_statement }}.

Thank you,
{{ store_name }}

Product lesson

This template is especially useful in an app template library because it encourages a merchant to define a default operational path instead of improvising every time.

Template 6: preorder or launch delay

Preorders need their own delay language. The customer already accepted a wait, which does not mean you can communicate loosely. If anything, it means the opposite. Launch products, limited editions, and allocation changes are emotional purchases. When that crowd goes quiet, social media does not.

Copy block

Template 6: preorder or launch delay

Best for

release-date changes, supplier allocation changes, production pushes

Subject line

Preorder update for {{ product_name }}

Email body

Hi {{ customer_first_name }},

We have an update regarding your preorder for {{ product_name }} in order {{ order_number }}.

The original expected ship window was {{ original_ship_window }}.
The updated expected ship window is {{ revised_ship_window }}.

This change is due to {{ delay_reason_long }}.

We know preorders depend on good expectation-setting, so we wanted to tell you as soon as the timeline changed.

If you want to keep the preorder open, no action is needed.
If the updated timing no longer works for you, reply to this email and we’ll help with your options.

Thank you for your patience,
{{ store_name }}

For niche merchants: name the exact product, edition, or wave. A generic "your preorder is delayed" email generates follow-up tickets from customers trying to figure out which of their three preorders just moved.

Template 7: EU and UK cancellation-ready version

This version adds stronger rights-aware language for EU or UK customers when the delivery commitment has slipped materially. It does not overstate the law, but it makes the customer’s next step clear enough that they do not need to guess.

Copy block

Template 7: EU and UK cancellation-ready version

Best for

EU or UK stores, or region-aware sending logic for those customers

Subject line

Update on the delivery timing for order {{ order_number }}

Email body

Hi {{ customer_first_name }},

We are writing to let you know that order {{ order_number }} will not arrive within the timeframe we previously indicated.

Original delivery estimate: {{ original_delivery_window }}
Updated delivery estimate: {{ revised_delivery_window }}

Reason:
{{ delay_reason_long }}

If you would like to keep the order open, we will continue to process it against the updated timeline above.

If this timing no longer works for you, please reply to this email and we will help with cancellation and reimbursement where applicable.

If you need the goods for a specific date-sensitive reason, please tell us that in your reply so we can review the order appropriately.

Kind regards,
{{ store_name }}
{{ support_email }}

The phrase “where applicable” is deliberate. It avoids making a blanket promise that every scenario gets the same remedy, while still making the cancellation path clearly visible. That is the balance most merchants need.

Template 8: U.S. FTC-style delay option notice

This is the most compliance-specific template on the page. Use it when your U.S. store cannot ship on time and the FTC’s shipment-delay framework applies. The customer needs a real choice: keep waiting or get their money back. Not a vague "thanks for your patience."

Do not copy this blindly into every context. Your exact handling can depend on whether this is the first delay, whether the revised date is definite, whether the delay exceeds 30 days, and whether silence can legally be treated as consent in your fact pattern.

Copy block

Template 8: U.S. FTC-style delay option notice

Best for

U.S. consumer orders where you cannot ship within the promised time

Subject line

Action needed for order {{ order_number }}

Email body

Hi {{ customer_first_name }},

We are unable to ship order {{ order_number }} within the original shipping timeframe.

Original shipping timeframe: {{ original_ship_window }}
{{ revised_date_block }}

Please choose one of the following options:
1. Keep the order open and accept the revised shipping timeline
2. Cancel the order and receive a prompt refund for the unshipped merchandise

To let us know your choice, use one of these options:
- Reply to this email
- Visit: {{ response_url }}
- Call: {{ support_phone }}

{{ silence_rule_statement }}

We’re sorry for the inconvenience.

{{ store_name }}

App design recommendation

Build this template with conditional legal copy. The final paragraph should change depending on whether the merchant is dealing with a short first definite delay, a longer delay, or an indefinite delay.

Subject line library

Delay-email subject lines should tell the customer what happened before they open the message. If they have to open the email to find out it is about a delay, you have already created friction.

  • Update on your order {{ order_number }}
  • Your order {{ order_number }} will ship on {{ revised_ship_date }}
  • Delivery update for order {{ order_number }}
  • Action needed for order {{ order_number }}
  • One item in your order is delayed
  • Preorder update for {{ product_name }}

Avoid subject lines that sound like marketing. "Exciting update on your order!" followed by a delay is how you train customers to distrust your emails. In service communication, clarity beats flair every time.

Variables to support in your template system

If you are adding templates to your app, prioritize variables that map to real operational facts. The customer’s first name is nice. The revised ship date is necessary. Know the difference.

A strong first version would support:

  • customer_first_name
  • order_number
  • product_name
  • ready_items_summary
  • delayed_items_summary
  • original_ship_date_or_window
  • original_delivery_window
  • revised_ship_date
  • revised_ship_window
  • revised_delivery_window
  • delay_reason_short
  • delay_reason_long
  • tracking_number
  • tracking_url
  • carrier_name
  • carrier_delay_note
  • next_update_date
  • response_deadline
  • default_action_statement
  • response_url
  • support_email
  • support_phone
  • store_name
  • silence_rule_statement
  • revised_date_block

Two implementation choices will save you more support tickets than you expect:

  • Jurisdiction switch: let the merchant choose a legal mode such as general, EU/UK, or U.S. delay-consent.

  • Promotion toggle off by default: if the merchant wants to add a coupon or product recommendation, make that a separate choice with a warning.

Good template systems encode policy

The best template libraries do not just store text. They encode when certain clauses appear, which variables are required, and which risky content blocks are disabled by default.

Best internal links

Related:

Shopify preorders guide

,

Shopify returns policy guide

,

Shopify analytics playbook for operators

,

Shopify support burden estimator

,

Editorial standards and methodology

.

Sources and further reading

FAQ

Are shipping delay emails transactional or marketing emails?

They are safest when they are purely transactional or service messages. Keep them factual and avoid adding promotional content, discounts, product recommendations, or campaign blocks unless you are prepared to comply with marketing-email rules that may apply in the recipient’s jurisdiction.

What should a shipping delay email always include?

At minimum: the order reference, what is delayed, the original expectation, the revised ship or delivery estimate if known, what the customer can do next, and a direct contact path. In many cases you should also state whether cancellation or refund is available.

Can I promise a new shipping date if I am not sure?

Do not invent precision. If you do not have a reliable revised date, say that clearly and explain when you will update the customer next. A false precise date is worse than an honest range and can create both legal and support risk.

Should I include a discount code in a delay email?

Not by default. A goodwill code can help in some cases, but it should usually be sent separately. Mixing service communication with promotional content can change the compliance profile of the email and makes the message harder to keep operationally clean.

Related resources

Keep exploring the playbook

Templates

Shopify preorder delay email template

A practical and legally careful preorder delay email guide for Shopify teams that need to reset expectations clearly, protect trust, and reduce avoidable support tickets.

templatespreordersemail
Templates

Shopify returns policy template

A practical and legally careful Shopify returns policy template with the core clauses most merchants need to state clearly before support has to explain them one by one.

templatesreturnspolicy