Quick answer
FBT offers require trigger products configured in the KitForge editor. Trigger product metafields document and support identification of which Shopify products act as FBT anchors — critical for catalogs that programmatically assign offers.
- FBT triggers are defined in KitForge offers, resolved by product ID on PDP.
- Metafields help operations teams tag triggers — not replace offer config.
- Readiness enforces trigger ≠ add-on variant rules.
- Coexistence and priority determine which FBT shows when multiple exist.
Readiness rules for triggers
KitForge readiness enforces that trigger variants are not duplicated as add-ons, that prices are loaded, and that discount labels exist. Metafield-based catalog tagging should feed into offer creation, not bypass readiness.
Scaling FBT across large catalogs
For hundreds of triggers, use collection-based ops: identify hero SKUs via metafields or tags, then bulk-create FBT offers in KitForge with shared add-on sets. Test one trigger PDP before rolling out.
KitForge supports one FBT widget per PDP after priority — avoid overlapping duplicate trigger configs.
Final recommendation
KitForge FBT trigger products anchor the widget to specific PDPs. Use metafields for catalog ops; use KitForge admin for live offer configuration and readiness.
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 trigger multiple FBT offers?
Multiple offers may exist; priority (lower number first) and coexistence determine which renders on the PDP.
What is a trigger product vs add-on?
Trigger is the main PDP product. Add-ons are optional extra variants the shopper can checkbox into the cart with bundle discount.