KINDERAI / MERCHANT GUIDES
How to test an AI chatbot for your Shopify store
A good chat demo is a starting point. Before an assistant answers real shoppers, test it against your own products, policies and customer journeys. The aim is simple: find where it gives useful help, where it needs better information and where a person should take over.
Start in an unpublished theme preview or a controlled test store. Use a small set of real product details and approved policy answers. Keep a record of the question, expected answer, actual answer and next action. You do not need to place an order to test product discovery and cart behavior.
1. Ask one question with an exact store answer
Choose a policy with a clear answer, such as the conditions for free shipping. Ask it in two different ways. The assistant should preserve your conditions rather than invent a broader promise. If the answer is wrong, check the underlying store information and repeat the test after correcting it.
2. Ask for a product you actually stock
Give a budget and a useful preference: “I need a linen shirt under $70.” Check whether the suggested product matches both. Follow the product link and compare the price, currency and availability with the storefront. A persuasive description is not enough if the shopper reaches a different item.
3. Try a request the store cannot satisfy
Ask for an unavailable size, a sold-out product or a category you do not sell. The assistant should explain the limitation and offer an appropriate next step. It should not silently ignore the requirement or pretend an item exists. This test often reveals more than an easy recommendation.
4. Verify the variant and cart
Choose an available color and size, then add the item through the assistant. Open the actual cart and confirm the variant and quantity. Repeat with an unavailable option. Watch for duplicate additions and stale prices. A simulated website demo is useful for exploration, but it does not prove the behavior of your real Shopify cart.
5. Check private order help separately
Use a controlled test customer account and a test order you own. Check what happens when the shopper is signed out, signed in and asking about an order that cannot be found. The assistant should not reveal private order details to an unauthorized visitor. Where tracking is missing, it should say so rather than invent a delivery status.
6. Look at the phone experience
Open the widget on a phone-sized screen. Can you type with the keyboard open, read product cards, close the conversation and continue shopping? Check whether the launcher covers cart controls, cookie preferences or another important button. Test both a product page and the cart page.
7. Define when a person gets involved
Ask an ambiguous question and a request outside the assistant’s permissions. Decide what the next step should be: a clarifying question, a store contact route or merchant review. Verify the actual handoff behavior your app supports. Do not treat a polite “I will help” as proof that a support request was created.
Keep the first scorecard small
Use seven rows, one for each check above. Mark each Pass, Needs information, Product issue or Not supported. Resolve important failures before enabling the assistant widely. Repeat the affected checks when you change your catalog, policies, theme or app configuration.
Once shoppers begin using it, review recurring questions and failed answers. Count successful tasks and useful next steps before attributing sales to chat. A conversation followed by a purchase is not, by itself, proof that the assistant caused the purchase.
Try the approach: explore the KinderAI interactive preview, then read the setup guidance and plan limits. The preview uses fictional products, scripted answers and a simulated cart; it does not configure your store.
Your seven-check worksheet
For each check, write: expected result, actual result, status and next action. Keep customer details out of your notes.
| Check | Expected result | Actual result / next action |
|---|---|---|
| Store policy | ________________ | ________________ |
| Product and budget | ________________ | ________________ |
| Unavailable request | ________________ | ________________ |
| Variant and cart | ________________ | ________________ |
| Private order help | ________________ | ________________ |
| Mobile experience | ________________ | ________________ |
| Human next step | ________________ | ________________ |
Statuses: Pass · Needs information · Product issue · Not supported. Print this page using your browser to keep a working copy.
Next: prepare useful store answers or test product recommendations.
