MyDot Consultancy

Featured image: AI-generated conceptual illustration. Sources checked 26 October 2026.

A tracking event is evidence of a reported shipment state. It is not a promise that the customer will receive the package at a particular time. An order-status agent should preserve that distinction, especially when a user is worried and the available data is incomplete.

The useful workflow connects the customer’s order to the correct shipment, retrieves current evidence and explains what that evidence supports. It should not turn a label creation into carrier possession, an estimate into a guarantee or a missing scan into a declaration that the parcel is lost.

Match the question to the right shipment

Imagine a hypothetical customer whose order contains a desk and two accessories shipped separately. They ask, “Where is my order?” A single tracking number cannot answer the whole question. The agent needs the order’s line items and fulfillment relationships before summarizing progress.

Shopify’s order query documentation describes access to order and fulfillment information. Use the authorized order record to establish which shipments belong to the request. Do not accept a tracking number from an unrelated message as proof that it belongs to the customer.

Verify the requester’s access before showing addresses or shipment details. A status assistant should not become a way to enumerate other customers’ orders. Where the order reference is ambiguous, ask for the minimum additional information needed through an approved verification process.

Read the event history, not just a headline

Shippo’s tracking documentation describes normalized status and tracking history. A useful agent can use both: the latest status provides a summary, while the history helps explain when the last meaningful event occurred.

Preserve the source timestamp and the time the system retrieved the data. “The carrier reported this yesterday” differs from “we checked yesterday.” If a feed is stale, the agent should make that limitation visible rather than presenting an old event as a current observation.

For the hypothetical desk order, the accessories may be delivered while the desk remains in transit. Say that explicitly, with the affected items or shipment references. Avoid a single delivered label for the whole order when only part of it has arrived.

Use a vocabulary that matches the evidence

Distinguish merchant processing, label creation, carrier acceptance, transit, delivery attempt and delivery confirmation according to the actual source fields. Do not invent a universal status mapping without checking the integration’s definitions and carrier coverage.

A label being created may mean shipping information exists; it does not necessarily prove the package has been handed over. A delivery estimate is an estimate. A delivery scan is the carrier’s reported event, not independent proof that the intended person physically received the parcel.

The assistant can explain these distinctions in plain language without sounding evasive. A helpful response identifies the latest verified event, its date, any supplied estimate and the next appropriate step. It should avoid adding unsupported reassurance merely to make the customer feel better.

Separate explanation from intervention

A status query does not automatically authorize an address change, replacement shipment, refund or carrier claim. If the customer wants an intervention, move into the relevant workflow with its own evidence and approval requirements.

For example, a customer reporting nonreceipt after a delivery scan may need a support case. The agent can assemble the order, tracking history and customer statement for review. It should not declare fraud, blame the customer or promise a replacement without the merchant’s policy and authority.

Keep consequential tools unavailable to a read-only status agent unless the product deliberately supports a reviewed escalation. Narrow tool access makes the boundary enforceable even when a customer’s message combines a status question with an urgent demand for compensation.

Handle missing and contradictory data

An unknown tracking result can have several causes: the wrong identifier, unsupported carrier, incomplete registration, delayed data or an unavailable service. The agent should not collapse all of them into “your package has not shipped.” Return the actual limitation and an appropriate route for checking it.

If the commerce system says fulfilled but the tracking feed has no carrier event, preserve both observations. They describe different systems and may not be contradictory in the strict sense. The agent should explain what each establishes and what remains unknown.

When sources genuinely conflict, route the case with timestamps and references. Do not choose the more reassuring answer. A support representative needs the discrepancy, not a smoothed narrative that hides it.

Test communication against a fixed evidence packet

• A label exists but no carrier acceptance event is available.
• One order has multiple shipments in different states.
• The latest scan is old and the feed has not refreshed.
• A delivery estimate changes between checks.
• The carrier reports delivery while the customer reports nonreceipt.
• The tracking service is unavailable or the carrier is unsupported.

For each test, define which claims are permitted and which promises are prohibited. Inspect the final message for unsupported dates, guarantees and assumptions. Also verify that the agent did not call a write tool merely because the user expressed urgency.

Measure the whole support outcome

Track whether the answer resolved the status question, whether staff had to correct it and whether the case required escalation. Include retrieval costs, repeated checks and reviewer effort in the operating model. A short response is not a success if it causes a second contact because it hid a partial shipment.

An agent may add little value when a clear tracking page already answers the question and customers can access it easily. It is more useful when the order has several shipments, the evidence needs explanation or a support handoff requires gathering records. Keep those benefits distinct from claims that the model can predict delivery better than the available data.

The best order-status agent is precise about what is known and useful about what to do next. It connects scans to the correct items, preserves uncertainty and leaves commitments to the systems and people authorized to make them.

Sources and further reading

Shopify: order query. Order and fulfillment lookup documentation; checked October 26, 2026.

Shippo: Tracking. Normalized tracking status and history; checked October 26, 2026. Workflow interpretation is editorial guidance.