Most online stores should optimize five event-driven email flows: order confirmation, shipment update, delivery or exception update, return/refund confirmation, and account/payment/security notice. They give customers useful information at key moments after purchase or when account details change. Treat these as a practical starting set, not a universal checklist: automate the events your store actually supports, and make each message accurate and easy to act on.
What makes an email transactional?
A transactional email is triggered by a customer’s purchase, fulfillment, return, account change, billing event, or service request. Nielsen Norman Group’s ecommerce taxonomy includes confirmations, shipment and delivery notifications, return and refund notices, account and billing messages, and customer-service responses. The exact flow depends on what a store sells and the services it offers. Nielsen Norman Group’s ecommerce report also distinguishes these messages from prompts such as abandoned-cart reminders and return-to-site messages; those promotional prompts may have different consent requirements depending on jurisdiction and implementation.
As an Amazon Associate I earn from qualifying purchases.
Transactional messages can be sent by email, SMS, or push notification. Choose a channel based on the event’s urgency, customer preference, the information needed, and whether your systems can deliver an accurate status. Available evidence does not establish a universal performance ranking among these channels.
1. Order confirmation: make the purchase easy to verify
Send a clear confirmation after the order is placed. The customer should be able to check what they bought and the information used to fulfill the order without searching through the store.
#1 Best Overall
- Include the order number and an item summary.
- Show relevant billing and shipping information.
- Give an expected delivery timeline when one is available and supported by fulfillment data.
Braze’s order-confirmation guidance identifies these as typical details for the message. Braze’s order-confirmation email guide
2. Shipment update: explain what has changed
Send a shipment update when an order is dispatched. State the current status plainly and provide a tracking route when one is available. Shipment, pickup, and delivery notifications are related, but they describe different events; avoid treating “shipped” as equivalent to “delivered.”
Use a fulfillment sequence that follows the actual order: confirmation first, shipment notification when it leaves, then a delivery notification when delivery is recorded. Nielsen Norman Group specifically discusses streamlining sequences such as order confirmation, shipping notification, and delivery notification. Nielsen Norman Group’s ecommerce report
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →3. Delivery or exception update: close the loop honestly
Notify customers when an order is marked delivered, delayed, or otherwise needs their attention. Make the distinction between a confirmed event and an estimate clear: do not promise a precise delivery time unless your fulfillment data supports it. If the status is an exception rather than a completed delivery, explain the known issue and what the customer can do next.
4. Return or refund confirmation: state what happened next
Confirm meaningful return and refund events, including when a return is received or a refund is initiated. Explain what has happened and, where relevant, what step remains. Do not describe a refund as complete if it is only being processed. Nielsen Norman Group’s fulfillment taxonomy includes cancellation, return, and refund notices. Nielsen Norman Group’s ecommerce report
5. Account, payment, or security notice: make important changes visible
Use transactional notices for relevant account and billing events, such as an account change or payment-related update. Tell the customer what changed in direct terms and include a suitable next step when action is needed. These notices are useful only when they reflect a real event; avoid bundling promotional copy into a message customers need to trust for account or payment information.
How to optimize the five flows as a system
Review the whole message, not just its wording
For each flow, check the sender, subject line, preheader, body, and message format. Nielsen Norman Group identifies these as areas covered in its ecommerce report, which draws on five rounds of ecommerce studies and contains 143 recommendations. Those figures describe the report’s scope, not a promise that any single email change will improve results. Nielsen Norman Group’s ecommerce report
Free tools Windows power users keep installed
One-click scans. No signup required.
Match automation to real events
- Trigger a message from the event it describes, such as an order being placed or a shipment being dispatched.
- Keep status language aligned with the information available to your store; do not turn an estimate into a confirmed fact.
- Check that the sequence makes sense to a customer following the order from purchase through delivery.
- Keep transactional notices distinct from abandoned-cart reminders and other promotional prompts.
Measure results without mistaking averages for guarantees
Omnisend’s 2025 report says one in three people who click an automated message make a purchase, compared with one in 18 for scheduled messages. That finding concerns automated messages broadly, not transactional emails specifically, and it is not a forecast for an individual store. The same report says that 24 billion emails, 230 million SMS messages, and 413 million push notifications were sent in 2024. Omnisend’s 2025 report
Track each flow against its purpose: whether customers can identify the order, understand its status, or take a necessary account action. A purchase-conversion rate alone cannot show whether a service notification is accurate or useful.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why clear delivery and return updates matter
Delivery and return expectations can affect whether shoppers complete a purchase. DHL eCommerce’s 2025 shopper research covered 24,000 online shoppers across 24 global markets, but its US release and global release report different delivery and returns figures. Keep any statistic tied to the specific release and geography rather than combining those rates. DHL eCommerce’s 2025 report
Quick Recap
Where to start
- List the customer events your store can reliably detect: purchase, dispatch, delivery or exception, return or refund, and account or billing change.
- For each event, decide what a customer needs to know at that moment and what status your systems can confirm.
- Build the messages around those facts, then review sender, subject, preheader, body, and format.
- Test the sequence from the customer’s perspective, including cases where an event is delayed or cannot be confirmed.
- Measure each message according to its job, and revise it when customers lack necessary information or the message no longer matches the underlying event.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems
