The short version: transactional emails (order confirmed, shipped, out for delivery, delivered, plus receipts, refund notices, and account messages) are the most-opened messages any brand sends: 45 to 65% opens as a class, two to three times marketing email's 21.5% average, with order confirmations leading at 60 to 70%. The pattern holds across verticals: in food and beverage, transactional emails click at 6.5% against the category's 2.8% overall average. Most brands hand this audience to unstyled Shopify defaults. Owning the stack in Klaviyo turns the account's best-seen real estate into brand, retention, and (carefully) revenue.
Why the defaults are a waste
The customer awaiting an order opens everything you send about it, and the default notifications spend that attention on nothing: no brand voice, no education, no next step, often not even consistent design with the site they just bought from. The opportunity is not turning receipts into promotions (that path leads to spam complaints and legal trouble, covered below); it is the difference between a notification that merely notifies and one that also teaches, reassures, and sets up the relationship. Every category post in this series leans on the same insight: the supplement build loads usage education into the shipped email, and the considered-purchase build makes the delivery arc carry the craft story.
The migration decision: Klaviyo, defaults, or hybrid
Three postures, in descending order of control:
- Full Klaviyo ownership: route the platform's order events into Klaviyo flows marked as transactional, disable the overlapping platform notifications, and design the stack like the brand asset it is. Maximum control of design, content modules, and event timing; requires care that every notification the platform legally must send still sends.
- Hybrid, the common right answer: leave the bare legal receipts on the platform, and build the experience layer in Klaviyo triggered off the same events: the branded shipped email with education, the delivered email that opens the support channel and starts the post-purchase clock. Lower migration risk, most of the value.
- Styled defaults, the minimum: at least template the platform notifications to match the brand. No excuse not to; it is an afternoon of work.
What belongs in each email
Order confirmed
The receipt, complete and scannable, first and always: items, totals, address, support contact. Then the below-the-fold slots: what happens next with honest timing, the category's first education beat (usage for consumables, preparation for furniture), and at most one relevant recommendation row. The receipt is the contract; everything else is a guest in its house.
Shipped
Tracking up top, then the richest education slot in the stack: the customer has days of anticipation and nothing to do with it. Usage guides, results timelines, care preparation, the brand story: whatever the first-use experience needs them to know, teach it in transit.
Out for delivery
Short and operational: arriving today, anything they should do (someone home, clear the hallway), support one tap away.
Delivered
Confirm, open the support channel proactively (if anything is wrong, here is the fast path), restate the guarantee, and hand off: this email is the trigger boundary where the marketing post-purchase flow takes over, timed from delivery rather than order date.
The unloved ones: refunds, failed payments, account notices
Refund confirmations written with grace win back more future orders than most winback emails; the failed-payment notice is the front door of the dunning flow and deserves its no-shame, one-button build. Every notice a customer receives in a moment of friction is a brand test scored double.
The compliance line, drawn plainly
Transactional emails are exempt from marketing consent rules (they send to people who have not opted into marketing, which is their superpower), and that exemption survives only if the message stays primarily transactional. The working rules: the transactional purpose leads and dominates the layout; commercial content stays secondary in placement and proportion (a recommendation row, not a sale banner above the receipt); subject lines state the transaction, never the promotion; and unsubscribing from marketing never stops order notifications. In Klaviyo terms: the flow email is explicitly marked transactional, it ignores marketing suppression for exactly these sends, and anything that would embarrass that designation in front of a regulator or a spam-complaint reviewer gets cut. When in doubt, the receipt wins.
What to measure
- Opens against the class benchmarks: 60 to 70% on order confirmations, 45 to 65% across the stack. Materially below usually means the stack is sending from an unbranded domain or landing in spam, which is a deliverability alarm worth chasing
- Clicks against the transactional norm (the F&B data's 6.5% against 2.8% shows the class premium): tracking clicks are expected, but education and recommendation clicks are the earned ones
- Attributed revenue from recommendation modules, watched with suspicion: it should be a pleasant side effect. If transactional revenue becomes a target, the incentive to over-commercialize the stack follows, and the exemption erodes
- Support-ticket rate on order-status questions, the truest measure of the stack doing its actual job: a well-built stack answers the where-is-my-order question before it gets asked
Frequently asked questions
Should transactional emails live in Klaviyo or the ecommerce platform?
Hybrid is the common right answer: legal receipts stay on the platform, the branded experience layer (shipped, delivered, education) runs in Klaviyo off the same events. Full migration buys maximum control for teams ready to own the checklist.
Can transactional emails include marketing content?
Secondary content, yes: one recommendation row below the transactional payload, education freely. The transactional purpose must lead in subject line and layout, or the consent exemption that makes these emails special stops protecting them.
Do transactional emails send to non-subscribers?
Yes, that is the point: order notifications go to everyone who orders, regardless of marketing consent, and must keep sending even after a marketing unsubscribe. Which is exactly why the content rules matter.
What open rate should the stack hit?
Order confirmations benchmark at 60 to 70%, the stack overall at 45 to 65%. Below that band, suspect deliverability or an unbranded sending setup before suspecting the audience.
Where does the post-purchase flow start relative to the stack?
At the delivered event. The stack owns purchase-to-delivery; the marketing flow owns everything after, timed from the box arriving, not the order being placed.
Sources
- MailerToGo. Transactional email open rate benchmarks.
- CUFinder. Food and beverage marketing benchmarks.
- Klaviyo. Email marketing benchmarks.