Transactional Emails · Order Confirmation, Shipping & Receipts

The distinction between transactional and marketing email has both legal and practical significance. Under CAN-SPAM, transactional emails are exempt from some marketing email requirements — specifically the requirement to include an unsubscribe mechanism — because they are responses to an action the recipient took, not unsolicited commercial messages.

Note: under GDPR, even transactional emails sent to EU recipients must comply with data processing requirements — users must have consented to the use of their email for the type of communication involved. Pure service transactional emails (order confirmations, account security) are generally covered by contract (necessity of contract) as a lawful basis; embedding marketing content in transactional emails may require separate consent.

• Lead with the most important information. Order confirmations should open with the order number and confirmation — not branding or marketing messages. The recipient's primary question is "did my order go through?" — answer it immediately.
• Make tracking links prominent. Shipping notifications exist to let customers track their orders. The tracking number and a direct link to the courier's tracking page should be the most prominent elements.
• Include all relevant reference information. Order number, date, and customer service contact details should always be present — recipients often forward transactional emails to customer service or reference them later.
• Use plain, clear language. Transactional emails are functional communications. Marketing language ("Amazing news — your order is on its way!") feels misaligned with the functional purpose and can obscure the critical information.
• Mobile-first design. Order confirmations and shipping notifications are opened on mobile more than any other email type — customers check order status on their phones. Single-column, large text, tap-friendly CTAs.

Transactional emails have a higher deliverability standard than marketing emails — they must reach the inbox every time because they contain time-sensitive information (order confirmations, password resets, shipping tracking). A marketing email that lands in spam is a missed revenue opportunity; a password reset email that lands in spam is a customer service crisis.

Why separate infrastructure is recommended

Sending transactional emails from the same IP address and sending domain as marketing emails means your marketing deliverability issues can affect transactional deliverability. A spam complaint spike from a poorly-targeted promotional campaign can temporarily damage the IP reputation that also sends your order confirmations.

Recommended: use a dedicated sending subdomain for transactional email (transactional@mail.yourdomain.com vs marketing@updates.yourdomain.com) and, for high-volume senders, a dedicated IP or dedicated sending service (Mailgun, Postmark, SendGrid with transactional configuration) separate from your marketing ESP.

Because transactional emails achieve high open rates, they offer revenue opportunity beyond their functional purpose — but this must be handled carefully to avoid degrading trust.

• Cross-sell in order confirmation. After the confirmation details, a "Customers also bought" or "Complete the look" product block is contextually appropriate and genuinely useful — the customer just bought and may want to add to their order.
• Review request in delivery confirmation. The moment an order is delivered is the optimal time to request a product review — the experience is fresh and positive (assuming the product arrived correctly).
• Referral programme in receipt. A satisfied purchaser is a prime candidate to refer a friend. Including a referral offer (both get £10 off) in the receipt email reaches the customer at peak satisfaction.
• Loyalty point balance in confirmation. For businesses with loyalty programmes, showing the points balance and progress toward the next reward in order confirmations increases programme engagement.

Transactional email is typically sent via API rather than through a campaign interface. The application (your e-commerce platform, CRM, or custom code) calls the transactional email provider's API when a trigger event occurs (order placed, password reset requested). Providers specialising in transactional email include Postmark, Mailgun, SparkPost, and SendGrid's transactional configuration.

Key infrastructure requirements: high deliverability SLAs (99.9%+); delivery speed (password reset emails must arrive within seconds, not minutes); comprehensive logging (timestamps, delivery status, open tracking per message); and dedicated IP options for volume senders who need to protect transactional deliverability from any marketing reputation impacts.

Authentic Sources