The Coffee Shop Supplier Ordering Schedule

The cost of 11 AM

Your dairy's cutoff is 4:50 PM. Your paper-goods supplier cuts off at 10:50 AM. Your bean roaster needs orders by 9 AM on Monday for a Wednesday delivery.

Miss any of these windows and the consequences cascade. No order today means no delivery tomorrow. No delivery means you are short on milk for the Saturday rush, or out of cups by Sunday afternoon.

In my experience, a missed cutoff is one of the most preventable ways a week goes sideways. It happens not because people are careless, but because the information needed to place the order is not ready early enough, or the deadline slips through the cracks during a busy morning.

You do not need to remember four clocks. You need one weekly ordering schedule that already knows them. This post builds it.

Why cutoffs get missed

The information is not ready

To place an order, you need to know what you have and what you need. If your morning count has not been done yet, or yesterday's delivery has not been logged, you are working with stale data. The manager knows they need to order but cannot figure out quantities until they count, and by then the cutoff has passed.

No one owns the task

"Someone should place the paper order" is not a system. When ordering responsibility is shared informally, it is easy for everyone to assume someone else handled it. This is especially true on busy mornings or during shift transitions.

The deadline is invisible

A cutoff time stored in a supplier's email from six months ago is not a usable deadline. If the cutoff is not surfaced in the daily workflow, it competes with every other demand on the manager's attention. And it usually loses.

Lead time confusion

"Next day delivery" sounds simple, but it depends on the cutoff. An order placed at 10:51 AM for a supplier with a 10:50 AM cutoff is not next-day delivery. It is two-day delivery. And if tomorrow is Sunday and they do not deliver on Sundays, it is three-day delivery. These edge cases catch people off guard.

Building a cutoff-proof system

Step 1: Document every supplier window

Create a single reference with every supplier's ordering details. Yours will read something like this, with your own suppliers swapped in:

This seems basic, but in my experience the details rarely live in one place. They are scattered across emails, supplier websites, and the manager's memory.

Step 2: Calculate order-by times

Work backward from the cutoff. If the cutoff is 10:50 AM and you need 15 minutes to review and submit the order, your real deadline is 10:35 AM. If counting takes 10 minutes before that, you need to start counting by 10:25 AM.

For each supplier, define:

• Count start time: When the relevant items need to be counted
• Review start time: When the manager needs to sit down and finalize quantities
• Submit deadline: The actual cutoff, minus a 5-minute buffer

Step 3: Assign ownership per supplier per day

Instead of "someone should order," make it explicit. Monday's paper order is assigned to the opening manager. Wednesday's bean order is assigned to the shift lead. Put names on tasks.

Step 4: Make cutoffs visible

The best system is one where approaching cutoffs are impossible to ignore. A countdown timer on a dashboard, a scheduled notification 30 minutes before cutoff, or a daily checklist that includes order deadlines. Whatever mechanism you use, the cutoff should be surfaced proactively, not discovered reactively.

Step 5: Build in escalation

What happens if the primary person is busy, sick, or forgot? Define a backup. If the paper order has not been submitted by 10:30 AM, the task escalates to the cafe manager or owner. This is not about blame. It is about ensuring the order goes in.

The delivery calendar view

One of the most useful planning tools is a weekly view showing expected deliveries by day. Say your paper-goods supplier delivers daily, your dairy runs Monday through Saturday, and your roaster arrives mid-week:

Monday: paper, dairy Tuesday: paper, dairy, beans (if ordered Mon) Wednesday: paper, dairy, beans Thursday: paper, dairy Friday: paper, dairy Saturday: paper, dairy Sunday: paper only (no dairy truck)

This view immediately reveals the risk days. Sunday has no dairy delivery, so Friday's dairy order needs to cover through Monday. If you are closed Monday, Friday's order needs to cover through Tuesday.

Planning orders against this calendar prevents the "we ordered but we won't get it in time" surprise.

Build your week around the windows

Here is the walkthrough, using a supplier set most cafes will recognize: a paper-goods supplier with a 10:50 AM cutoff and next-day delivery every day, a dairy with a 4:50 PM cutoff and no Sunday truck, a roaster that needs orders by Monday 9 AM for a midweek arrival, and a matcha supplier five to seven business days out.

Start with the tightest clock and work outward.

Monday is the heavy morning. The roaster's window closes at 9 AM, before the rush settles. That means bean quantities get decided Sunday, not Monday. Then the 10:50 paper cutoff, then the 4:50 dairy cutoff. Three windows, one day; Monday is where an undocumented schedule fails first.

Tuesday through Thursday are maintenance days. Paper before 10:50 if the count says so, dairy before 4:50. These are the days to check the long-lead items: if the matcha tin is at or below par, Tuesday is the order day, because five to seven business days from Tuesday still lands inside next week. Working out how far ahead to order matcha is the whole game here; order it Friday and you are hoping.

Friday is the biggest order of the week. The dairy placed before 4:50 PM Friday is the one that has to survive Saturday's rush and Sunday's empty delivery slot. Size it for two and a half days, not one. This is where ordering from your count instead of your gut earns its keep; the quantity math for that Friday order is the difference between a calm Sunday and a corner-store run.

Saturday closes the loop. The 4:50 dairy order Saturday is Monday's milk. Skip it and Monday opens on whatever Friday left behind.

Written out, the whole schedule fits on an index card:

• Sun evening: decide bean quantities
• Mon: beans by 9:00, paper by 10:50, dairy by 4:50
• Tue: paper by 10:50, dairy by 4:50, check matcha and other long-lead tins
• Wed / Thu: paper by 10:50, dairy by 4:50
• Fri: paper by 10:50, the big dairy order by 4:50
• Sat: dairy by 4:50 for Monday

Your suppliers and clocks will differ. The method does not: tightest window first, long leads on a fixed check day, and the weekend gap sized into Friday. For items with week-long leads, project stock to the delivery after next, not the next one; projections do this arithmetic continuously.

Emergency protocols

Even with a good system, orders will occasionally be missed. Have a plan:

• Identify backup suppliers for critical items. Which grocery store stocks your oat milk brand? Can you buy emergency dairy from a restaurant supply store?
• Know the cost premium. An emergency run means corner-store prices and markup, and that premium is the real price of a missed window.
• Log every miss. Track which supplier, which day, why it was missed, and what the impact was. Patterns will emerge (for example, Monday cutoffs are missed more often because weekends disrupt the routine).

Start with the index card

Write your version of the weekly schedule today: every supplier, its window, its delivery days, its lead time, and who owns it on which day. Tape it where the orders get placed. The quantities can come from math later; the schedule has to exist first, because no amount of good ordering arithmetic survives a window you did not know was closing.