Let customers ask "where is my order" on WooCommerce, safely
Customers ask "where is my order" because it's urgent and obvious. If you let them check status on your site (via a chatbot or widget), you cut support volume and speed up answers. Done wrong, it exposes personal data and creates fraud risk. This guide gives a practical, step‑by‑step implementation for WooCommerce: what to allow, what to hide, and how to test it.
Design goals (short)
- Answer order status without exposing sensitive data.
- Require the order number and exact billing email before returning details.
- Keep the store integration read‑only and auditable.
- Provide a smooth handoff to human support for anything sensitive.
What to allow the chatbot to say
Limit responses to:
- Order status (processing, shipped, completed, refunded).
- The order date, total, currency, and items when the integration provides them.
- A tracking link only when a separate, trusted source actually provides it.
Do not return:
- Shipping and billing addresses.
- Full billing information or payment card details.
- Internal notes, gift messages, or staff comments.
- Anything that would let someone impersonate the buyer.
Check the order number and email before showing details
For the WordPress plugin described here, the customer must supply both the order number and the exact billing email. The order feed compares the email with the order's billing email and gives the same not-found response for an absent order or a mismatch. This reduces the information an attacker can learn from guessing.
The matching email is a lookup check, not proof that the visitor controls that mailbox. Keep the returned fields limited, avoid addresses and payment details, and offer human support when a lookup fails. A merchant needing stronger identity assurance should design an authenticated or one-time-code flow separately; the plugin does not claim to provide either.
Use read‑only access to WooCommerce
With the SuperBot WordPress plugin, install and activate it, copy your Site ID from the dashboard's Setup Guide, then enable the widget in WordPress. For WooCommerce-aware answers, copy the private Store metadata, Products and Orders feed URLs from the plugin settings into Dashboard → Settings → AI Connect. Those endpoints read store data; they do not change orders or stock. You do not need to create a separate WooCommerce REST API key for this plugin.
Keep the feed URLs private because they contain a site-specific token. If one leaks, rotate the token in WordPress and update the URLs in the dashboard. The endpoint can also accept the token in an X-Superbot-Token header, which avoids placing it in a query string in access logs. Verify the connection and its permissions before going live.
Redaction rules to apply
The plugin's order feed returns order number, status, date, total, currency and item names, SKUs and quantities after a match. It does not return the billing email, addresses, payment details or internal notes. Design the chat answer around those actual fields. If you add tracking data from another service, review that service's access and response fields separately.
Test a failed lookup as carefully as a successful one. A wrong email should not reveal whether the order number exists.
Prevent automated abuse
Bots can try to guess email and order-number pairs. The plugin limits failed order lookups per IP and returns a rate-limit response after too many misses. Test that limit in a controlled environment. Review your own web server and security tooling for broader abuse monitoring; the plugin does not promise CAPTCHA, per-device limits or support alerts.
Fallback to human handoff and transcript
Not every question can be answered automatically. Provide a smooth transfer:
- Offer a "Contact support" button that opens a shared team inbox with full transcript.
- Keep the relevant chat transcript available to the agent without repeating private details in a public reply.
- Let agents take over the conversation in the same thread — no need to force the customer into email.
A shared inbox and full transcript help agents resolve complex cases faster and avoid repeating questions.
Implementation checklist for WooCommerce (concrete steps)
- Install the official plugin on a WordPress site with WooCommerce active.
- Add the Site ID, enable the widget, and connect the private feed URLs in AI Connect.
- Configure order lookup flow:
- Ask for the customer-facing order number and billing email.
- Show order data only if both match.
- Check that responses include only the fields listed above.
- Check the plugin's failed-lookup rate limit.
- Configure human handoff: shared inbox, transcript capture, and a clear escalation button for agents.
- Update your privacy policy and help centre with how chat handles personal data and retention.
- Test with test orders, a wrong email, an absent order, and repeated failed lookups.
What to test before you go live
- End‑to‑end lookup with a test order and its exact billing email.
- A customer-facing sequential order number, if your store uses one.
- Lookup with wrong email (should not return order).
- Repeated failed lookups from the same IP (should eventually be rate limited).
- Response check: customer-facing text does not include addresses or payment data.
- Human handoff: transcript searchable in the agent inbox.
Measure these outcomes: successful self‑service rate, time to first response for handoffs, and any incorrect disclosures found in audit logs.
Measuring success and iterating
Track these metrics:
- Resolution rate: percent of "where is my order" requests resolved by the bot.
- Escalation volume: how many required a human.
- CSAT or quick thumbs up/down at the end of the chat.
- Knowledge gaps: common queries the bot failed to answer so you can add answers to your help centre.
If you have analytics in your support tool, watch for repeat requests about the same order — that indicates the bot's information is unclear or the tracking data is stale.
Example short conversation flow
Bot: "I can check the current status. What are the order number and billing email?" Customer: "[order number] and [email]" Bot: "The order is processing. Would you like to contact support about it?"
Keep answers short and action oriented.
Vendor notes
If you evaluate prebuilt chat agents, confirm they:
- Use read‑only WooCommerce access.
- Check order lookups against the matching billing email.
- Provide shared inbox and transcript for human handoff.
The plugin provides the read-only WooCommerce feed described here. Verify its current listing and test the flow on your own store before using it with customer orders.
What to do this week
- Install the plugin and connect its private feed URLs through AI Connect.
- Draft the order-number and exact-billing-email question for customers.
- Test the response fields and the failed-lookup limit.
- Run a correct match, a wrong-email lookup, and a human handoff with test orders.
- Add a short privacy note to your help centre explaining chat order lookups.
