If you run Magento 2, you have already seen the pitch: drop a chatbot on the storefront and shoppers will find products faster. Then the demo starts, and the bot either invents a SKU from a product page crawl — or the install guide quietly assumes you are on Hyvä only.
Neither is good enough for a real catalog.
Claspwell is a catalog-aware Magento 2 / Hyvä AI sales assistant. The storefront widget is built for Hyvä, Luma, and Blank — not Hyvä-only. Shoppers get category-first discovery and answers from a live catalog sync, not from guessing at HTML.
This post is for Magento merchants and front-end teams who need to know what “works on our theme” and “knows our catalog” actually mean before they book a call.
The two problems Magento chatbots usually get wrong
1. Theme lock-in
Hyvä is excellent. Many modern Magento builds use it. But a large share of stores still run Luma or a Blank-based custom theme. If the sales assistant only ships as a Hyvä Alpine widget with no path for Luma or Blank, you are stuck waiting for a theme rewrite — or bolting on a generic third-party chat that never sees Magento properly.
Claspwell’s storefront approach:
- Hyvä: Alpine deferred widget, designed for Hyvä performance habits
- Luma: Magento module + widget, guided / manual onboarding (same product surface)
- Blank (and Blank-based themes): Magento module + widget — again, not Hyvä-only
You do not need to be “Hyvä-ready” to evaluate Claspwell. Theme fit is part of the assisted install conversation, not a silent prerequisite.
2. HTML guessing vs catalog truth
Generic AI chatbots often crawl or scrape rendered pages. That looks fine in a demo with ten products. On a real Magento catalog it falls apart:
- Configurable parents and child SKUs get mixed up
- Price display may ignore “From” pricing patterns
- Category context is missing, so the bot answers store-wide instead of inside the shopper’s browse path
- Content goes stale the moment merchandising changes
Claspwell is built the other way around: sync the Magento catalog, then answer from that living data. Category-first discovery means the assistant resolves where the shopper is in the tree, then searches inside that context — instead of treating every message like a free-text Google query over scraped HTML.
What “catalog-aware” means in practice
For merchants and FE leads, the useful checklist is short:
- Live catalog sync — not a one-off page crawl
- Category-first discovery — browse context before broad search
- Configurable products — parents handled properly; child SKU maps back to parent
- From pricing — so the assistant does not invent a single hard price when Magento shows a range
- Living knowledge base — product truth stays tied to Magento as the catalog changes
That is different from a GPT wrapper that “reads your site.” If your catalog is the source of truth in Magento admin, the sales assistant should read Magento — not yesterday’s HTML.
How the widget sits on the storefront
On Hyvä, the widget follows Alpine deferred-loading patterns so it does not fight Core Web Vitals goals. On Luma and Blank, you still get the Magento module + storefront widget path via guided / assisted install — there is no fantasy of a one-click Marketplace “install and forget” button that magically works on every custom theme.
Security basics that matter to Magento teams:
- Hard store_id isolation
- CORS allow-lists
- Captcha on public entry points
- JWT session handling
- Public store key in the browser — no secrets in the storefront
Three-tier AI routing keeps simple catalog questions cheap and fast, and escalates harder intents without dumping every message into the heaviest model.
What is live vs what is planned
Be precise with stakeholders:
- Live focus today: storefront catalog Q&A and product discovery for Magento 2 (Hyvä / Luma / Blank paths as above)
- Cart assist: planned — not marketed as live
- WhatsApp / Instagram / order-agent channels: not live product claims
Shared Catalog and customer-group (B2B tier) pricing are not claimed as v1. If your store relies on those, say so in the discovery call so expectations stay honest.
How onboarding actually works
Claspwell is high-touch on purpose. There is no Stripe self-serve checkout and no one-click Magento install that pretends every theme and catalog is identical.
Typical flow:
1. Request — tell us about Magento version, theme (Hyvä / Luma / Blank / custom), and catalog shape
2. Meeting — walk through discovery goals and constraints
3. Proposal — plan and commercial fit
4. Assisted install — usually 1–2 weeks after access (install included)
5. Go live — widget on the agreed theme path with catalog sync running
If you need a partner agency in the loop, that is a normal part of the conversation — not an afterthought.
Pricing (net, orientation)
Exact fit depends on catalog size and support needs. Published orientation:
- Essential — €99
- Growth — €249
- Scale — €499
- Agency — from €990
See current detail on /pricing. To start the integration conversation, use /request-integration.
Who this post is for
- Magento merchants who still run Luma or Blank and do not want a Hyvä-only AI tool
- Hyvä teams who want a deferred Alpine widget and catalog sync — not a crawl bot
- FE / agency leads who must answer “will this break our theme?” before promising a chatbot
If your priority is a generic website chat that scrapes pages, Claspwell is the wrong product. If your priority is a Magento-native sales assistant that respects theme reality and catalog truth, start here: /magento-2-ai-chatbot and /request-integration.