Can AI Answer Where Is My Order on WhatsApp in 2026?

Roughly the same message arrives every day, in a dozen spellings. "Where is my order." "Any update on my parcel." "Wein el order?" It is the highest volume question in commerce, it carries no new information, and somebody on your team is typing the answer by hand while a customer with money in their hand waits behind it in the queue.

Order status is the one customer question that automates cleanly, because the answer already exists inside your store and only needs fetching. Three things have to be true. Your store has to emit the event: Shopify fires fulfillments/create, fulfillments/update and orders/fulfilled webhooks carrying the tracking number, so the status is available the moment it changes. The message has to be matched to the right customer, which means the phone number on the order and the number in the chat agree, or the customer gives you an order number to look up. And the reply has to fit Meta's rules. A reply sent inside the 24 hour customer service window needs no template and costs nothing. A status update you send first is a utility template that must be approved in advance, and since 1 July 2025 utility templates sent inside an open window are free. Answer fast and the answer is usually free.

"Where is my order" is three questions wearing one coat

The same seven words mean different things depending on when they arrive, and an automation that returns one canned reply to all three feels broken even when the data is correct.

The first two automate completely. The third automates partially, because most couriers give you a status and a scan location, not a promise. The fourth should never be automated, and the useful design decision is making sure it reaches a person quickly instead of looping the customer through the same status line a third time.

What your store has to hand over

On Shopify the plumbing is the easy part, and it is worth knowing the shape of it before you buy anything.

Shopify exposes webhook topics including fulfillments/create, fulfillments/update and orders/fulfilled. When a fulfilment is created with a tracking number, Shopify can resolve the tracking company and tracking URL automatically from the number format. That gives you a push event rather than a polling loop, which is the difference between a reply that arrives in two seconds and one that arrives when a cron job next runs.

There is one limit that catches people. A Shopify fulfilment carries a single tracking number. If an order ships in two boxes, that is two fulfilments, two tracking numbers and two events, while the customer is still thinking about one order. Any automation you build has to decide what to say when an order is half shipped, because "your order is on its way" is a lie the customer will discover at the door. Say two of three items shipped, and name the ones still coming.

WooCommerce, Salla and Zid all expose comparable order and shipment events. The pattern is the same everywhere: the store knows, the courier knows, and the customer is the last to find out.

What it costs to answer, honestly

This is where most order status projects get their budget wrong, in both directions.

Meta bills per message delivered, not per conversation, since 1 July 2025. Two rules matter more than the rate card:

• Service messages are free. When a customer messages you, a 24 hour customer service window opens. Replies inside that window are not templates and Meta does not charge for them. A customer asking "where is my order" has just opened that window themselves.
• Utility templates sent inside an open customer service window are free too, as of 1 July 2025. Sent outside a window, they are charged at the utility rate for the recipient's country.

So a reactive answer costs nothing. A proactive shipping notification, the one you send at three in the afternoon when the courier scans the parcel, costs the utility rate, because no window is open. That is still usually the better trade, since the notification you send prevents the question you would otherwise answer, but price it deliberately rather than by accident.

Rates move, and they move regionally. Meta's 1 August 2026 pricing update raised utility and authentication rates in several markets including Kuwait, Morocco and Oman, and a further update to service and utility pricing is scheduled for 1 October 2026. Check the current rate card for your markets before you model anything, and read our breakdown of what the WhatsApp Business API really costs for the four line items nobody warns you about.

A rough shape of the trade

For a store shipping 600 orders a month, the arithmetic below is an illustration of the structure of the cost, not a benchmark. Put your own volumes and your own market rate into it.

The middle row is where most commerce brands land. The third row earns its keep for high value or fragile goods and irritates everybody else.

Where this breaks in the Gulf and the Levant

Three regional realities decide whether the automation feels premium or feels cheap.

Courier data quality. A tracking number from a regional carrier is not always machine readable, and last mile subcontracting means the scan you receive can be hours behind the driver. If you cannot get a reliable status, say what you do know and the time you knew it, rather than inventing precision you do not have.

Cash on delivery changes the question. For a customer paying cash, "where is my order" is often really "when do I need to have the money ready and be at home". A status line that ignores the amount due answers the wrong question. Include the amount and the expected day.

The message will not arrive in clean English. Real inbound is dialect, Arabizi and code switching, sometimes in one sentence. A system that only parses English and Modern Standard Arabic will treat "wein sar el order tabaee" as noise and hand it to a human, which puts you back where you started. We go through this properly in does AI customer service really work in Arabic.

What to do this week

1. Pull last month's WhatsApp messages and count how many were tracking questions. That number is the size of the prize, and it is usually larger than anyone guesses.
2. Check whether your store actually emits a fulfilment event with a usable tracking number today. If fulfilments are marked by hand at the end of the day, fix that before buying any automation, because no tool can send an event that never fires.
3. Write the three replies by hand: order received, order shipped, order half shipped. If you cannot write the half shipped one clearly, your automation cannot either.
4. Decide your escalation rule now. Ours is simple: after the promised delivery date, a tracking question goes to a person, not to a status lookup.

Answering "where is my order" is not a chatbot problem, it is a data plumbing problem with a conversation on the end of it. plum is the AI that sells on WhatsApp, and it reads your store so tracking questions get answered in the same thread where the next sale happens. See how it works, or start with how to automate WhatsApp for your business.