Quick answer
KitForge add-to-cart failures on the storefront usually trace to unavailable variants, missing required FBT selections, locale-specific cart routes, or inventory blocking max sellable quantity.
- FBT requires at least one selected add-on by default.
- Console network tab shows the exact Cart API error.
- Test in the market/locale your customers use.
- Zero max sellable quantity disables bundle purchase paths.
Ajax Cart API and locales
KitForge uses Shopify's locale-aware Ajax Cart routes. Multi-market stores should test add-to-cart in each published locale.
Cart drawer themes may need section IDs in refresh targets — KitForge targets common drawer section names.
Inventory and validation
Even if add-to-cart succeeds, checkout validation may block oversell. Fix component stock before blaming the widget button.
Final recommendation
Add-to-cart failures are almost always variant availability, FBT selection rules, or inventory — not mysterious widget bugs.
If you want this kind of offer to feel native to the buying journey, Kitforge Bundles is built around that exact problem: turning related Shopify products into clearer bundle offers before the shopper reaches checkout.
FAQ
Does KitForge support accelerated checkout buttons?
Bundle offers use widget add-to-cart flows. Buy-now buttons on the base product may bypass bundle logic for inline fixed kits.