Define what each message confirms
An order-received email may not mean payment is settled or the item has been dispatched. Use wording that matches the actual state. List which system sends each message so the store, payment gateway and fulfilment integration do not produce conflicting updates. Customers should understand the order reference and the action, if any, they need to take.
Include enough detail to resolve a question
Show the purchased items, selected variants and useful contact information. Include a link to the relevant order view where access is appropriately protected. Do not put unnecessary personal or payment information into subject lines. Confirm that the reply address is monitored and that support staff can locate the same order reference in their tools.
Test delivery and presentation
Check actual receipt with authorised test orders rather than relying only on an email preview. Review mobile rendering, image alternatives and links. Verify the sending domain and provider authentication using the provider’s instructions. Inbox delivery still depends on multiple systems; monitor bounces and complaints instead of treating API acceptance as a guarantee that the customer saw the message.
Plan messages for exceptions
Decide how delayed dispatch, payment uncertainty, cancellation and partial fulfilment are communicated. Avoid sending several contradictory automated messages while staff are resolving an issue. Give the team a way to review message history and resend an appropriate update. Recheck the templates after changes to shipping rules, payment integrations or brand contact details.
Your practical checklist
- Match wording to real order states
- Use consistent order and variant references
- Test receipt, mobile layout and replies
- Cover delays, cancellations and partial fulfilment
Working through a similar question?
We’re happy to help you find a practical starting point.
Talk to AMGK