WooCommerce integration

The WooCommerce integration ships as a WordPress plugin that authenticates to the Zubby SaaS using a Bearer token + an X-Store-ID header. Once paired, the plugin syncs your catalog over WooCommerce’s REST API, exposes an endpoint the SaaS uses to pull live cart and customer data, and auto-injects the widget on every storefront page.

Get the plugin

From your Zubby dashboard click Connect store → WooCommerce. We generate a one-time setup code and a download link for the latest plugin build, both scoped to the workspace you’re logged into.

Install in WordPress

1. 1

   Open the WordPress admin

   Go to Plugins → Add new → Upload plugin.
2. 2

   Upload the zip

   Choose salespilot-ai.zip, click Install now, then Activate.
3. 3

   Open the settings page

   Find Zubby AI in the WordPress sidebar, or visit Settings → Zubby AI.

Pair with setup code

Paste the six-character code from the Zubby dashboard and click Pair. Behind the scenes the plugin:

1. Calls /api/v1/stores/woo/pair on the SaaS with the code and your site URL.
2. Receives a long-lived store token, encrypts it with the WordPress salts, and stores it in the wp_options table.
3. Registers itself as a webhook endpoint for product, order, and customer events.

API base URL

The plugin defaults to https://api.zubbyai.com. If you’ve been routed to a private region (EU, AU) by support, change it under Advanced → API base URL before pairing.

First catalog sync

Click Sync now. The plugin paginates through products in batches of 100, posts them to the SaaS, then waits for the embedding worker to finish before flipping your store status to green. Big stores stream for a few minutes; you can leave the page and check back.

Verify the wiring

Two health checks confirm the plugin is talking to Zubby:

• The settings page header shows Paired in green with your store ID and the time of the last successful ping.
• Dashboard → Catalog in Zubby lists the product count you’d expect.

How the widget gets onto your storefront

By default the plugin injects the widget loader via WordPress’s wp_footer hook on every storefront page. If you’ve built a custom theme that doesn’t call wp_footer, see the widget bridge guide for manual injection.

Troubleshooting

Four issues account for almost every WooCommerce install problem:

Self-hosted plugin notes

The WooCommerce plugin ships as a standard WordPress plugin archive. If you’re forking it for a private region or air-gapped host, point your build step at your fork’s release archive — and keep the plugin’s text domain and option keys unchanged so upgrades and stored credentials keep resolving.

Sample API call (advanced)

If you want to verify the auth from the WP-CLI:

# From WP-CLI on the WooCommerce host
wp option get salespilot_ai_store_id
wp option get salespilot_ai_token | head -c 8
# → sk_live_

curl https://api.zubbyai.com/api/v1/plugin/woocommerce/ping \
  -H "Authorization: Bearer $(wp option get salespilot_ai_token)" \
  -H "X-Store-ID: $(wp option get salespilot_ai_store_id)"
# Expected: { "ok": true, "lastPingAt": "2026-..." }

Uninstalling

Deactivate the plugin from WordPress’s Plugins page. The Zubby SaaS receives a teardown event, revokes the store token, and clears the encrypted secret from wp_options. Workspace analytics persist for 90 days in case you reinstall.