Quick answer
In KitForge FBT, the trigger product is the product a shopper is viewing. When that product's ID matches an active FBT offer, the app proxy returns add-on recommendations and the theme widget renders below or near add-to-cart.
- Trigger product = the PDP SKU that activates FBT.
- Add-ons are optional; trigger is mandatory for FBT to appear.
- App proxy matches product ID to trigger configuration.
- Coexistence may hide FBT when fixed kit inline is on same PDP.
Why FBT is trigger-centric
Unlike fixed kits where any component PDP can show an inline widget, FBT is asymmetric — recommendations radiate from one anchor product. That matches how shoppers land on a hero SKU from search or ads.
KitForge stores trigger assignment in offer configuration and exposes it through the app proxy response for storefront rendering.
Choosing good trigger products
Best triggers are high-traffic heroes with natural accessory relationships — serums with tools, cameras with cases, candles with trimmers. Low-traffic triggers produce low FBT views regardless of add-on quality.
Final recommendation
A trigger product is the FBT anchor — configure it to the SKU shoppers actually land on, verify the widget on that PDP, and choose heroes with clear accessory relationships.
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 a trigger for multiple FBT offers?
KitForge resolves multiple offers via offer priority — one FBT shows per PDP. Create distinct offers only when you intend to swap by schedule or priority.
Can the trigger also be an add-on in another FBT?
Yes — triggers and add-ons are per-offer. The same SKU can trigger Offer A and be an add-on in Offer B on different PDPs.