How to give trade customers an order cut-off without sounding like you're firing them

The message at nine the night before

You've planned the morning. You know what's going in each box, you've prepped against it, and you're about done for the day. Then the phone goes at nine: "any chance of a couple more if you've got them?"

Now you've got two answers and both cost you something. You say yes, and you're back out in the shed or up before you meant to be, rejigging what was settled. You say no, and it feels like turning away a customer who was only trying to give you more business. Neither is the message you want to be sending at nine at night.

I lived on the wrong side of this when I grew microgreens for trade. Orders and changes arrived across scattered messages, never as one list, and I planned what to grow from those messages plus whatever I could hold in my head. It went wrong in both directions: waste some weeks, a shortfall others. The late "couple more" was only the visible edge of a bigger problem, which was that orders never actually stopped arriving, so there was never a clean moment to plan against.

The fix is an order cut-off: a day and a time by which orders for the next delivery have to be in. The deadline itself is the easy part. The hard part is introducing one to people who've always messaged you whenever it suited them, without making them feel less welcome. That's what this is about.

A cut-off is a production decision, not admin

It's tempting to file a cut-off under admin, alongside the invoicing and the price list. But a cut-off decides your production. It's the line between taking orders and making the order.

You can only decide what to make once you know what's been asked for. While orders are still landing, every number you're working to is provisional, and prep done against a provisional number is prep you might have to redo. The cut-off is simply the moment you declare the taking-orders phase closed and the making phase open. Before it, you're a shop with the door open. After it, you're a producer with a list.

That reframing matters because it changes what you're doing when you set a cut-off. The deadline is what lets you make exactly what someone asked for, properly, instead of guessing and hoping. Describe it that way and the wording gets easier, because you end up stating how the work gets done rather than apologising for a rule.

Where it goes in the week

Put the cut-off far enough before delivery that you can genuinely plan and prep against a settled list, and no further. Every hour you move it earlier is an hour you're asking customers to predict their needs from further away, and a café guessing on Sunday what it'll need on Friday will guess badly and then want to change it, which puts you right back where you started.

So work backwards from your delivery. Ask the honest question: once orders are in, how long do I need before delivery to make, pack and get there without a scramble? For me, growing, that lead time was fixed by the crop itself, not by choice. For a baker it's the bake and the prove; for someone assembling to order it might be short. Whatever it is, that's your gap. The cut-off sits at the far edge of it, not a day earlier for comfort.

Name a time, not just a day. "Orders by Wednesday" invites something landing at eleven at night, technically on Wednesday, no use to you. "Orders by 5pm Wednesday for Friday delivery" is a line people can actually see.

The wording that lands

Here's the whole trick, and it's genuinely just wording. Same rule, said two ways.

The version that stings: "I'm no longer taking orders after Wednesday." That's a door closing. It tells the customer about a thing they can no longer do.

The version that lands: "To make sure you get exactly what you order, I need it in by 5pm Wednesday for Friday." That's a door held open. It tells the customer what they get in return, which is the right thing made for them and actually there on the van.

It's the same cut-off. One frames the deadline as your restriction, the other frames it as their result. You're not spinning anything, either. The reason the earlier version is true is the reason the cut-off exists: a late order is the one most likely to be short or wrong, because it lands after you've planned. Telling a customer the deadline exists so their order is right is just describing what's actually happening.

Put it where the order happens

Enforce a rule person by person and it stops being a rule. It becomes an argument you have over and over. The cut-off should be a standing fact people meet before they've even thought about ordering late, not a thing you invoke after they have.

So write it down where the ordering actually happens. On the price list, it's one line among the handful a trade buyer needs before they can order from you cold. When someone new asks how it works, it's in the standard reply you send, sitting there in plain sight. The order cut-off belongs on the same short list as your delivery days and payment terms. Once it's written where they order, you're not the one saying no on a Wednesday night. The page already said it, calmly, before anyone got close to the deadline.

This is also what stops the cut-off being about you. Nobody feels singled out by a line on a price list. They feel singled out by a text that reads as though you're telling them off.

The genuine exception

You'll still get the late ask, and sometimes you'll want to say yes. A good customer, a small addition, a week you happen to have the room. Saying yes now and then keeps the rule intact. The damage comes from saying yes in a way that quietly resets everyone's expectation of where the line is.

The move is to grant the exception and name it as one, in the same breath. "I can do it this once because I've got a bit spare today, but I can't promise it after the Wednesday cut-off as a rule." You've helped them, and you've reminded them the cut-off is real, without a lecture. The favour stays a favour. It doesn't become the new normal by accident.

The failure is the silent yes. Say yes with no comment three weeks running and you've taught that customer the Wednesday deadline is decorative, and now you're back to orders landing whenever, which is the thing you were trying to end.

What changes once it holds

When the cut-off holds, there's a moment in the week that didn't exist before: the point where orders stop and you're looking at one settled list. Not six threads to reconcile, not messages plus memory. One list, with a total you can actually plan against.

That's the difference between guessing and knowing. The waste-or-shortfall swing I kept hitting came straight from planning against a target that was still moving when I started making. A firm list at a firm time takes the movement out. You make to a number, not to a hope.

The list has to live somewhere, mind. A cut-off with the orders still scattered across six WhatsApp threads and no order book only tells you the taking-orders phase is over, it doesn't hand you the total. Whether that's a notebook, a spreadsheet or somewhere like makeweek that turns the messages into one order list, the cut-off and the list are the pair that do the work together. The deadline stops the orders; the list is what you plan from once they've stopped.

Set yours this week. Pick the delivery you care about most, work back to the last honest moment you can still make and pack without a scramble, and name the day and the time. Then write the version you'd be comfortable sending, the one about them getting exactly what they asked for. Put it on the price list. That's the whole job, and it's the difference between a business that takes orders whenever they land and one that decides, on purpose, when the making starts.