To make an allocation stick, limit how many bottles each customer can buy across orders. A cart limit only sees one cart, so a customer can buy 2 now and 2 more tomorrow. A per-customer limit remembers past orders and blocks the extra bottles at checkout, including Shop Pay and other express checkouts.
Why allocations need a per-customer limit
An allocated release is small on purpose. If a few customers can take most of it, the members who waited all year miss out, and some of those bottles end up on resale sites. A cap per order doesn't help: anyone can place a second order. What works is a cap per customer, counted across every order they place.
Pick the rule
| You want | Limit Type | Scope | Max Count | Period |
|---|---|---|---|---|
| 2 bottles of this release per customer | Total Quantity (units) | Specific Product (the release) | 2 | Lifetime |
| 12 allocated bottles per customer per year | Total Quantity (units) | Specific Collection (allocated wines) | 12 | Per Year |
| Up to $600 of allocated wine a year | Total Spend | Specific Collection (allocated wines) | 600 | Per Year |
Per release or per year
| Lifetime on the release | Per Year on a collection | |
|---|---|---|
| Resets | Never | For everyone on January 1 |
| Counts | That one product | Every product in the collection, together |
| Fits | A spring and a fall release, each its own product | One yearly allowance across all allocated wines |
Lifetime is the cleaner choice for releases: make each release its own product, and each one gets its own allowance. Per Year follows the calendar year, so a bottle bought on December 31 and one on January 1 fall in different years.
You can combine them: 2 per release, and no more than 12 a year across the collection. Each rule is checked at checkout.
Bottles or spend?
Count bottles when the releases are similar in price and the point is fair shares. Count spend when prices vary a lot, from a $30 rosΓ© to a $150 reserve, and you'd rather give each member a budget than a bottle count. Total Spend adds up what the customer spent on products in the collection, in your store's currency.
A worked example
A winery has a spring and a fall release, each its own product in a collection called "Allocated". Rules: 2 per release (Lifetime), and 6 per year across "Allocated".
| Date | Order | Already bought | Result |
|---|---|---|---|
| March 10 | 2 Spring Pinot | 0 | Goes through |
| March 12 | 1 Spring Pinot | 2 of the release | Blocked: release limit is 2 |
| September 15 | 2 Fall Syrah | 2 this year | Goes through: 4 of 6 this year |
| October 1 | 1 Reserve (also in "Allocated") | 4 this year | Goes through: 5 of 6 |
| January 5 | 2 bottles from a new release | 0 this year | Goes through: a new year |
Set it up in OrderRules
- In Customer Limits, tick Enable per-customer limits.
- Add a rule: Limit Type Total Quantity (units), Scope Specific Product, choose the release, Max Count 2, Period Lifetime.
- Check the wording in Settings β Customer Limit Messages. One template covers every rule and fills in the product and the number, so a blocked member sees which wine and how many.
- Test it with a logged-in test customer: buy 2, then try a third.
Per-customer limits are on the Pro plan. Counting starts when you save the rule, so set it up before the release opens.
Release-day checklist
- A week before: create the release as its own product, add the rule, and test it with a test customer.
- Tell members they'll need to log in, and what the allocation is. Put it on the product page too: "Allocation: 2 bottles per member."
- At release: publish the product. Members who already have accounts check out as usual.
- During the release: watch for several accounts shipping to one address.
- After: leave the rule in place. Lifetime rules keep counting, so a late order can't top up an allocation.
What customers see
- On the product page: a badge with the allocation and, for a logged-in member, how many bottles they have left.
- Logged in, within the allocation: checkout goes through as usual.
- Over the allocation: checkout is blocked with your message, whether the extra bottles are in this cart or were bought before.
- Not logged in: checkout shows your log-in message. While customer limits are on, guest checkout is blocked across the store.
What it can't do
- Different allocations per membership tier. A rule has one number for everyone.
- Members-only access. OrderRules limits how much each account buys, not who can buy. Use a members-only app for that.
- Tell two accounts apart. The limit counts customer accounts, not people or addresses. Check shipping addresses on allocated orders before you ship.
- Count a case as 6 bottles. Limits count units. A case sold as one product counts as one; sell bottles in sixes with a step quantity instead.
- Age checks or alcohol shipping rules. Use an app or service built for alcohol compliance.
POS orders aren't blocked, but they count toward the customer's limit. Cancelling an order in full gives the allowance back; a refund on its own doesn't.
If it doesn't seem to work
- A member bought more than the allocation. Check that both orders were placed while logged in to the same account, and after you saved the rule.
- A member's allowance came back. One of their orders was cancelled in full, which releases it.
- The yearly rule seems too strict. It counts every product in the collection. Check nothing else is in "Allocated".