Wavize – AI Shopping Assistant & E-commerce Chatbot for WooCommerce

Turn product questions into confident purchases.

Your visitors have questions before they buy. Wavize connects your WooCommerce
catalogue to an AI shopping assistant that helps them find relevant products,
understand their options and move toward checkout, right on your store.

Recommend products from your connected catalogue, answer buying questions,
guide shoppers to product pages and help existing customers track orders after
verification. Configure the assistant in Wavize; the connector installs the
widget and notifies the service when your catalogue changes.

The plugin is free. The external Wavize service is paid. A Wavize account and
an active subscription are required after any trial. There is no permanently
free SaaS plan. Review the plans and trial conditions,
including payment-method and automatic-renewal requirements, before subscribing.
No separate WordPress plugin licence is required.

Help shoppers choose, not just search

• Product discovery: understand a shopper’s request and suggest relevant products.
• Answers before purchase: use the connected catalogue and knowledge configured in Wavize to answer buying questions.
• Product cards and variants: show product information and supported variants in the shopping widget.
• Native cart access: guide visitors to their WooCommerce cart and add supported products through the native cart flow.
• Order tracking: help customers check an existing order after reference and email verification.
• Automatic catalogue updates: notify Wavize when products, variations or stock change.
• Assisted-sale measurement: provide signed attribution metadata and order-reference notifications for the Wavize analytics service.
• Multilingual experience: translatable plugin administration through WordPress.org language packs, plus local PDF guides in eight languages.

Features in the hosted widget depend on your Wavize plan, account status,
configuration and product types. AI responses may be inaccurate; review your
sources and test important shopping journeys. No increase in sales is guaranteed.

Connect your store without copying keys or scripts

Open Wavize in WordPress, choose Connect my WooCommerce store, sign in to
Wavize and approve read-only catalogue and order access. Initial indexing starts
after authorization. View the connection status, indexed product count and last
completed synchronization from the local dashboard.

This WordPress.org edition requires WooCommerce to be installed and active.
Install and activate WooCommerce before activating Wavize. If WooCommerce becomes
unavailable, new connections and the widget are paused; saved connection settings
are preserved. Activate WooCommerce again to resume using the connector.

Built around your store’s existing workflow

The connector uses WordPress enqueueing and scheduled events, and WooCommerce
order objects for attribution. Both classic checkout and the Store API checkout
hook are supported. The order-storage integration declares HPOS compatibility;
it does not write attribution directly to the WordPress posts tables.

The external service manages the assistant, catalogue processing, conversations,
usage quotas and subscription access. This plugin does not replace your checkout,
charge customers or edit your product catalogue through its service connection.

External services and data

This plugin is a connector to Wavize, which supplies
the hosted AI processing, content indexing and conversation management.
The service is essential; the plugin is not a standalone AI engine.

Before connection: the plugin does not contact Wavize. Its administration
styles, scripts and images are local. There is no plugin analytics or tracking.

When you click Connect Wavize: the plugin sends your public site URL,
connector version, interface language and a temporary random authorization
state to https://wavize.com/commerce/native/launch. Your browser is redirected
to Wavize for sign-in and approval. The callback is verified against the
initiating WordPress administrator. A one-time local state and result code are
sent to /commerce/native/exchange to obtain the public widget token and, for
WooCommerce, the private connection credentials.

WooCommerce authorization: the official /wc-auth/v1/authorize flow asks
for read-only API access. WooCommerce sends a key, secret and key identifier
directly to the Wavize callback URL. Read-only access can include product and
personal order information; it is not restricted to public products. Wavize
uses catalogue data (identifiers, names, descriptions, prices, images, product
URLs, categories, attributes, variations and availability) and accesses order
information for customer-verified tracking. It does not request write access
to products or orders.

After WooCommerce connection: authenticated notifications, status requests,
manual resynchronization and disconnection use
https://wavize.com/commerce/native/connections/{id}/event. Event requests
contain the event name, connector version and a private bearer credential.
Product-change notifications do not contain the product or customer records;
the Wavize service reads the catalogue through the approved WooCommerce API.
Notifications are debounced; failed notifications have bounded retries.
Administration status polling is bounded and pauses in background tabs.

Shopping attribution: when the Wavize service has placed its signed,
short-lived wavize_attribution cookie after an assistant conversation, this
connector copies that opaque token into the private _wavize_attribution order
metadata during classic or block checkout. For attributed orders, new-order,
refund and status-change notifications contain only the order reference; Wavize verifies
the signed token and reads the authoritative order through the approved
read-only WooCommerce API. The connector never sends order totals, products,
customer details or the attribution token in an event notification. Identical
notifications are debounced and failed notifications have bounded retries.

On the public site after connection: the plugin loads the documented
Wavize service script from https://wavize.com/chatbot/js. The visitor browser
then communicates with Wavize to operate the assistant. Depending on the
features enabled in Wavize, this can include the current page URL, messages,
conversation/session identifiers, technical browser and connection information
(including IP address), information entered into contact forms and optional
voice inputs. Wavize supplies the service’s runtime and related resources.
The widget token is a public installation identifier, not a merchant API secret.
The connection screen explicitly asks the administrator to authorize the assistant
and any Wavize branding link enabled for the selected plan on the public site.

The site owner is responsible for appropriate visitor information and consent
where required. Suggested privacy text is available in WordPress Settings >
Privacy. Developers may use wavize_load_widget to prevent enqueueing the
widget until the site’s consent mechanism allows it. This is not a bundled
cookie-consent solution; ensure any page cache respects that choice.

Terms of service
| Privacy policy
| Contact Wavize

The local ?wc-ajax=wavize_product endpoint supplies only published, visible,
non-password-protected product data needed by the shopping widget. It does not
return order records, customer details, API secrets or attribution tokens.
Adding items uses the visitor’s WooCommerce Store API cart, not the service’s
read-only merchant API key. For subscriptions, bundles, configurable add-ons
or other unsupported product types, keep the store’s native product form.

License

Copyright 2026 Wavize. Plugin code, administration styles, scripts and included
Wavize branding assets are distributed under GPLv2 or later. Third-party platform
marks retain their licences and trademark rights; see ASSETS-LICENSES.txt.
No endorsement by WordPress, WooCommerce or their owners is implied.