Yazoh AI For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
After connecting, the plugin sends the store’s product categories, products,
customers (users with the customer role) and orders – with their line items –
to Yazoh, which uses them for its AI features.
External services
This plugin relies on one external service: Yazoh (https://www.yazoh.io), the
AI service the store connects to. The plugin does not work without it. It
contacts no other service, loads no remote scripts, styles or fonts, and
nothing is sent until an administrator chooses “Connect to Yazoh”.
All requests go from this site’s server to https://www.yazoh.io (a developer
can point them at another Yazoh deployment with the YAZOH_WC_API_BASE_URL
constant, see Development). Every request carries this site’s home address in
its User-Agent header. After connecting, requests also carry the connection
token Yazoh issued.
What is sent, why, and when:
- Connecting (when an administrator presses “Connect to Yazoh”): the store’s
home address, the address Yazoh returns to after sign-in, the plugin and
WooCommerce versions, a random installation identifier and secret, and
one-time values that secure the sign-in (PKCE challenge, state, a hash of a
browser-binding secret). The administrator’s browser is then sent to Yazoh
to sign in and choose the store; it carries the browser-binding secret in a
form post. On return, a one-time code is exchanged for the connection token.
Purpose: link this store to the administrator’s Yazoh account. - Connection status (when “Refresh status” is pressed) and disconnecting
(when “Disconnect” is pressed, or the plugin is deleted while connected):
the connection token only. Purpose: show whether Yazoh still accepts the
connection, and revoke it. - Synchronising (when “Sync now” or “Full resync” is pressed, then in the
background through Action Scheduler until the run completes): the store
currency, then categories, products, customers (users with the customer
role) and orders with their line items, as the WooCommerce REST API (v3)
represents them – including customer names, email addresses, phone numbers
and billing/shipping addresses. Passwords, session tokens and
credential-like fields are removed before sending. Purpose: give Yazoh the
store data its AI features analyse. - Yazoh Copilot (when a shop manager or administrator asks a question on
WooCommerce > Yazoh Copilot): the question, the conversation it continues,
and, when given, feedback on an answer. Opening the screen lists earlier
conversations from Yazoh. Purpose: answer questions about the store’s data. - Storefront shop assistant (when a shopper sends a message in the chat): the
text of the question only, sent by this site’s server. No shopper identity,
cookie, IP address or order data is sent, and Yazoh does not store the
question or the answer. Purpose: answer product questions from the
synchronised catalogue.
Yazoh is a service of Bugtreat Technologies. Its terms and privacy policy
apply to this data:
- Terms & Conditions: https://www.yazoh.io/terms
- Privacy Policy: https://www.yazoh.io/privacy
Storefront shop assistant
Once the store is connected, a “Chat with us” button appears on storefront
pages. Shoppers can ask about products, prices and availability; answers come
from Yazoh’s shopper assistant and are grounded in this store’s synchronised
catalogue. The browser talks only to this site (admin-ajax); the connection
token never leaves the server.
It is not shown while WooCommerce’s “Coming soon” mode is on, except to shop
managers and administrators. Order lookup is not part of the chat: shoppers are
asked to contact the shop about orders. Developers can turn the widget off with
the yazoh_wc_shop_assistant_enabled filter.
Encryption
The connection token and installation secret are stored encrypted with
libsodium, from the PHP sodium extension or the sodium_compat library that
WordPress includes. If neither is available the plugin pauses: it shows an
administrator notice, stores no credential, keeps any existing connection, and
does not affect the storefront.
What is not synchronised
- Product variations as separate records (a variable product lists its
variation ids). - Stock per location (a product’s own stock quantity and status are sent).
- Deletions: a product or order deleted in WooCommerce stays in Yazoh.
Usage
WooCommerce > Yazoh AI.
- Connect to Yazoh (administrators): sign in to Yazoh and choose the store.
- Sync now: sends what changed since the last completed synchronisation.
- Full resync: sends everything again.
Synchronisation runs in the background with Action Scheduler, one page at a
time, and resumes from where it stopped after a temporary failure. Operational
log lines (ids, counts and error codes only) are written to
WooCommerce > Status > Logs, source “yazoh-ai”.
Development
Set define( 'YAZOH_WC_API_BASE_URL', 'https://yazoh.test' ); in wp-config.php
to use a development Yazoh deployment. Yazoh refuses store addresses on
loopback or private networks, so a store on localhost cannot complete a real
connection.
Tests (PHP CLI, no Composer needed):
php tests/run.php– unit tests with WordPress stand-ins and a scripted
Yazoh.php tests/integration/woocommerce.php [dump-dir]– against the WordPress
install this plugin sits in, inside one database transaction that is rolled
back; outbound HTTP, mail and WooCommerce file logging are disabled for the
run. Requires every table to be InnoDB. Does not contact Yazoh.php tests/contract/backend-contract.php [--backend=DIR] [--bodies=dump-dir]- runs the request bodies through the E-Commerce AI backend’s own
PushBatchValidator and WooCommercePushMapper (needs that checkout; skipped
otherwise).
- runs the request bodies through the E-Commerce AI backend’s own
Screenshots
No screenshots provided
