Built for Magento catalogs, not crawled HTML
Shoppers describe a need. We resolve the Magento category first, clarify attributes, and return product cards with real SKUs from the synced catalog. B2B and technical questions can be answered from a curated knowledge base. Every session is bound to one verified store_id.
That is a different product from a snippet that pastes your homepage into a prompt. Integration is assisted and manual in v1: Magento catalogs are not one-click, and we will not pretend they are.
Category and attribute-aware product discovery
Category-first discovery is the core loop. The assistant matches shopper language to your Magento category tree, then searches inside that category — typically no more than two catalog queries per turn. Nested taxonomy stays intact.
Attribute clarifiers work like a trained sales associate: material, size, load class, and the other filterable attributes you map at install. The model does not invent stock. Cards come from catalog rows that are in scope for that store.
- Resolve category, then filter — not a keyword dump across the whole catalog
- Shopper-facing attributes you actually use to sell, mapped during onboarding
- Product cards with live SKUs; low-confidence turns fall back instead of guessing
How Claspwell handles configurable products
Magento configurable products are a parent SKU with simple children (color, size, length). A naive chatbot lists every child as a separate product and confuses the shopper. Claspwell surfaces the configurable parent on category and search cards. Simple variants stay internal.
If a shopper (or a barcode) names a child SKU, lookup resolves to the configurable parent so the conversation stays on the sellable product. Storefront cards use a From price when variant prices differ, and show price-on-request when there is no sellable price — the same honesty we use on the demo widget.
We map the option attributes you sell on during install. Customer-group and Magento Shared Catalog prices are not a published v1 capability; if your B2B catalog depends on them, we will say so on the discovery call rather than imply guest prices are entitlements.
Catalog synchronization, price and availability
The assistant answers from a synced Magento catalog, not from a nightly HTML scrape. Products, categories, searchable/filterable attributes, special prices, and stock signals are pulled into a tenant-scoped store. Sync cadence is a plan feature because freshness costs infrastructure and Magento API time.
- Essential: daily sync — €99 net / month
- Growth: hourly sync — €249 net / month (recommended)
- Scale: 15-minute sync — €499 net / month
- Special prices sync with the product. Stale data means stale answers — upgrade cadence when promotions and stock move fast
- Scoped catalogs can exclude categories (for example spare parts) so chat never offers out-of-scope SKUs
Magento store-view and tenant isolation
Each Magento store — or isolated store view we bind — is a tenant. Catalog, knowledge, conversation history, and Magento credentials never mix across store_id. The browser does not get to pick the tenant: session tokens carry a verified store_id after origin checks. Origins are allow-listed per store.
German, Swedish, and Slovak storefronts are separate subscriptions for that reason. Scale includes up to three store tenants on one contract; Agency is a quoted multi-store program. Pricing is per store on purpose, not “the whole company on Essential.”
Hyvä-compatible Alpine.js storefront widget
Hyvä merchants chose the theme for performance. A React chat island on every page would fight that investment. Claspwell’s storefront surface is a deferred script: launcher first, panel on demand, no RequireJS on Hyvä. The Magento module injects the widget and a public store key. Catalog search and model routing stay off the storefront.
OpenAI keys and Magento OAuth credentials never ship to the browser. Luma-compatible installs are in scope for the same guided onboarding. We do not publish a vanity kilobyte number; the design constraint is Core Web Vitals — deferred load, no layout-shifting iframe, theme-token friendly UI.
Privacy & security (honest v1)
Hard per-store isolation: catalog, conversations, and Magento credentials never mix across store_id. Magento credentials are stored encrypted at rest. Visitor IPs for chat sessions are hashed. Conversations use a retention window (default target: 90 days) and can be deleted via product APIs.
Question text may go to an inference provider (for example OpenAI) to generate answers that need a full model. We do not claim SOC 2 or ISO certification. We do not name a hosting region or provider as a current fact. Merchants remain controllers for shopper conversations; we act as processor under their instructions where applicable.
Implementation process
v1 is high-touch on purpose. There is no Stripe checkout and no Magento auto-install.
- Request — store URL, Magento version, Hyvä usage, catalog shape
- Meeting — 30–45 minutes: stores in scope, attributes, access owners
- Proposal — written tier, timeline, and out-of-scope items
- Install — module, store key and origin, attribute mapping, first catalog sync, knowledge seed (1–2 weeks after access is ready; staging first when possible)
- Go live — widget on the storefront, isolation confirmed, support channel opened
Magento AI chatbot pricing
Install included. We install the Magento module with you: store key and origin, attribute mapping, first catalog sync, and knowledge-base seeding. No setup invoice. You pay the monthly plan after we confirm fit. Prices are net; VAT is added on the invoice where it applies.
Essential is €99 / 750 conversations / daily sync. Growth is €249 / 3,000 conversations / hourly sync — the usual default. Scale is €499 / 10,000 conversations / 15-minute sync / up to three stores. Agency is from €990 for quoted multi-store programs. Annual billing is −15% on the monthly fee, invoiced 12 months upfront.
Only sessions that reach the AI path count. Extra conversations bill at €0.10 / €0.06 / €0.05 by tier. At 200% of the allowance the AI path throttles to deterministic catalog and knowledge answers until you upgrade.
Vs a generic website chatbot
A crawler reads HTML. It does not know Magento configurable parents, store-view catalogs, or allow-listed origins. Claspwell syncs Magento structure, returns real SKUs, and keeps secrets off the browser. WhatsApp, refunds, and order agents are different jobs — not v1 core.