Order confirmation emails: what to include and Gmail markup
Short answer: A good order confirmation email arrives within a minute, has a subject line with the order number, and shows what was bought, the total paid, the delivery address and method, when to expect the order and how to get help, with a clear "View order" link. If many of your customers use Gmail, you can also add structured order data to the email using schema.org's Order type, which Gmail documents for receipts and a "View order" action. Gmail only shows richer features to registered senders who meet its authentication and volume guidelines, so get the basics right first.
What customers look for
People open order confirmations to check they ordered the right thing, to know when it arrives, and to find it again if something goes wrong. Make each of those quick:
- Subject line: "Order 10483 confirmed: arriving Thu 14 Nov" beats "Thank you for your purchase!"
- Order number near the top, in text, not only in an image.
- Items: name, variant (size, colour), quantity, price, and a small photo.
- Totals: subtotal, delivery, discounts and total charged, with the payment method shown safely (for example, card ending 4242).
- Delivery: address, method and expected date or window.
- Next steps: when they'll get a shipping email with tracking.
- Help: how to change or cancel, and how to contact you, with a reply-to address that reaches a person.
- "View order" button linking to the order page in their account or a secure order status page.
Keep marketing light. A small "you might also like" section is fine; a full promotional email is not.
Technical basics
- Send it immediately. Customers often refresh their inbox straight away. Queue the email reliably so a slow mail provider doesn't block checkout.
- Authenticate your domain. Set up SPF, DKIM and DMARC for the sending domain so confirmations reach the inbox.
- Use a transactional sending stream separate from marketing, if your email provider supports it.
- Plain-text version: include one; it helps some clients and deliverability.
- Mobile layout: single column, large tap targets, readable without images.
- Accessible: real text, meaningful alt text, sufficient contrast.
Gmail order markup
Gmail supports structured data in emails, using schema.org vocabulary in JSON-LD or microdata. Google's reference for the Order type describes an order as a confirmation of a transaction, a receipt, which can contain multiple line items. Required properties include:
merchant, with itsname, the party taking the order;orderNumber, the merchant-specific identifier;priceCurrencyandprice;acceptedOffer, describing the item or items.
The reference also shows how to add a View order action by setting the url property, and how to add a ViewAction to link into a mobile app.
You add this markup inside the email's HTML, alongside the visible content. It doesn't replace the visible email; customers still need everything listed above in readable form.
Registration and requirements
Google's "Register with Google" guide explains that schemas you send to yourself can be tested right away, but to show them to other users you must register. Its sender guidelines include:
- emails authenticated with DKIM or SPF, with the authenticated domain matching your From address's domain;
- a consistent history of sending a high volume of mail from your domain, on the order of hundreds of emails a day to Gmail, for at least a few weeks;
- a very low rate of spam complaints.
The registration process involves sending a sample email from your production servers to an address Google specifies, so it can check compliance.
For a small shop sending a handful of orders a day, the volume requirement may rule this out for now. That's fine: a clear, well-structured confirmation email matters far more than markup.
Testing
- Place real test orders with different items, discounts and delivery methods.
- Check emails in several clients, including phone apps, with images off.
- Confirm links go to the right order and work for logged-out customers where appropriate.
- If you add markup, send to yourself in Gmail to test, and validate the JSON-LD.
- Check the email arrives in the inbox, not spam or promotions.
Order changes and partial confirmations
Confirmations aren't one email. Plan the related messages at the same time, with consistent design and the same order number in every subject line: payment failed or pending, order edited, item out of stock or substituted, partially shipped, cancelled and refunded. Customers compare these emails with the original confirmation, so totals and item names should match exactly. If an order is edited after confirmation, send an updated summary rather than a vague "your order has changed" note.
Keep a copy and a record
Store a copy of what was sent, or at least the data used to build it, with each order. When a customer says "my confirmation said something different", support can see exactly what they received. Log delivery events from your email provider too, so you can tell whether an email bounced, was delayed or was simply missed in the inbox.
An illustrative example
A hypothetical Austin coffee roaster's confirmations had the subject "Thanks!" and showed items only as images. Customers emailed asking whether orders had gone through. The roaster changed the subject to include the order number and expected dispatch date, made all details real text, added a "View order" button and a plain-text version, and set up DKIM and DMARC. Order-status questions to support dropped. Once sending volume grew, the developer added Order markup and tested it in Gmail before applying for registration.
FAQ
Do I need markup for Gmail to show my email properly?
No. Markup enables extra features; a normal HTML email displays fine.
Should confirmations include the full card number?
Never. Show only the card type and last four digits.
Can I include a review request?
Not yet. Ask after delivery, when the customer has the product.
What if the email is delayed?
Show a clear confirmation page at checkout too, so customers know the order went through.
If your order emails confuse customers or keep landing in spam, send us a sample confirmation.