Quick answer
On a product page with an inline fixed kit purchase option, KitForge defaults to hiding the FBT widget. Change coexistence to show_below if accessory upsell should appear under the kit choice.
- hide_fbt is the default coexistence with inline fixed kits.
- show_below stacks FBT under the kit widget intentionally.
- Only one FBT offer displays per page.
- Simplify before stacking multiple widget types.
Merchandising recommendation
If the inline kit already includes accessories, FBT may be redundant. If the kit is core-only, show_below FBT can capture extra items without replacing the kit story.
Launch checklist
Reproduce fbt hidden when fixed kit is on the same product page 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 “FBT hidden when fixed kit is on the same product page,” 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
Hidden FBT is usually intentional coexistence. Adjust settings if your merchandising plan needs both kit and add-ons visible.
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 FBT and quantity breaks both show?
Yes with coexistence show_below/show_above. Defaults vary — configure both FBT and QB coexistence in each offer editor.
What should I do before publishing changes related to FBT hidden when fixed kit is on the same product page?
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.