AI chatbot on Shopify: the problem isn't products, it's variants
"Do you have that shirt in blue?" is the most common question an online shop gets, and it's the one most AI assistants answer wrongly with a confident face. Not because the model is weak: because on Shopify the shirt isn't what you sell.
TL;DR
- In Shopify the product is a container; the purchasable thing, with its own price and stock, is the variant.
- An assistant that indexes products rather than variants will say "yes, available" when all you have left is the red XL.
- The struck-through price lives in a separate field (
compare_at_price), and an assistant that doesn't read it doesn't know the item is on sale. - Connecting is an Admin API token: no code, but it's worth knowing what you're authorising.
The difference that decides everything
Open a product in the Shopify admin: a shirt. Below it, the variants table — blue/S, blue/M, red/XL — and each one has its own price, its own SKU and its own stock. The product itself has none of those three: it's the title, the description, the photos.
Almost every error you'll see follows from this:
| The customer asks | Assistant reading products | Assistant reading variants |
|---|---|---|
| "Do you have it in blue?" | "Yes, available" | "In blue we have the S; the M arrives Thursday" |
| "How much is it?" | A price — whichever it found | The price of that variant |
| "Is it on sale?" | Doesn't know | Yes, and by how much |
The first one isn't lying: it's answering the wrong question, because the wrong question is the only one it can ask of the data it has.
Three things to ask before signing
1. Do you index variants or products?
That's the question. If the answer is vague, ask for a demonstration: have the assistant asked about a size you know is sold out while others are in stock. An assistant reading variants will tell you; one reading products will offer you the shirt.
2. Do you read the compare-at price?
Shopify keeps the full price in a field separate from the selling price. If the assistant only reads the latter, it doesn't know you're running a promotion — and the customer asking "is this discounted?" gets told no, during your own sale.
3. How do you handle long catalogues?
Shopify returns products in pages, and moving to the next one means following a reference it sends back in the response. Anyone who implemented the integration in a hurry stops at the first page: with two hundred products you'll never notice, with two thousand the assistant silently ignores half your catalogue. Ask how many products it imported and compare it with the number in your admin.
How it connects
- From the Shopify admin you authorise read access to the catalogue. It's the same mechanism as any app: no terminal, no key to paste by hand.
- The assistant imports products, variants, prices and availability.
- You set language, tone and three or four priority rules — shipping, returns, sizing: the ones you don't want improvised.
- You publish the widget.
One piece of advice on the first step: look at what you're authorising. Answering questions about the catalogue needs read access to products, and that's it. If the permission request covers editing orders or reading customers, it's fair to ask what they're for before confirming.
When an assistant on Shopify becomes genuinely useful
Not when it answers — when it tells you what you're failing to write on your product pages. After a week of real conversations, the list of recurring questions is your copywriting to-do list: if thirty chats asked about fit, that information is missing from the page and you're losing orders from the people who never asked.
FAQ
Do I need to know how to code?
No. Authorisation happens from the Shopify admin, like any other app.
Does it see up-to-date stock and prices?
Up to date as of the last sync, not in real time: the assistant answers from a copy it re-reads at intervals. That applies to every platform and I've explained it in full in the WooCommerce guide — it holds identically here.
Does it handle variants with multiple options, like size and colour together?
That is exactly the question to ask whoever is selling it to you, and it's the one in the title. The right answer is yes, with a demonstration.
What if I use WooCommerce?
Same footing, different authorisation: WooCommerce guide.
ShopBrain imports your Shopify catalogue, answers from your real data and hands over to a person when a request is delicate — and the same assistant answers on WhatsApp and Telegram too. On variants, put us through the same test I suggested above: it's the right way to choose, with anyone.
If you're still weighing it up, continue with how not to get fooled by fake AI chatbots.
Related articles
- When the posting and the interview describe different rolesA hiring process produces four documents — the posting, the technical exercise, the final interview, the rejection email — and each says something different about the real role. How to read them before investing weeks.
- When the interview measures a conflict that isn’t yoursIt wasn't the first time I'd seen this pattern at a large, well-run company: whoever writes the posting wants one thing, whoever evaluates you needs another. How to spot it before you sign.
- The worst bug does not break the feature. It breaks the view26 tools connected and working in production, the dashboard showed zero. The bug had been there for months for another product too, and nobody had seen it because whoever could notice had admin permissions.