A WooCommerce store is a WordPress site first and a store second, and the questions customers ask reflect that. Some are about the site itself — shipping policy, return window, whether a product's in stock. Others are about a specific order that's already been placed. Most support tools handle one of these well. AIVA handles both from the same conversation.
Two kinds of questions, one widget
A customer messaging a WooCommerce store might ask "do you ship to Kochi?" in one breath and "where's my order from Tuesday?" in the next. The first is a content question — the kind of thing already written down somewhere on your site or in your policies. The second needs a live look at actual order data. AIVA is built to answer both without the customer having to know which kind of question they're asking, or which system holds the answer.
That split is easy to underestimate until you look at a real transcript. A single conversation regularly moves between the two without the customer noticing any seam — the same way it would with a good human staff member who happens to know both the store's policies and today's dispatch log.
What connects, specifically
- Order status and tracking, pulled from WooCommerce order data — not a generic "3-5 business days" line
- Shipping, returns, and product questions, answered from what you've told AIVA about your business
- Booking, if your store also takes appointments or consultations alongside product sales — a salon selling retail products through WooCommerce while also booking chairs is a common combination
- Basic order details — what was ordered, the delivery address on file, whether a coupon applied — the same lookups a staff member would otherwise do by opening the order in wp-admin
- A hand-off to you for anything that isn't a straightforward lookup — a damaged item, a refund dispute, an order that genuinely went missing
A conversation that shows the split
Here's what that actually looks like in one exchange. A customer opens the widget and asks "do you have the ceramic planter in the blue glaze back in stock?" — a content question, answered from your product and inventory info. Two messages later, same conversation: "also, my order from last week hasn't shipped yet, can you check?" — now it's an order question, and AIVA looks up the actual WooCommerce order instead of guessing. The customer never had to restart the conversation, open a different tab, or explain that they'd already asked something else. It's one thread, answered from two different sources, without the seam showing.
It's still just a WordPress site
Because WooCommerce runs on WordPress, adding AIVA doesn't mean adopting a new platform or migrating anything. It's the same widget embed used on any WordPress site — three lines of code, placed once — that now also has order data to draw on. If you've already got a page builder, a caching plugin, and a theme you like, none of that changes.
The order-data connection is separate from the widget embed, and neither depends on the other. You could run the widget for content questions alone and skip the WooCommerce connection entirely if you don't need order lookups — though for an active store, that's usually the whole point of connecting it.
It pairs with your payment gateway too
Order status is only half of what customers ask about — the other half is the payment itself. If your store takes payments through Razorpay or Stripe, AIVA connects to those separately, so "did my payment go through" gets answered from the actual transaction, the same way "where's my order" gets answered from the actual shipment. Connect one, both, or neither — they're independent integrations, useful together for a store where checkout questions and delivery questions both land in the same inbox.
What doesn't come from WooCommerce
Worth drawing the line clearly. AIVA reads order and product data from WooCommerce — it doesn't edit products, change prices, adjust stock counts, or modify an order itself. A refund, a cancellation, an address change on an order already placed — those are handed to your team rather than actioned automatically, because each one is a judgment call about that specific order, not a lookup. The integration is built to answer questions fast, not to run your store's back office.
What data flows where
Worth spelling out plainly, since "connect your store" can sound vaguer than it is. Order data flows one direction: from WooCommerce into AIVA, read-only, so a conversation can reference a real order the moment someone asks about it. Nothing flows back into your store's database beyond the connection itself — AIVA isn't writing rows into WooCommerce, adjusting anything in wp-admin, or leaving a footprint anywhere a customer or another plugin would see.
The customer detail inside that order data — name, delivery address, phone number, what was bought — stays scoped to answering that specific customer's own questions in that conversation. It isn't exported to a third party or repurposed for anything beyond the support conversation it was pulled in to answer. If you also connect Google Sheets or a CRM for your own records, that's a separate, deliberate connection you set up yourself — WooCommerce order data doesn't automatically end up anywhere beyond AIVA answering the question in front of it.
Common questions about the setup
A few things worth knowing before connecting. Extensions that add to WooCommerce's order system — subscriptions, deposits, appointment add-ons — are generally visible the same way standard orders are, since they still create an order record inside WooCommerce that AIVA reads from. Multi-language stores work the same way the widget does elsewhere — AIVA answers in the language the customer uses, regardless of which currency or default language the store displays. And connecting WooCommerce doesn't touch your checkout flow or page speed, since it's a data read on the backend, not a script added to the storefront beyond the widget itself.
Setup
Connect WooCommerce from your AIVA dashboard settings — a store URL and the usual authorization step — and order data starts flowing in, read-only, the same day. The widget itself installs the same way it would on any WordPress site, and the two steps don't depend on each other — do them in either order, or skip the order connection entirely if content answers are all you need.
Who this is for
Smaller WooCommerce stores where the same one or two people handle both "update the homepage banner" and "answer the customer email" — which is most of them. If a dedicated support platform feels like overkill for your order volume but your inbox says otherwise, this is the middle option — support that scales with a store still run by its owner, not a team you have to hire ahead of demand. It also fits stores that sell on Shopify as a second channel; the underlying pattern — content questions plus order questions, one widget — is the same regardless of which cart software is actually running.
Read more on the WordPress integration if you're setting up the widget for the first time, check SMS if that's a channel your customers already use, or start free to connect your store. Full setup steps are in the docs, and the rest of what AIVA connects to is on the integrations page.