Skip to content
AskVault Docs
Try Free →

The wc_order_status skill (WooCommerce)

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 4 min read

What the skill does

Same pattern as the Shopify wismo_order_status skill but for WooCommerce stores. Customer asks "where is my order?", bot looks up live data, replies with tracking details. No human involved.

For e-commerce stores running WordPress + WooCommerce, this skill plus the WooCommerce integration deflects 30 to 50% of typical support volume.

The skill is on Growth and above. Growth+

How a typical interaction looks

Customer asks "where's my order?". Bot:

  1. Asks for order number or checkout email.
  2. Customer provides one (or both).
  3. Bot calls WooCommerce REST API live.
  4. Replies with status, carrier, tracking, ETA.

End-to-end: 2 to 5 seconds. The customer sees the bot "typing" briefly before the answer.

Customer identification

The bot needs to match the customer to an order. Two modes:

  • Loose (default). Customer provides either the order number OR the email used at checkout. First match wins.
  • Strict. Customer must provide both, and they must reference the same order. Use for stores where order IDs might be guessable.

Configure under AI Agents > Skills > wc_order_status > Verification Mode.

What's returned

A typical bot response:

Here's the status of your order #4521:

Status: Shipped Carrier: DHL Express Tracking: [tracking-link] Estimated delivery: May 20, 2026 Items: Blue Denim Jacket (M), 1

Anything else I can help with?

Configure which fields the bot includes (line items, prices, shipping address) under Skills > wc_order_status > Response Fields.

Tracking info from shipping plugins

WooCommerce out of the box stores order status and carrier name. Tracking numbers usually come from shipping plugins:

  • WooCommerce Shipment Tracking (official plugin).
  • AfterShip for WooCommerce.
  • TrackShip.
  • Custom themes that store tracking in order meta.

AskVault auto-detects the most common plugins. For a custom setup, map the tracking-number meta key under Skills > wc_order_status > Tracking Field.

Multi-store setup

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

For a multi-brand retailer with 3 WooCommerce stores, you'd have 3 AskVault workspaces. Each one's wc_order_status skill is independent.

Order history depth

WooCommerce stores orders indefinitely by default. AskVault can look up any order regardless of age. For stores with archived order tables (some performance setups archive old orders), the lookup might fail for very old orders. Bot offers to escalate to a human.

Combining with cart_recovery

The cart_recovery skill detects when a visitor adds items to their cart but doesn't check out. Combined with wc_order_status, the same conversation flow covers both pre-purchase ("can I get help with this product?") and post-purchase ("where is my order?") use cases.

Enable both under AI Agents > Skills in the dashboard.

Limits

  • WooCommerce API rate limits. Most hosts throttle at 10 to 60 requests per minute. AskVault stays well under this.
  • Lookup latency. 1 to 4 seconds, host-dependent. Slow WordPress hosts can fail the 10-second AskVault timeout.
  • Order privacy. Read-only access. Bot can never modify orders.

Common pitfalls

Bot says "I couldn't find that order". Order number missing the # prefix, typo, or different store. Bot offers to escalate.

Tracking link missing. Your shipping plugin stores tracking in a custom meta key AskVault didn't auto-detect. Configure the field mapping.

Slow responses. WordPress host is slow on REST API calls. Cache product/shipping zones, upgrade your host, or use a CDN.

Wrong currency. Multi-currency plugins sometimes return prices in store base currency rather than customer's local. Configure currency handling under Skills > wc_order_status > Currency.

FAQ

Can the bot cancel an order?

No. Read-only access prevents this by design. Cancellations escalate to a human via the escalate_to_human skill.

Can the bot apply a discount code to an existing order?

No. Read-only. For order-modifying actions, escalate to a human.

Does it work with WooCommerce subscriptions?

Yes for read-only status lookup. The bot can answer "when's my next renewal?" or "what subscription am I on?". For pause/cancel/upgrade actions, escalate.

What about WooCommerce Bookings, Memberships, or Marketplace extensions?

Custom field mapping covers most. For deep extension-specific logic, use the custom_webhook skill to call your custom logic.

How is this different from Shopify's wismo_order_status?

Same skill pattern, different backend. wismo_order_status calls Shopify's Admin API; wc_order_status calls WooCommerce's REST API. Both produce equivalent customer experiences.

Was this page helpful?