WooCommerce shopping and privacy

What you’ll accomplish

Understand what the assistant can do, what shoppers must confirm and where native store access is required.

Finish with

Shopping help with clear permissions and recovery

This guide describes the WooCommerce development candidate. Use it only when enabled for your project and approved store/plugin combination. Start with Connect WooCommerce.

Product knowledge and current prices

Public products, their options and translations use the same WordPress source and indexed-word allowance as public pages. Complete product families publish together; a partially imported family is not offered as a complete selection. Draft, private, hidden, password-protected and coming-soon products are excluded. Private orders and cart, checkout and account pages do not become public Knowledge.

Descriptions and live shopping details have separate update health. A healthy page check cannot make an unverified product current. Temporary outages have a maximum 72-hour descriptive grace from the last verified update. Confirmed removal or lost authorization stops affected use immediately. A healthy deliberate pause is different from a connection outage; unchanged descriptions can remain usable while native price and cart checks still happen when needed.

Prices, stock and native quantity limits come from the shopper's current store context. Supported tax/currency/options must agree before a change is sent. Subscriptions, bundles, required add-ons or unfamiliar pricing/language setups may need the native product page. A fallback link is not permission to invent an option or promise a price.

Cart changes and checkout

The assistant works with the shopper's existing native cart. Adding a product, changing quantity, removing an item and applying/removing a shopper-provided coupon require an informed click. If the shown price, options or quantity terms change, the shopper reviews a new confirmation. A model request alone cannot complete the change.

An interrupted response can leave the result unconfirmed. Ask the shopper to check the native cart and use the offered review path. Repeating the same request does not authorize another send. Never report an uncertain request as completed. The store decides coupon eligibility and combinations.

Checkout links open the native store checkout. Chat4U does not collect card details, create/pay an order or issue a merchandise refund through these tools. A checkout link or cart action is not evidence of a purchase.

Private order help

Customers use native sign-in or the dedicated guest-verification form. The guest form sends its email, order selection and code to the store, using the store's transactional mail setup. Do not ask for a password or code in ordinary chat. A successful guest check authorizes one order for ten minutes; private per-turn proof expires after a minute and is checked again before the answer is released.

Only minimized authorized status, items and supported tracking details are used. Those results may reach the configured AI processor for that answer. Private answers are replaced by a neutral marker in durable chat history. Information the visitor independently types into ordinary chat still follows normal chat handling. A sign-in or verification failure must not reveal whether someone else's order exists.

Optional purchase measurement

Measurement starts off and requires both the merchant's settings and supported explicit visitor permission. Current adapter qualification is limited to the listed WP Consent API/Complianz versions and WooCommerce Stripe captured-payment contract. It is not universal gateway or consent-manager support. Other payment methods, test-mode charges, manual paid statuses and checkout clicks do not prove a measured sale.

Qualified payment and refund updates revise associated totals. Turning measurement off stops updates to past totals, so later refunds may be absent. Visitor withdrawal removes attributed evidence and prevents older references from reviving after a later Allow. Necessary minimal receipts for uncertain cart changes are separate. Association with a chat does not prove that the chat caused a sale.

Removing access and data

Removing the source from an assistant stops that assistant's store answers and shopping help; its other sources still work. Removing the whole Knowledge source does not disconnect the site or cancel service billing, and automatic checks do not recreate the source. Turning off public products also disables dependent product-card/cart/coupon help. Native checkout and order help can remain separately enabled when their access permits it.

Expiry blocks access independently from deletion. Native and SaaS cleanup have separate evidence. WordPress privacy tools remove/export Chat4U's metadata; they do not delete the merchant's underlying order. Known correlation metadata has a 90-day cleanup horizon, with bounded retries and minimized replay protection. An unreachable plugin or merchant backup can delay physical deletion; revoking an encryption key is not proof that every backup was erased.

Last updated on