Order delay SMS templates for Shopify merchants

Why delay SMS templates need a different standard

SMS is not "email, but shorter." It is a different channel with different rules, and most of those rules boil down to: you get one shot to say something useful before the customer either ignores it or panics.

A delay email can carry nuance and fallback detail. A delay SMS gets one job: say what changed and what to do next. If the text tries to do anything more ambitious than that, it usually becomes noise.

On Shopify, this matters more than it should. Native SMS notifications are limited, so richer delay texts usually require an app or custom workflow. That means your template library should not just store wording. It should encode the operational logic behind why the text exists.

The legal and platform baseline

There are two layers to get right with delay SMS, and most teams only think about the first one.

The first layer is consumer-rights and communications law. A delay text about an existing order is usually safest when it is purely administrative. If you add marketing copy, discount pushes, or product suggestions, you move into a riskier category.

The second layer is platform and workflow design. The text has to match your store’s actual order state, your order page, and your real support process. A text that promises a date your ops team cannot hit is worse than sending nothing at all.

For EU and UK-style flows, a proactive delay message helps with transparency, but it does not erase the customer’s rights if delivery slips materially. For U.S. flows, merchants should be especially careful about consent, opt-outs, and not assuming every automated text is exempt.

What a safer delay SMS includes

Good delay texts are short because they are disciplined. Bad delay texts are short because they left out everything useful.

A safer order delay SMS usually includes:

• Order reference
• What changed
• Revised date or range, if known
• One next step, not three competing calls to action
• A trusted reply path or order-status link

In practice, one text should contain exactly one of these actions:

• reply to this message
• view order status
• contact support
• confirm whether to keep waiting

If you try to cram all of them into 160 characters, the result is a text that asks the customer to do four things and they end up doing none of them.

What not to send

Bad delay texts fail in the same ways bad delay emails do, except with less room to recover:

• they say “slight delay” without a new timeframe,
• they sound apologetic but not informative,
• they guess a date that is not operationally reliable,
• they mix customer-service content with marketing copy, or
• they point the customer to multiple links and next steps at once.

Avoid filler phrases like “we appreciate your continued support” unless the actual update is already crystal clear. In SMS, every extra word is stealing space from the thing the customer actually needs to know.

Template 1: short operational delay

Use this when the order is only slightly behind and you have a credible revised ship date.

warehouse backlog, restock handoff, minor processing slippage

{{ store_name }}: Order {{ order_number }} is slightly delayed. New ship date: {{ revised_ship_date }}. We’ll send tracking as soon as it ships. Questions? Reply here.

Template 2: revised ship date confirmed

Use this when the original promise changed materially and you need to reset expectations clearly.

supplier delay, made-to-order timing shift, inventory handoff change

{{ store_name }}: Update for order {{ order_number }}. We now expect it to ship on {{ revised_ship_date }} instead of {{ original_ship_date_or_window }}. If this no longer works for you, reply to this text.

This is one of the most useful templates in the set. Without it, the customer emails support to ask what happened. With it, they already know and can decide what to do.

Template 3: indefinite delay

Most merchants avoid this template because admitting uncertainty feels wrong. But if you do not have a real date, honesty is both the safest and the most useful thing you can send.

customs issue, inbound stock uncertainty, supplier disruption

{{ store_name }}: We have a delay on order {{ order_number }} and can’t yet confirm a ship date. We’ll update you again by {{ next_update_date }}. If you don’t want to keep the order open, reply to this text.

The key is the next update promise. "We don't know" is acceptable. "We don't know and we'll disappear until we figure it out" is not. Give them a date for the next check-in.

Template 4: carrier delay after dispatch

This is different from a pre-shipment delay. The order has already moved, so the text should orient the customer around tracking and the revised delivery window.

weather disruption, hub congestion, customs review, carrier backlog

{{ store_name }}: Order {{ order_number }} has shipped, but the carrier reports a delay. New delivery estimate: {{ revised_delivery_window }}. Track here: {{ tracking_or_status_url }}

Template 5: split shipment choice

This template works when part of the order is ready and part is not. One important catch: only offer choices your ops flow can actually handle. If you cannot really split the shipment, do not pretend you can.

mixed-stock orders, delayed line items, partial fulfillments

{{ store_name }}: One item in order {{ order_number }} is delayed until {{ revised_ship_date_or_window }}. Reply 1 to wait and ship together, 2 to ship available items now, or 3 to cancel the delayed item.

If you use numeric reply flows, test them. A customer replying "2" and getting no response is worse than not offering the choice at all.

Template 6: preorder delay

Preorder customers already accepted a wait. That does not mean you can be vague about a second wait. The text should still reset the promise in plain language, just with a different emotional baseline.

release-date changes, allocations, production delays

{{ store_name }}: Preorder update for {{ product_name }} in order {{ order_number }}. New expected ship window: {{ revised_ship_window }}. If you’d rather cancel, reply to this message.

Name the product explicitly. "Your preorder is delayed" means nothing to a customer with three open preorders.

Template 7: EU and UK rights-aware version

Use this when the timing change is serious enough that you want a stronger rights-aware message without overloading the text.

material delay for EU or UK customer flows

{{ store_name }}: Order {{ order_number }} won’t arrive within the original timeframe. Updated estimate: {{ revised_delivery_window }}. If this timing no longer works for you, reply here and we’ll help with next steps.

Short, but the customer’s options are still visible. That is the whole trick with rights-aware SMS.

Template 8: U.S. action-needed version

Use this when a U.S. customer needs to actively decide: keep waiting, or cancel. This is the strictest template in the set, and sometimes the most necessary.

delayed shipment where you want a clean keep-or-cancel flow

{{ store_name }}: Action needed for order {{ order_number }}. We can’t ship within the original timeframe. New estimate: {{ revised_ship_date_or_window }}. Reply KEEP to wait or CANCEL for the next step.

Subject line equivalents and trigger labels

SMS does not have subject lines, but your internal trigger labels still matter. Anyone reading the codebase or the automation config should know exactly what each template does from the label alone:

• short_delay_notice
• revised_ship_date_notice
• indefinite_delay_notice
• carrier_delay_notice
• split_shipment_choice
• preorder_delay_notice
• eu_uk_delay_notice
• us_action_needed_delay

Variables to support in your template system

For SMS, fewer variables is better. Prioritize the ones that change the customer’s decision. The order number matters. The store name matters. A personalized greeting adds zero value in 160 characters.

• store_name
• order_number
• product_name
• original_ship_date_or_window
• revised_ship_date
• revised_ship_date_or_window
• revised_delivery_window
• revised_ship_window
• next_update_date
• tracking_or_status_url

Two implementation choices matter a lot:

• Jurisdiction-aware templates, at least general, EU/UK, and U.S.
• Promotion disabled by default for delay texts

The best template systems do not just save copy. They enforce rules: which variables are required before send, which risky wording gets blocked, and when a merchant needs to pick a different template entirely.

Best internal links

Related:

,

,

,

,

.

Sources and further reading

• FCC, Telephone Consumer Protection Act rules

• FCC 24-24, consent and revocation order

• ICO, Electronic and telephone marketing

• ICO, Identify direct marketing

• Your Europe, Shipping and delivery

• Shopify Help Center, Setting up SMS notifications

• Shopify Help Center, Understanding order status pages

• Shopify Help Center, Customizing notification templates

• Shopify Help Center, Collecting customer contact information