An order confirmation should answer one question clearly: what order did the store accept? Generate it from the committed order record after the payment and order workflow reaches the store's defined success state. Do not use a button click or an analytics event as proof that an order exists.
Confirm the record, not the attempt
Choose the system of record for the order number, items, quantities, prices, discounts, tax, shipping charge, delivery address, payment status, and fulfillment status. The confirmation page and message should read from that record. If payment is authorized but not captured, or the order needs manual review, say so in plain language instead of presenting it as shipped.
Shopify's store-notifications documentation explains that customer and staff notifications are triggered by events such as order placement, fulfillment, refunds, exchanges, and account changes. Those are different lifecycle events. Keep the initial confirmation separate from shipping, cancellation, refund, and exchange notices so each message has one purpose.
Include useful, bounded details
Show a recognizable store name, order identifier, order date, purchased items and quantities, price breakdown, delivery method, destination summary, current payment state, and a safe way to view or ask about the order. Avoid putting sensitive payment credentials or unnecessary personal data in the subject line or URL. Mask payment details and use authenticated order-status pages when the platform provides them.
State the shipping expectation the business can actually meet. The FTC's Mail, Internet, or Telephone Order Merchandise Rule guide says covered sellers need a reasonable basis for a stated shipping time; if no time is stated, the guide describes a 30-day default, along with consent and refund duties when shipment is delayed. Legal obligations vary by transaction and jurisdiction, so use qualified counsel for the store's specific policy rather than copying a generic deadline.
Design the failure path
A customer may finish checkout while email delivery is delayed, filtered, or rejected. Keep the on-site result accurate, provide a way to retrieve the order through the customer's account or support process, and let staff resend from the existing record rather than creating another order. If the store cannot find an order, verify payment status before asking the customer to buy again.
Use idempotent message triggers where the platform permits it. Record the order event, template version, recipient destination, send time, provider response, and resend action. A duplicate confirmation is usually less harmful than a duplicate charge, but repeated messages can confuse customers and staff, so make retries observable.
Test the complete lifecycle
Place controlled test orders for common payment and delivery combinations. Verify the page and message totals match the admin record; links use the intended host; mobile layouts remain readable; accessibility labels are meaningful; and replies reach a monitored channel. Test pending payment, failed payment, cancellation, partial fulfillment, refund, and resend behavior.
Review templates whenever product, tax, shipping, return, or support processes change. A practical order confirmation is not a marketing flyer. It is a durable receipt of what the store accepted, paired with honest next steps and a traceable route to help.
Sources
- Store notifications — Shopify Help Center
- Business Guide to the FTC's Mail, Internet, or Telephone Order Merchandise Rule — Federal Trade Commission