Post-Purchase Message Template: Follow the Order Status

Post-purchase messages go wrong when the marketing calendar ignores the order. A review request may arrive before delivery, or an offer may interrupt an unresolved complaint.

Start with the latest order and service information. Then choose one job for the message: confirm, update, help, request feedback, or make a later offer.

Copy the post-purchase message record

Order and customer ID:
Contact channel and permission:
Current order, delivery, return, and support status:
Source checked and time checked:
Message job: [confirm | update | help | feedback | later offer]
Facts allowed in the message:
Message:
Help owner and context to pass:
Messages to pause:
When to stop pending messages:
What to do when information or delivery fails:
Proof of completion and review owner:

Estimated completion time: 15–20 minutes once the team knows where to check the order and service case. Copy the record into a document, CRM note, or spreadsheet and fill every line before configuring automation.

Field guidance

  • Link one stable order/customer identity to its permitted contact route.
  • Use current order, shipment, delivery, return and service records; the latest consequential state wins.
  • Store the verified source and timestamp so stale tracking cannot be repeated as current.
  • Give each message one job and allowlist its exact facts, instructions and source versions.
  • Name the help owner and the context included in handoff.
  • Let complaint, return, delivery exception or failed use override feedback and commercial messaging.
  • Define exit, failure fallback, completion evidence and a measurable QA sample.

Shopify documents customer-visible order status and tracking mechanisms. Treat this as a vendor state-model reference, not proof of another platform's feature or delivery performance. Review the source.

Fictional filled example: delayed shipment

Order and customer ID: Fictional order O-908 and customer C-31
Contact channel and permission: Email allowed for order updates
Current order, delivery, return, and support status: Carrier reports a delay; not delivered; no return; fictional service case S-44 is open
Source checked and time checked: Current order and carrier events checked 15 August 2026 at 14:00 ICT
Message job: Update and help
Facts allowed in the message: Order ID, checked delay, unavailable delivery date, case ID, and owner-approved next-update time
Message: “Order O-908 is delayed. The current tracking page shows no delivery date. Case S-44 is open; next update by 18:00 ICT.”
Help owner and context to pass: Ecommerce service inbox receives the order, carrier event, prior promise, and customer messages
Messages to pause: Review request and product recommendations until delivery is confirmed and S-44 is closed
When to stop pending messages: New carrier event, owner update, cancellation or refund, invalid contact, or customer reply
What to do when information or delivery fails: State that tracking is unavailable; stop; send the record to the service owner
Proof of completion and review owner: Update sent and next-update promise saved; ecommerce service checks missed or contradictory updates weekly

The exception is missing tracking information. The record tells the team to say what is unknown and hand the case to a person instead of repeating stale information.

Quality checklist

  • Order identity and contact permission match the source record.
  • The newest consequential state is used with a visible timestamp.
  • Approved fields match one message job.
  • Service exceptions suppress feedback and commercial actions.
  • Reply, return, refund and state change cancel stale sends.
  • Applicable sender controls are tested; Google's guidance does not replace legal review.

Common mistakes and controls

Mistake Control
Asking for a review before delivery Gate feedback on confirmed delivery and no open issue
Hiding an exception behind promotional copy Give service state priority over commercial messaging
Repeating stale tracking Check source timestamp and say when status is unavailable
Splitting one order across owners Use one current service owner and traceable case

Frequently asked questions

When should product-use guidance be sent?

Only after the relevant delivery/use state is confirmed and the guidance matches the purchased item and current approved instructions. Do not assume the customer has received or opened it.

Should feedback and cross-sell share a message?

Usually separate them. Feedback asks about completed experience; a commercial recommendation creates another job and may be inappropriate during an unresolved issue.

What if tracking data conflicts?

Do not choose the more optimistic source. Show the uncertainty, preserve both timestamps, and route to the fulfilment owner.

Which metrics matter?

Track state accuracy, conflicting messages, promise adherence, service handoff, premature feedback/commercial sends, complaints and opt-outs.

What to do next

Define the conditions under which a resolved order becomes eligible for the customer feedback request workflow or a separate recommendation workflow.

Evidence and limitations

This template does not guarantee delivery, retention or repeat purchase and does not claim an Easy AI integration or capability.

FAQ

Recommended for you