The standing order that never stood
A named-problem piece on the wholesale "standing order" that isn't: a recurring order changes just often enough that you re-check and re-key it by hand every week, and that maintenance never gets logged as work. First person from the microgreens side, five-to-ten accounts. This revision removes the critic's sole blocker, the invented "three accounts" threshold, replacing it with "when you're small", since the only account figure available is the recorded five-to-ten range. Recognition only, no product pitch. General throughout; no research or applications attached.
The scroll-back before you pack
Before I packed, I would go back up the message threads and read them again. Not to find new orders. To check the ones I thought I already had.
The account that takes the same thing every week: was it the same this week? Most weeks the answer was yes. But last week it hadn't been, and I only caught that because I happened to reread the thread before I cut. So this week I read it again, and the week after, because once you have been caught out you stop trusting the word "usual".
That small act of not trusting an order I supposedly already had is the thing I want to name. It never went on a list. It felt like nothing at all. And it was, in truth, the order book being quietly rebuilt by hand every single week.
What the word promises
"Standing order" sounds like a decision you make once. Set it, and it repeats. Predictable work, predictable delivery, money you can more or less count on. You plan your growing around it and never have to think about it again.
That is not what a standing order is when you sell to trade. It is a default. A good one, usually. Right most weeks.
And wrong often enough that you can never quite put it out of your mind.
The small changes that break it
None of the changes were dramatic. That is exactly why they were dangerous.
Can you do an extra tray this week, we've got something on. Skip me next week, we're away. We're closed for the bank holiday. Can you bring a bit more Thursday, there's an event. Each one is reasonable. Each one is a small kindness a good supplier says yes to without a second thought. And each one lands as a single line in a thread, hours or days before the order it changes, sitting among messages about a delivery time and a question about an invoice.
Say yes to five of those across five to ten accounts in a week and the "recurring" order and the actual order have drifted apart. Not by much. By enough.
The work that doesn't look like work
Here is what closing that gap actually took. Before every pack, I held the default in my head, read back through the week's messages, and adjusted the default by whatever those messages said. Then I trusted the result enough to cut against it.
That is a task. It happens every week, it has a real cost when you skip it, and it takes proper attention because the messages arrive scattered rather than as one list. But it never felt like a task, because from the inside it presents as remembering. You are not doing admin. You are just keeping it all in your head, the way you always have. Which is fine when you're small and quietly ruinous as you add accounts, and it is a big part of why those threads never add up to an order book.
Two ways to get it wrong
When the standing order and the real order drift apart, you get it wrong in one of two directions.
You trust the default when it was actually lower this week, and you cut too much. That surplus does not keep. It goes in the bin, and you paid for the seed and the bench space and the hours to grow something nobody ordered.
Or you trust the default when it was actually higher, or you missed the message asking for the extra tray, and you turn up short. Now you are apologising to an account that did tell you, and was right to expect you to have read it.
I got it wrong in both directions. Waste some weeks, shortfall others. The fiction feeds both, because a fiction you half-believe is worse than no order at all. No order and you would ask. A standing order and you assume, and the assumption is what bins the tray or lets the account down.
Why it never makes it onto a list
You will not find "re-check the standing orders" written down anywhere, on anyone's task list or in any tally of the hours the week takes. It isn't a job. It is a low hum of doubt you carry to the packing table: is the usual still the usual, did I miss one, is there a message from Tuesday I've forgotten.
So the first useful thing is simply to call it what it is. A recurring order is not a thing that recurs on its own. It is a thing you keep true by hand, every week, at some cost to your attention and occasionally to your stock. Naming that does not make the changes stop arriving. It does stop you treating the maintenance as nothing, which is the first step to giving it somewhere to live other than the back of your mind.
The standing order rarely stands. Knowing that, and building your week as though it were true rather than hoping it is, is most of the difference between a Wednesday that runs and one that catches you out.