You're going to be short this week: the heads-up that keeps the account
A how-to on the shortfall heads-up: the message a producer sends once they can see they won't fill an order, days before delivery, so the kitchen can re-plan instead of finding out when the box lands light. Covers what the message says, who to tell first across a handful of accounts, not over-promising, and follow-through. First person from the microgreens and chef sides. General: no research or application notes attached, no figures beyond the five-to-ten range. One link to the delivery-receiving post; light makeweek mention, no claim it forecasts yield.
The gap you can see before anyone else can
A few days before delivery you look at what's actually ready against what's been ordered, and the two numbers don't meet. A crop came up short. A batch didn't go right. Demand ran ahead of what's on the bench. However it happened, you are going to be short, and you know it now, while there is still time to do something.
That is the whole opportunity, and most of us waste it.
When I grew microgreens I planned from scattered orders plus memory, and I got it wrong in both directions. Some weeks I had trays I couldn't sell. Other weeks I was short. The short weeks are the ones that teach you something, because they force a choice: say nothing and hope it reads as close enough, or pick up the phone while the chef can still act on it.
The surprise is the damage, not the missing tray
I spent about a decade on the other side of that delivery, receiving from producers in professional kitchens. So I can tell you exactly what a short box costs, and it isn't the product.
A kitchen can work around less. If a chef knows on Tuesday that Thursday's order is coming light, they re-plan. They change the special, pull the dish, source the gap from someone else, or shrink the portion. That's a normal day's problem-solving.
What a kitchen cannot work around is a box that arrives light during prep, with the dish already built around it and no warning. By then it's a hole in the service, discovered at the worst possible moment, by the person who trusted you to turn up with what they ordered.
The light box does the one thing you never want it to do: it delivers the bad news for you, on the morning, when it's too late to be useful. A chef checking an order against the docket as it lands is checking whether you're reliable. I wrote before about what a chef does with your delivery in the two minutes after it lands. A box that's quietly short fails that check in silence, and silence is what loses you the account.
Tell them the moment you know
The value of a heads-up is entirely in the notice. All of it. A warning on the morning of delivery is barely a warning; it's a confession with better timing than the box.
So the rule is simple and slightly uncomfortable: tell them as soon as you're sure, not when it's convenient for you to make the call. The temptation is to wait, because waiting leaves room for the shortfall to fix itself, for the last trays to come good, for the problem to not be a problem. Sometimes it does fix itself. More often you've just burned the one thing the chef needed, which was time.
If you're genuinely not sure yet, say that too. "I might be short on the pea shoots for Thursday, I'll know for certain by tomorrow morning and I'll ring you either way." A chef can plan around a maybe. They can't plan around nothing.
What the message actually says
A good shortfall message is short and it's four things: how short, on what, for which delivery, and what you can do instead.
Not an apology that spirals for three paragraphs. State it as a fact and a plan.
Something like: "Thursday's order, I'm going to be short on the coriander. I can do about half of what you asked, or I can swap the rest for something else that's good this week, or I hold it and make the next order right. Which works for you?"
That's the shape. The fact first, so they know the size of the problem straight away. Then the options, so the message hands them a decision instead of handing them your stress. A chef reading that knows in ten seconds how big the problem is and what their choices are. It reads as a supplier with a grip on a bad week, which is worth a great deal.
Resist the urge to over-explain why. The chef doesn't need the agronomy. A line is plenty: "the cold snap knocked the last sowing back." Then move to the plan.
Who gets told first when more than one is short
When I was supplying somewhere between five and ten accounts, a short week was rarely one account's problem. The shortfall had to be spread, and that meant a decision: who gets the full order, and who takes the cut.
The worst way to make that decision is the way it tends to get made by default, which is whoever happens to message you first that morning gets served, and the rest get what's left. That lets the order of your inbox decide who you let down, which is no way to choose.
Make the call deliberately instead. Before you send anything, decide who takes the cut and who stays whole. The account that ordered a set amount for a dish that only works at that amount is more exposed than the one who can flex. The account you've let down recently has used up its goodwill and shouldn't be first in line to be let down again. You know your accounts. Spend thirty seconds spending that knowledge on purpose.
You can only do this if you can see the whole week in one place: everything committed, totalled, against what you'll actually have. If your orders are scattered across threads and memory, you can't see the gap coming and you can't share out the shortfall fairly, because you can't see the whole picture at once. This is the quiet case for keeping your week's orders in one list rather than six conversations, which is the job makeweek is built to do. It won't tell you a crop is going to fail. Nothing short of a crystal ball will. What it can do is show you what you've promised, so the gap is yours to see first.
Don't promise it won't happen again
The instinct, when you've let someone down, is to swear it'll never happen again. Don't, unless you can actually guarantee it. You grow things, or you bake them, or you brew them, and living product doesn't sign up to your guarantees.
An over-promise you can't keep is a second letdown you've booked in advance. The chef remembers you said "never again," and the next short week, which will come, now reads as you breaking your word rather than as the weather.
Say what's true instead. "This happens a few times a year and I'll always give you as much notice as I can." That's a promise about your conduct, which you control, not about the harvest, which you don't. Chefs have run kitchens on seasonal supply their whole careers. They don't expect a producer to be infallible. They expect to be told in time.
Make good, and the bad week does you a favour
The last part is the one that turns the whole thing from an excuse into a track record: do exactly what you said you'd do.
If you promised half the coriander, deliver half, not a third. If you said you'd make the next order right, make it right without being reminded. If you offered a swap, make the swap genuinely good and not the thing you were going to struggle to sell anyway.
Follow-through is what tells the chef the heads-up was reliability under pressure and not the first wobble of a supplier about to become a problem. Handled cleanly, a bad week can leave you more trusted than a run of quiet ones, because the chef has now seen what you do when it goes wrong. That's information they didn't have before, and it's worth more than the order you couldn't fill.
A shortfall you announce early, share out fairly, and make good on is just a producer being honest about a hard week. A shortfall the box announces for you is the story a chef tells the next producer who asks for the account.