The page and the email after purchase

A post purchase experience is two surfaces that say the same thing: the confirmation page, and the email that follows. Both should tell the buyer what happens next, when the order arrives, and how to ask a question.

People do not linger to interpret a vague receipt. Nielsen Norman Group has long noted that page visits are short, often under a minute on average, and that visitors read only a fraction of the words on a page unless the point is obvious immediately. A confirmation that opens with a paragraph of thanks, and hides the delivery window below a set of product recommendations, fails that test. The buyer came to learn whether the order is real.

The page is a receipt with a next step

The confirmation page has one job. Prove the payment worked, and say what the brand will do now. Design it like a receipt a person can photograph, because many of them will.

Put these in the first view, in this order:

1. A plain statement that the order is placed, with the order number.
2. What they bought, in their words: the product name, the variant, the quantity.
3. The amount paid, matching the figure they approved at checkout.
4. What happens next: packed, sent, available to download, or booked.
5. When: a date or a range you can keep.
6. How to ask a question: an address or a path a human reads.

A single sentence of thanks can sit above that list. “Thanks, Maya. Your order is in.” is enough. A manifesto, a discount on the next purchase, and a row of unrelated products are a different page. They can wait until the receipt is complete.

Use the brand’s type and a quiet layout. The moment after payment is not a place to introduce a new visual idea. It is the place the shop either sounds calm or sounds like a template. Match the words you used on the button they just pressed. If the button said “Pay,” the page should say that payment succeeded, not “Your request is processing” with no number.

The three facts, written so they survive

What happens next should be a verb and an owner. “We pack this on weekdays and hand it to the carrier” is a fact. “Your journey begins” is not. If a digital product is available now, the next step is the link, placed before any other module. If a physical order waits on a weekend, say that.

When it arrives should be the same window checkout implied. If you showed “4 to 6 business days” beside the shipping price, repeat “4 to 6 business days” here. Do not upgrade the promise because the page feels like a celebration, and do not downgrade it into “soon.” If the window depends on a region, name the region you used. A range you can meet is better than a precise day you hope for.

How to ask a question should be a destination that works. A support address a person reads is the usual answer for a small brand. A link to the order in an account works if they have an account. A chat widget that is offline, or a no-reply address, is not a question path. Put the hours next to the address if you are not there every day. The buyer should know when a human will see the note.

If something can still be changed, say the cutoff beside the order number. “Address changes until we pack, by email” is a complete instruction. If nothing can be changed, say that too. Silence reads as “try the back button,” and the back button is the wrong tool after payment.

The email in plainer words

Send the email immediately, from a name the buyer can connect to the shop. The subject line should carry the fact: the brand, the order number, and that the order is confirmed. A clever subject makes the message look like a campaign, and campaign mail gets skipped.

Inside, repeat the six items from the page, in plainer words and with less layout. The email may be opened on a phone three days later, in a list of other mail. The first lines should still make sense alone:

• Order number.
• What they bought.
• What they paid.
• What you will do next, and when.
• Where to reply.

Keep the legal and tax lines that your region requires. Keep them after the human facts, not in front of them. A receipt that opens with a paragraph of company registration details trains people to search the message for the only number they wanted.

Do not add a new offer that changes the story. A coupon in the confirmation email can be fine for a brand that always works that way. It should not sit above the delivery window, and it should not imply the order is unfinished until they use the code. One quiet line under the receipt is the most it should occupy.

Match the page if anything slips. If the page says the workshop will write when the piece ships, the email should say that, not “Your package is on the way” on the same afternoon. Contradictions create the support ticket you just tried to prevent.

What not to pile on

The confirmation is a poor place for a second shop.

Skip a survey before the receipt is visible. Skip an account wall if they checked out as a guest. You may offer an account in one sentence, using the email you already have, so they can see this order later. You should not hold the order number hostage until they pick a password.

Skip a wall of recommendations of products they did not buy. A single related piece, under the receipt, is plenty if you have a real reason: a refill, a size that completes the set, care for the material they just bought. “You may also like” with eight tiles is the marketplace habit. A brand shop can be more edited than that. The companion idea is the checkout that got them here: the form should not have promised a calm ending and then delivered a catalog.

Skip stock photography of a delivery van if you do not operate that van. Use the product image they already believe, at the same crop as the shop. The confirmation is part of the grid’s promise.

When something goes wrong

Payment can succeed while the confirmation page fails to load. The email is the backup. Write it so that it alone is enough to prove the order. Include the support path in plain text, not only as a button image. Some mail clients will show the text and drop the picture.

Payment can also fail after the person thought it worked. The failure page needs the same discipline: what happened, whether they were charged, and what to do next. “Something went wrong” with no next step sends them to the bank app and then to you, angry, with no order number. If you have the attempt id, show it.

A later shipping email is a different message. Send it when the state actually changes, with the carrier and the tracking if you have them. Do not reuse the confirmation subject line. The buyer should be able to tell the two notes apart in the inbox.

Hanabi’s work on brand shops treats this page as part of the interface, not as a default the platform happened to print. The words are UX writing: name the action, say what happens next, and leave the mood for a single line.

The form that feeds this page is where most of the friction is decided. Read the checkout fields that cost the sale before you rewrite the thank-you screen. A clear confirmation cannot repair a total the shopper never agreed to.

If you want the purchase path designed through to this page, see Hanabi’s services. The studio designs and builds the shop, including the screen and the email that prove the order is real.