It is Thursday night and there are 31 orders for Saturday. The oven, the van and your two pairs of hands can do 20.
Nobody did anything wrong. The store just never knew there was a limit. Shopify tracks how many of a thing you have. It has no idea how many things you can make, pack or deliver in a day.
If you run a bakery, a florist, a meal prep kitchen, a print shop or anything else made to order, this is the problem that decides whether Saturday is profitable or a mess. Here is how to fix it properly.
The short answer
Cap orders by the day you fulfill them, not the day they are placed, and count every sales channel against the same number. Shopify cannot do this natively. There is no daily order limit setting anywhere in the admin.
The closest native tool is inventory. Set a product's stock to your daily limit and it sells out when you hit it. That works for one product with no lead time. For everything else you need something that counts committed work per day and closes the date, not the product, when it fills.
Merchants are asking this right now
On August 22, 2026 a merchant posted the exact question in the Shopify Community. With room for about 20 orders a day: “When you reach your limit, how would you prevent the next customer from ordering?”
Replies came in within a day, and together they map the whole problem:
- Use real inventory, not code. Native stock tracking means the sold-out state closes orders for you once the count hits zero.
- Hiding the button does not work. Two replies warned that CSS tricks fail against cart permalinks and saved carts. The customer simply checks out anyway.
- Reset it every night. One suggested a scheduled task that sets the variant back to 20 just after midnight in your store time zone.
- Count by delivery day, with weights. The last reply pointed out that capacity belongs to fulfillment dates, not calendar days, and that a big order uses more of it than a small one.
Every one of those is right. Stacked together, they still break.
Why the stock-count trick breaks
Stock set to 20, reset at midnight, is the standard advice. It fails in five predictable places.
1. Your limit is shared. Your stock is not. You can make 20 orders a day across 40 products. Inventory counts each product on its own, so 40 products at 20 each is a daily cap of 800.
2. You sell on one day and make on another. A Saturday order placed on Tuesday uses Saturday's capacity. A midnight reset counts orders by the day they were placed, so Saturday fills up quietly all week and the counter never notices.
3. Not every order is one unit of work. A three-tier wedding cake and a box of six cookies both count as one order. Your kitchen disagrees.
4. The reset overwrites real numbers. A cancellation at 4pm should free a slot. The midnight job wipes it. And if you also sell ready-made items, a blanket reset destroys those counts too.
5. Other channels do not ask. Shopify's own help page notes that the continue selling setting “doesn't apply to orders placed from Shopify POS”. Phone orders, draft orders and wholesale all use the same hands, and none of them checks your cap.
What about delivery date apps?
A date picker is the right instinct: the customer picks a day, and full days are blocked. It is also always an app. Shopify's local delivery setup covers zones, radius, postal codes and pricing, and says nothing about dates, time slots or daily limits.
Check two things before you trust one:
- Does it count orders from POS, drafts and manual entries, or only checkouts that went through its own widget?
- Does a cancelled order, or a changed delivery date, give the slot back?
If the answer to either is no, you will oversell on exactly the busy days you bought it for. And a picker only covers delivery and pickup. Shipped made-to-order goods have the same problem with no calendar at all.
What a real capacity cap has to do
Strip it down and a working cap needs four things:
- One capacity number per day, shared across every product, with heavier weights for big jobs.
- Every order counted against the day it will be made, from every channel.
- A date that closes when it fills and reopens when an order is cancelled or moved.
- A storefront that shows the next open day instead of a sold out badge.
The last one is the one merchants miss. Sold out on a cake you bake fresh every day is not true, and it sends the customer to a competitor for an order you had room for on Tuesday. Next available: Thursday keeps the sale.
The playbook
As a Dugong playbook, in plain language:
# trigger
Every new, edited or cancelled
order from any channel, plus a
7am daily brief
# steps
1. Read capacity: 20 points a day,
wedding cakes cost 5, closed
on Mondays
2. Assign each order to the day it
gets made, from its delivery
date or lead time
3. Sum committed points per day
across online, POS, draft and
wholesale orders
4. Close a day at 90 percent:
block it in the date picker and
show the next open day on
product pages
5. Reopen the day when an order
is cancelled, refunded or moved
6. Flag any day that still goes
over, before anyone starts work
7. Send a morning brief: today,
tomorrow, and the days filling
fast
Step four closes at 90 percent, not 100. Two customers can be at checkout at the same moment. A small buffer is cheaper than an apology.
Step six is the safety net. Nothing on a storefront stops every edge case. So the automation re-checks the numbers after every order and tells you while you can still call a customer, not at 6am on Saturday.
Step seven turns the cap into a planning tool. If Friday is full by Tuesday every week, you do not have a capacity problem. You have a pricing problem, or a hiring one.
Where AI earns its place
The counting is simple arithmetic. The hard part is the mess around it. A delivery date typed into a cart note. “For my mom's birthday on the 14th”, which means it has to be made on the 13th. A custom order with six extra lines that is obviously a big job. Rules break on all of that. A model reads it the way your staff would.
The honest limit: a storefront cap cuts overselling, it does not make it impossible. The only layer that can refuse a checkout outright is checkout validation with Shopify Functions, and orders still arrive through POS and drafts. That is why step six exists.
Set it up this week
Write down your real daily number. List your three heaviest products and what each one costs in capacity. Decide how a full day should look to a customer: next open date, pre-order, or hidden.
Then count last month's orders by the day they were made, not the day they were placed. Most shops that do this find two or three days they overbooked without noticing. Those days are exactly where the cap pays for itself.
Running a made-to-order shop with a capacity story, the Saturday with 31 orders, the app that forgot about POS, the week you turned the store off to catch up? The inbox is open: field-notes@dugong.live. We are collecting case studies for the next issue.