Minimum Quantity per Product for WooCommerce: safe setup, failure cases, and rollback

Direct answer

Store one whole-number minimum on the product, pass it to WooCommerce's native quantity input, and reject a proven lower value during add to cart, cart update, and the final cart check. Do not change price, stock, product type, cart contents, or order data, and do not silently raise the customer's quantity.

Minimum Quantity per Product for WooCommerce follows that boundary. Free handles one native simple product. Pro adds bounded variation and category precedence plus one short validation sentence.

The smallest useful rule is one integer

A merchant who sells samples in sets of ten does not necessarily need minimums, maximums, decimal steps, role pricing, country rules, wholesale tiers, pack conversion, measurement pricing, and scheduled promotions. Each extra rule creates another interaction with stock, pricing, validation, blocks, extensions, and themes.

The narrow model is easier to explain and safer to reverse:

Clearing the StoreFixKit field or deactivating the plugin removes the behavior. WooCommerce data does not need migration or repair.

Use WooCommerce's native quantity contract

WooCommerce's current quantity input template receives minimum, maximum, step, input value, and accessibility values from WooCommerce. A focused plugin can increase only the returned minimum when the exact product and saved rule are valid.

The browser input is not security. Customers, bots, themes, or extensions can submit a different value. Server-side checks remain necessary:

1. Add to cart rejects a smaller submitted quantity.
2. Cart update rejects a smaller line quantity.
3. The final cart check catches a persisted invalid line before checkout.

WooCommerce's cart implementation is the parent system. A minimum plugin should return a validation decision through documented hooks, not rewrite the cart behind WooCommerce's back.

Do not auto-correct the cart

Changing six requested units into ten may look convenient, but it changes the customer's decision and the order value. It can also interact with stock limits, coupons, shipping thresholds, taxes, or payment authorization.

A safer failure is explicit:

• keep the submitted cart unchanged;
• show one escaped WooCommerce notice;
• explain the exact minimum;
• let the customer choose the next quantity.

This keeps product and commercial truth with the shopper and WooCommerce.

Diagnose a minimum-quantity problem

Public support reports show why broad quantity logic deserves caution. One merchant reported a hidden quantity field and broken control, another reported an order quantity-step error, and a separate topic records a fatal error in quantity-rule code. These reports prove those individual failures occurred; they do not prove every competing plugin fails in the same way.

Save only on the exact authorized product

The product field must be an owned value, not an unbounded request variable. A safe save path checks:

1. WooCommerce's product-save nonce.
2. Permission to edit the exact product.
3. The product is the supported native type.
4. The submitted value is intentionally empty or a whole number from 2 through 999.
5. Empty means delete only the owned key; invalid means preserve the last valid value.

The WordPress add_meta_box() reference describes the native editor integration point. The important security decision is still object-level authorization at save time.

Give variation and category rules a visible order

A paid layer should add capacity without turning Free into a remote dependency. One deterministic order is enough:

1. Variation minimum.
2. Parent product minimum.
3. Lowest matching configured category ID.
4. No StoreFixKit minimum.

Category rules should be capped. StoreFixKit evaluates at most 25 configured rules and at most 25 category terms. Over-budget or malformed context returns the earlier valid result instead of scanning the catalog or guessing.

Test the invariants, not only the screenshot

Use this release checklist:

1. A value from 2 through 999 saves on an authorized simple product.
2. Empty removes only the owned minimum.
3. Invalid or forged input preserves the last valid value.
4. The native quantity field starts at the effective minimum.
5. One fewer unit is rejected during add to cart.
6. The exact minimum proceeds through native validation.
7. Cart update and final cart checks reject lower values once.
8. Price, stock, coupons, taxes, shipping, products, customers, and orders are unchanged.
9. Unsupported product types fail passive in Free.
10. Pro removed or license unavailable leaves Free rules working.
11. Update, downgrade, rollback, deactivation, and both uninstall modes preserve parent commerce data.
12. Desktop and mobile show no clipped quantity or Add to cart controls.

Resource boundary

The public path needs only the exact product values already involved in WooCommerce's quantity workflow. It does not need a catalog query, custom table, scheduled job, queue, telemetry event, JavaScript control, stylesheet, or StoreFixKit storefront request.

In the Batch 13 release gate, all six Free and Pro plugins together added three database queries at the median and P95 on the measured public page, no StoreFixKit HTTP calls, no unrelated frontend assets, and no owned-state writes. That is a dated test result on the StoreFixKit demo environment, not a promise that every hosting stack has the same timing.

Common mistakes

Treating the HTML minimum as enforcement

Browser attributes are helpful input hints. Server validation remains the authority.

Supporting every quantity model in one plugin

Maximums, decimals, packs, role pricing, measurement units, and wholesale tiers are separate products with separate failure modes.

Silently increasing the cart

This changes the customer's intended order. Reject and explain instead.

Guessing on unsupported products

Grouped, external, subscription, bundle, composite, and block-only flows have different ownership. Free should return native behavior when it cannot prove the exact contract.

Making Free depend on billing

The product's Free minimum must continue when Pro or the license service is unavailable.

Market boundary

The category has current free competitors and an official paid WooCommerce Marketplace offer for broader quantity rules. That proves a market category exists; it does not prove StoreFixKit demand or revenue. The narrower commercial hypothesis is that a nontechnical merchant will pay for reliable variation and category reuse after one Free product rule solves the visible problem.

Measure that hypothesis with legitimate active installs, completed setup, below-minimum validation success, trial starts, paid conversions, support burden, refunds, and renewals. Do not substitute competitor installs or marketplace prices for StoreFixKit traction.

FAQ

How do I set a minimum order quantity for one WooCommerce product?

Save one bounded integer on that product, pass it to WooCommerce's native quantity arguments, and enforce it again during server-side cart validation.

Does minimum quantity change stock?

Not in this design. Stock and backorders stay entirely with WooCommerce.

Should the plugin automatically increase a smaller cart quantity?

No. It should reject the request and let the customer choose, because increasing quantity changes the intended purchase.

Can the same rule work on variations?

Yes as a bounded Pro feature with explicit variation, parent, and category precedence. Free deliberately limits itself to native simple products.

What happens when the plugin is deactivated?

Its filters and validators disappear immediately. The saved owned value can remain dormant for recovery, while WooCommerce returns to native quantity behavior.