How OpenCart Option Stock Settings Create Unavailable Promises

# How OpenCart Option Stock Settings Create Unavailable Promises An option-heavy product is not one inventory decision. It is a product stock gate plus a set of option-value gates. A shirt may have product quantity, while every size and color value can also carry its own quantity and “subtract stock” behavior. The storefront presents one product, but fulfilment depends on the selected path. The risky gap appears when presentation and fulfilment disagree. A value can remain visible even though its quantity is exhausted. If subtraction is enabled, checkout may reject the choice. If subtraction is disabled, the store may accept an order it cannot fulfil. Both cases deserve attention, but they are different operational problems. ## Model the gates before changing them Start with a read-only inventory of: - product quantity and product subtraction behavior; - required choice options; - each displayed option value, quantity, and subtraction behavior; - disabled products that may be reactivated later. For every product, calculate the number of advertised combinations and the subset that passes both the product and option-value gates. Use a stable ordering and bounded arithmetic so the same catalog produces the same result every time. ## Separate warnings by intent Zero quantity with subtraction disabled is an overselling risk. Zero quantity with subtraction enabled is an unavailable promise. A required option with no values blocks every configuration. Low stock is neither of those; it is an early-warning threshold. [Vamao OpenCart Catalog Availability OS](/products/vamao-opencart-catalog-availability-os) keeps these categories separate, simulates the resulting promise coverage, and never changes product or checkout data.