How to add a chatbot to WooCommerce (setup guide, start to finish)

You can go from zero to first customer reply in about 15 minutes. This guide walks through the full WooCommerce chatbot setup process — choosing the right plugin, installing it, syncing your product catalog, building a knowledge base, customizing the widget, and testing before you go live. No fluff, no theory, just the steps.

The stores that get value fast are the ones that prepare their knowledge base content before they touch a plugin. The ones that struggle skip testing and go live with an empty knowledge base. This guide will keep you in the first group.

Written by Rob Abrahams, founder of Storebird. Last updated: April 12, 2026.

What you need before you start (prerequisites)

Do not install anything yet. Get these ready first, and the entire setup takes one sitting instead of three.

Technical requirements

• WooCommerce 5.0 or later. Most chatbot plugins require WooCommerce 5.0+ for proper REST API access. Check your version under WooCommerce → Status → System status. If you are below 5.0, update first.
• WordPress admin access. You need to be able to install plugins and configure settings. Editor or Shop Manager roles are not enough.
• A modern WooCommerce theme. Any actively maintained theme works — Astra, Flatsome, OceanWP, Blocksy, Storefront. Avoid themes that haven't been updated in over a year; they tend to conflict with new plugins.

Content you should have ready

This is what most people skip. Prepare these before you touch the WordPress dashboard:

• Your return policy text. Full text, not a link to a PDF. The chatbot needs to quote specific return windows and conditions.
• Shipping information. Delivery times by region, shipping costs, free shipping thresholds.
• Your top 20 FAQ answers. Export the last 90 days from your helpdesk and tally the most common questions. Typical topics: order tracking, return process, payment methods, sizing/fit, product care.
• Brand colors and logo. Hex codes for primary and accent colors. A square logo or avatar for the chat widget.

If you run WPML, also have your translated policies ready. A chatbot that answers in Dutch but quotes your English-only return policy is worse than no chatbot at all.

Step 1: Choose and install your chatbot plugin

Not all chatbot plugins are built the same. Before you install anything, understand what you need. For a full comparison, read our best AI chatbot for WooCommerce guide. The short checklist:

• Does it read your WooCommerce catalog directly? A catalog-aware chatbot answers "do you have this in blue, size L?" from live data — not scraped pages.
• Does it handle order tracking? Where-is-my-order queries are 30–50% of support volume. If the chatbot cannot answer those, you are automating the wrong half.
• Flat pricing or per-reply? Per-reply pricing punishes you for traffic spikes.
• Does it need an OpenAI API key? Some plugins require your own key, which means a separate account and potential runaway costs.

For this guide, I use Storebird as the reference — the chatbot I built specifically for WooCommerce. The general steps apply to any plugin.

To install: In WordPress admin, go to Plugins → Add New, search for your chatbot plugin, click Install Now, then Activate. You can also download from the WordPress.org plugin directory and upload the ZIP under Plugins → Add New → Upload Plugin.

Do not install two chat widgets at the same time. If you are replacing Tidio, Crisp, WoowBot, or anything else, deactivate it first. Two widgets confuse customers and double your JavaScript load. For the full walkthrough with screenshots, see our install documentation.

Step 2: Connect to WooCommerce and verify catalog sync

Once the plugin is active, connect it to your WooCommerce store so it can read your product catalog and order data. With Storebird, this is one step: enter your license key (or start the 14-day free trial) and the plugin connects to your WooCommerce data through the WooCommerce REST API automatically. Other plugins may require you to generate REST API consumer keys manually (WooCommerce → Settings → Advanced → REST API) or enter an OpenAI API key.

After connecting, verify the sync. This step is easy to skip and important not to:

• Product count. Does the chatbot dashboard match your WooCommerce product count?
• Variable products. Pick a product with variations. Ask "do you have [product] in [color], [size]?" — it should check live stock.
• Prices. Ask about a product's price. It should return the current price including sale prices.
• Out-of-stock items. Ask about a known out-of-stock product. The chatbot should say it is unavailable.
• Categories. Ask "what do you have under €50?" and confirm the chatbot navigates your catalog.

If the sync looks wrong, check that your WooCommerce REST API is accessible (some security plugins block it) and that products have complete data.

Step 3: Build your knowledge base

The product catalog handles product questions. The knowledge base handles everything else — return policy, shipping, payment methods, store policies, sizing, care instructions.

How to add knowledge base content:

1. Navigate to the chatbot's knowledge base section in your plugin settings.
2. Paste your return policy text — the full text, including exceptions for sale items and international orders.
3. Add shipping information by region and method.
4. Add payment method details (cards, Klarna/iDEAL/PayPal, payment-on-delivery).
5. Add product-specific guides: sizing charts, care instructions, compatibility info.
6. Add answers to your top 20 customer questions.

Tips from experience:

• Be specific. "Free returns within 30 days for unworn items in original packaging. Sale items: store credit only. Return shipping: free within EU, customer pays internationally." — that is the level of detail the chatbot needs.
• Include edge cases. "Can I return a sale item?" "Do you ship to Norway?" Customers ask the edge cases. Cover them explicitly.
• Update it. After the first week live, check which questions escalated to a human — those are your knowledge base gaps.

For a WooCommerce chatbot to handle real customer conversations, the knowledge base is the difference between "useful on day one" and "another abandoned plugin." I have seen stores with 10,000+ products get the catalog sync right but fail on a basic "can I return this?" — because nobody pasted the return policy. Do not be that store.

Step 4: Customize your widget and branding

The default chatbot widget will work, but it will look like a default chatbot widget. Five minutes of customization makes the chatbot feel like part of your store.

What to customize:

• Colors. Match your brand colors. The widget should look like it belongs on your site, not like a third-party embed.
• Avatar or logo. Upload your store logo or a custom avatar for the chat header.
• Greeting message. Replace "Hi! How can I help?" with something store-specific: "I can help with product questions, order tracking, and returns — ask me anything."
• Welcome prompts. Surface your most common questions as suggested buttons: "Where is my order?", "What's your return policy?", "Do you ship to [country]?".
• Widget position. Bottom-right is standard. Only move it if your theme has a conflicting element in that corner.

A chatbot that matches your store's look gets noticeably more engagement than a generic widget. Five minutes of customization is worth it. Check Storebird's pricing and features for full widget customization options.

Step 5: Test with real questions (the 10-question checklist)

This is the most important step in the entire setup — and the one most merchants skip. Do not go live until you have tested all ten of these questions, or your store's equivalent. Each one maps to a real customer scenario that will happen within the first 48 hours.

Ask these 10 questions before going live

1. Product variation query. "Do you have [product] in [color], [size]?" — The chatbot should check live stock and answer correctly.
2. Out-of-stock handling. "Is [known out-of-stock product] available?" — It should say no, and ideally suggest an alternative.
3. Where is my order? "I placed order #12345, where is it?" — If order tracking is connected, the chatbot should return the status. If not, it should explain how the customer can check.
4. Return policy. "Can I return this item?" — The chatbot should quote your return window, conditions, and process from the knowledge base.
5. Shipping question. "Do you ship to [country]? How long does it take?" — The chatbot should return the correct delivery time and cost from your knowledge base.
6. Price query. "How much is [product]?" — The chatbot should return the current price, including any active sale price.
7. Language detection (if using WPML). Switch your store to a different language and ask a question. The chatbot should reply in the customer's language, not your default language.
8. Vague or ambiguous question. "I need help with something" — The chatbot should ask a clarifying question, not guess or give a generic response.
9. Human handoff trigger. "I want to talk to a real person" — The chatbot should escalate to live agent handoff immediately, without arguing or asking "are you sure?"
10. Off-topic question. "What is the capital of France?" — The chatbot should stay on topic and explain that it handles store-related questions only. It should not answer random trivia.

Grade each answer: correct, partially correct, or wrong. If more than two are wrong, go back to steps 2 and 3 before proceeding. Product and stock failures usually point to a catalog sync problem — check that your REST API is accessible and that product data is complete. Policy failures mean the knowledge base needs more content. This checklist catches 90% of issues before a single customer sees the chatbot. The stores that skip it are the ones that deactivate the plugin after a week.

Step 6: Go live, avoid common mistakes, and monitor the first 7 days

Once testing passes, make the widget visible to all customers. But first, the mistakes I see on every other WooCommerce store:

• Installing two chat widgets at the same time. Two widgets = two JavaScript loads, two greeting pop-ups, confused customers. Deactivate the old chatbot first.
• Skipping the knowledge base. Catalog sync without a knowledge base means the bot cannot answer "what is your return policy?" — a top-three question on every store.
• Not testing variation queries. Most merchants test with "hi" and call it done. Customers ask about specific sizes, colors, and stock.
• Going live without human handoff configured. No handoff = dead end for the customer. Always set up at least one team member for handoff notifications.

Day 1–3: Watch every conversation. Fix incorrect answers immediately. Add answers for questions the chatbot could not handle. If more than 40% of conversations escalate, your knowledge base is too thin.

Day 4–7: Pattern recognition. Every WooCommerce store converges on a handful of repeat questions. Make sure the chatbot handles those perfectly. A well-configured chatbot should handle 60–80% of conversations without human intervention. If you are below 50%, the knowledge base needs work. Check your chatbot dashboard for revenue attribution — conversations that led to completed orders.

After the first week: Expand the knowledge base for the questions you saw most. Update welcome prompts. Review the knowledge base monthly — weekly for the first month. After 30 days, check revenue attribution: conversations that led to orders, not just ticket deflection. For broader strategy, read our WooCommerce chatbot guide.

Frequently asked questions

How do I add a chatbot to WooCommerce? Install a chatbot plugin from the WordPress plugin directory, connect it to your WooCommerce store, sync your product catalog, add knowledge base content (return policy, shipping, FAQ), customize the widget branding, test with real questions, and go live. The process takes about 15 minutes if you have your content ready.

What do I need before installing a WooCommerce chatbot? WooCommerce 5.0 or later, WordPress admin access, your return policy text, shipping information, answers to your top 20 customer questions, and your brand colors. Having these ready before you start means the setup is a single sitting, not a multi-day project.

Does adding a chatbot slow down my WooCommerce store? A well-built chatbot plugin lazy-loads the widget, so it does not block page rendering. Storebird loads asynchronously and has been tested against Astra, Flatsome, and Blocksy with no measurable PageSpeed impact.

Do I need an OpenAI API key? Some plugins require it. Storebird does not — it runs on its own infrastructure. If a plugin requires an OpenAI key, factor in $50–$200/month in API charges on top of the subscription.

How long does WooCommerce chatbot setup take? About 15 minutes from install to first customer reply, assuming your knowledge base content is ready. Catalog sync is automatic.

Can a WooCommerce chatbot answer product variation and stock questions? Only if it reads your WooCommerce catalog directly. Storebird syncs with WooCommerce's data model — products, variations, attributes, prices, and live stock — so it answers these from real data.

What is the best chatbot plugin for WooCommerce in 2026? For catalog-aware AI with flat pricing, Storebird is built for this. For a full comparison of all options — including Tidio, WoowBot, Intercom, and others — read our 2026 WooCommerce chatbot comparison.

Should I configure human handoff before going live? Always. Going live without handoff means the chatbot has no escape route for questions it cannot answer. Set up at least one team member for handoff notifications. It takes two minutes and prevents the most common "chatbot fail" scenario — a customer stuck in a loop with no way to reach a human.

If you have not picked a chatbot yet, start with Storebird's 14-day Pro trial — no credit card, full catalog sync, running in under 15 minutes. If you want to compare options first, our 2026 WooCommerce chatbot comparison covers every serious option on the market.