Skip to content
ManualOut
All posts
Product7 min read

Multi-Channel Order Processing for Distributors

Email, PDF, spreadsheet, WhatsApp, voice. Five channels, one item master, one set of account rules — and only the reading stage should differ between them.

Most distributors take orders on five channels and have five different ways of handling them. Email goes to the shared inbox. WhatsApp lives on a phone on someone's desk. Voicemails get written on paper first. PDFs get opened, read, and retyped.

That is five processes, five places for an order to get lost, and five different answers to the question "what did this customer actually order?"

The channels differ less than they appear to

Strip away the transport and every one of these arrives as the same thing: a customer saying what they want, in their own words, in whatever form was closest to hand.

"12 ctn still water 500" is the same instruction whether it was typed into an email, sent on WhatsApp, spoken into a phone, or printed on a purchase order. The reading is different. Nothing after the reading is different at all.

So the pipeline should fork once and then converge

ManualOutPO #12031Need attention
Source · Voice23:04

Voice note · 0:34

"Hi, it's Danny at Palewood. For Friday — two cases of the plum tomatoes, four of the chopped, um... six bags of the 00 flour, three of the semolina. And can I get eight litres of the rapeseed. Oh and the good olive oil, two of those. That's it. Cheers."

The original message stays attached to the order — permanently.

Extracted itemsMeridian · NORTHGATE
ProductUnitQtyLine
Plum Tomatoes 2.5kg — 6pkCTN2$36.80
Chopped Tomatoes 2.5kg — 6pkCTN4$68.80
Flour Type 00 — 25kgBAG6$135.00
Semolina — 25kgBAG3$59.40
Rapeseed Oil 1LLTR8$36.80
Olive Oil — extra virgin?"the good olive oil" — three products could matchLTR2
Order value
$336.80
Minimum
$200.00
Status
Minimum met

Recorded at 11pm, read at 11pm. The recording stays attached to the order, so when Danny says he asked for the extra virgin, you can listen.

The same order arriving three ways. The extracted lines are identical — the channel is a detail of the reading stage, not a different pipeline.

There is exactly one stage where the channel matters — turning the incoming thing into text and line items. After that, every order should hit the same path:

  • Identify the account. Which customer, which entity, which delivery point.
  • Match each line to the item master, using that account's ordering history.
  • Apply the account's rules — price list, minimum order value, cutoff, warehouse.
  • Write the sales order to the ERP.
  • Route anything unresolved to a person, with the original message attached.

If a WhatsApp order and an email order take different paths through those five steps, you do not have multi-channel order processing. You have several single-channel processes and a naming convention.

Why the convergence is the point

Once every channel produces the same structured order, several things stop being problems.

Your cutoff becomes real, because it is evaluated on arrival regardless of how the order arrived. Your minimums apply to the voice note as well as the PDF. Your reporting covers all your orders rather than the ones that came through the systems that record things.

And the question "how many orders did we take on WhatsApp last month?" acquires an answer, which for most distributors it currently does not have.

Keep the original, always

One rule matters more than the rest: whatever the order came in as, keep it, and attach it to the sales order.

When a customer says they ordered six and the order says twelve, the argument ends in four seconds if the original message is one click from the order line. If it is on someone's phone, or in a shared inbox with four hundred other emails, or on a voicemail that has since been deleted, the argument ends differently — usually with a credit note.

The thing not to do

The instinct is to reduce the number of channels. Twenty years of portals, apps and order forms says this does not work, because the channel is the customer's choice and they have consistently declined to change it.

Adding a channel costs you nothing if the pipeline converges after the reading stage. It costs you a whole new process if it does not. That is the actual design decision, and it is upstream of every other one.

See it run on one of your own orders

Send us a real order — the messiest one you can find. We will run it live and show you what happens when it works, and when it does not.