Taking orders over WhatsApp without typing them in twice

Where an order that arrives over WhatsApp breaks today

It does not break when the customer writes. It breaks afterwards.

Taking orders over WhatsApp works fine until somebody has to move that chat somewhere else. To a spreadsheet, to the management system, to a notebook. Every hand-transcribed order is an opportunity for error: wrong product, misread quantity, a price from another list.

And the error does not show up there. It shows up in the warehouse, or on the invoice, or when the customer receives something they did not order.

"The big oil" is not a product code

Real orders do not arrive tidy. They arrive the way people talk.

You get "send me 20 of the big oil", which could be three different SKUs. You get "10 boxes" without saying of what. You get a two-minute voice note with six products and a correction halfway through. You get "the usual".

Somebody on your team translates all of that into a clean order. That translation is real work, and it is invisible: it is not in any report, but it eats the mornings.

Taking the order and recording it are two different jobs

Separating them is what changes the outcome.

Taking the order is understanding what the customer wants and confirming it. Recording it is leaving it written down with the codes, quantities and prices your operation uses. Almost every tool solves the first half and hands you back the second.

When the order is born already recorded, the second half disappears. Nothing gets transcribed because there were never two versions of the same order.

You define the order's fields

A generic form makes you lose exactly the piece of data you need.

You define what fields an order carries in your business: delivery zone, payment terms, account number, the reference your warehouse uses. And the conversation asks for exactly those, not a standard list that suits anybody.

The options of a multiple-choice field are ordered however you drag them, and that order is what gets offered. It looks like a detail until you have twelve zones and the most used one is last.

The order number is assigned automatically

Every new order gets its number, starting wherever your current numbering left off.

It is assigned at the moment the order is created and cannot be edited afterwards. That is deliberate: a number you can rewrite is no use for disputing anything.

Three limits worth knowing up front:

• Orders created before numbering was switched on stay without a number.
• It is one numbered field per order.
• They are plain digits: no prefixes, no leading zeros, no resetting each January.

Who touched that order and when

Every order carries its own timeline, and it does not get rewritten.

It holds the creation, the status changes, the edits and the deletions, with the date each happened. When somebody edits, what changed is stored: which field, what label it had that day, and what happened to the order's products.

It answers a very concrete question that always comes up: "who put 30 instead of 3?". The answer stops depending on somebody's memory.

The internal notes your customer never sees

Discussions about an order end up in a separate chat nobody can find two weeks later.

Internal comments live on the order itself. You can mention a colleague and they get the notification with a direct link. They are flat: no nested replies, no reactions, no attachments.

And they are genuinely internal. The conversation serving your customer neither writes them nor knows they exist.

How many messages it takes for this to matter

More than it looks, even in a small business.

At one of our customers, a building management company, the WhatsApp operation moves about 312 conversations and around 4,137 messages a month: 1,247 incoming and 2,890 outgoing. That is not a retail chain. It is a business with a WhatsApp that never stops.

In a wholesaler that same count comes with orders inside it, and each one gets transcribed. Multiply by twelve months and there is the real cost of the spreadsheet.

What it does not do

Worth saying, because the category over-promises.

It does not guess a product that is not in your catalogue. It does not invent a price. It does not confirm stock your system did not confirm, and if your system does not answer, it says so instead of assuming. And when the order calls for a commercial decision that is not its to make, it passes it to a person.

Key takeaways

• The problem with taking orders over WhatsApp is not receiving the message, it is recording it again somewhere else.
• The customer's real language ("the big oil", "the usual") is what makes transcription expensive.
• You define the order's fields, and the conversation asks for exactly those.
• The order number is assigned automatically at creation and is not editable afterwards.
• The timeline answers who touched what and when, without depending on memory.
• Internal comments stay on the order, and your customer never sees them.