Minimum Order Quantities: Which Items Must a Shop Count Together?

A minimum purchase rule answers whether a basket may proceed. A quantity discount answers which price applies. Define these separately: a shopper can qualify for a price yet still have a basket that does not meet your purchasing rules.

Before commissioning the feature, write down the scope of each rule. Does it apply to one variation, the whole product family, a category or the complete order? The word “minimum” alone does not tell the developer which items to count.

Distinguish a lower limit from a purchase multiple

A lower limit and a buying step solve different problems. In a fictional catalogue, a product might require a minimum of six pieces but allow larger purchases only in groups of three. Seven pieces would meet the lower limit but not the grouping rule. State both requirements rather than calling either one a pack size.

The WooCommerce Min/Max Quantities extension documentation describes minimum and maximum limits at product, variation, category and order level, together with a “Group of” setting for purchase multiples. These are capabilities of that extension, not a claim that every WooCommerce installation includes them.

Do not assume a quantity rule changes the unit sold, the warehouse packaging or the price. Those decisions need their own specification. Also define the effect of reducing the cart later: the customer should see the outstanding requirement before trying to confirm the order.

Decide whether variations can combine

If a customer buys different colours or sizes, can those quantities satisfy one shared requirement? A mixed purchase and several independently restricted variations are different policies.

Ask for a concrete demonstration using two variations. The extension documents a Combine Variations option and says that enabled combined rules are validated in cart and checkout. A valid-looking quantity on an individual product screen is therefore not the complete acceptance test.

Keep rule precedence explicit when a product also belongs to a restricted category. Require the chosen implementation to show which constraints apply, rather than assuming every category restriction disappears when one product field is set.

Clarify what an excluded item still contributes

“Exclude this product” is ambiguous. It can mean the product is not subject to a restriction, or that its quantity and value must not contribute towards a wider order requirement. Do not treat those as interchangeable.

The cited documentation describes product exclusions, but separately provides a developer snippet for ignoring an item's quantity or price when checking order rules. Have the developer demonstrate the actual counting result; a checked exclusion box is not enough evidence.

For monetary thresholds, agree the amount basis, currency and treatment of discounts, tax and delivery. This guide does not establish those calculations or the legal acceptability of a minimum order policy. Have the commercial and legal policy reviewed where appropriate.

Make a rejected basket recoverable

Tell the shopper which rule failed and what permitted change would resolve it. Do not silently increase quantities or add paid items to reach a threshold. If different rules cannot be satisfied together, flag the configuration for staff rather than leaving the customer in a loop.

For acceptance, try a quantity below the minimum, an allowed multiple, a disallowed intermediate quantity, mixed variations and an excluded item. Repeat after removing a product and after returning to a saved basket. Inspect checkout as well as the product page, without placing real test orders.

Include these examples in the brief for your shop project, alongside the acceptance criteria. The useful result is an explainable purchasing boundary, not merely a disabled checkout button.