← All writing

Integration

An AI chatbot for a Shopify store, installed with a script tag

Chatterbox goes on a Shopify store as one script tag in theme.liquid. There is no Shopify App Store listing and no live product or inventory sync today. It answers policy, shipping, returns and pre-sales questions from the pages it has crawled, and captures the lead when it cannot.

A small packing table with kraft cartons, packing tape and scissors, one carton open and part-filled.

Start with the two things most Shopify chatbot pages leave until the footnote.

There is no Chatterbox app in the Shopify App Store. You install it by pasting a script tag into your theme, the same way you would on any other website.

There is no live product or inventory sync. Chatterbox reads your storefront the way a visitor's browser would, and it knows what those pages said when it last read them. It does not hold a connection to your catalog, so it does not know that a size ran out an hour ago.

Decide whether that is acceptable before you read further, because the rest of this page assumes it is.

Installing it on a Shopify theme

From your admin, open Online Store, then Themes, then Edit code, and open theme.liquid. Paste the one-line script tag from your Chatterbox install page immediately before the closing </body> tag and save. The widget appears on every page the theme renders.

Duplicate the theme before you edit it if this is a live store. That is standard practice for any theme change and takes ten seconds.

The widget stays under 15KB, which matters more on a Shopify storefront than on a brochure site. You are already carrying app scripts, a pixel or three and a review widget, and mobile conversion notices every one of them.

What it answers well on a store

The questions that cost you sales at eleven at night are rarely about a product. They are about the deal around it.

Do you ship to my pin code, and how long does it take. What is the return window and who pays the reverse shipping. Is there a COD option. Is this the price with GST. What happens if the size is wrong. Do you have a physical store I can visit. Is this warranty valid in India.

Every one of those has a published answer on a well-built store, and every one of them gets asked anyway, because customers do not read policy pages. That is the work a Shopify chatbot actually does, and Chatterbox does it from the pages you already wrote, showing which passage each answer came from.

For pre-sales questions it cannot settle, it asks for a name and phone number rather than inventing a fit guide or a delivery promise. On a high-consideration product, that lead is worth more than a deflected ticket.

Product questions, honestly

Chatterbox can answer from product and collection pages it has crawled. If a product page states the fabric, the dimensions or the care instructions, the bot has that.

What it does not have:

Live stock. A crawled page is a snapshot. Between crawls, "in stock" is whatever the page said last time.

Live prices. Same problem, and worse, because a stale price reads to a customer as a promise. If you run frequent sales, keep pricing questions pointed at the product page rather than expecting the bot to quote a current number.

Order status. There is no connection to orders, so "where is my parcel" belongs in your existing account or tracking flow.

Every SKU in a large catalog. Crawl allowances are per plan, at 10 pages on Starter and Pro, with ₹500 buying ten more. A 400-product store is not going to be crawled product by product at a sensible price. Point the crawl at your policy, shipping, returns, FAQ and about pages, and treat product detail as a bonus rather than the plan. The pricing page has the current allowances.

Re-crawl a source once a day when you change your site, and treat the freshness of your own storefront as your responsibility rather than the bot's.

Planned, not shipped

A native Shopify integration with an App Store listing and a real catalog feed is a reasonable thing to want and it does not exist today. If a vendor's page implies otherwise about their own product, ask them to show you the app listing.

What exists today is the script tag, the crawl, the refusal when the answer is missing, and the phone number captured instead. Answers work in English, Hindi and Hinglish out of the box, which on an Indian D2C store covers most of what lands in the widget.

Before you switch it on

Pull up your last fifty customer messages and check that each question has a real answer somewhere on your store. Vague shipping copy produces vague answers, and a returns policy written by your theme's demo content produces a confidently wrong one. The content checklist is the pass to run first.

If policy and pre-sales questions are what you are losing sales to, start on the Free plan, crawl your policy pages, and ask it the five questions you answer on Instagram DMs every week.