Six WhatsApp threads and no order book

The order that arrives at half past six

A message comes in at 6.34pm. "Same as last week but no radish, and can you do an extra punnet of the pea shoots." No greeting, no quantities written out in full, because the person sending it is halfway through prep and already thinking about the next thing. You know exactly what they mean. You also know you will have forgotten the "no radish" part by Thursday morning unless you do something about it right now, and right now you are packing someone else's order.

I took orders this way when I was growing microgreens and selling to trade. They did not arrive as a list. They arrived as messages, scattered across the week, in whatever shape the customer happened to be in when they thought of it. "Same as usual." A change to last week's order buried in the middle of a message about something else. Part of it now, the rest of it whenever the customer next thought of it.

The thing is, I had been on the other end of that exact message. I spent about a decade cooking, and I was head chef in the French Alps for a stretch of it. When you are the chef, you fire the order off between two jobs and trust the producer to sort it out. You are not thinking about their order book. You are thinking about your section.

Why the thread feels fine

For a while it genuinely is fine.

The chat thread is fast. The customer is already there, already messaging you about the delivery that was late or the invoice they meant to pay. Adding "and next week make it three, not two" costs them nothing. It costs you a second to read. When you are supplying a handful of accounts, you can hold the whole week in your head, and the thread is just a record of conversations you already remember having.

That is the trap, and it is worth being honest about. The thread does not break when you have five accounts. It works beautifully. It keeps working right up until the week it does not, and by then you have built your entire order-taking around it.

What a thread cannot do

A chat thread is a conversation. An order book is a different object, and the difference is not cosmetic.

A thread has no total. You cannot look at it and see how many punnets you need to grow for Thursday, because the number is spread across nine messages, three of which amend earlier ones. To get the total you have to read the whole thread back and do the sum in your head, every time, for every customer.

A thread has no cut-off. An order that lands at 6.34pm on Wednesday looks identical to one that landed on Monday. Nothing in the thread tells you which side of your planning deadline it fell on. So either you honour a change that came in too late and scramble, or you miss it and disappoint someone.

And a thread has no single view of one day. You cannot see Thursday. Thursday is smeared across six separate conversations, each in its own thread, each with its own amendments buried three messages up. To know what Thursday actually is, you open all six, read each one to the bottom, and assemble the day in your head. Then you do it again on Friday because you are not sure you got it right.

None of this is a failing of the person messaging you. They are doing the sensible thing. The thread is just the wrong tool being asked to be a ledger.

The week it stops working

For me it showed up first in production planning. I was working out how much to grow from a mix of the messages and my own memory of what people usually took, and I got it wrong in both directions. Some weeks I grew too much and it went to waste. Other weeks I came up short and had to tell someone I did not have what they were expecting.

Standing orders were the worst of it. A recurring order sounds like the safe part of the week, the bit you do not have to think about. In practice mine rarely stood. "Same as last week" quietly became "same as last week except" often enough that the word recurring was a fiction I kept alive by hand, rereading old threads to find out what last week had even been.

Then there is the order you simply do not see. It is sitting in a thread you did not reopen, because you had no reason to think that customer had messaged. Nothing surfaced it. You find it on Thursday, after the growing was already decided, and there is nothing to be done. That is the week the thread stops looking fine, and the frustrating part is that the information was there the whole time. It just was not anywhere you could act on it.

What an order book actually gives you

An order book is not a fancier chat. It is one place where an order becomes a fixed thing with a customer's name on it, a delivery day, and lines you can count. Once an order is written down like that, the questions the thread could never answer become easy. What does Thursday look like. How much do I grow. Who has not confirmed yet. Did that late change land before or after my cut-off.

You do not need software to get the idea. A notebook with a page per delivery day is already more of an order book than fifty messages, because it has a shape you can total and a place changes are supposed to go. The point is not the tool. The point is that orders live somewhere that is built to be read at a glance, instead of somewhere built for chat.

The catch with the notebook is that the order still arrives in the thread. You are still the one transcribing "same as last week but no radish" onto the page, and if you are packing when it lands, that is the moment the detail gets lost.

Let the thread be the way in, not the place it lives

The chat thread is not the enemy. It is genuinely how your customers want to order, and telling a chef to fill in a form instead is a good way to lose the chef. What you want is for the message to keep coming in on WhatsApp, and for it to stop being where the order lives.

That gap is the one thing makeweek is built to close. You keep your customers as contacts, and when an order comes in as a WhatsApp message, it can be turned into a draft order against that customer, with the line items pulled out, so the day assembles itself into something you can total and check instead of a thread you have to reread. The message stays casual. The order stops being scattered.

If you are taking orders across six threads right now and it is working, I am not going to tell you it is broken. I am telling you which week it breaks, so you recognise it when it comes.