WooCommerce Chatbot: How to Get One That Actually Understands Your Catalog

If you run a WooCommerce store and search for “WooCommerce chatbot”, you'll land on plugin listicles that get rewritten every January. They all compare the same things: pricing, install counts and dashboard screenshots. And they all skip the only question that matters: will the bot actually know what you sell?

Because that's the real problem. A chat that greets people beautifully but replies “I don't have that information” when asked about a size, a price or whether something is in stock doesn't save you work — it adds to it. This guide covers what actually decides whether a chatbot works on a WooCommerce store: variations, stock, sales, taxes, and how all of that stays up to date. No plugin list and no year in the title, because none of this will change next January.

The problem: a chat that doesn't know what you sell

Most chats installed on WooCommerce stores come in two flavors. The first is live chat: a little window where the customer writes and you (or someone on your team) answer by hand. It works — but only when someone is on the other side, and store questions arrive at 11 pm.

The second is the canned-response bot: customer clicks “shipping”, the shipping text appears; clicks “returns”, the returns text appears. Fine for general questions. But the moment someone types “do you have mountain bikes in size M under $900?”, it's over: that answer isn't behind any button, because it lives in your catalog and changes every week.

And here's the trap with many “AI” chatbots: they bolt a language model onto the bot, but feed it your web pages as if they were running text. The result is a bot that writes beautifully and gets the important part wrong, because a catalog isn't text: it's data with attributes (price, size, stock, category) that needs filtering, not “similarity”. We cover this in depth in why most chatbots can't find products in your catalog.

What a chatbot has to understand about a WooCommerce store

WooCommerce has quirks of its own that no “best chatbots” article mentions — and they're exactly where generic bots fail. If you're evaluating any solution (ours or anyone else's), ask about these four things:

1. Variations

In WooCommerce, a bike that comes in three sizes and two colors isn't one product: it's a “parent” product and six child variations, each with its own price, its own stock and sometimes its own photo. A bot that only reads the product page sees the parent and misses the rest. The most common question a store customer asks — “do you have it in size M?” — is answered at the variation level, not the parent. If the chatbot doesn't go down to that level, it can't sell.

2. Stock, which WooCommerce expresses three different ways

Some stores manage exact quantities (“4 left”), some only mark in stock or out of stock, and some variations inherit stock from the parent product. There's also the “available on backorder” status — purchasable even with no units on hand. A serious chatbot has to understand all three forms and never invent quantities where the store only says “in stock”.

3. Prices as the customer sees them

If a helmet is on sale, your customer sees “was $89, now $69” on your site — and the bot should say exactly that, not just one of the two numbers. Then there's tax: some stores save prices tax-inclusive, others save them tax-exclusive and add it at display time. If the bot reads the raw number from the database, it may quote a price that doesn't match what the customer has right in front of them on the product page. The correct rule is simple to state and easy to get wrong: the bot quotes the price exactly as the store displays it.

4. The real-world mess of WordPress

Product descriptions on a real WooCommerce store are full of leftovers from visual page builders (Elementor, Divi, WPBakery): bracketed codes the customer never sees but that live inside the text. If the bot is fed that without cleaning, the garbage ends up in its answers. And if your store uses a translation plugin like WPML or Polylang, every product exists duplicated in several languages — a bot that swallows everything indiscriminately will mix languages in its replies.

Do you need a WooCommerce chatbot plugin?

It's the most common search and the decision almost nobody explains to you. There are two ways to put a chatbot on a WooCommerce store, and the difference matters more than the brand you pick:

A plugin installed inside your WordPress. Everything runs on your hosting: the bot, its logic and its AI calls. The upside is it installs from the plugin directory like anything else. The downsides are the usual WordPress ones: it's one more piece loading your server (and WooCommerce stores typically live on shared hosting, where every plugin counts), one more piece to update, and one more piece that can conflict with your theme or another plugin. On top of that, the AI quality is capped by whatever that plugin does internally — and processing a catalog properly (variations, filters, structured search) is infrastructure work that hardly fits inside a plugin.

An external service connected through the WooCommerce API. The catalog syncs outside, on the chatbot's platform, and the only thing living on your site is the chat widget (a few lines of code, like Analytics). Your hosting processes nothing: not the AI, not the search, not the conversations. The connection uses the REST API WooCommerce ships with — the same one management apps and invoicing systems use — with keys you generate yourself and can revoke anytime.

We built Bravos AI the second way, and not by accident: the heavy lifting of understanding a catalog (variations, stock, “under $X in size Y” filters) needs its own database and search infrastructure. That can't be done well inside the customer's shared hosting.

How it connects (step by step, no coding)

Here's the full process with Bravos AI. No code to touch, nothing to install in your WordPress:

1. Generate API keys in your store. In your WordPress: WooCommerce → Settings → Advanced → REST API → Add key. Set the description to “Bravos AI”, choose Read/Write permissions (needed so your store can notify us of changes) and copy the two keys that appear — they're shown only once.
2. Paste them in the Bravos dashboard. Under Integrations → WooCommerce: your store address and the two keys. When you test the connection you'll see what we detected: how many products you have, your currency, and how your store handles tax (prices tax-inclusive, tax-exclusive, or taxes disabled). If you have a multilingual plugin like WPML or Polylang, we let you choose which language the bot will work with.
3. Choose how much stock the bot should reveal. Three options: don't mention stock at all, say only in stock / out of stock, or give exact quantities if your store manages them.
4. Connect, and the catalog imports itself. Every product comes in with its name, category, description (already cleaned of page-builder codes), price as your store displays it, variations with their stock, and the link and photo so the bot can show them in the conversation.
5. Put the widget on your site. A few lines of code, pasted once. If your site is WordPress, the full guide is in how to add a chatbot to WordPress in 5 minutes.

From there, the bot answers about your catalog, your pages and your documents, in the customer's language (13+ languages, without you translating anything).

What happens when you change a price or run out of stock

This is the question you should ask any vendor, because a bot with an outdated catalog is worse than no bot: it recommends sold-out products and quotes old prices.

With Bravos it works in two layers. Instantly: when you edit a product in your WooCommerce (price, stock, description, anything), your store notifies us and the change shows up in the bot within seconds. And every night: the full catalog is checked against your store, in case any notification got lost — which can happen in WordPress, because deliveries depend on an internal mechanism that's unreliable on low-traffic stores. The honest version: changes arrive instantly when your store sends the notification, and the nightly check guarantees nothing stays behind for more than a day.

This also means there's no “retraining” and no re-sync button to remember when you change products. It maintains itself. If you want to see how other platforms compare on this, we analyzed it in how to keep your chatbot data up to date without Zapier or n8n.

What it looks like in a real conversation

Picture a cycling store. This is what changes when the bot actually filters the catalog instead of matching similar text:

Look at the details, because that's where the difference lives: the price filter is real (no $950 bike sneaking in “because the text looks similar”), the sale is quoted with the before-and-after, the size is a variation with its own stock, and “available on backorder” isn't confused with sold out. All of that comes straight from the WooCommerce data, not from the model's imagination.

Same for questions that aren't catalog questions — shipping, returns, sizing, warranty — because the bot is also fed your pages and documents. The combination of both is what makes the experience seamless for the customer.

When you don't need it

Honesty first — that's the whole point of not being a plugin listicle:

• If your catalog is a handful of products with no variations and your customers always ask the same four questions, a free canned-response bot may be enough.
• If you barely get any inquiries, fix that with a good FAQ page first. A chatbot amplifies support demand you already have; it doesn't create it.
• If what you want is human chat during business hours and you have someone to staff it, simple live chat does the job. The chatbot shines exactly where the human doesn't reach: nights, weekends, and the 40 repeated questions a day.

For everyone else — stores with a real catalog, variations, changing sales and customers asking at all hours — a catalog-connected chatbot is where it pays for itself. For the broader online-store case (abandoned carts, purchase doubts), there's more in our ecommerce chatbot guide.

In summary

• The criterion for choosing a WooCommerce chatbot isn't the feature list: it's whether it understands your catalog — variations, stock, sales and taxes as the customer sees them.
• You don't need a plugin: connecting through the WooCommerce REST API leaves your hosting alone and the AI runs on dedicated infrastructure.
• Connecting with Bravos AI is an API key + pasting the widget. No coding, nothing installed in your WordPress.
• Catalog changes arrive instantly when your store sends the notification, and a full nightly check guarantees nothing stays outdated.
• Works with WPML/Polylang (you pick the catalog language) and answers your customers in 13+ languages.

Is there a free WooCommerce chatbot?

Free canned-response bots, yes. A real AI chatbot that understands your catalog and is free forever, no — AI has a cost per answer and somebody pays it. What does exist is the trial: with Bravos AI you get the full PRO plan for 7 days; we notify you before charging and if you cancel before day 7 you pay nothing.

Does a WooCommerce chatbot work with variable products (sizes, colors)?

With Bravos AI, yes — and it's one of the things we cared most about getting right: every variation syncs with its own price, stock and photo, and the bot answers at the variation level (“do you have size M left?”). Grouped and external/affiliate products aren't synced for now, and the dashboard shows how many were skipped — no silent truncation.

Will a chatbot slow down my WooCommerce store?

Not if it connects through the API: the only thing living on your site is the chat widget, which loads like any external script without touching page load time. The catalog is processed outside your hosting, and the sync is designed to treat it gently: few simultaneous requests at a calm pace, built for the shared hosting where most WooCommerce stores live.

Do I need to know how to code to add a chatbot to WooCommerce?

No. The only two technical steps are generating the API key in WooCommerce (four clicks in your WordPress dashboard) and pasting the chat widget on your site once. Everything else is configured from the Bravos dashboard.

What happens when I change a price or a product sells out in my WooCommerce store?

With Bravos AI, your store sends the notification and the bot reflects the change within seconds. On top of that, the full catalog is checked every night in case any notification got lost. No retraining, no buttons to remember.

Does the chatbot work with multilingual WooCommerce stores (WPML or Polylang)?

Yes. On connection the multilingual plugin is detected and you choose which catalog language the bot will use; translation duplicates are discarded so languages don't get mixed in the answers. And this is independent from the language the bot serves customers in: it replies in the customer's language even if your catalog is in just one.

Does the chatbot work if my product descriptions are built with Elementor or Divi?

Yes — descriptions are cleaned before they reach the bot. The internal page-builder codes (those bracketed snippets your customer never sees) are stripped during import, so the bot works with the actual product description.