To automate “Where is my order?” emails on Shopify, connect your support inbox to order and tracking information, define what each order status means, and review the resulting replies before enabling automatic sending. When the order cannot be matched or the shipment needs investigation, route the request to a person.
WISMO means “Where is my order?” It includes requests for tracking links, shipping updates, and explanations for delays. These questions look similar, but an unfulfilled order, a newly created label, and a disputed delivery require different answers.
First, make tracking easier to find
Shopify’s order status page gives customers a place to check their shipment after tracking information has been added. Shipment updates depend on the carrier and available tracking data. Make sure your shipping notifications and customer-facing tracking links work before adding another support workflow.
This gives customers a self-service route and makes your email responses more useful. A reply can explain the current situation and point to the appropriate tracking destination rather than merely saying “your order is on its way.”
What information does a WISMO reply need?
- A customer and order match that your team can trust.
- The current fulfillment status and relevant shipment details.
- A tracking link, if available for that shipment.
- Your processing and delivery policies, including business-day definitions.
- An escalation path when the source data does not answer the customer’s question.
Do not assume that every order contains a delivery estimate or that Shopify’s order data contains every carrier scan. If an arrival date is not available, the reply should say what is known and offer an appropriate next step.
Choose a response for each status
| Situation | Reply approach | Review trigger |
|---|---|---|
| Order not fulfilled | Explain the current status and your processing policy. | The order is outside your promised processing window. |
| Tracking label created | Share the link and describe only the available status. | No carrier movement beyond your investigation threshold. |
| Shipment in transit | Share verified tracking information. | Repeated follow-up or an unclear delay. |
| Split shipment | Explain each shipment separately. | Items or tracking details do not match the request. |
| Marked delivered, customer disagrees | Acknowledge the discrepancy and hand over for investigation. | Human review from the start. |
| No reliable order match | Ask for the information needed to locate the order. | Do not reveal order details until verification is sufficient. |
Set up the workflow in five steps
1. Connect your store and support inbox
Confirm that the tool can retrieve the order information you need and reply from the correct support address. Check requested permissions and the actions the integration supports. Reading order information and changing an order are different capabilities.
2. Document your shipping rules
Provide processing times, shipping destinations, delivery estimates, and the point at which your team investigates a delay. Distinguish an estimate from a guarantee. Define what happens on weekends, during preorders, and for products with different dispatch schedules.
3. Define missing-data behavior
Write an explicit instruction for absent tracking, multiple matching orders, and unavailable delivery dates. “Ask for clarification or send to review” is more useful than “always reassure the customer.” A confident-sounding response can still be wrong.
4. Review representative drafts
Test ordinary tracking requests alongside split shipments, address-change requests, repeated complaints, and unmatched orders. Include a customer who asks about two orders in the same message. Compare every draft with the order record and your policy.
5. Enable a narrow automatic category
Begin with the cases that passed review consistently. Keep investigations and uncertain matches with your team. Recheck replies after a shipping-policy change or a carrier disruption. For a broader rollout, use our customer support workflow guide.
Two example WISMO replies
These are templates, not live order updates. Replace every bracketed field with verified information and remove anything that does not apply.
Tracking is available
Hi [first name], I checked order [order number]. The latest available shipment status is [verified status]. You can follow updates here: [tracking link]. [Include a carrier estimate only if one is available, clearly labeled as an estimate.] If the status has not changed by [policy-based follow-up date], reply here and we’ll investigate.
No tracking number yet
Hi [first name], order [order number] is currently [verified fulfillment status], and there is no tracking number available yet. Our processing window for this item is [relevant policy]. [If already overdue: I’m passing this to our team to check the dispatch status.] We’ll share an update when we have confirmed information.
See our Shopify customer service email templates for returns, damaged items, and other common support scenarios.
Measure resolution, not just replies sent
Track the number of WISMO conversations, first-response time, manual review time, incorrect status statements, and repeat contacts about the same order. Count a conversation once when measuring its outcome; several replies do not mean several resolved issues.
Use your pre-automation results as the baseline. An increasing auto-reply rate is only useful if answer quality and customer outcomes hold up. If customers keep asking the same question after a reply, inspect the answer and source data before widening automation.
Using Respondro for Shopify WISMO emails
Respondro uses Shopify order context and your store’s rulebook to draft customer support replies. Its Review Board lets you inspect the conversation and edit the answer. On eligible plans, auto-reply can be enabled with confidence checks and a minimum five-minute send delay.
Book a demo to walk through an order-status workflow and explore the settings for your store.
Frequently asked questions
Should every WISMO email be automated?
No. Ambiguous matches, missing data, delivery disputes, and policy exceptions need a defined review path. Automate only the categories your testing supports.
Can the AI promise an arrival date?
Only communicate a date when an appropriate source supports it, and distinguish an estimate from a guarantee. Do not turn a general shipping window into a specific promise.
Does sending a tracking link resolve the ticket?
Not necessarily. A customer may need an explanation of a delay or help with a delivered-but-missing parcel. Answer the actual question and review follow-up messages.