---
title: "Limits enforcement completed, and a cleaner delivery setup"
description: "Every combination of customer limit now enforces, cancelled orders give capacity back, and the delivery screens got a proper redesign."
contentType: "changelog"
locale: "en"
localized: true
source: "https://orderrules.com/changelog/limits-enforcement-complete"
slug: "limits-enforcement-complete"
date: "2026-09-10"
tags:
  - "Improved"
  - "Fixed"
---
Every combination of customer limit now enforces, cancelled orders give capacity back, and the **Delivery** screens got a proper redesign.

- 🐛 **Fixed (Pro):** Cancelling an order now **returns the customer's used allowance**. Previously a cancelled order still counted against a customer's limit, so a shopper could be blocked by a purchase that no longer existed.
- 🚀 **Improved (Pro):** Per-customer limits now enforce across **every combination** of limit type, scope and period — orders, quantity, spend and weight, applied storewide, per product or per collection, over a day, week, month or rolling window. Some combinations previously configured without enforcing.
- 🐛 **Fixed (Pro):** Saving a per-customer limit scoped to a **collection** could fail outright. It now saves correctly.
- 🚀 **Improved (Advanced):** The **Delivery** screens were rebuilt — availability rules and time-slot templates are now individual cards with status badges, rules open for editing in place instead of jumping to the bottom of the list, and the setup guide is clearer.
- 🐛 **Fixed:** Product limit **quantity** caps are now included in the Usage % and status badge on the Products table. A product at its quantity cap previously showed as having room left.
- 🚀 **Improved:** Choosing a product that already has limits now takes you straight to editing it, instead of silently creating a second entry.
- 🐛 **Fixed:** Limit values are now validated on save — daily can't exceed weekly, weekly can't exceed monthly, a minimum order quantity can't be set above its own quantity cap, and negative or fractional values are rejected. Impossible combinations previously saved and then blocked every checkout.
- 🐛 **Fixed:** Storefront messages containing an apostrophe displayed as `We've` instead of `We've`.
- 🐛 **Fixed:** The customer weight-limit banner now shows reliably on product pages.
- 🚀 **Improved:** The dashboard's **Product limits** overview now counts collection and tag limits too, so the number matches what's actually configured.
- 🚀 **Improved (Pro):** Analytics can now read the **full 90-day window**. The app asks for the additional permission only when you open the report that needs it.
- 🚀 **Improved:** Scheduled summary emails and reports now run reliably on their own schedule.

Most of this is the unglamorous half of a rule engine: the combinations that configured but didn't fire, and the values that saved but couldn't work. If you set a limit and it behaved oddly, it's worth another look.

[Per-customer limits →](/docs/customer-rules/per-customer-order-limits) · [Delivery setup →](/docs/delivery/getting-started-delivery-dates)