01
Describe the task
Interpret a supplied order and shipping record, then write a precise status update without filling gaps with assumptions.
Operate any store · Orders
Explain order and shipping status clearly
Translate a messy order record into a customer update that says what happened and what comes next.
The workflow
Bring the truth. Make the next move clear.
02
Provide the working context
- The copied order, fulfillment, and tracking events in chronological order
- The relevant shipping, cancellation, or refund policy text
- Any action already taken by the customer or support team
03
Review how Claude handles it
- Builds a clean timeline from the supplied events and highlights missing timestamps
- Distinguishes store processing, carrier movement, and unverified delay causes
- Drafts the update in plain language with the next concrete checkpoint
- Explains refund eligibility only from the supplied policy and marks uncertain cases
What you get
A fact-checked order update, delay explanation, or refund-eligibility draft for an agent to approve.
Before you run it
Questions for this workflow
Can Claude explain a delayed order from a pasted tracking record?
Yes. Claude can arrange the pasted events into a readable timeline, identify the last verified scan, and draft the next update. It should not state why a carrier is delayed or promise a delivery date unless that information appears in the record you supplied.
What context should I provide first?
Start with the copied order, fulfillment, and tracking events in chronological order. Then add the relevant shipping, cancellation, or refund policy text. Keep the source material current, remove sensitive information that is not needed, and tell Claude which facts are verified so gaps remain visible instead of being filled by assumption.
What should I review before acting on the result?
Review the source facts, assumptions, calculations, and any marked gaps behind this deliverable: A fact-checked order update, delay explanation, or refund-eligibility draft for an agent to approve. Compare it with the live system or responsible teammate, and check before approving any action.
Keep moving
Related use cases
Setup
Connect Claude to the store you already run
Give Claude a trustworthy view of your store without changing platforms or pretending every stack has a connector.
Run this workflow
Product content
Turn one product truth into channel-ready copy
Build distinct product copy for each selling surface from one approved set of facts.
Run this workflow
Reporting
Build a weekly store performance brief
Convert the numbers you already review into a short operating brief with clear follow-ups.
Run this workflow