Dingbo AI
Dingbo AI · Field notes

AI Customer Service for WooCommerce, Magento, Custom Stores

Updated 2026-11-19 · Shenzhen Dingbo Intelligent Technology Co., Ltd.

Dingbo AI builds and runs AI agents for customer service. You pay per completed task.

Want AI to take over a repetitive job? Get a free assessment

Email only. We reply within 24 hours, free of charge.

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

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:

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:

A checklist before you start

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.

Which job eats the most hours on your team? Tell us in one line and we will sketch a plan for free

We connect to the systems and documents you already use, the AI works through your process, and your people review and approve. You see real numbers from a pilot before you pay for anything, then you pay for completed work.

Or email us directly: yzh317179958@163.com

Free assessmentReply within 24h