AI order status lookup, connected to your own API.
Help customers check order and shipping status in their language. Connect a read-only order endpoint you control that validates the order number and email together before returning data. On WooCommerce, add a small endpoint on your server using read-only REST credentials.
¿Dónde está mi pedido DEMO-1042? Mi correo es ana@example.com.
Read-only order lookup · configured endpoint required
get_order({ order_id: "DEMO-1042", email: "ana@example.com" }) → status: "en tránsito", carrier: "Transportista Demo", eta: "2–3 días hábiles"
AI reply
Tu pedido está en tránsito con Transportista Demo. La fecha estimada en el sistema es dentro de 2–3 días hábiles.
Your server must validate the order number and email together. Platform embedding does not grant order access.
An order lookup with server-side checks
Tool name
get_order
Description
Read status, carrier, and estimated arrival only after validating the order number and email.
Endpoint URL
GET https://api.example.com/verified-orders/{order_id}?email={email}
Authentication
Authorization
Input mapping
order_id ← input.order_id
email ← input.email
Output mapping
status ← order.status
carrier ← shipping.carrier
eta ← shipping.eta
Example configuration. Point it at an order endpoint you control; on WooCommerce, a small endpoint on your server with read-only REST credentials. Configure the endpoint and mappings.
The server must validate order_id and email together before returning data. Keep WooCommerce credentials on your server; an AI instruction is not an access check.
Connect the order source you control
Use your own order API. On WooCommerce, add a small endpoint on your server that reads orders with read-only REST credentials; don't point the tool at the WooCommerce REST API directly, because it does not check the email. Configure the endpoint and field mapping for the data you need. This requires setup; it is not a native platform connector.
Check the order number and email on the server
Your endpoint must require and validate both the order number and the customer’s email before returning any order data. Enforce this on the server, not through instructions to the AI. Keep REST credentials on the server.
Explain the status across languages
Retrieve status, carrier, and estimated arrival from your connected source. Answer in the customer’s language and distinguish an estimate from a confirmed delivery. Use your knowledge base for store policies.
Embed the conversation; connect data separately
You can embed the widget on Shopify or Nuvemshop, but embedding does not grant automatic order access. Platform connectors are future work. Requests to change an order go to your team; tools stay read-only.
Questions before you connect
What do I need to query orders?
An order endpoint you control that validates the order number and email together. On WooCommerce, a small endpoint on your server that uses read-only REST credentials. Configure authentication and return only the order fields needed for the answer.
Does embedding on Shopify or Nuvemshop enable order lookup?
No. The embed snippet adds the conversation interface. It does not read platform orders. Native platform connectors are future work; order lookup needs a separately configured data source.
Can a customer look up an order with just its number?
Your server must reject that request. Both the order number and email must be validated before data is returned. An AI prompt alone does not enforce this boundary.
Can AI change or refund an order?
No. Version one only reads order and shipping information. Requests needing a change can be handed to your team with the conversation context.
Every customer answered in their own language. Your team steps in when needed.
Connect your knowledge base: AI answers in your customer's language and hands off to your team when needed.
