WooCommerce AI Chatbot Setup: Connect an AI Agent to Your Store in a Week

Connect an AI agent to WooCommerce, and let it run support

Adding a chat widget to a WooCommerce store takes minutes. Getting an AI agent that actually looks up orders, processes refunds to your rules, recovers abandoned carts and keeps your inbox in order takes about a week, and most of that week is you checking its work, not wrestling with settings.

This guide walks through connecting Omni to a WooCommerce store: what it does once it's live, what you decide along the way, and the realistic timeline. We make Omni, so we have a perspective. Where a plain chat widget is enough for your store, we'll say so.

TL;DR

To set up an AI agent on WooCommerce: connect it to your store's REST API, give it your policies and product content to read, set the rules for what it can do on its own, then add its chat widget. With Omni, that means connecting WooCommerce via Application Passwords, confirming your refund and escalation limits, and going live in about a week. Once it's running, Omni handles order updates, returns and refunds within your rules (asking you first above your threshold), abandoned cart recovery and inbox triage. Pricing is one flat rate: £250/month for the first 10 founding places, then £500/month, everything included. See pricing.

Chatbot or agent: know which one you're setting up

Most "WooCommerce AI chatbot" guides walk you through installing a widget that answers FAQs from a page you upload. That's useful, but it's the floor. The moment a customer says "yes, refund it" or "where's my order?", a chatbot stops and hands the work back to you.

An agent doesn't stop there. Connected to your WooCommerce REST API, it reads live order data and takes actions: it looks up the tracking number itself, processes the refund within your policy, updates the order status. The difference is the whole point of setting AI up in 2026, and it's covered in depth in our agentic AI vs chatbot guide. For the full landscape of what AI does across a WooCommerce store, our complete guide to AI for WooCommerce covers customer service, operations, marketing and finance.

This guide is about setting up the agent kind, specifically Omni.

What Omni does once it's connected to WooCommerce

Before the setup steps, here's what you're setting up. These are the four things Omni does on a WooCommerce store from day one.

Order updates and tracking. "Where's my order?" is roughly a third of inbound on a typical WooCommerce store, and the answer is already in your store and the carrier's tracking. Omni reads it via the WooCommerce REST API and answers instantly, any time of day, in the customer's language. Your evenings stop disappearing into the same lookup.

Returns and refunds, to your rules. A customer asks to return something and Omni reads your return policy and the order's age. Within window and under your threshold, it processes the refund and updates the order. Above your threshold, or outside policy, it brings it to you to approve, with the order and the conversation attached. You set the limit; Omni works inside it.

Abandoned cart recovery. When a cart's been sitting a couple of hours, Omni sends the recovery message itself, referencing the actual items and answering the likely objection. If the customer replies "is this in stock in size 10?", Omni answers rather than dropping them into a dead-end template.

Inbox triage. Not every message is a "where's my order?". Omni reads what comes in, resolves what it can, and surfaces the rest to you in order of what needs you, so a complaint about a damaged delivery doesn't sit behind forty routine questions.

None of this is a widget bolted to the side of your store. It's an agent working inside it.

Before you start

Two things to have ready.

Admin access to your WooCommerce store. You'll generate a WooCommerce REST API key (via Application Passwords or the WooCommerce API settings) so Omni can read order data and act on it. We walk you through this on the call. It's a few clicks, not a developer task.

Your policies, written down. This is the one real prerequisite. Omni can only follow rules it can read. Your return policy, shipping policy and key product information need to exist as text somewhere: your FAQ page, your policy pages, or a document you hand over. If your return policy is currently "it depends, message me", write it down first. That's not Omni's limitation; it's the thing every AI needs and most setup guides skip.

You don't need to format any of this specially. Omni reads your site and your policy pages as they are.

Setting up Omni on WooCommerce, step by step

The timeline below is honest. Installing the widget is the quick part; getting the agent working well is the week.

Step 1: Connect WooCommerce (day one)

You generate a read/write WooCommerce REST API key and give Omni access. That lets Omni look up orders, check refund eligibility, update order status and process refunds within the limits you'll set next. We do this together on a short call so the permissions are right the first time.

Step 2: Let Omni read your store (day one to two)

Omni reads your storefront, product pages and policy pages. This is how it learns to answer in line with your actual returns window, your real shipping times, and your specific products, not a generic FAQ. You don't re-enter any of this; Omni ingests it. If a policy is missing or ambiguous, this is where it shows up, and it's worth fixing now rather than after go-live.

Step 3: Set the rules (day two to three)

This is the part that matters most and the part a plain chatbot doesn't have. You decide:

• The refund threshold. Below this, Omni handles eligible refunds on its own. Above it, Omni asks you first. Pick a number that fits your margins: £100, £500, whatever's right.
• Escalation triggers. What always comes to you: a complaint naming a staff member, a custom-order question, anything mentioning legal action, a refund above threshold. Define these explicitly rather than hoping the agent guesses.
• Tone. Omni answers in your store's voice. You confirm it sounds like you before any customer sees it.

Step 4: Test against your real store (day three to five)

Ask Omni the questions you already know the answers to. "What's your return policy?" "Where's order #1247?" "Can I return this after three weeks?" Check it reads your live order data correctly, that refunds land where they should, and that the escalation rules fire. Test the edges: a request outside policy, a frustrated customer, a question your content doesn't cover. This is where you build trust in the agent before it's live.

Step 5: Go live (about a week in)

Add Omni's chat widget to your storefront, switch it on for all visitors, and confirm it's appearing and answering. The widget is one surface; Omni is also reachable from the owner companion app, so you can see what it's handling from your phone.

That's the week. The technical setup is a couple of days; the rest is you checking its answers and tuning its limits until you trust it with your customers.

Week one: watch, then loosen

For the first week live, look at the conversations once a day. Three things to check:

• What it's resolving. This is the volume coming off your plate. Most stores see the bulk of "where's my order?" and routine returns handled end-to-end within the first couple of weeks.
• What it's escalating that didn't need to be. If Omni is bringing you things it could safely handle, loosen a rule. If it's handling something you'd rather see, tighten one.
• What your content doesn't cover. If several customers ask the same thing and Omni can't answer it, that's a gap in your policies, not the agent. Add it; Omni picks it up.

The setup isn't a one-time event you walk away from. It's a week of watching, then a steady state where Omni handles the routine and brings you the rest.

When a plain chat widget is enough

We'd rather you set up the right thing than the most expensive thing.

If you're doing under five orders a day, you can answer every message yourself in twenty minutes. A free chat widget and a good FAQ page will serve you better than an agent until your volume grows. If your product is genuinely consultative (bespoke, high-ticket, the conversation is the sale), customer-facing AI is the wrong call, though Omni can still organise your inbox behind the scenes.

The agent earns its place when you're answering the same question for the tenth time, when "where's my order?" is eating your evenings, and when refunds and returns are a daily tax on your attention. If that's your store, the week of setup pays for itself fast.

Setting up Omni

Omni is built for ecommerce SMBs on WooCommerce in the UK and Ireland: one flat monthly rate in GBP, no per-conversation or per-ticket charges. Every capability is included: order updates, returns and refunds to your rules, abandoned cart recovery, inbox triage.

The first 10 founding places are £250/month after a 30-day trial, which is 50% off the standard £500/month. There's no long contract, and you can cancel by email. See pricing for the current detail.

If you want to see how Omni compares to the tools you may already be weighing (Tidio, Gorgias, Intercom), our honest ecommerce AI support comparison is the place to start. If you already know you want an agent on your WooCommerce store, pricing is straightforward and setup takes about a week.