Order Restrictions for WooCommerce

If your store loses money on low-value orders

A small order costs almost as much to prepare and ship as a large one, and many payment gateways charge a fixed part per transaction. Shops that sell on thin margins often notice it late, once the month is already closed. This plugin is for that store owner: it sets minimums, maximums and per-customer caps so that orders arrive already making sense.

It also helps if you sell in multiples (boxes, packs), if you want to limit an offer to a few units per person, or if you need to close orders once you can no longer fulfil more. It won't help if you are looking for this:

• Discounts or volume pricing: here a purchase is only allowed or blocked, the price is not changed.
• Stock management: it limits what can be bought, it does not count or replenish inventory.
• Rules based on the history of someone buying without an account: check in the demo how it behaves with a customer who has not logged in.

An order minimum that doesn't leave the customer in the dark

The order total restriction sets a minimum, a maximum or both. The useful part is in the filters: each rule can apply to certain products, categories, product types, tags or brands, and to specific users or roles.

• Your own error message, so the customer knows how much is missing instead of hitting a silent block.
• An option to lock the checkout button until the rule is met.
• Priority between rules, for when several affect the same customer.

A well-set minimum raises the average order value; one that is too high scares off sales. Start with a moderate minimum and see how many carts fall below it before raising it.

Order Restrictions for WooCommerce and the gateway that doesn't pay off

Each payment gateway can have its own range of amounts. The classic example: hiding cash on delivery on orders above $500, or keeping an expensive method for when the order justifies it. Besides the amount, you can show or hide gateways based on cart contents, country, zip code, user or user role.

Zip codes support wildcards and numeric ranges, and rules can have validity dates, handy for seasonal payment methods. If several rules match, you choose whether the first or the last one wins.

Selling in fives or just two per category

Quantities are defined at three levels: global for the whole store, per category and per product, where the product page can override the general setting. Besides minimum and maximum there is a step increment: if you sell in multiples of 5 or 3, the customer won't be able to add 4.

There is also a limit on items per whole order, with customizable messages that accept placeholders such as [min_qty] and [max_qty]. Quantity rules support validity dates and user or role filters, and they combine in layers with product rules.

Cutting off the customer who has already bought too much

Some limits look at the customer's past. You can limit by the amount they have already spent or by the number of previous orders, and the latter supports periods: all time, day, week, month, year or custom dates, with the counter resetting by itself. It is useful for capping trial orders or promotional offers.

The product restriction prevents buying the same item more times than set (permanent by default, with an optional period). The store restriction closes new orders once a number of orders or a total amount is reached, for example $1000, which helps if your capacity to fulfil is limited.

Rules that clash and customers without an account

What happens if two rules affect the same order?

You can assign priority to rules; for payment gateway rules you choose between first or last match.

Can I customize the notices?

Yes, each restriction has its own error message, shown on the product page or in the cart depending on the case.

Is it useful for wholesalers?

You can apply rules by user role, for example a different minimum or different gateways for wholesale accounts. What it doesn't do is create wholesale prices.

Are the restrictions permanent?

Product and store restrictions are permanent by default, with an optional period; quantity and gateway rules support validity dates.