Problem-first guide
How to keep customers updated on orders and shipments without doing it by hand
Last updated September 3, 2026
Send customer updates from real order events: confirmation, production or processing change, shipment, delivery exception, and completion. Each message should state what changed, what happens next, and when the customer should expect another update.
Use your commerce or shipping system as the source and automate only messages backed by verified status data. Route delays, address problems, and unclear scans to a person before making a promise.
Or hand it to Pally
Free to start. No app to install.
A practical approach
What to do.
- 01
Map the order events
List the status changes customers actually care about, from accepted order through delivery or pickup. For each event, name the source system, the condition that triggers a message, and the next expected event. Remove internal stages that do not change the customer's plan. Mapping takes a focused setup session, and custom work may have fewer clean events than standard shipping. It prevents vague updates and duplicate messages fired by several systems for the same underlying change.
- 02
Write factual templates
Create one plain template per event with the customer's name, order reference, current status, next step, expected timing when verified, and a working support path. Shipment messages should use the carrier and tracking link supplied by your shipping system. Avoid promising a delivery date when the source shows only an estimate. Templates make communication consistent, while they can sound mechanical. Add a short brand voice without burying the status customers opened the message to find.
- 03
Separate normal and exception flows
Let verified routine events send through the approved automation. Route stalled orders, conflicting statuses, address problems, stock issues, and carrier exceptions to a human queue with the source details attached. Define who owns that queue and when the customer receives an interim update. Human review slows the exceptional message, but it prevents automation from repeating false reassurance. Tell the customer when you are investigating and give the next time they will hear from you.
- 04
Test and audit delivery
Place test orders through every common path and confirm the trigger, recipient, wording, links, time zone, and stop conditions. Check that cancellation or refund prevents later shipment messages. Review failed sends and a sample of successful updates each week, then compare customer replies with the system status. Testing and audits add operational work. They catch silent failures, duplicate notices, and broken tracking links before customers learn that your automated updates cannot be trusted.
The Pally option
The short version: text Pally
Pally is one option for monitoring connected email and messages when customer questions and delivery changes need your attention. It can summarize relevant threads, prepare an update from the available context, and schedule an approved message for later. Customer messages remain under your control because Pally shows you the wording before sending.
Inbox, triaged
Ask what actually needs you. Pally reads the pile, flags the few, and drafts the replies.
See the recipeSay it later
Write it now, land it at the perfect moment: pally sends exactly when you say.
See the recipePackage tracker
Everything you've ordered, watched in one place: out for delivery, running late, or sitting on your porch.
See the recipeOptions
Other tools people use
Fair alternatives, including ones that overlap with Pally.
Shopify
Shopify fits merchants who want customer order notifications driven by the commerce system holding the order status.
Custom production stages and unusual exception handling may need added workflows or personal contact.
ShipStation
ShipStation fits businesses that want shipping operations and customer tracking communication tied closely together.
It cannot explain business-specific delays that happen before a shipment enters the carrier flow.
Zapier
Zapier fits businesses that need to connect order events with a separate email, messaging, or task system.
Multi-system automations require careful testing and can pass along stale or conflicting status data.
Questions
Frequently asked questions.
Which order events deserve a customer message?+
Send an update when the customer's expectation or required action changes. Confirmation, shipment, delay, delivery exception, pickup readiness, cancellation, and refund are common examples.
Should delay messages be automatic?+
Automate a factual notice when the delay status is verified and the next step is known. Route unclear causes, revised promises, refunds, and sensitive customer situations to a person.
How do I prevent duplicate updates?+
Choose one source system and one message owner for each event. Give every order event a unique identifier and test what happens when status data changes twice.
Keep reading
