Order Status Chatbot: Answers "Where's My Order?" Without Showing Anyone Else's
In short: "Where's my order?" isn't answered on any page of your store. BotChata answers it in two ways. Order status from your store (Shopify, WooCommerce, Magento, PrestaShop) is shown only after the shopper gives the order number and the phone or email on that order. Carrier tracking (UPS, DHL and others) works from the tracking number. Both are on the Base plan, $39/mo.
A use case of AI chatbot for your website. The wider picture for stores: AI chatbot for e-commerce.
Two questions, two sources
A shopper who types "where's my order" can mean two different things. That decides where the bot gets its answer.
| What the shopper types | Where the answer comes from | Plan |
|---|---|---|
| "How long does shipping take?", "Do you ship to Canada?" | your store's pages | any, including free |
| "1Z999AA10123456784 — when will it arrive?" | the carrier's API, by tracking number | Base, $39/mo |
| "What's happening with order #1042?" | your store: Shopify, WooCommerce, Magento, PrestaShop | Base, $39/mo |
If both your store and a carrier are connected, a tracking number goes to the carrier and an order number goes to the store.
BotChata also does this on Shoper and Horoshop, which are covered on our Polish and Ukrainian pages. This page sticks to the four platforms above.
How the bot looks up an order: six steps
This is the part almost nobody documents. Every check is done by BotChata's code, not by the language model.
- The question goes to your store, not to product search. If a message has "order", "package" or "shipment" plus "where", "status", "tracking" or "number", BotChata forces the store's order tool. So "1042" is never read as a product name.
- No number? The bot asks for one. The tool hands the bot an instruction instead of data: ask for the order number first.
- Number but no contact? The bot asks for the phone or email used on the order. Without a contact, no request goes to your store at all.
- The check. Phone numbers are compared on their last 9 digits, so a country code or a leading zero makes no difference. Emails are compared case-insensitively. Under 7 digits never matches, and neither do placeholders like
0000000000— guests type those into required fields, and without this rule such orders would be open to anyone. - Match. The bot gets a short summary: status, whether it's paid, total, shipping method, tracking number if the order has one, and the items with quantities (the exact fields depend on the platform, see the table below). Name, address, phone and email are not in the summary at all. Proving you know one contact is no reason to be read the rest.
- No match. The bot gets one sentence: the contact doesn't match, reveal nothing. The model never had the order data, so there's nothing to talk it out of.
Why so strict. Order numbers run in sequence: 1041, 1042, 1043. If the bot gave out status by number alone, anyone could walk a hundred numbers and read other people's purchases. A number is easy to guess; a shopper's phone or email isn't.
What the bot sees on each platform
| Shopify | WooCommerce | Magento | PrestaShop | |
|---|---|---|---|---|
| Number it looks up | #1001 — found from "1001" or "#1001" | the order number, including a numbering plugin's prefix (BC-1042 = bc-1042) | 000000123 — also from "123"; prefixes on multi-store | 9-letter reference (XKBKNABJK) or the numeric ID |
| Contacts checked | email and phone on the order, the customer and the addresses | billing email and phone, shipping phone | customer email; email and phone on billing and shipping addresses | customer email; phones on delivery and invoice addresses |
| Status | payment + fulfillment + carrier event (in transit, delivered) | WooCommerce status (processing, completed, on hold…) | status code (pending, processing, complete…) | status name in the order's language; paid / shipped |
| Tracking | carrier, number and tracking link from the fulfillment | only with Shipment Tracking or the free Advanced Shipment Tracking | tracking numbers from the order's shipments | tracking numbers per carrier on the order |
| Watch out for | orders from the last 60 days are visible | another tracking plugin = order without a tracking number | the token needs orders and shipments rights (below) | the webservice key needs order rights (below) |
Magento returns a code, not your label. Magento's REST API gives the status code, not the label you set in the admin. The bot gets processing, not "Picking at the Dallas warehouse". For configurable products the variant is in the item name ("Linen tee Blue", not "Linen tee").
Magento: the token. An integration token (System → Integrations) only works if Stores → Configuration → Services → OAuth has "Allow OAuth Access Tokens to be used as standalone Bearer tokens" set to Yes. With it off, Magento refuses every call with the same message it uses for missing permissions, so the two look identical. Orders need Sales → Operations → Orders → Actions → View; tracking numbers also need Shipments. Without Shipments the status still comes through, with tracking marked unknown rather than as an empty list that would read like "not shipped yet".
PrestaShop: your product-search key usually isn't enough. A webservice key made for product search normally has products only. Order status needs read (GET) access to orders, customers, addresses, order_states, currencies, carriers, order_carriers. Without orders, customers or addresses the shopper hears "temporarily unavailable". Without the others the answer still comes, but without the status, currency, carrier or tracking number. The "Test connection" button checks product search only, so it won't flag missing order rights.
PrestaShop split carts. One cart shipped by two carriers is two orders sharing one reference. The bot shows both shipments — but only if the contact matches in each of them.
Carrier tracking: what the bot sees
Add your UPS, FedEx or DHL API credentials and the bot checks a shipment by its tracking number. The answer is the carrier's public tracking, by number — per the carrier's API documentation, the carrier answers every API account alike, not with a shipper's view. That's why the bot doesn't ask for a phone number with a tracking number.
- UPS and FedEx use OAuth client credentials; BotChata exchanges and refreshes the token itself.
- DHL, DPD, GLS and InPost also track by number, on Base.
- USPS, Royal Mail and Canada Post aren't integrated.
What the bot doesn't do
- It doesn't change orders. No cancelling, no address changes, no reshipping. The integration only reads.
- It doesn't give status without the check — not even to "it's my order, just tell me".
- It has no delivery dates of its own. The summary contains only the dates your store or the carrier returned.
- Shopper needs an address change? On Business the bot can hand the conversation, with its history, to a person on your team via Telegram.
How to set it up
- Put the bot on your site with one script tag. It answers shipping and returns questions from your pages straight away (any plan). Step-by-step: Shopify, WooCommerce.
- Functionality → Integrations, pick the card:
- Shopify — store domain → "Connect" → approve access in Shopify;
- WooCommerce — REST API keys with Read permission (WooCommerce → Settings → Advanced → REST API), or the automatic connect button on the card;
- Magento — store URL and an integration token with the rights above;
- PrestaShop — store URL and a webservice key with the rights above;
- UPS / FedEx — client ID and secret from developer.ups.com / developer.fedex.com; DHL — API key from developer.dhl.com.
- Test it on yourself. Place a test order with your own phone number and ask the bot twice: with the right number and with someone else's. The second attempt should end in a refusal with no order details.
Answers from your site — free forever. Carrier tracking and order status from your store — from Base, $39/mo. Pricing · Integrations guide.