Blackout dates on Shopify: planning holiday and peak-season deliveries

Blackout dates are the days customers can’t select in your delivery date picker: holidays you’re closed, shutdown weeks, capacity-capped days around peak season. On a Shopify store doing scheduled deliveries, they’re the difference between a holiday week you planned and a holiday week that happened to you.

The unplanned version looks like this: a national holiday lands mid-week. Orders placed for the holiday itself are impossible, the day before is overloaded, your courier runs a reduced schedule you learned about from a flyer, and half your staff booked leave around it. Meanwhile the calendar on your storefront keeps offering every single day like nothing is happening.

That’s the week you find out whether your delivery scheduling can block dates. If it can’t, you spend it apologizing, refunding rush orders, and manually calling customers to move deliveries they already planned around.

I’m the developer of MSK: Delivery Date Scheduler, and this article is about the unglamorous setting that prevents that week: blackout dates. It’s written for Q4 planning, but the same mechanics apply to any closed day, from a public holiday to a trade show where your whole team is working a booth.

What a blackout date does

A blackout date is a day the customer cannot select. Full stop. It doesn’t shift orders, doesn’t ask the customer anything, and doesn’t appear in the picker at all. Combined with your delivery days and lead times, it defines the set of dates your storefront is willing to promise.

In my app, blackouts are entered as ranges, a start date and an end date, not one day at a time. That distinction sounds small and isn’t. Holiday planning is done in blocks: closed December 25 to 26, reduced capacity January 1 to 5, team off for a week in August. Entering those as ranges takes thirty seconds. Entering them day by day is why some stores just… don’t, and ride into peak season with an open calendar.

The three-layer calendar

Before blocking anything, get the layers straight, because they stack:

1. Delivery days handle the repeating closure: never Sundays, never Mondays, whatever your week looks like. Put every regular off-day here, once.
2. Blackout ranges handle the exceptions to the pattern: holidays, shutdowns, inventory counts, the trade show. Anything with a start and an end.
3. Lead time and cutoff handle readiness, the gap between ordering and delivery. They don’t know about holidays on their own, which is the point of layering.

The interaction is where merchants get caught. Say your last delivery day before a holiday is Tuesday the 23rd, and the next is Friday the 27th. With a 1-day lead and a 2 PM cutoff, a customer ordering Tuesday at 5 PM doesn’t get Wednesday; it’s blocked. They don’t get Thursday either. The picker walks them straight to Friday, showing “today’s cutoff has passed” on the way. Layer the rules and the calendar sorts itself; fight them and you’re hand-editing dates during your busiest week.

A Q4 planning checklist

Work through this before the season starts, not during it. Roughly in order:

October: map every fixed date. Public holidays for every market you deliver to, your own closing days, your courier’s published holiday schedule. If you deliver to several countries, remember their holidays differ. Enter each block as a blackout range, with a note to yourself about which is which.

Early November: set the capacity crunch blackouts. These aren’t closure days; they’re days you’re technically open but can’t take more scheduled orders. Black Friday week is the classic. If your delivery operation maxes out, block the days that will fill first. It feels wrong to close off days in your busiest month. It’s better than the alternative: taking orders for December 24 on December 20 and failing at a quarter of them.

Mid-December: lengthen the lead time, not the blacklist. As Christmas approaches, the honest move is usually a longer lead time rather than more blackouts. Lead time is one number; the blackout list is twenty rows. Raise it, and every remaining date shifts out automatically. Drop it back in January.

Decide your last-order date, and advertise it. Work backwards from your last delivery day: lead time plus cutoff. Then put “order by December 19 for delivery before Christmas” in your announcement bar and product pages. The blackout system makes this promise true; the marketing makes it sell. (For the bar itself, I’ll admit a bias: I also built MSK: Announcement Bar Timer, which exists precisely for deadline messaging like this.)

January: clean up. Remove the seasonal blackouts, restore the lead time, and note what actually broke for next year. The range list from this year is your starting template for the next.

The mistakes I see

Blocking the holiday but not the day before. If December 25 is blocked, demand piles onto the 24th. If the 24th is genuinely your max-capacity day, block or shorten it deliberately. The calendar always routes around a black hole; decide where the traffic goes.

Blackout dates entered in the wrong year. Worth saying because it happens constantly: check the year on every range. A blackout on 12/25/2025 does nothing for 2026, and the failure mode is silent.

Forgetting the return trip. Peak season isn’t just deliveries out; it’s also returns and exchanges in January. Plan a little lead-time slack for the first week of the new year, when your team is processing the aftermath.

Treating blackouts as a substitute for capacity planning. Blocking dates reduces the days you can promise; it doesn’t add capacity. If your December problem is throughput, no calendar setting fixes it. What the calendar does is make sure you only promise what your throughput can honor, which is the part of the problem a store can actually control.

One honest limitation

Blackouts in my app are store-wide and absolute. There’s no “partially blocked, only ten slots left” and no per-product exceptions. If you need a day that’s closed for one product line but open for another, or slot-level capacity, that’s outside what it does today. For a single-operation store, which is most stores doing scheduled delivery, store-wide blocking covers the real cases, but you should know the edge before you plan around it.

Getting started

If you take one thing from this article: spend one hour in October with your calendar, your courier’s calendar, and the blackout list, and you’ll save yourself the apology-email week in December. The picker respects every range you enter, in the customer’s own language, with no theme edits needed to install.

MSK: Delivery Date Scheduler is $5 a month with a 7-day free trial, and support goes to the person who built it, answered within 24 hours. The full setup guide covers the rest of the settings, and the app details are here.