Skip to content
AskVault Docs
Try Free →

How to connect WooCommerce to AskVault

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

What this integration unlocks

One skill: wc_order_status. Customer asks "where is my order?", the bot looks up the order live from WooCommerce by order ID + email, and replies with status and a tracking link when one is available.

Available on Growth and above. Growth+

Setup

Five minutes end-to-end.

  1. In AskVault, open AI Agents > Skills > wc_order_status. Click Enable, then Connect WooCommerce.
  2. Enter your store URL when prompted (e.g. https://shop.example.com).
  3. You're redirected to your store's WooCommerce authorization screen. Sign in as an admin or shop manager and approve the request.
  4. WooCommerce redirects you back to AskVault and provisions the API credentials automatically — there's nothing to copy or paste. Connection shows active, and AskVault auto-subscribes to the order and product webhooks it needs.

Test by asking the bot "where's my order?" with a known test order ID and the matching email. Bot should return live status.

Permissions

WooCommerce's app-authorization handshake only offers a single read/write grant for this flow — there's no narrower read-only option to request. In practice, AskVault only issues GET requests to look up a single order by ID for wc_order_status; it never calls a write endpoint.

Store URL formatting

The store URL must include the protocol and domain. Examples:

  • https://shop.acme.co (correct)
  • https://acme.co/shop/ (correct, if WooCommerce runs at a subpath)
  • acme.co (wrong, missing protocol)
  • https://acme.co/shop (wrong, missing trailing slash for subpath stores)

If you're not sure, paste your store's homepage URL and AskVault auto-corrects.

What the customer sees

When a customer asks "where is my order?":

Sure! Could you share your order number and the email you used at checkout?

Customer responds. Bot looks up via WooCommerce API. About 2 to 4 seconds later:

Here's the status of your order #4521:

Status: Shipped Tracking: [tracking-link]

Anything else I can help with?

If the order can't be found (wrong number or different email), the bot offers to escalate to a human.

Verification mode

wc_order_status always requires both the order ID and the email on the order — there's no order-number-only lookup. If the email doesn't match the order's billing email, the bot won't return the order details.

Multi-store setup

Each WooCommerce store needs its own AskVault workspace and its own connection. Cross-store lookups aren't supported. For a 3-store retailer, you'd have 3 separate AskVault workspaces.

Shipping and tracking

The bot returns a tracking link when one is available. It reads the _wc_shipment_tracking_items order meta field used by the WooCommerce Shipment Tracking plugin (and compatible plugins that write to the same field) — no carrier name is currently surfaced, and there's no configurable field-mapping UI. If your tracking plugin writes to a different meta key, the tracking link won't be picked up today.

Limits

  • WooCommerce REST API rate limits. No hard limit, but most WordPress hosts throttle at about 10 to 60 requests per minute. AskVault stays well under this for normal traffic.
  • Order history depth. No hard cap on the WooCommerce side, but very old orders (3+ years) might be archived in some setups.
  • API timeout. AskVault times out the lookup at 15 seconds. Slow WordPress hosts may fail the lookup.

Common pitfalls

Connection shows an error after approving. The store's callback POST to AskVault didn't complete (a firewall or security plugin blocking outbound requests is a common cause). Retry the connect flow; if it keeps failing, check your site's outbound-request logs.

"Where's my order" fails to find a match. The email you asked for doesn't match the order's billing email exactly, or the order ID is wrong. Both are required — there's no order-number-only lookup.

Slow lookups (>5 seconds). WordPress host is slow. AskVault can't speed this up — consider a faster WooCommerce host.

Tracking link missing. Your shipping plugin doesn't write to the _wc_shipment_tracking_items meta field, so AskVault has nothing to read. There's no configurable mapping today.

FAQ

Does this work with WooCommerce subscriptions?

Not today — wc_order_status looks up orders only; there's no subscription-status lookup. Subscription questions escalate to a human.

Can the bot apply a discount code?

Not for WooCommerce coupons. The discount_negotiator skill applies Stripe coupons and requires the Stripe integration, not WooCommerce.

What about WooCommerce extensions like WooSubscriptions or WooMemberships?

Not supported by wc_order_status today — it only reads standard order fields plus the shipment-tracking meta key above. For anything extension-specific, use the custom_webhook skill to call your own logic.

Does the bot work with WooCommerce Multistore?

Each store needs its own connection and its own AskVault workspace. Cross-store lookups aren't supported.

Is there a webhook for real-time order updates?

Yes, and you don't need to configure it — AskVault registers order.created, order.updated, product.created, product.updated, and product.deleted webhooks on your store automatically when you connect.

Was this page helpful?