Skip to content
AskVault Docs
Try Free →

WooCommerce integration use cases

Written by , Founder, AskVault · Reviewed by Aashiq
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, tracking, and estimated delivery.

Example:

Your order #2057 (placed May 10) shipped on May 12. Status: in transit. Tracking: [USPS 9400-1234-5678]. Estimated delivery: May 16. Want updates by email when it arrives?

Latency: about 2 seconds. Handles about 30 to 45% of post-purchase tickets. See the wc_order_status skill.

2. Abandoned cart recovery

For WooCommerce stores with cart-abandonment tracking:

  1. Cart abandonment detected (typically after 30 minutes of cart inactivity).
  2. AskVault receives the webhook via the WooCommerce plugin's notification hook.
  3. cart_recovery skill fires. Reaches out via email or WhatsApp (if opted in).
  4. Recovery message offers help:

Hi Alice, you left items in your cart. Need help with sizing, shipping, or returns? I can answer.

Recovery rate: 8 to 15% of carts when message is personalized vs 3 to 5% for generic dunning emails.

Configure the trigger delay and channel preference under AI Agents > Skills > cart_recovery.

3. Product Q&A from the catalog

AskVault auto-indexes your WooCommerce product catalog:

  • Product titles, descriptions, short descriptions.
  • Variations (sizes, colors).
  • Categories and tags.
  • Custom attributes (materials, dimensions, weight).
  • Product images alt text.

Re-sync runs every 6 hours by default; faster sync available on Business.

Sample interaction:

Customer: "Does the women's running shoe come in size 9 wide?"

Bot: "Yes, the Trailblazer Pro Running Shoe comes in women's sizes 6 through 11, with wide and standard widths. Size 9 wide is currently in stock with 3-day shipping."

The bot cites the product URL, letting the customer click to buy directly.

4. Return processing

WooCommerce returns are typically handled via plugins (Returns and Warranty Requests, etc.). AskVault integrates with the common ones:

  1. Customer requests a return.
  2. Bot pulls the order, confirms eligibility (return window, item not final-sale).
  3. If eligible:
    • Generates a return RMA number.
    • Sends a return label by email.
    • Marks the order in WooCommerce as "Return requested".
  4. If not eligible or edge case:
    • Escalates to a human agent with full context.

About 55 to 70% of return requests handle via self-service. The rest escalate cleanly.

5. Customer order history

For identity-verified customers, AskVault can answer questions about their order history:

"What's my last 3 orders?"

Bot pulls from WooCommerce:

  • Order #2057 (May 10): $89.50, shipped, tracking [link].
  • Order #2034 (Apr 28): $123.00, delivered.
  • Order #2010 (Apr 15): $45.00, delivered.

Powered by identity verification. Anonymous visitors can't query other customers' orders.

Setup walkthrough

About 30 minutes:

  1. Install the WooCommerce REST API plugin (often pre-installed on modern WP).
  2. Generate API keys under WooCommerce > Settings > Advanced > REST API. Pick "Read/Write" scope.
  3. Connect to AskVault under Integrations > WooCommerce > Connect. Paste consumer key and consumer secret.
  4. Pick the store URL (e.g., https://yourstore.com/wp-json/wc/v3).
  5. Verify connection. Should succeed within 30 seconds.
  6. Enable skills: wc_order_status, cart_recovery, ticketing_router as needed.
  7. Sync the product catalog. Initial sync takes about 1 minute per 100 products.

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.

AskVault supports both with parallel feature sets. See Shopify use cases for the equivalent 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

Subscribe to:

  • order.created. New order placed.
  • order.updated. Status change (shipped, delivered, refunded).
  • product.created and product.updated. Catalog changes (triggers re-indexing).
  • customer.created. New customer registered.

Configure under Integrations > WooCommerce > Webhooks.

Multi-store support

For workspaces with multiple WooCommerce stores:

  • Connect each store as a separate integration source.
  • Route conversations by domain (which store the customer is on).
  • Available on Business and above.

Useful for multi-brand operators or regional stores under the same company.

Plan availability

  • Free. No WooCommerce integration.
  • Starter. Basic order lookup. Starter+
  • Growth. Full WISMO, cart recovery, product Q&A. Growth+
  • Business. Adds multi-store, return processing, customer order history. Business+
  • Enterprise. Custom integrations, dedicated infra.

Privacy and PCI

Same as other e-commerce integrations:

  • AskVault never sees raw card numbers (PCI scope stays with your payment processor).
  • AskVault reads order data, customer profiles, product catalog. Encrypted at rest.
  • Workspace isolation prevents cross-store data leak.

See GDPR compliance and sub-processors.

Performance considerations

WooCommerce REST API performance varies by hosting:

  • Shared hosting (Bluehost, GoDaddy). API can be slow (1 to 5 seconds per call). Bot answers may take longer.
  • Managed WP (WP Engine, Kinsta). Fast (under 500 ms). Recommended for high-volume.
  • Self-hosted optimized. Fastest with caching and Redis.

For stores serving over 1,000 orders per day, managed WP or optimized self-host is strongly recommended.

Sample customer journey

End-to-end:

  1. Customer browses product page. Widget greets.
  2. Customer asks about sizing. Bot answers from product details.
  3. Customer adds to cart. Cart abandonment timer starts.
  4. Customer leaves without checking out. 30-minute timer expires.
  5. cart_recovery triggers via WhatsApp (if opted in).
  6. Customer comes back, completes purchase.
  7. 2 days later, customer asks WISMO. Bot pulls tracking, answers in 2 seconds.
  8. Package delivered. 7 days later, bot asks for review.

Across this journey, AskVault handles 4 distinct conversation patterns with about 50 to 70% ticket deflection.

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.

Limits

  • Products indexed. Up to 5,000 per workspace.
  • Orders queryable. No hard cap.
  • Sync cycle. As fast as every 1 hour.
  • API rate limit. WooCommerce REST API typically rate-limits at 25 requests per second; AskVault auto-throttles.

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. Configure under Integrations > WooCommerce > Order Number Format.

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

Product changes don't show in bot answers. Sync hasn't run. Trigger manual re-sync, or bump frequency to every hour.

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?

Yes via audience tags. Tag categories you want public vs internal under Knowledge Hub > WooCommerce Source > Audience.

Does the bot edit WooCommerce data?

By default, no. Read-only API access. Write actions (return RMA generation, status updates) require the Read/Write scope.

Was this page helpful?