For online stores with a way to read order data

A clear order answer, in your customer’s language.

Connect your order API or WooCommerce read-only REST credentials. Your server verifies the order number and email before returning order or shipping details to the conversation.

Start free trial

Sample data · fictional

Online stores

Customer

¿Dónde está mi pedido DEMO-1042? Mi correo es [email protected].

Read-only tool

get_order({ order_id: "DEMO-1042", email: "[email protected]" }) → 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}
Authentication: Authorization: Bearer {{ORDER_API_SECRET}}
Input mapping: order_id ← input.order_id email ← input.email
Output mapping: status ← $.order.status carrier ← $.shipping.carrier eta ← $.shipping.eta

Example configuration. Use your order API or WooCommerce read-only REST credentials; configure your endpoint and mappings.

The server must validate order_id and email together before returning data. Keep WooCommerce credentials on the server; an AI instruction is not an access check.

Connect the order source you control

Use your own order API, or connect WooCommerce through read-only REST credentials. 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 API you control, or WooCommerce read-only REST credentials with a server endpoint that validates the order number and email together. 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.

Let customers ask. Let AI check your system.

Connect your knowledge and read-only APIs for orders, transfer status, invoices, or plans. Answer in your customer’s language.

Start free trial