5 Elements Every Order Confirmation Page Needs
An order confirmation page needs five elements to prevent anxiety-driven support tickets: a clear order number, a delivery estimate, an itemized total, a visible contact path, and a next-steps summary. Miss any one of these and shoppers who just paid you will open a support ticket, message you on Instagram, or call their bank to ask what the charge was for.
What a confirmation page needs to include
Most stores treat the confirmation page as an afterthought. It's the screen nobody reviews after launch, because nobody thinks of it as a conversion surface. It isn't one, technically. But it is the page that decides whether a shopper feels done or feels uneasy, and uneasy shoppers generate work.
We audit this page against the same rule book we use for product pages, cart and checkout. Five items show up again and again as the difference between a confirmation page that closes the loop and one that opens a support ticket.
- Order number. Not buried in small print. Large enough to copy-paste into a support form without hunting for it.
- Delivery estimate. A date range, not "processing." Baymard's research on checkout abandonment shows shoppers abandon carts over missing delivery information at the pre-purchase stage, and the same anxiety returns after purchase if the estimate never shows up. See our breakdown of why shoppers abandon checkout when delivery dates aren't shown.
- Itemized total. Subtotal, shipping, tax, discount, and the final charge, matching what will actually appear on the card statement.
- Contact path. A real link or email, not a generic "contact us" that dead-ends at a form with no context.
- Next steps. What happens now, in plain words. When they'll get tracking, how to change the order, what to do if something's wrong.
None of these are hard to build. The reason they're missing so often is that confirmation pages are usually built once, early, by whoever set up the checkout flow, and never touched again.
The same five elements apply whether you're selling a physical product, a digital download, or a subscription, though the details shift. A digital-only order doesn't need a delivery date range, but it does need a working download link and a note on how long that link stays active. A subscription order needs the next billing date treated as its own line item, not folded into the itemized total, because "when will I be charged again" is a different question from "what did I just pay."
Why customers email support after checkout anyway
A shopper who just paid you is briefly the most anxious version of themselves they'll be in the whole relationship. They've handed over card details, they have no product in hand yet, and the only proof they have that anything happened is whatever is on screen right now.
If that screen is thin, generic, or ambiguous, the brain fills the gap with worry. NN/g's research on error prevention repeatedly finds that uncertainty, not bad news, is what erodes confidence fastest. A vague confirmation page doesn't need to say anything wrong to cause a support ticket. It just needs to say too little.
The pattern we see in audits is consistent: the same cost surprises that cause cart abandonment before purchase resurface as support tickets after it. Baymard's widely cited figure is that 48% of checkout abandoners cite unexpected extra costs as the reason. We wrote about this in why shoppers abandon checkout over hidden fees and surprise costs. If a shopper who didn't abandon still sees a total on the confirmation page that doesn't match what they expected at checkout, that's a support ticket or a dispute, not an abandoned cart. Same root cause, different exit point.
Split orders make the same problem worse. A shopper who ordered three items and gets a shipping notice for only one, with no mention on the confirmation page that the order ships in two parcels, will not wait to see if the second box arrives. They'll email you the same afternoon, because the confirmation page never told them to expect a split shipment in the first place.
Does a good confirmation page reduce chargebacks and returns?
This is the question store owners ask us most, usually after a payment processor flags their chargeback rate. The honest answer is that a confirmation page won't stop fraud-driven chargebacks. It can meaningfully reduce the other kind: "friendly fraud" and confusion disputes, where the cardholder genuinely doesn't recognize a charge or thought they'd cancelled something.
The mechanism is simple. A chargeback for "unrecognized transaction" is far more likely when the confirmation page shows a total that doesn't clearly break down into subtotal, shipping and tax, or when the merchant name on the page doesn't match what will appear on the bank statement. Take a $92 order that shows as "SQPMT34521 LLC" on a statement instead of the store's name. If the confirmation page never mentions that the billing name differs from the storefront name, the shopper has no way to connect the two, and the dispute gets filed against a name they don't recognize. A single line on the confirmation page, "charges will appear as [name] on your statement," closes that gap for free.
Returns work on a similar logic. A shopper who can see the return window and process on the confirmation page is a shopper who doesn't need to search your site later, frustrated, when the item doesn't fit. We cover the return-policy side of this in why shoppers abandon cart without a visible return policy, and the same visibility logic applies after purchase, not just before it.
None of this shows up as a single metric you can point to before you've made the change. It shows up as fewer disputes and fewer "is this legit" emails over the following billing cycle, which is exactly the kind of change a store owner notices in support ticket volume before they notice it anywhere else.
What good looks like
Most confirmation pages fail quietly. They're not broken, they're just thin. Here's the difference in practice.
"Thank you for your order! Your order is being processed."
"Order #48213 confirmed. Arriving Thu 14 Nov - Sat 16 Nov. Charged: $84.50 ($76.00 + $8.50 shipping). Questions? Reply to this email or chat with us. We'll email tracking within 24 hours."
The "after" version answers four questions a shopper has before they've had a chance to ask them: did it work, when will it arrive, what did I pay, and who do I ask if something's wrong. That last question matters more than it looks. NN/g's usability research on error prevention and recovery makes the same point about any transactional screen: showing the recovery path before it's needed reduces the volume of people who go looking for it in a panic.
A well-built confirmation page also needs to render fast and correctly on the device it's viewed on, which for most stores is a phone. We've written separately about mobile checkout mistakes that apply just as much to the page immediately after checkout as to the steps before it. A confirmation page that takes eight seconds to load, or that clips the order number off the edge of a small screen, generates its own support tickets regardless of what content is on it.
Edge cases that trip up even good confirmation pages
Most confirmation pages fail on the simple cases: no order number, no delivery date. The ones that get the basics right often still fail on the edge cases, because nobody tests a confirmation page against anything other than a single item, in stock, shipping to the same address as billing.
Backorders and partial stock. If one item in the order is backordered, the confirmation page needs to say so, item by item, rather than showing one delivery date for the whole order. A shopper who ordered two items and expected both by Friday will contact support the moment only one arrives, even if the delay was disclosed at checkout, because the confirmation page is what they actually remember.
Split shipments. An order that ships in two or more parcels needs to say that on the confirmation page, not just in a second email sent days later. Otherwise the first parcel arriving alone reads as a mistake, not as expected behaviour.
Guest checkout. A shopper who checked out as a guest has no account page to log into later and check order status. The confirmation page is the only record they'll have unless the email is kept, which makes the order number and a "track your order" link that works without login even more important for guest orders than for account orders. We cover the account-creation trade-offs in guest checkout best practices that actually cut abandonment, and the same logic extends past checkout into the confirmation page.
International orders. A delivery estimate that doesn't account for customs clearance, or a total that doesn't show whether duties are included, generates a specific kind of support ticket: "where is my package" mixed with "why was I charged again at the door." If duties aren't included in the total, the confirmation page needs to say so plainly, not leave it to be discovered at delivery.
Order confirmation page checklist
Use this as a working list, not a redesign brief. Most of it is copy and layout, not engineering.
- Show the order number in large, copyable text near the top.
- State a delivery date range, even a wide one, rather than saying nothing.
- Break the total into subtotal, shipping, tax and discount.
- Link directly to a real contact channel, not a generic "help" page.
- Say "processing" with no timeframe attached.
- Show a total that doesn't match the checkout summary the shopper just approved.
- Bury the return policy link where only the persistent will find it.
- Assume the shopper will read the confirmation email if the page itself is thin.
If you want the full context for how this page fits into the rest of the purchase flow, our audits score confirmation pages as one part of a 115-point rule book covering product page, cart and checkout. You can see the full list of 115 checkout UX rules we test stores against, including the ones specific to post-purchase pages.
One accessibility point worth flagging separately: the contact link and order details need to be reachable by keyboard and screen reader, not just visually present. WCAG's guidance on name, role, value for interactive elements is the relevant baseline, and it's an easy thing to break when a confirmation page is built as a static template rather than tested as a real page.
Frequently asked questions
What should an order confirmation email say?
The email needs the same five elements as the page: order number, delivery estimate, itemized total, a contact path, and next steps. Most shoppers close the browser tab right after paying and check their inbox instead, so if the email is thinner than the page, you've moved the anxiety rather than removed it. Keep the subject line specific, something like "Order #48213 confirmed" rather than "Thank you for your purchase," since that's what shows up in a crowded inbox and what the shopper searches for later.
Why do customers contact support after checkout?
Uncertainty, not necessarily a real problem. A shopper who can't see a delivery estimate, can't find their order number, or sees a total that doesn't match what they expected at checkout will fill that gap with a support ticket rather than wait and hope. Baymard's research on checkout abandonment shows the same cost-related uncertainty that stops purchases before checkout is what triggers tickets after it, just moved one step later in the journey.
Does a good confirmation page reduce returns?
Indirectly, yes. A confirmation page that shows the return window and the process for starting a return reduces the number of shoppers who arrive frustrated at a return three weeks later having forgotten or never seen the policy. It won't stop returns caused by fit or quality, but it reduces the returns caused by confusion about the process itself, which is a meaningful share of return-related support load for most stores.
What's the difference between the confirmation page and the confirmation email?
The page is what the shopper sees the instant they finish paying, while their attention and anxiety are highest. The email is what they'll actually search their inbox for later, days or weeks after the purchase, when they've forgotten the exact wording on the page. Both need the same five core elements, but the email needs to stand on its own since it's the more durable record the shopper keeps.
What about orders with backorders or split shipments?
Treat them as their own case, not a variation of the standard confirmation page. State the delay or the split at the item level, on the page itself, rather than relying on a follow-up email days later. A shopper who sees the split disclosed upfront reads the second parcel as expected. A shopper who finds out from an incomplete box reads it as a mistake, and emails support to confirm it.