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.

1. Install and activate WooCommerce. Then upload the Wavize ZIP in Plugins > Add New > Upload Plugin and activate Wavize.
2. Open Wavize in the WordPress administration.
3. Read the service and data information, then click Connect my WooCommerce store.
4. Sign in to your Wavize account, or create one and review the subscription conditions.
5. With WooCommerce active, approve the read-only authorization request.
6. Return with the same WordPress administrator that started the connection.
7. 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.

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.