Quick answer
Max sellable quantity is floor(component_available ÷ quantityConsumed) for each component; the bundle limit is the minimum across components. Zero means at least one component has no remaining capacity for another kit.
- One OOS component zeros the entire kit.
- quantityConsumed multiplies inventory pressure.
- Checkout validation backs up max sellable on the storefront.
- Webhook sync keeps counts current without manual recalculation.
Why KitForge calculates this
Selling bundles you cannot assemble creates refunds and partial shipments. KitForge recalculates on inventory_levels/update webhooks and enforces limits at checkout validation.
Dashboard vs storefront lag
Allow a short window after inventory changes for webhooks to refresh snapshots. If zero persists, inspect each component's available count in admin.
Launch checklist
Reproduce fixed kit max sellable quantity is zero 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 “Fixed kit max sellable quantity is zero,” 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
Max sellable zero is protective, not punitive. Find the limiting component and fix stock or recipe.
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
Does this apply to FBT and quantity breaks?
Max sellable applies to fixed kits with components. FBT checks per add-on availability. Quantity breaks use variant inventory on the eligible SKU.
What should I do before publishing changes related to Fixed kit max sellable quantity is zero?
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.