Detailed explanation
WooCommerce is the trickier platform to build AI chat for. Unlike Shopify, every store runs its own WordPress + WooCommerce + plugin stack — so an AI chat needs to handle wide variation in catalog schema, hosting, and CDN configuration.
The bar to clear:
- A maintained plugin available from WordPress.org (or via direct install).
- Full catalog sync via the REST API on install, then incremental updates via webhooks.
- Compatibility with common WooCommerce extensions (Subscriptions, Bookings, Memberships).
- Server-side webhook auth using HMAC + per-store secrets.
- A widget that doesn't break under Cloudflare or aggressive plugin caches.
Why Zubby wins for WooCommerce
We treat WooCommerce as a first-class connector, not an afterthought. The plugin is constant-time authenticated, the catalog sync handles 50k SKUs without timeouts, and the widget is ~28KB so it loads cleanly even on the most plugin-bloated WordPress site.
Why this matters
Most "AI chat" plugins on WordPress.org are wrappers over a generic LLM with no grounding. They hallucinate prices, invent shipping rules, and embarrass your brand. A grounded WooCommerce-native AI is a different category of product.
How Zubby does it
The Zubby WooCommerce plugin authenticates each request to our SaaS with a Bearer token + Store ID header, checked in constant time against an encrypted-at-rest credential. Every product update triggers a webhook that re-embeds the affected row within minutes. The chat surface is grounded — if it can't find the answer in your data, it escalates rather than improvising.