Configurable products are where generic Magento chatbots embarrass themselves. Magento stores a parent SKU and simple children for size, color, or length. Search that dumps every child into chat looks like a warehouse spreadsheet, not a sales associate. Claspwell is built to talk about the parent the shopper can actually configure.
This is a product fact, not a slogan: category and search cards hide simple variants that belong to a configurable parent. SKU lookup of a child resolves to that parent. Details and limits below — and on /magento-2-ai-chatbot.
What Magento configurables actually are
The parent is the sellable product in the category. Children carry option values and often their own prices and stock. Layered navigation already understands this. Chat that ignores it will recommend a blue XL simple that is not visible, or three cards that are the same jacket.
How Claspwell surfaces parents and children
Shoppers see the configurable parent. Internal variants stay classified for stock and option logic, not as competing search hits. If a shopper pastes a child SKU from a packing list, find-by-SKU walks to the parent so the next turn can still talk options instead of a dead simple.
Storefront cards use a From price when variant prices differ, and can show price on request when there is no sellable price. We would rather under-claim than invent a number.
Attributes you must map
Option attributes (size, color, length, whatever you sell on) have to be in the shopper-facing map at install. Unmapped options will not clarify well. That mapping is included in the guided Magento install — not a marketplace “enable all attributes” toggle.
What v1 does not claim
Customer-group and Magento Shared Catalog prices are not a published v1 capability. Guest specials sync; B2B price lists that depend on logged-in group identity need an explicit conversation on the discovery call. We will not pretend a public catalog price is an entitlement.
Why this beats a crawler
HTML does not encode parent/child relationships cleanly. A crawler will index child PDPs if they are reachable and then recommend them. Catalog sync plus parent collapse is the Magento-native fix. Pair it with stock freshness on /blog/magento-chatbot-price-stock-validation.