Ecommerce SMS notifications: order updates and checks
Plan ecommerce SMS notifications around a verified order event, accurate message fields and customer preferences, then check failures and repeated events.
- Published
- Last updated
Ecommerce SMS notifications send customers factual updates when an order event occurs. Connect each text to the correct order, respect the customer’s channel preferences and suppress repeated or outdated events before sending.
An order confirmation, a dispatch notice and a delivery exception need different evidence. A purchase record proves an order exists. It does not prove a parcel has left the warehouse.
Choose the order event and message
Choose the event that proves the status you want to communicate. For purchase confirmation, use the accepted order record. For dispatch, use a shipment record supported by your fulfilment process. For a delivery exception, use the carrier’s recorded exception. A support update needs an actual response or case change.
Before selecting an SMS service for ecommerce, document the store connection, event name, recipient field and message owner. Confirm that the connection exposes the event you need. An app installed successfully can still lack the delivery-exception event your template assumes.
Separate order updates from marketing. The Australian Communications and Media Authority (ACMA) warns that a mostly factual message containing promotional content can still be commercial. Adding a discount to a dispatch text changes its purpose. Commercial messages need consent, sender identification and a working unsubscribe method. A purchase alone does not establish inferred marketing consent.
See the ACMA’s spam guidance and its warning about promotional service messages.
Record the customer’s notification choice separately from marketing consent. For businesses covered by the Australian Privacy Principles, use and disclosure must follow the permitted purpose under the privacy regulator’s guidance. Give your messaging provider only the details needed for delivery and support.
Write a factual short notification
Write the store name, a limited order reference and the verified status before the customer’s next action. Keep addresses, payment details and item-level sensitive information out of the text. A phone’s lock screen can expose the message.
These fictional ecommerce SMS templates illustrate the content. They are examples for a configurable transactional service, not editable Shopify native messages.
Order received
Wattle Store: We’ve received order #4821. Open your order confirmation to review it. For help, use Contact on our store website.
Parcel dispatched
Wattle Store: The parcel for order #4821 has been dispatched. Track it through your secure order page. For help, use Contact on our store website.
Use this only after your dispatch evidence supports it. If a label exists but the parcel is still waiting, describe that actual state instead. Never turn label creation into a promised delivery date.
Delivery exception
Wattle Store: The carrier reports a delivery problem for order #4821. Open your secure order page for the latest update, or contact our support team through our store website.
When your service inserts a link, use its protected order-status destination. Never build a public URL containing the customer’s address, phone number or full order contents. Check that an unrelated customer cannot retrieve the order by changing its reference.
Verify the store-to-message flow
Start a Shopify SMS integration check with the native order-confirmation route. Shopify’s SMS instructions support Australian business addresses and distinguish this route from transactional apps.
- In Settings > Checkout, choose Phone number or email under Customer contact method, then save.
- Confirm native order-confirmation SMS is active under Settings > Notifications > Customer notifications.
- Use an isolated test customer and a phone you control. Place an authorised test order using phone contact, with no email on the customer profile.
- Match the received confirmation to the order reference. Native Shopify sends one order-confirmation SMS for an eligible customer without an email. It does not send shipping texts, and its SMS content cannot be edited.
For extra order updates, use a transactional app with documented event support. Native confirmation is free to the merchant. An app has its own charges and configuration.
Failure checks for a configurable SMS flow
| Test case | Expected outcome | If it fails |
|---|---|---|
| The same event arrives twice | One notification for that order event | Enable the service’s duplicate suppression or have the integration owner implement it |
| Cancellation arrives before a queued dispatch message | Obsolete dispatch message is suppressed | Recheck the current order state immediately before sending |
| Customer corrects their number | Future messages use the verified new contact | Check whether the app reads the current order contact or an old copy |
| Provider rejects the recipient | Failure is recorded and support can respond | Correct the number through the customer-verification process |
| An old status arrives after a newer status | Customer receives no backwards status update | Compare event order and current shipment state |
Use international phone formatting. Shopify’s documentation specifies E.164 format, including the country code. Keep the evidence from each test separate from your real customer list.
Recover and keep records
Retry only an eligible message whose underlying order status is still true. Use the provider’s documented retry controls. A permanent invalid-number error needs correction, while a temporary delivery failure can qualify for a bounded retry. Stop retrying after the configured limit and assign the failure to support.
A delivery receipt reports a channel outcome. It does not prove the customer read the text or accepted an order change. Give customers a staffed contact route, especially where the sender cannot receive replies.
Keep the order/event reference, template version, preference evidence, send attempt and provider result in access-controlled records. Assign operations to event accuracy, customer support to exceptions and a named copy owner to template approval. Set a retention period appropriate to the records and their purpose.
Before enabling a paid flow, record the plan entitlement, destination coverage, message charges and spending limit. The Wati Shopify integration has separate subscription and template-message charges, and its app guide describes an additional plugin charge. SMS and WhatsApp billing need separate checks in the account.
For a branded Australian sender, follow the ACMA’s sender ID registration requirements through your message provider. Unregistered branded messages can appear as Unverified.
Distinguish the actual message channel
A WATI Shopify integration can use different messaging routes. The standard Wati Shopify app documents WhatsApp order confirmation, shipment/tracking and fulfilment messages. The Wati Shopify integration’s separate Advanced Automations documentation lists WhatsApp, Rich Communication Services (RCS) and SMS, with Business-plan access.
For WhatsApp, select the actual order event and an appropriate approved template. The WhatsApp Business Messaging Policy requires recipient opt-in and approved templates to initiate conversations. Respect opt-outs and provide a human support route. A WhatsApp preference does not automatically authorise SMS fallback.
For the Wati Shopify integration’s Advanced Automations, connect Shopify, enable the feature under Automated Messages and review the rule’s event, conditions and channel sequence. Configure fallback and stop conditions deliberately. Check SMS destination availability and recipient permission independently of the WhatsApp configuration.
Test a WhatsApp order event and an SMS event separately on phones you control. Record the selected channel, rendered template, order reference and delivery result for each. A WhatsApp chat icon appearing on the store proves neither notification route works.
Coordinate post-purchase emails with these texts so both channels use the same order facts. Enable a notification only after its event, recipient and failure route produce the expected result.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.