Goal
Reduce where-is-my-order contacts with precise, timely status updates.
Template Hedgehog
Open navigation
Shipping update
Keep customers informed on fulfilment progress with clear tracking and status context.
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 when parcel status changes after dispatch.
Layout
Shipping Notification System
Pro archive
This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.
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.
shipment.tracking_number
Carrier tracking reference.
shipment.status_label
Current fulfilment status.
shipment.track_url
Carrier or branded tracking destination.
Variant routes
- Delivery delayed: Adjusted copy for weather, customs, or carrier delays.
- Delivered confirmation: Final state variant with support route for missing parcels.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Full MJML source for this workflow
- Compiled HTML output ready for ESP upload
- Variant-ready workflow pack files
- Versioned workflow updates inside Template Hedgehog Pro
Linked production layout
Shipping Notification System
Shipping update email combining tracking context, support links, and a clean legal footer.
Component stack
Header Centred, Shipping Notification Tracker, Support Links Light, Footer Privacy Light
Source file
shipping-notification.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
- Carrier status text can exceed expected length and wrap unpredictably on mobile.
- Track URL integrity must be checked after ESP link wrapping.
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.
Use this workflow inside Pro.
Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.