Right after "buy it" comes "where is it?"
Anyone who has bought something online knows this. The moment the order is placed, attention shifts to the delivery. If an agent placed that order for you, it should be able to answer, and answer accurately.
Order tracking for AI agents isn't a bonus feature. It's part of the product.
Why order status is part of the product
An agent that can buy but can't follow up leaves people hanging. They'd have to leave the conversation, find an email, open a page and read it themselves. That defeats the point of having an assistant.
There's also a trust issue. If an agent guesses at a delivery date, and it's wrong, the person stops believing it. A status an agent can read and repeat is worth more than a confident guess.
What the agent can read
JENNi's MCP server includes get_order_status. It needs the private order token from the shopper's JENNi order page, so only someone with that token can look the order up.
It returns:
- Status: one of
placed,processing,out_for_delivery,delivered,needs_attentionorcancelled. - ETA, when it's known.
- Courier tracking.
- Whether the card was charged.
That last field is easy to overlook and often the one people care about. "Did you charge me?" is a very common question, and the agent can answer it from the order itself.
What an agent can say at each stage
The statuses map to plain sentences.
- placed: "Your order is in."
- processing: "JENNi is working on your order. I'll check again for the next step."
- out_for_delivery: "It's on its way. Here's the ETA and tracking."
- delivered: "It's been delivered."
- needs_attention: "Something needs a closer look. JENNi is the seller and handles issues, so I'll point you to your order page."
- cancelled: "This order was cancelled. Here's whether your card was charged."
The agent doesn't need to invent anything. It reads the field and says what it means. If the ETA isn't known, it says that instead of making one up.
Same day versus shipped
Orders move differently depending on how they're fulfilled.
A local delivery can arrive the same day, but only when the quote said "Get it today". A shipped order takes the time shipping takes. In both cases the status field is the source of truth, not an assumption from when the order was placed.
An agent should avoid promising a date it was never given. It can repeat the delivery promise from the quote, and then use the live status and ETA from get_order_status as the order moves.
Keeping people informed without making them check
The best update is the one a person doesn't have to ask for.
For builders, that suggests a simple habit. When a person asks about their order, call get_order_status and answer from the result. Keep the answer short: where it is, when it's expected, and whether the card was charged. If the status is needs_attention, say so early and send them to their order page.
You can also set expectations at the time of purchase. Tell the person what the delivery promise was, and that you can check on it whenever they want.
A note for shoppers
You don't need an agent to follow your order. After you buy at shop.jennipro.com, your JENNi order page shows where things stand. The private order token that lets an agent look up your order comes from that same page, so you stay in control of who can check on it.
If you'd like an assistant to keep an eye on an order for you, you can share the token with it. If you'd rather not, the order page is always there.
Build on it
Connect to JENNi's MCP server at https://shop.jennipro.com/mcp. Shoppers can follow their orders from the order page after buying at shop.jennipro.com.