Goal
Confirm order details and reduce follow-up contacts about status or receipt access.
Template Hedgehog
Open navigation
Order confirmation
Confirm post-purchase details with an operational structure that support teams can trust.
Workflow assembly
Trigger to production output
01
Trigger
Real send event
02
Workflow
Message journey
03
Layout
Complete structure
04
Components
Reusable blocks
05
Production output
Workflow structure
Sent immediately after checkout is completed.
Layout
Order Confirmation System
Core included
This workflow is part of Core and remains included in Pro. Use it as a starter production system, then move to Pro when recurring lifecycle, transactional, campaign, and newsletter work needs the full archive.
Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.
What the production package needs.
A workflow is useful when the implementation contract is visible before anyone starts editing markup.
order.number
Customer-facing order reference.
order.total_gbp
Order amount charged.
order.manage_url
Destination for tracking and support actions.
Variant routes
- Digital delivery: Replaces shipping blocks with download and access instructions.
- Back-order notice: Adds fulfilment delay messaging with expected dispatch date.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Core archive: MJML source, compiled HTML, preview, and setup guidance for this starter workflow.
- Pro archive: this workflow plus the full recurring workflow set, QA notes, implementation guidance, Studio waitlist priority while Studio is in development, and updates.
Linked production layout
Order Confirmation System
Order confirmation email combining a transaction summary, a small cross-sell row, and a legal close.
Component stack
Header Centred, Order Confirmation Summary, Related Products Row, Footer Privacy Light
Source file
order-confirmation.mjml
QA and handoff.
The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.
QA risks to review
- Order tables can break alignment if product names or SKU strings are unbounded.
- Fallback plain-text links are needed for clients that suppress button styles.
Handoff steps
- Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
- Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
- Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.
Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.
Start with this workflow in Core.
Core is enough when the essential starter workflows solve the immediate implementation. Pro is the upgrade when the same source-to-handoff process becomes recurring work across more sends.