Still with the warehouse
The order could still be waiting because:
- an item is backordered
- stock is being transferred
- the order is waiting for consolidation
- fulfillment has not started
Ecommerce & online retail / Order visibility
Tell customers what is happening, not just what tracking says.
After checkout, customers want certainty. A useful response should identify the order’s current state, explain what that state means, and make clear whether the customer needs to do anything next.
ORDER VIEW
ILLUSTRATIVE WORKFLOWONE CHECKOUTSeveral possible order states
ORDER CONTEXTStore / fulfillmentPayment · stock · packing
Carrier / shipmentIn transit · delay · customsCURRENT
Customer checkpointDelivery · pickup · next step
Read the operational state first, then explain what happens next.
THE CUSTOMER QUESTION“Where is my order?” can mean very different things.
Start with the actual state
One order can have several different stories.
The first job is to identify what is happening before explaining it. Connected order, fulfillment, and carrier data can provide that context.
ORDER RECORDWHAT THE CUSTOMER SEES DEPENDS ON THE STAGE
- 01Payment accepted but not yet fulfilled STATUS TYPE
- 02Item waiting for stock
- 03Order being packed
- 04Partially shipped
- 05Handed to the carrier STATUS TYPE
- 06Delayed in transit
- 07Held in customs
- 08Ready for pickup
- 09Marked delivered STATUS TYPE
- 10Split across several shipments
When identification details are required, AI Form can collect the necessary order information first.AI FORM
The useful answer
A strong order answer has three parts.
01Current stateWhat is happening right now?
02MeaningIs this normal, delayed, blocked, or incomplete?
03Next checkpointWhen should the customer expect the next update, delivery, pickup readiness, or intervention?
AI Answer can turn operational status data into a response built around those three questions.
Status context + store policy
FOLLOW THE FAILURE POINT
Exception handling should follow the failure point.
The AI agent should interpret the problem at the correct stage instead of treating every delivery question as one generic support case.
SITUATIONWHAT THE CUSTOMER NEEDS
Not yet shippedFulfillment status and expected dispatch
Carrier delayRevised delivery expectation
Split shipmentWhich items are in each package
Tracking stalledWhether the normal window has been exceeded
Marked deliveredStore-specific missing-delivery steps
Address problemWhether the shipment can still be changed
Pickup orderPreparation or collection status
International shipmentCustoms or handoff context
Know where the delay began
Fulfillment delay and carrier delay are not the same.
A customer may see “delayed,” but the reason matters. Order data tells the agent where the delay occurred.
Already with the carrier
The shipment has left fulfillment and is moving more slowly than expected.
Explain the revised delivery expectation.
One checkout · multiple packages
Split orders need a shipment-level view.
A customer who receives two of three items may think something is missing when the final item is still moving through a separate fulfillment path.
The AI agent can break the order down by item, shipment, warehouse, carrier, and delivery estimate. This prevents normal split fulfillment from becoming an unnecessary missing-item case.
SHIPMENT DETAILORDER VIEW
01ItemWhich item is in each package
02ShipmentEach separate fulfillment path
03WarehouseWhere a package is being handled
04CarrierWho has the shipment now
05Delivery estimateWhen each package is expected
Fulfillment changes the meaning
Different fulfillment models change what “status” means.
The AI agent should interpret the fulfillment model before explaining status.
Store pickup
The key question is usually whether the order is being prepared or ready for collection.
Preorder
The useful date may be release or fulfillment timing rather than carrier tracking.
Dropshipped item
The merchant may need to explain a supplier-controlled shipment separately from its own warehouse orders.
International delivery
Customs, cross-border handoffs, or local-carrier transfer may create status events that do not appear in domestic delivery.
From explanation to action
Policy determines when a delay becomes an action.
Order data explains what happened. Store policy determines when the business should intervene.
Order dataStore policyNext step
POLICY CAN COVER
Lost-package thresholdsAddress changesCarrier claimsDelivery investigationsReplacementsRefundsPickup expiration
That allows the AI agent to distinguish between “wait for the next scan” and “this now requires action.”
Escalation at the exception boundary
Routine status questions do not need a person.
Cases that may require Human Handoff include refund or replacement approval, carrier dispute, fraud concern, manual address intervention, unresolved delivered-not-received claim, or repeated fulfillment failure.
HANDOFF CARRIESOrder stateShipment detailsWhat has already been explained
AskHandle building blocks
Components for this workflow.
AI Form
Collect the necessary order information first when identification details are required.
Data Search
Retrieve connected order, fulfillment, and carrier data to identify the real state.
AI Answer
Turn operational status data into an answer about the current state, its meaning, and the next checkpoint.
Doc Search or Data Search
Provide store rules around lost-package thresholds, address changes, carrier claims, delivery investigations, replacements, refunds, and pickup expiration.
Human Handoff
Route cases that need approval or intervention with the order state, shipment details, and explanation already attached.
Practical questions
Order status & delivery support.
Can the AI agent look up a specific order?
Yes, when order data is available through a connected system or API.
Can it explain delivery delays?
Yes. It can use fulfillment and tracking information to explain where the delay occurred and what the current expectation is.
Can it handle split shipments?
Yes. Shipment-level data can be used to explain which items have arrived and which are still moving separately.
Can it support pickup and preorder orders?
Yes. The response can follow the fulfillment model rather than assuming every order is a standard carrier shipment.
What happens when a delivery issue needs intervention?
The conversation can move to Human Handoff with the order and exception context already attached.
Reserve human attention for orders that need a decision.
Order visibility is not only a customer-experience problem. Clearer automated handling can help an online retailer.
- Reduce repetitive “where is my order?” contacts
- Distinguish normal fulfillment from real exceptions
- Prevent split shipments from becoming false missing-item cases
- Explain delays with more precision
- Apply store policy at the correct point
- Send only intervention-ready cases to staff