It's quarter to six on a Friday and the espresso machine isn't even warm yet, but you're already thumbing through three text threads. One to the fish guy. One to the bread route. One to the linen service. You're trying to remember how fast the cod moved last weekend while you unlock the door with your other hand.
So you fire off the orders, guess a little high on some things and a little low on others, and get on with your morning. Then Saturday comes in hotter than you figured, and by seven you're scraping the bottom on the one thing everybody wants.
Here's the part worth fixing. You already know roughly what you need each week, because last week told you. The ordering doesn't have to start from a blank screen every Friday. You can set up a standing weekly order that drafts itself from last week's pace, pings you with a number, and lets you confirm or tweak it in a single reply.
What a standing order really means here
A standing order is just a recurring draft. Same suppliers, same rough list, built automatically on the same schedule, ready before you'd normally sit down to do it.
The trick is that it isn't frozen. A plain repeating order (ship me the same case count every week) ignores the fact that some weeks you're slammed and some weeks it's quiet. What you want instead is a draft that looks at how fast you actually went through things last week, nudges the suggestion up or down, and then waits for your yes.
Think of it as a prep cook who writes the order up for you. They don't send it. They hand it over and ask if the numbers look right. You glance, you fix the one that's off, you hand it back.
How the draft knows what to order
Two inputs do most of the work, and neither one is fancy.
First is last week's pace. If your point-of-sale system (the register software that rings up every ticket) tracks what sold, the draft can work backward from it. Forty orders of stuffies means roughly this many quahogs. A packed Saturday brunch means this much bread. It's just counting, done for you.
Second is a quick low-stock check, which is the part only you can do. Before the draft goes out, it texts you a short list of the items that run out fastest and hurt most when you're short. You walk the walk-in for thirty seconds, tap a couple of numbers, and the draft updates.
By the time it lands in your hands, a good draft has pulled together four things:
- Standing items you buy every single week, carried over automatically.
- Pace-adjusted quantities nudged based on how last week actually sold.
- Your low-stock answers from the thirty-second count.
- A plain total per supplier so you can sanity-check the dollars before anything sends.
The thirty-second check that keeps it honest
You might wonder why you can't just let the thing count sales and send the order on its own. You can, technically. You shouldn't, and here's the reason.
Sales data tells you what left the kitchen. It doesn't know you dropped a full pan of clams Tuesday, or that the walk-in door sat ajar overnight, or that you're running a raw bar special this weekend that never showed up in last week's numbers. A count with your own eyes catches what the register can't see.
That's the whole deal with this kind of automation. It's good at the boring, repeatable counting. It's bad at knowing what's going on in your building right now. So you keep the two jobs apart: let it draft, you do the final look. The habit, once it's running, takes about this long:
- Open the text when it lands (same time each week, so it's routine, not a surprise).
- Walk the line and the walk-in for the five or six items it flagged.
- Tap in the counts, or just reply with the ones that are off.
- Read the total once. If it looks sane, send it. If it doesn't, fix it first.
Where this breaks, and what to do about it
Honest talk: a standing order is only as good as the week behind it. A handful of situations will throw the draft off, and you should know them going in.
- Holiday weeks. The Fourth, Christmas Eve, a big feast on Federal Hill. Last week's pace means nothing when this week is triple it. Override those by hand.
- New menu items. Anything that wasn't selling last week has no history, so the draft can't guess it. Add those yourself until they've got a few weeks on the books.
- Supplier switches. If the fish guy moves you from whole fish to fillets, the counts stop lining up. Someone has to update the standing list when that happens.
- Weather and events. A regatta weekend in Newport or a surprise warm spell fills every patio in the state. The draft won't know that. You will.
None of these make a standing order useless. They just mean it's a strong first draft, not a decision. On a normal week it saves you the whole chore. On an odd week it saves you the typing and leaves the thinking to you, which is exactly the right split.
Worth doing this week
You don't need software for any of this to start. The first version can be mostly habit with a little help.
- Write down your standing list. Every supplier, every item you order most weeks, and a normal quantity. One page. That's the backbone of the whole thing.
- Pick your flag items. The five or six things that are pricey, run out fast, or sink a service if you're short. Those are what the low-stock check should ask about.
- Set one order time per supplier. A fixed slot beats three scattered texts. Fish by Friday noon, bread and linens by Thursday night, whatever fits the routes.
- Do one week by hand first. Run the count, write the draft yourself, and see how close last week's numbers get you. That tells you whether automating it is worth the bother.
- Then automate the draft, not the send. When you're ready, we can set the pace tracking and the weekly reminder to run on their own, with the final yes always left to you.