Skip to content
AskVault Docs
Try Free →

WooCommerce integration use cases

Written by Joseph Russo, Principal Architect, Networks and Tech, AskVault · Reviewed by Allison Chan
Last updated: · 5 min read

1. Order status lookup (WISMO)

The most common e-commerce query. The wc_order_status skill handles:

  1. Customer asks "Where is order #2057?"
  2. Skill queries WooCommerce REST API for the order.
  3. Bot replies with status and tracking.

Example:

Your order #2057 has shipped. Tracking: [USPS 9400-1234-5678].

See the wc_order_status skill.

2. Abandoned cart recovery: not available for WooCommerce

The cart_recovery skill is gated on a connected Shopify store (requires_provider="shopify" in the skill registry). A store running WooCommerce only cannot enable it, and nothing in the WooCommerce connection sends AskVault cart-abandonment events. AskVault doesn't run abandoned-cart recovery on any platform today. Use your store's own abandoned-checkout emails.

3. Product Q&A from the catalog

The WooCommerce integration does not sync your catalog. Connecting the store enables the order skills; it does not import products, and there is no scheduled re-sync. Product answers come from one place only: the crawl of your public storefront that runs when you first set the workspace up, which reads WooCommerce's public store feed.

What that crawl indexes per product:

  • Product name and description (short description used when there's no long one).
  • Price (including price ranges) and currency.
  • Stock status (in stock / out of stock).
  • Categories.
  • Average rating.

Not indexed today: variations (sizes, colors), custom attributes (materials, dimensions, weight), product image alt text, and per-variant SKUs or stock.

Ask for one of those and the bot is instructed not to invent it: every specific fact in an answer is required to come from the indexed material. That is an instruction to the model, not a blocker that inspects the reply before it is sent. But it will not announce the gap either. When a question is only partly covered, the agent is instructed to answer confidently from what the material does cover rather than reply "I don't have that information", so the unindexed detail is simply absent from the reply instead of being called out. The plain "I don't have that information in my knowledge base" only comes back when retrieval finds nothing at all. And only while strict retrieval is on, which is the default but is a switch you own under Knowledge > settings. Full behaviour: what a knowledge gap actually returns.

To update products that changed, select their product pages in the Knowledge page and click Resync selected: AskVault checks each page and re-reads the ones that changed, including the product details the page publishes. If a price change doesn't show up after Resync, see why. To add new products, run Add Source > Web Crawler > Domain Crawl again for your store: it adds product pages that aren't indexed yet, with their product details, but it doesn't re-read pages you already have. Paid plans can set an automatic re-crawl schedule, but until automatic re-crawl is on for your account a scheduled check may not re-read a changed page, so keep using Resync to be sure (details).

Sample interaction:

Customer: "How much is the Trailblazer Pro and is it in stock?"

Bot: "The Trailblazer Pro Running Shoe is $129 and currently in stock."

The bot cites the product URL, letting the customer click to buy directly. Asked about a size or width instead, it answers from what the product page does cover, name, price, stock status, and cites that page. It is instructed not to state a size it hasn't indexed, and it won't flag the missing variation data either, so judge coverage from the cited sources rather than from how confident the answer sounds.

4. Return questions

AskVault cannot process a WooCommerce return. It has no return or RMA call, so it cannot raise an RMA, email a return label, or move an order to "Return requested". (Cancelling an order that hasn't shipped yet is a separate, optional skill that is rolling out; see Let shoppers fix or cancel an order.) Anything of that kind still happens in your WooCommerce admin or your returns plugin.

What the agent can do is answer the question and hand it over:

  1. Customer asks about returning an order.
  2. Bot answers from your indexed returns policy and, where the customer has verified the order, from the order's own status.
  3. escalate_to_human passes the conversation to your team with the order in context, so the refund or RMA is raised by a person.

5. Order lookup for a verified customer

A customer who can verify an order can ask about that order:

"Where is order #2057?"

Bot pulls that order from WooCommerce:

  • Order #2057: shipped, tracking [link].

There is no "list my last 3 orders" capability: the adapter looks an order up by its own number (lookup_order(order_id)), it does not search a customer's order history. A customer who wants a full history is pointed at their WooCommerce account page.

Every order lookup is checked against the order itself before anything is returned: for an order with an email on file, the visitor must give that email. Phone, WhatsApp and cash-on-delivery orders placed without an email cannot yet be looked up by phone number alone; the bot currently needs the order number and an email for every lookup. Knowing or guessing an order number is never enough on its own. See wc_order_status for the exact rule.

Setup walkthrough

  1. Check the WooCommerce REST API is reachable: it ships with WooCommerce on modern WordPress; no extra plugin needed.
  2. Start the connection from the WooCommerce card on the skill that needs it (for example wc_order_status under Automation > Skills). WooCommerce is not listed in the App Directory today, so that's the entry point.
  3. Enter your store URL when prompted (e.g. https://yourstore.com).
  4. Approve access in WooCommerce. AskVault sends you to your own store's authorization screen; WooCommerce issues the Read/Write keys and posts them back. You never paste a consumer key or secret into AskVault: if a page tells you to, it's out of date.
  5. Verify the connection shows as active.
  6. Enable the wc_order_status skill.

There is no catalog-sync step: WooCommerce product answers come from the storefront crawl described under Product Q&A, not from this connection.

Test by asking a sample order question in the Chat Playground.

WooCommerce vs Shopify

When to pick which:

WooCommerce.

  • WordPress-based stores.
  • Lower transaction fees (none from WooCommerce itself; payment processor fees apply).
  • More flexibility (custom plugins, themes).
  • Larger learning curve.
  • Common in India, EU, and SMB segments globally.

Shopify.

  • Hosted SaaS.
  • Better default UX out-of-the-box.
  • More expensive at scale (transaction fees plus subscription).
  • Common in US, Canada, AU.

Feature sets are not identical: cart recovery is Shopify-only, as above. See Shopify use cases for that flow.

Authentication patterns

WooCommerce supports several auth methods:

  • REST API keys (recommended). Consumer key plus consumer secret. Most common.
  • OAuth 1.0a (legacy). Used for older WooCommerce versions.
  • JWT (with plugin). For custom integrations.

AskVault uses REST API keys by default. Rotate keys under WooCommerce admin if compromised.

Webhook events

AskVault subscribes your store to these topics automatically when the handshake completes: there is no webhook screen to configure, and the list is fixed:

  • order.created. New order placed.
  • order.updated. Status change (shipped, delivered, refunded).
  • product.created, product.updated and product.deleted. Catalog changes.

Product webhooks do not trigger re-indexing today: they are recorded, and the storefront refresh steps under Product Q&A are still what update answers. Customer events are not subscribed to at all.

Several stores

Each workspace connects to one WooCommerce store. If you run several stores or brands, give each its own workspace: Growth includes 5 workspaces and Business 15, each with its own knowledge base, widget and store connection.

Plan availability

  • Free. No WooCommerce integration.
  • Starter. No WooCommerce integration.
  • Growth. Full WISMO and product Q&A. Growth+
  • Business. More workspaces (15), so more stores. Business+
  • Enterprise. A custom allowance, quoted by sales.

Privacy and PCI

Same as other e-commerce integrations:

  • AskVault never sees raw card numbers (PCI scope stays with your payment processor).
  • AskVault reads two things from your store: its status endpoint, and an individual order when a customer has verified that order. It does not read customer profiles and it does not pull your product catalog through this connection.
  • Encrypted at rest.
  • Workspace isolation prevents cross-store data leak.

See GDPR compliance and sub-processors.

Performance considerations

Every order answer waits on a live call to your WooCommerce REST API, so your hosting sets the speed:

  • Shared hosting (Bluehost, GoDaddy). API calls are slower, and bot answers take longer.
  • Managed WP (WP Engine, Kinsta). Faster. Recommended for high-volume stores.
  • Self-hosted optimized. Fastest with caching and Redis.

We have not published a benchmark for any of these tiers; measure your own store's /wp-json/wc/v3/ response time if you need a number.

Sample customer journey

End-to-end:

  1. Customer browses product page. Widget greets.
  2. Customer asks about price and stock. Bot answers from the indexed product page and cites it.
  3. Customer buys.
  4. Two days later, customer asks WISMO. Bot verifies the order and answers with the live status and tracking.
  5. Customer asks about returning it. Bot answers from your policy and escalates to your team to raise the RMA.

Planned features (on the roadmap)

Documented for accuracy:

  • Subscriptions plugin support. Today, one-time orders. WooCommerce Subscriptions integration planned.
  • Multi-currency display. Today, customer's currency from the order. Inline conversion planned.
  • Pre-order handling. Today, treated as standard. Native pre-order status messaging planned.
  • Custom-field-aware product Q&A. Today, standard product fields. Custom ACF field support planned.
  • Cart recovery for WooCommerce. Today, Shopify only.
  • Returns (RMA). Not available. Address fixes and cancel-before-shipping are optional skills that are rolling out.

Limits

  • Products indexed. Bounded by your plan's content cap (MB), not by a product count: see plans and limits.
  • Orders queryable. One at a time, by order number, after verification.
  • Refresh. Manual: Resync selected for changed product pages (small changes can be missed), Domain Crawl again for new ones. Paid plans can set an automatic re-crawl schedule, but until automatic re-crawl is on for your account a scheduled check may not re-read a changed page, so keep using Resync to be sure (details).
  • API rate limit. Set by your own WooCommerce host, not by AskVault.

Common pitfalls

API connection fails. Permalinks not set to "pretty" in WordPress. Set under Settings > Permalinks to anything other than "Plain".

Bot doesn't recognize orders. Order number format mismatch: check the number the customer is quoting is the WooCommerce order ID.

Slow API responses. WooCommerce host underpowered. Move to managed WP or enable WP caching plugins.

Product changes don't show in bot answers. Nothing refreshes your storefront on its own, and running the Web Crawler again skips pages you already have. Select the changed product pages in the Knowledge page and click Resync selected; if a price change still doesn't show up, see why. For new products, run Add Source > Web Crawler > Domain Crawl again for your store.

FAQ

Does this work with WooCommerce Subscriptions?

Today, basic order lookup works. Recurring subscription management (cancel, change plan) is on the roadmap.

Can I use this with non-WooCommerce WordPress?

For Q&A on WordPress content (no commerce), use WordPress integration. Commerce features require WooCommerce.

Does this work with WP Engine, Kinsta, etc.?

Yes. Any host running WooCommerce with REST API enabled works.

Can I limit bot access to specific product categories?

Partly. The connection does not import products, so product answers come from crawled pages. Exclude those pages from the crawl, or set their source's audience to internal in Knowledge, which hides them on every public channel.

Does the bot edit WooCommerce data?

No. The only thing AskVault writes to your store is its own webhook subscriptions, created and removed during connect and disconnect. The bot cannot change a status, issue a refund or raise an RMA today. Address-fix and cancel-and-refund skills are built but not yet available.

Was this page helpful?

Product recommendations in chat

Once your catalog is in, your agent can answer product, price, stock and "what do you recommend" questions with real products: cards carrying the price, availability and a link straight to the product page on the web widget, Block Kit cards in Slack, and the same details as text on WhatsApp and Telegram.

Everything it shows comes from the synced catalog. If a visitor asks for something you do not stock, the agent says so rather than inventing a product or a price. Check Knowledge › Products to see exactly which products the agent can see.

Your WooCommerce products are read from your store's public Store API feed when AskVault crawls your site: there is no separate product connection to set up.

This is the recommend_product skill. It is off by default: turn on Product Recommendations on the Skills page for the workspace you want it on. (In preview: if it is not in that list, it is not switched on for your account yet.)