Quick answer
When a shopper adds a KitForge fixed kit, Cart Transform represents the kit in cart with expanded child SKU lines for fulfillment while applying the configured kit price structure.
- Fixed kits require Cart Transform — this is core KitForge architecture.
- FBT and QB do not use Cart Transform for their primary mechanics.
- Fulfillment sees components, shoppers see one kit offer on PDP.
- Test cart line structure before launching high-volume kit campaigns.
Inventory and max sellable quantity
Cart Transform works with KitForge inventory logic — the minimum available component quantity caps how many kits can sell. Checkout validation blocks oversell if inventory changes between PDP view and checkout.
Fulfillment integrations
Expanded child SKUs align with pick/pack systems. Order metafields supplement Cart Transform output for 3PLs that need explicit kit breakdown JSON.
Final recommendation
Shopify Cart Transform is what makes KitForge fixed kits work at cart and fulfillment. Verify expanded lines and inventory caps on every new kit before go-live.
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 Cart Transform fail silently?
Misconfigured kits fail readiness before publish. Post-publish issues usually trace to manual cart adds bypassing the widget path.
Do returns reference kit parent or components?
Fulfillment and returns typically operate on expanded child lines as configured in your Shopify setup.