Directory / plugin
Antom Shopping Agent
v1.1.2 · by antomintegration
Add an AI shopping assistant to WooCommerce for product discovery, cart support, checkout guidance, and order assistance.
About this plugin
Antom Shopping Agent is an AI shopping assistant for WooCommerce. It helps shoppers discover products, review product information, manage their cart, use eligible coupons, provide delivery details, and continue to checkout through a conversational storefront experience.
Key features
- Product search by keyword, category, price range, popularity, or recency
- Product details, variations, stock information, pricing, and customer reviews
- Cart item addition, quantity updates, and removal
- WooCommerce coupon discovery and application
- Billing and shipping address collection
- Available shipping-method selection
- WooCommerce checkout using payment methods enabled by the merchant
- Order-information lookup for authorized shoppers
- Streamed AI shopping-assistant responses
- Configurable assistant name, icon, support email, and suggested question
- English and Simplified Chinese support
Antom Shopping Agent requires WooCommerce 3.6.4 or later and at least one enabled Antom payment method. Merchants must complete the required Antom onboarding and KYC process before activation.
Current release limitations
This release is intended for installation, deactivation, deletion, and reinstallation validation. The production chat service is not yet available. Product synchronization remains configured for development/testing and is rejected outside the development environment. Do not use this build for production product synchronization. An empty catalog displays no preview products.
External Services
Antom Shopping Agent uses Antom-hosted services to load the storefront assistant and generate responses to shopper questions.
Installation authentication uses the Antom imgs gateway. Activation registers the store domain or signs a credential rotation; deactivation and deletion send signed lifecycle notifications. Chat sessions exchange a server-held installation credential for a short-lived JWT bound to a visitor identifier. Installation secrets remain in WordPress options and are not sent to the browser. Uninstall retains these credentials and their store bindings so reinstall can authenticate and rotate them; appearance and initialization settings are removed. A retained credential does not override the backend installation status. The default authentication gateway is https://imgs-sea.alipay.com/mgw.htm; test environments are selected explicitly through the env/chat_env URL parameters. Without these parameters the plugin uses production.
Services
- Frontend JavaScript assets load the shopping-assistant interface on storefront pages after Antom Shopping Agent is configured.
- The Antom Bot Chat API processes shopper questions and returns assistant responses.
- The product synchronization service receives development-only start, status, and stop requests. Its endpoint and merchant context remain configured for development/testing; production synchronization is unavailable. Product webhooks are rejected until signed delivery is configured.
When and what data is sent
The frontend assets are requested when a visitor opens a storefront page after Antom Shopping Agent is configured. When a visitor interacts with the assistant, the service may receive the shopper’s question, session identifiers, current page URL, information entered into the assistant, storefront session context, and standard HTTP request information such as IP address, user agent, referrer, and request time.
When a merchant starts, checks, or stops product synchronization, the plugin sends the request type, store and merchant identifiers, and session context to the configured service. Product-webhook requests also send the event type and supplied product details, including catalog and inventory information. The PHP Chat and synchronization proxies currently forward the complete incoming Cookie header as platformSession; reducing that data and replacing the development synchronization configuration require backend coordination before production release.