AI Customer Service for WooCommerce, Magento, Custom Stores
An AI customer service agent does not depend on Shopify. It depends on six pieces of data that every online store holds, whatever it is built on. Our production deployment reads them from nine Shopify storefronts; this page lists the six, and how a WooCommerce, Magento, BigCommerce or custom-built store exposes each one. If your store can answer these six questions through an API, the agent can do the work described in our case study.
The six things the agent reads
- An order, by order number. Items, quantities, amounts, payment status, the shipping address.
- Orders, by customer email. Customers write without their order number. The agent searches by the email used at checkout and confirms the match before showing details.
- Fulfilment status and tracking number. Whether the order has shipped, with which carrier, under which number.
- The store or market the order belongs to. Prices, shipping options and return policies differ by country.
- Product facts and stock. Which version the customer bought, and whether an item is in stock today.
- Refund and return records. What has already been paid back or sent back, so the reply does not contradict it.
All six are read-only. The agent does not edit orders, cancel them or issue refunds. Those are actions, and actions go to a person.
WooCommerce
WooCommerce has a REST API with keys that can be created as read-only. Orders can be fetched by number and searched by billing email, and products carry stock status. One point needs checking in every WooCommerce store: tracking numbers. WooCommerce itself has no tracking field. The number lives in whatever shipment tracking plugin the store uses, or in the order notes, and the agent has to be pointed at the right place. A store that keeps tracking numbers only in emails sent by the warehouse has nothing for the agent to read.
Magento and Adobe Commerce
Magento exposes orders, shipments with their tracking entries, products and stock through its REST API. Access is granted by an integration token whose permissions are set per resource, so the token can be limited to reading sales and catalogue data. Magento stores often run several store views for different countries and languages inside one installation. Each order records its store view, and the agent uses it to choose the right policy and language.
BigCommerce
BigCommerce API accounts are created with scopes, and orders, products and customers can each be set to read-only. Shipments, with tracking numbers, are a sub-resource of the order.
A custom-built store
A store built in-house has no standard API, and it does not need one. It needs two read-only endpoints: one that returns an order by number, and one that returns the orders for an email address, each including fulfilment status, tracking number, market and refund records. Each one is a single query. If no developer is available, a read-only database view serves the same purpose.
What happens when a lookup fails
On every platform, the integration must return one of four results: found, confirmed that none exists, found part of the record, or could not check. A plugin conflict or a timeout on a WooCommerce site is a "could not check", and the agent must say it could not read the order right now. An integration that returns an empty result in that situation makes the agent tell a paying customer that their order does not exist.
Where the conversations come from
The store platform is only the order side. Customer messages arrive through channels, and the agent connects to those separately:
- Email. The support mailboxes, read over IMAP and answered in the same thread. See AI for a shared support inbox.
- Chat. A chat window on the website and inside the mobile app. See AI chat on website and app.
- A helpdesk. If your team works in Zendesk, Freshdesk or Gorgias, the agent attaches there. See adding an AI agent to a helpdesk.
What the work looks like once connected
The volumes below come from the Shopify deployment, counted on 19 November 2026 for the previous 30 days. The same jobs run on the six data points above:
- 15,725 chat conversations answered by AI, across nine storefronts.
- 36,789 customer emails received, each with an AI draft that has the order and shipment already checked.
- 26,451 replies sent using an AI draft: 3,331 by the AI on its own, 3,781 approved without an edit, 19,339 edited and then sent.
- 1,694 tickets created by the chat AI for requests that needed a person.
A checklist before you start
- Create a read-only API key or token. Do not hand over an admin login.
- Find where tracking numbers are stored, and confirm they are stored for every shipment.
- List your stores or store views with their countries and languages.
- Confirm that refunds are recorded on the order, not only in the payment provider.
- Export a few hundred real conversations for the replay test described in how to run an AI agent pilot.
For the Shopify version of this page, see what to connect on Shopify. Tell us which platform your store runs on and the free plan names the endpoints we would read, within two working days.