Quick answer
When FBT add-ons do not appear, the product is usually not a trigger, the offer is inactive, unavailable add-ons are hidden, or coexistence rules hide FBT because a fixed kit inline widget is present.
- FBT lives on trigger PDPs only.
- Fixed kit on same page may hide FBT by default.
- All add-ons OOS + hide unavailable = empty widget.
- Readiness errors prevent activation entirely.
Readiness rules that block publish
Trigger cannot equal add-on variant. Duplicate add-on variants fail readiness. Fix in editor before expecting storefront output.
- trigger_addon rule
- duplicate_addons rule
Display styles
checkbox_list, product_cards, and compact_rows change layout but not eligibility. Switch styles if shoppers miss add-ons on mobile.
Launch checklist
Reproduce fbt add-ons not showing on 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 add-ons not showing on 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
Confirm trigger mapping and coexistence before redesigning the offer. Most missing FBT cases are configuration, not theme conflicts.
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 one product be both trigger and add-on?
Not for the same offer — readiness blocks trigger variants from appearing as add-ons.
What should I do before publishing changes related to FBT add-ons not showing on 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.