Quick answer
Widget-only discounts mean tier prices and FBT savings apply when cart lines are created through KitForge widgets with _kitforge_* line properties. Manual adds of the same products follow standard variant pricing unless separate discounts exist.
- Widget path and manual add path can price differently.
- Line properties mark widget-initiated lines.
- Explain widget usage in product copy for QB tiers.
- Analytics attribution follows the same widget path.
Merchandising copy
Use labels like Volume discount applied automatically on QB widgets. FBT should show savings on selected add-ons before add-to-cart.
Testing
Always test both widget path and manual add path. Only the widget path should reflect bundle pricing for widget-only offers.
Launch checklist
Reproduce widget-only discount not applying outside kitforge widget on a known product with a clean browser session after confirming the app embed is active.
Confirm variant coverage, mobile layout, and that the discount only applies through the intended path so shoppers are not surprised at checkout.
- Preview the offer on a real product page and on mobile.
- Place a test order that exercises the discount and inventory path.
- Brief support on what is included and what is not.
- Document the success metric before you scale the offer.
Mistakes that quietly kill conversion
Debugging discounts before confirming the widget mounts wastes time. Network responses from the Kitforge offers proxy should be the first technical check.
For “Widget-only discount not applying outside KitForge widget,” keep the page focused on one primary next step. Extra widgets, stacked badges, and unclear exclusions increase bounce more often than they increase AOV.
- Do not hide eligibility rules until checkout.
- Do not bundle unrelated leftovers without a customer story.
- Do not skip mobile QA on choice-heavy widgets.
- Do not launch without a rollback plan for the discount.
How to measure whether it worked
A fix is complete only when the storefront, cart line properties, and checkout total all match the intended offer.
If the metric moves but support volume rises, fix presentation or inventory rules before cloning the offer across more SKUs.
- Attach rate on treated product pages
- AOV and contribution margin after discounts
- Refund or fulfillment exception rate
- Time for a teammate to edit the offer safely
Final recommendation
Widget-only discounts align price with presentation. Train support to recognize manual-add vs widget-add carts.
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
Can I disable widget-only?
widgetOnlyDiscount is part of KitForge's integrity model for FBT/QB. Changing behavior may desync PDP display from checkout.
What should I do before publishing changes related to Widget-only discount not applying outside KitForge widget?
Preview on mobile, place a test order, and confirm inventory and discount behavior match the storefront promise. Only then activate for all traffic.
When is Kitforge Bundles the wrong tool?
If you only need a simple Buy X Get Y or free-gift discount with no product-page merchandising, native Shopify discounts may be enough. Kitforge is built for fixed kits, FBT, and quantity-break widgets with inventory validation.
How long should I wait before judging the offer?
Give the offer at least one to two weeks of normal traffic, or enough orders to see attach rate stabilize. Seasonal spikes can distort a shorter window.