AI chatbots for ecommerce answer shoppers in chat, on your store. From your pages they can answer product, shipping and returns questions. With a data connection they can also give live stock and a customer's order details.
What a chatbot can say depends on the data you give it, so plan by data source. We recommend Asyntai, our own product, which answers from your store's content and connects to live data from the Standard plan.
Three shoppers open the chat on a Saturday evening. One asks "Does this jacket run small?" The second asks "Is the medium back in stock?" The third asks "Where is my order?" These look alike in the chat window, but each one needs a different source. The first answer sits on a product page. The second changes through the day. The third belongs to one customer.
Where each shopper question gets its answer
Sort your own in-chat ecommerce questions into these three groups before you compare tools. Copy thirty recent questions from your inbox and mark each one.
| Source | Typical questions | What you set up | Asyntai plan |
|---|---|---|---|
| Your published pages and files | "Do you ship to Canada?" "Is this machine washable?" "How long do I have to return it?" | A crawl of your site, plus uploaded files and written answers | All plans. Crawl limits: 50, 250, 1,000 and 5,000 pages |
| A live catalog feed | "Is the medium in stock?" "What does it cost today?" | A web address that returns your data as JSON, CSV or plain text | Standard and above. Feed Max, for large catalogs, on Pro |
| The customer's own data | "Where is my order?" "What did I buy last time?" | User Context, a custom tool, or both | Standard and above |
If most of your thirty questions land in the first row, a page-based setup covers them. If order questions lead your list, budget for the data connection from the start.
Why a chatbot contradicts your team, and how to stop it
Store owners often ask how to teach an ecommerce AI agent their returns, warranty and shipping policies so that it stops disagreeing with staff. Asyntai answers from the content it reads, and most tools of this type work in a similar way. So a wrong policy answer usually starts with the content. Look for these four causes.
An old page is still public
Last year's holiday returns page still says 60 days. The crawler reads it like any other page.
Two pages disagree
The FAQ says free returns. The terms page says the customer pays return postage.
The exception was never written
Your team knows that sale items are exchange only. No page says so.
The bot was never told when to stop
Nobody said that warranty claims on damaged goods must go to a person.
Fix the source first. Correct or remove the old page, then crawl again. Put each exception in writing where the AI can read it. Then add rules to the AI instructions, in plain sentences. For example:
Our returns window is 30 days from delivery.
Sale items can be exchanged but not refunded.
Never promise a refund, a delivery date or a discount.
For warranty claims on damaged goods, ask for the order
number and email, then tell the customer our team will reply.
If our pages do not cover a question, say so and offer our
contact page.
Replace these sentences with your own rules. Then ask your support staff for the cases that cause arguments, and run those cases in the test chat. Test messages do not count toward your monthly allowance, up to a fair-use cap.
| Ask this | A correct reply |
|---|---|
| "I bought this in the sale. Can I get my money back?" | States your sale rule, with no exceptions added |
| "It arrived broken and I want a new one today." | Collects the details and passes the case to your team, with no promise on timing |
| "Your other page says 60 days." | Keeps to the current policy, or offers a person |
| "Do you sell gift cards?" (if your site does not say) | Says it has no information and offers a contact route |
After launch, read the chat logs each week, on any plan. From Standard, knowledge gaps list where the content did not cover a question. When a policy changes, update the page and crawl again on the same day.
Product questions and selling in chat
A shopper may describe a need instead of a product: "I need a gift for my dad who likes cooking, under $75." Filters and keyword search struggle with that sentence. An assistant that has read your product pages can suggest items and link to them. The quality of the suggestion depends on your descriptions. If your pages give no material, fit or size details, the chatbot has nothing to compare.
Your catalog size decides the setup:
A crawl of your product pages can be enough. Crawl again when prices or ranges change.
The Real-Time Data Feed, from Standard, handles feeds up to 200,000 characters. Changes to prices and stock in existing items show up in replies without a new crawl.
Real-Time Data Feed Max, on Pro, searches large feeds during the chat. The documentation has setup guides for platforms such as Shopify, WooCommerce and Magento.
Product cards, from Standard, show an image, a price and a button inside the reply. Proactive messages, on Pro, let the chatbot write first when something happens, such as an item going into the cart. For more on carts, read how to recover an abandoned cart.
Order questions need a connection
A crawl cannot answer "Where is my order?", because the answer is not on a public page. Asyntai has two ways to reach this data, both from Standard.
User Context suits signed-in customers. Your site passes the details it already holds, such as the customer's name and recent orders, when the chat starts. Asyntai has guides for platforms including Shopify, WooCommerce and Magento.
Custom tools suit values that appear during the chat. You point the AI at an endpoint of your own, and it calls that endpoint with what the customer typed, such as a tracking number. You need an endpoint that already returns the data, so involve your developer. What the AI can do depends on what your endpoint does.
One point for that developer: decide what each endpoint reveals. An order number alone should not expose a customer's address. Have the endpoint check a second detail, and return only what the chat needs.
When a person should take over
Some conversations need your team, such as a damaged item, a large trade order or an angry customer. From Standard, escalation lets the AI offer a person. If the shopper agrees, your team gets an email with a link to the conversation, and the AI keeps replying until someone joins. Business hours stop the chat from promising a person at night. Outside those hours, the AI says when your team is back and asks for an email address.
Human takeover lets your staff enter any live chat, and the AI stops replying to that visitor until they hand it back. Tickets, also from Standard, record problems that need follow-up, and your team can assign and answer them.
Adding it to your store
| Platform | How it goes on | Guide |
|---|---|---|
| Shopify | The Asyntai app with its app embed in theme settings, or the embed code in theme.liquid | Shopify |
| WooCommerce | The embed code in the footer, through a header and footer plugin or your theme | WooCommerce |
| Magento | The embed code through the admin panel, for example in a CMS block | Magento |
| Other stores | The embed code before the closing </body> tag. Guides cover platforms such as PrestaShop and BigCommerce | All platforms |
After installing, buy something from your own store on a phone. Check that the chat button does not cover the add-to-cart or pay button. If it gets in the way on one page, Exclude Pages can hide it there.
Other ecommerce chat tools
These tools take different routes, and they are listed in no ranking order.
Listed as free on the Shopify App Store.
An AI sales associate for Shopify storefronts. How it differs from Asyntai: it is an app for Shopify, and Asyntai installs on Shopify and on other store platforms.
Free with 50 conversations a month. Starter $24.17, Growth from $49.17 a month. Lyro AI from $32.50 a month for 50 conversations.
Live chat with flows and an AI add-on. How it differs from Asyntai: human and AI conversations have separate meters, and Asyntai counts AI replies in one plan.
Starter $10 a month for 50 tickets. AI Agent $0.90 per automated interaction on an annual contract, $1.00 on a monthly one.
A help desk for online shops. Its page says each automated interaction also counts as one ticket, and it shows more than one price for its higher plans. How it differs from Asyntai: the bill follows tickets and interactions, and Asyntai has one monthly plan price.
Which Asyntai plan fits your store
One message is one AI reply, so count replies and not chats. Here are two example stores. Replace the inputs with your own numbers.
Volume is one half of the choice. The features you need are the other half. Product cards, live data, order details and human takeover start at Standard, whatever your volume. Proactive messages and branding removal are on Pro at $449, with 50,000 messages. The Free plan includes 50 messages a month, which is enough to test your thirty questions. See all plans.
Common questions
Can one chatbot serve shoppers in several languages?
Yes. Asyntai replies in the language of the shopper's message, even when your pages are in another language. From Starter, the widget's own text can show in 32 languages. Ask a native speaker to read a sample of the replies, including your returns wording.
How do I measure whether it pays for itself?
Compare your support inbox by topic before and after launch, and check whether delivery and returns questions fall. For sales, chat analytics start at Starter, and link tracking parameters are on Pro. Be careful with shoppers who chat and then buy, since many of them might have bought anyway.
Sources, read November 2026
Tidio pricing page (tidio.com/pricing). Gorgias pricing page (gorgias.com/pricing). Shopify Inbox listing on the Shopify App Store (apps.shopify.com/inbox). Vendors change their prices, so check the current page before you decide.