CHATTERgo integrates with Magento 2 and Adobe Commerce, keeping your catalog, orders, and customer context in sync so agents answer with current information.
Getting connected
Magento connections are set up with our team — contact us and we will help you connect your store and configure the sync.
What syncs
| Data | Used for |
|---|---|
| Products and store views | Product questions, recommendations, and search |
| Orders | Order status and order history in chat |
| Customers | Recognizing logged-in shoppers |
Catalog sync is self-healing: a nightly reconcile loop per store catches missed updates, and you get alerted if a mass product change is detected. Syncs to shared Magento servers are paced and store-scoped, with a circuit breaker that protects busy instances during full syncs.
Logged-in shopper recognition
The widget reads the logged-in customer from your Magento storefront, so conversations resolve to the customer record in the inbox instead of showing "Anonymous customer".
Because every Magento theme exposes customer data a little differently, the mapping is configurable per organization from Widget settings → Customer Identity: you define where the storefront stores the logged-in customer (a window variable or a localStorage bucket) and which fields carry their id, email, name, and phone. Verified Shopify storefront identity always takes precedence where both exist. See Customer identity.
B2B quantity-tier pricing
For Magento B2B (Company) accounts, price quotes in chat reflect the signed-in buyer's quantity-tier ladder, product cards can render an account quantity-pricing table, and the agent prices quantities from the ladder rather than the base catalog price.
When a customer group has no tier price configured, Magento serves a placeholder catalog price — CHATTERgo filters these placeholders so an inflated placeholder can never be quoted as a real price.
Firewall and CDN rules
If your storefront sits behind a WAF or CDN (Fastly, Imperva, Cloudflare), you can gate CHATTERgo's server-to-server calls behind a shared-secret request header. Once enabled, your hosting team writes narrow WAF rules that accept requests carrying the header — no broad allowlisting of our infrastructure. Ask us to enable the header for your organization.
Order status and history
Shoppers can ask about an order's status, list their past orders, and add items from a previous order straight back into the cart. Cancelled, closed, and refunded orders are reported accurately, and order cards render localized on Chinese-language storefronts.