Quick answer
KitForge fixed kits support inline placement on component product pages and standalone widgets on dedicated landing products. Inline captures organic traffic on each SKU; standalone centralizes email and paid deep links. Coexistence rules differ by placement mode.
- Inline kits on component PDPs capture organic SKU traffic.
- Standalone kits give one campaign URL for email and ads.
- Inline placement triggers coexistence — hides FBT/QB on that PDP.
- Hybrid models separate evergreen inline from campaign standalone.
Traffic source drives placement
Email and paid ads need a stable URL — standalone landing product. Organic search on component SKUs needs inline widgets so shoppers see the kit without hitting a separate page.
Theme and app embed
Default auto embed mounts near add-to-cart. manual_app_block requires adding KitForge section block in theme editor for hero placement on landing templates.
FBT and QB use trigger PDP placement — not standalone kit placement.
Final recommendation
Choose KitForge placement by traffic — inline for component discovery, standalone for campaign deep links, hybrid for mature catalogs running both evergreen and seasonal kits.
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 run on the same product as a standalone kit?
On different PDPs yes — kit on landing product, FBT on component singles. On one PDP, coexistence and priority apply.
Does placement affect kit pricing?
No — Cart Transform applies the same kit price regardless of inline or standalone placement.