Description
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.
Screenshots
Installation
- Install and activate WooCommerce. Then upload the Wavize ZIP in Plugins > Add New > Upload Plugin and activate Wavize.
- Open Wavize in the WordPress administration.
- Read the service and data information, then click Connect my WooCommerce store.
- Sign in to your Wavize account, or create one and review the subscription conditions.
- With WooCommerce active, approve the read-only authorization request.
- Return with the same WordPress administrator that started the connection.
- Configure the assistant in Wavize and test it on your store after indexing completes.
Requirements: a publicly reachable HTTPS website, single-site WordPress, active
WooCommerce (declared minimum: 7.0), and an administrator with manage_options. Localhost, private networks, inaccessible
maintenance sites and WordPress Multisite are not supported by this release.
The theme must use the standard WordPress enqueue and footer hooks.
Moving from another Wavize connector directory
Do not delete an active connector first. For the supplied private 2.5.1 edition, deactivate it, then install and activate this WordPress.org edition. The connection options are shared and the activation updates their owner. Keep only one edition active. After verifying the connection and widget, the inactive 2.5.1 edition can be deleted: its ownership check protects the migrated settings.
The previous wavize/wavize.php 2.5.2/2.5.3 package uses the same shared options.
Deactivate that edition without disconnecting or deleting it, then activate
this edition in wavize-ai-chatbot-shopping-assistant-for-woocommerce/.
Activation transfers ownership of the saved settings without reconnecting.
If this directory is already installed, use the normal ZIP replacement flow.
Very old versions earlier than 2.2.0 need a compatible private-edition upgrade before migration. Their uninstaller does not understand shared ownership. Deactivation alone does not cancel a Wavize subscription or revoke credentials.
FAQ
-
Is WooCommerce required?
-
Yes. From version 2.5.10, this WordPress.org edition is for WooCommerce stores.
WooCommerce must be installed and active. Existing connection settings are retained
on upgrade, but the widget requires WooCommerce to remain available. -
Is Wavize free?
-
The connector is free and open source. The external Wavize service requires an
account and a paid subscription after any trial. There is no permanently free
SaaS plan. Pricing, trial conditions and quotas are shown by Wavize before subscribing. -
The connection link expired or a previous attempt is stuck. What should I do?
-
Open Wavize in WordPress with the administrator account that started the connection.
When available, use Restart connection to retire only the unfinished attempt
and begin a fresh authorization. Continue with the same Wavize account; there is
no need to register again, purchase another subscription or disconnect an existing
working integration. A request currently being exchanged cannot be restarted.The plugin keeps the pending state outside the transient cache, but still rejects
expired, replayed or mismatched callbacks. A safe diagnostic label can appear on
the local Wavize screen if the return fails. Share that label with support rather
than sharing a full callback URL, which can contain private one-time parameters. -
Do I need WooCommerce?
-
Not to connect the website and display the assistant. Catalogue synchronization,
product recommendations, the shopping cart integration and order tracking require
WooCommerce with the appropriate read-only authorization. -
Where are the plans and usage limits configured?
-
In your Wavize account. This connector does not contain a hard-coded pricing table
or its own paid licence. Plan changes do not require editing this plugin’s files. -
Will the assistant work with every product type?
-
The inline product selector supports simple and variable products. Complex
products or custom add-ons may require the native product page. Developers can
return false fromwavize_widget_product_supportedfor products whose native
form must be retained. Variable products with over 500 children use a native-form
fallback by default. -
Is catalogue synchronization automatic?
-
Yes. Product, variation and stock changes schedule bounded notifications to Wavize.
The service performs indexing in the background, subject to the account limits.
On low-traffic sites, ensure normal WordPress cron execution. No separate plugin
synchronizer or mandatory external cron service is installed. -
How are assisted orders measured?
-
When an eligible conversation results in the service’s signed attribution cookie,
the connector can save that opaque value in private order metadata. Wavize checks
the proof and the order obtained through its read-only API. Opening a chat alone
does not guarantee attribution, and not every store order is counted as assisted.
Neither order totals nor customer details are sent in order-event notifications. -
What happens when the subscription expires or a payment fails?
-
The external service controls access according to the account status. Installing
or reinstalling the connector does not reset a Wavize trial, restore exhausted
quotas or override a suspended account. Manage billing in Wavize. -
What happens on deactivation, disconnection or removal?
-
Deactivation stops the local widget and scheduled jobs, while preserving settings.
Disconnect stops the widget, requests service disconnection and revokes the saved
read-only Wavize WooCommerce key. Failed remote disconnection is visibly retried
up to six times. You can also revoke the key in WooCommerce > Settings > Advanced > REST API.Uninstall removes this edition’s owned connection options and scheduled jobs
and attempts service disconnection and key revocation. If the network is unavailable,
complete disconnection in Wavize and verify the WooCommerce API key manually.Existing attribution metadata remains on orders; expiring short-lived retry
transients may remain until normal WordPress cleanup. No orders are deleted.
Removing the plugin does not cancel a Wavize subscription or erase data already
held by the external service. Use Wavize account controls or contact support. -
Why does a copy of my website need a new connection?
-
Connections are bound to the original site address. A copied site with a different
address must remove its local copied settings and connect independently, without
revoking the original site’s remote connection. -
Can I manage visitor consent?
-
Use your site’s consent solution and the documented
wavize_load_widgetfilter.
The filter can prevent the external widget from being enqueued. This plugin is
not a consent-management platform; page caching must respect the chosen approach.
Suggested disclosure text is added to WordPress Settings > Privacy. -
How are interface translations provided?
-
The plugin uses English source strings and the WordPress.org translation system.
Approved language packs are delivered by WordPress and follow the site or user
locale. Until a language pack is available and installed, the interface falls
back to English. This distribution does not bundle .po or .mo translation files.
Contribute translations at the Wavize translation project.The eight local PDF guides remain included. The hosted assistant uses the
language settings available in the connected Wavize account independently of
WordPress administration translations. -
Is documentation included?
-
Yes. Open Documentation (PDF) from the Wavize administration screen or the
Plugins list. A two-page guide is included locally in English, French, German,
Spanish, Italian, Portuguese, Dutch and Polish. The link follows your WordPress
user language, with English as the fallback. All eight guides can also be
selected under Help & privacy > Documentation (PDF) on the Wavize screen.The PDFs are stored in this plugin’s
docs/directory. They can be read before
connecting a Wavize account; opening a guide does not make a request to Wavize.
Editable Markdown sources are included indocs/source/. Reading local
documentation is independent of the paid external assistant service. -
Where can I get help?
-
Check your connection status in WordPress or contact Wavize.
Never post API secrets, visitor messages, customer details or private payment
links in a public support forum.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Wavize – AI Shopping Assistant & E-commerce Chatbot for WooCommerce” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Wavize – AI Shopping Assistant & E-commerce Chatbot for WooCommerce” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.5.11
- Update the plugin display name to Wavize – AI Shopping Assistant & E-commerce Chatbot for WooCommerce.
- Add eight screenshot captions for the WordPress.org listing. Localized images are maintained in the SVN assets directory.
- Link directly to the Wavize translation project. Continue using native WordPress.org language packs.
- Preserve WooCommerce requirements, connection security, saved settings, storefront behaviour and all eight local PDF guides.
2.5.10
- Make WooCommerce a required dependency for this WordPress.org edition.
- Protect activation on older WordPress versions and pause connection setup and the widget when WooCommerce is unavailable.
- Preserve saved connection settings and the existing WooCommerce authorization, catalogue and order integration.
- Align the administration, readme and eight local guides with the WooCommerce requirement.
2.5.9
- Make administrator capability, POST method and action-specific nonce checks explicit in every local administrative action; reject unauthorized requests with HTTP 403.
- Check administrator permission before handling a pairing or onboarding return; preserve the existing one-time state, original-user, site, expiry and replay protection.
- Keep the settings page read-only; connection ownership is recorded by the existing activation hook.
- Correct the WordPress.org contributor to wavizeai.
- Use native WordPress.org language packs instead of bundling translations or a custom translation loader. Keep translatable strings and all eight PDF guides.
- Clarify that WooCommerce is optional for the assistant and required for shopping features.
2.5.8
- Keep catalogue synchronization automatic. Offer manual recovery only for a failed or overdue automatic update confirmed by Wavize.
- Recheck eligibility before submitting a retry; fail closed when status is unavailable and distinguish a queued job from a no-op.
- Preserve the stable configured site identity fix and all pairing, widget, order-attribution and billing behaviour.
- Update the eight local guides and translated recovery messages.
2.5.7
- Bind pairing, setup continuation and saved-connection checks to the configured site URL rather than a language-filtered navigation URL.
- Prevent site_mismatch when a home_url filter adds parameters or a locale prefix on a public return. Keep public translations and product links unchanged.
- Preserve exact site, original-administrator, expiry, one-time state and concurrent-connection checks; recheck the site after the exchange.
- Keep connection options, commerce notifications, attribution, eight-language translations and PDF guides unchanged.
2.5.6
- Preserve the short-lived pairing and setup continuation with the local pending lock, so clearing a transient cache does not discard a valid connection request.
- Add a nonce-protected Restart connection action for an unfinished attempt; do not require a 20-minute wait or disconnect an existing account.
- Keep expiry, original-administrator, site and one-time exchange checks. Add safe diagnostic labels for rejected callbacks.
- Keep the eight languages, bundled PDF guides, WooCommerce order attribution and external service endpoints.
2.5.5
- Validate and unslash the attribution cookie at the input boundary, without changing valid signed tokens or repairing malformed values.
- Document the intentional use of the legacy WordPress plugin_locale filter for translation compatibility.
- Keep the existing connection, commerce integration, eight-language documentation and translation catalogues unchanged.
2.5.4
- Match the translation domain and bundled catalogue filenames to the directory slug expected by Plugin Check.
- Keep local translations available with installed WordPress.org language packs taking priority.
- Sanitize the attribution cookie after strict validation without altering a valid signed token.
- Sanitize public product URLs at input while preserving same-site and visibility checks.
- Extend safe activation migration checks to all three connector directory editions.
- Preserve all eight PDF guides, connection options, service endpoints, cart and order notifications.
2.5.3
- Bundle a concise two-page PDF guide in each of the eight interface languages.
- Point the Documentation link to the installed guide matching the user locale, with English fallback.
- Add local Documentation access in the Plugins list and an eight-language chooser in Help & privacy.
- Include editable documentation sources; preserve connection, catalogue, attribution, billing and quota behavior.
2.5.2
- Prepare the wavize directory edition while preserving existing pairing, catalogue and attribution protocols.
- Validate product lookup parameters and preserve the public storefront response contract.
- Declare WooCommerce HPOS compatibility for the existing order-object integration.
- Keep WordPress and other plugins’ administration notices visible.
- Refresh the marketing readme, service disclosure, privacy suggestion and eight-language interface catalogues.
- Preserve subscription handling in the external service; no prices or usage limits are hard-coded.
2.5.1
- Preserve all eight Wavize interface languages during native connection and public service links.
- Compatible with the shared R49 onboarding continuation, both from the plugin and from Wavize step 4.
- Existing native credentials, widget settings and catalogue remain unchanged during update.
2.5.0
- Adds public, read-only storefront product and variation data for the R14 shopping widget.
- Uses the visitor’s native WooCommerce Store API cart with nonce protection.
- Preserves connection settings, read-only catalogue permissions and attribution hooks.
- Products needing custom add-ons can use the wavize_widget_product_supported filter to keep their native form.
2.4.4
- Added signed assistant-to-order attribution metadata for classic and block checkout.
- Added debounced, reference-only order notifications so Wavize can verify attributed revenue through the existing read-only WooCommerce API.
- Kept all existing connection, catalogue, interface and multilingual behavior unchanged.
2.4.3
- Added a separately named, cache-isolated WooCommerce layout stylesheet.
- Forced the conversion benefits panel to occupy the full dashboard width, including with stale optimization caches.
2.4.2
- Expanded the WooCommerce benefits panel to a balanced full-width conversion layout.
- Restored the full AI Chatbot and Shopping Assistant plugin name.
- Added localized plugin names and descriptions for all seven bundled translations.
2.4.1
- Repositioned the plugin around WooCommerce shopping assistance and conversion.
- Replaced generic WordPress-assistant promotion with product discovery, recommendations, buying guidance and order tracking.
- Kept setup non-blocking when WooCommerce is inactive without changing connector behavior.
2.4.0
- Added complete Spanish, German, Italian, Portuguese, Dutch and Polish administration translations.
- Preserved English and French support and all existing WordPress and WooCommerce connector behavior.
2.3.0
- Continue Wavize onboarding after connecting a new account from WordPress.
- Renew an expired authorization after setup with the same administrator; OAuth states remain short lived and single use.
- Preserve direct connection for existing Wavize customers and automatic WooCommerce catalogue updates.
2.2.1
- Refined the WordPress and WooCommerce dashboard cards using local platform logos.
- Removed the illustrative chat preview; the dashboard shows actual connection information.
- Added the Wavize menu mark, grey at rest and white on the active item.
- Hide general admin notices only on the Wavize screen; retain Wavize connection messages.
- Preserve the existing connection, catalogue synchronization and visitor widget behavior.
2.2.0
- New local, responsive, accessible administration for website and shopping assistance.
- Keep the existing Connect Wavize flow, options and automatic catalogue synchronization.
- Add exact service URL checks and WordPress-native script enqueueing.
- Bind authorization to the site and initiating administrator; reject replayed callbacks.
- Handle WooCommerce activation changes without silently replacing the connection.
- Cover variation and stock notifications and bounded retry behaviour.
- Add visible disconnection retries, cleanup and safe private-edition migration.
- Document the paid external service, data flows, consent and retention boundaries.
- English source strings and bundled French translation.
2.1.2
- Native WordPress and WooCommerce connection with automatic widget installation.