Order Tracking in ChatGPT and Claude: Answer “Where Is My Order?” with Real Data

“Has my order shipped, and will the two items arrive together?” Answering that question often requires more than a tracking link. A store needs the order record, its shipments, and the latest available carrier information. An MCP-connected app could bring those details into the customer's conversation.

Consider a store that sells home-office supplies. This is an illustrative workflow using an existing commerce service, not a claim that a particular retailer uses Kernel Apps.

Look up the customer's actual order

The customer connects their store account. The app lists recent orders with dates and a short item summary, then lets them choose the relevant one. An order number alone should not grant access to a shipping address or purchase history.

Suppose the selected order contains a desk lamp and a notebook. The commerce service reports that the notebook has shipped while the lamp is still being prepared. The app should show two fulfillment states rather than collapsing the whole order into “shipped.”

Explain what the delivery information means

A carrier may report that a shipping label was created without confirming that it has collected the parcel. Keep those states distinct. Present the latest event and its timestamp, and identify a delivery date as an estimate when that is what the source provides.

If the carrier feed is unavailable, say which order details are known and which tracking details could not be refreshed. Do not turn the absence of a new scan into a confident claim that a parcel is lost or will arrive tomorrow.

Offer an appropriate next step

For the notebook, the app can provide the store's approved tracking link. For the unshipped lamp, it can explain the current fulfillment status and offer a support handoff if the customer needs help.

Changing an address, canceling an order, or arranging a refund introduces a different workflow. Keep those actions separate from tracking. If the store supports an address-change request, show the proposed change and confirm eligibility with the commerce service before reporting success.

Connect only the data this task needs

A useful first release needs customer-scoped order lookup, shipment details, approved tracking URLs, and a support path. It does not need payment-card data or unrestricted access to the customer database.

• Return item and shipment summaries rather than an entire internal order object.
• Avoid displaying full addresses unless the customer needs to review them for a specific action.
• Make the last refresh time visible when the information can be stale.
• Reopen the order after a refresh to confirm the interface reflects the service response.

In an interactive view, separate cards for each shipment make split delivery easier to understand. A text answer can give the same breakdown without implying that every host displays identical UI.

Measure whether customers receive an accurate shipment answer and whether stale-data errors are visible. Any reduction in support volume would need to be measured after release.

For the next step, read the customer support workflow and the private app launch checklist. Kernel Apps broader access is available through the waitlist.