Documentation / Compatibility and current boundaries

Min/Max · Development 0.12.0 · Updated 15 September 2026

Compatibility and current boundaries

A supported platform claim needs a tested version and a tested purchase flow. This is the current development status.

AreaRecorded evidence
Local reference environmentMinimum: WordPress 6.8, WooCommerce 10.6, PHP 8.2. Tested endpoints: WP 6.8 / Woo 10.6.0 and WP 7.1 / Woo 11.1.0, both on PHP 8.2.29. This does not certify every intermediate combination or other PHP branches.
Classic cart and checkoutStorefront tests include quantity changes and test orders.
Cart/Checkout BlocksTwenty Twenty-Five/Store API tests include invalid quantities and test orders.
Variations and HPOSSelected variation, parent-rule and order flows tested locally.
Elementor, Avada and other third-party stacksDeferred. No compatibility badge or universal support claim.
MultisiteFresh network activation and separate rules/messages across two sites passed at both tested endpoints. This is not a full network purchase or hosting certification.
External MCP transportNot accepted end to end. See the AI status guide.

Not implemented as product features

This plugin does not currently offer decimal quantities, arbitrary allowed-value lists, weight/postmeta totals, automatic discounts, scheduled rules, lifetime purchase limits per customer or automatic import from competitor plugins. A min/max quantity is a purchase constraint, not a discount or stock-management system.

Before adding another quantity engine

Two engines can impose different restrictions on the same cart. Reproduce the combined behavior on a staging store and keep one authoritative rule configuration where possible. Diagnostics can recognize some competing engines but cannot detect every custom implementation.

Release readiness

Public domain, distribution listing, additional PHP branches and platform combinations and public demo sandboxes are separate release tasks. The documentation explains the implemented behavior and limitations; it is not a certification of release readiness.