Required elements
The subject line states that the order is confirmed and carries the order number. Recipients search for these months later, so the number belongs in the subject rather than only in the body.
The order reference is the single most important field. It is what a customer quotes to support, what they search for, and what connects the email to every subsequent message about the same purchase.
Every claim here comes out of the order confirmation emails we collected, so you can check the reading against the emails themselves.
Line items show what was ordered, with quantity and price per item. Totals follow: subtotal, shipping, tax and the amount actually charged, which should match the figure on the customer's statement.
The shipping address is repeated back. This is the last practical moment a customer can catch a mistake, and repeating it converts a support call into a self-service correction.
Delivery expectation follows, whether a date or a range. Absence of this field is the largest single driver of "where is my order" contacts.
Payment method appears in truncated form, showing the card type and last four digits rather than anything more.
A support path closes it. For a message about money, somewhere to reply is the difference between a question and a chargeback.
Structure and timing
Send it immediately. A confirmation arriving an hour later has already generated the uncertainty it exists to prevent.
Lead with confirmation rather than with branding. The recipient opened this to verify something happened, so the first screen should answer that.
Keep the layout to one column and include a plain-text alternative. Some clients render only the text part, and an image-only confirmation carries no information at all when images are blocked.
State amounts in the currency charged, and include the tax breakdown where the jurisdiction requires it, since this message frequently serves as the customer's receipt for accounting purposes.
Compliance and classification
An order confirmation is transactional, which under CAN-SPAM exempts it from the opt-out and physical-address requirements that commercial email carries.
The exemption depends on primary purpose. Adding substantial promotional content, such as a full cross-sell block, can reclassify the message as commercial, at which point the missing unsubscribe link becomes a violation rather than an omission.
Modest related content is generally tolerated and is a judgement call rather than a bright line. The safe construction keeps the transaction above the fold and anything promotional clearly secondary.
The pattern holds in production. One account runs seventeen transactional templates with us, each four to six sections, each passing the automated compliance check before approval, covering welcome emails, password resets and event invites. The same check gates an order confirmation.
Headers must be accurate and the subject line must not be deceptive regardless of classification.
Deliverability
Send confirmations through the transactional stream on a sending domain separate from marketing. These messages need to arrive, and mixing them into campaign infrastructure exposes them to the complaint rate campaigns generate.
Do not use a no-reply address. A customer replying to an order confirmation has a real problem, and discarding that reply converts it into a chargeback or a public review.
Handle the failure case deliberately. A confirmation that hard bounces means the address captured at checkout was wrong, which is worth surfacing to the merchant rather than silently suppressing, because the order still exists.
A hold works the same way. When a first big send lands in manual review on our side, the hold itself is a transactional email: we are reviewing, we will be quick, reply to this if anything is wrong. A silent block is the one thing a message about money cannot afford.
The email with the highest open rate is the one nobody designs
Order confirmations run at 60 to 80 percent open rates, and most brands send a default template.
That gap is the whole argument. Nothing else you send gets opened at that rate, and nothing else you send is left so completely alone.
Treating it as a brand moment rather than a template slot is the correction, and the examples worth studying are the ones that did something with the space: a receipt with real design attention, a verification email turned into onboarding, a confirmation carrying a video. None of that changes what the message is for.
Restraint carries the design. Apple ships launch emails with three elements (image, headline, button) and Stripe holds its receipts to 472px. A confirmation that follows the same discipline reads as a receipt, not a newsletter.
Because the constraint is real: the order number, the total, the delivery expectation and the support path stay the most prominent things on the page. A confirmation exists so the reader can verify what they just did and find their way back if it is wrong. Design serves that, or it is decoration on a document people forward to their accounts team.
The support path is the part most often missing. A recipient reading a confirmation is either satisfied or has a problem, and the ones with a problem need somewhere to go that is not a no-reply address. Our own plain transactional design mode requires transaction details and a support path together for exactly that reason.
Send it immediately and make it findable later. A confirmation is retrieved far more often than it is read on arrival, so the subject line carrying the order number matters more than anything clever, because that is the string somebody will search six weeks from now.