How to Automate WhatsApp Orders Into Your ERP
What it takes to turn WhatsApp messages into ERP sales orders without retyping: the Business API, identifying the account, and handling voice notes and photos.
WhatsApp arrived on distributors' order desks without being invited. There was no rollout. A rep gave a customer their number, it was easier than email, and now a meaningful share of your order volume is in a chat app on a phone on someone's desk.
It works, which is the problem. It works well enough that nobody has had to fix it, and it is now a channel with no record, no cutoff enforcement, and a single point of failure named whoever owns the phone.
The phone on the desk is the actual risk
Before the automation question, the governance one. If orders arrive on a personal WhatsApp account:
- The order history belongs to the handset, not the business.
- Nothing is in the ERP until someone types it, so your order data is incomplete by definition.
- When that person leaves, the customer relationship leaves in their pocket.
- There is no audit trail for a disputed order beyond a screenshot.
That is worth solving on its own, before any AI enters the conversation.
Step one: the Business API, not the app
Automating WhatsApp means moving off the consumer app onto the WhatsApp Business Platform — Meta's official interface for businesses to send and receive messages programmatically.
Cornmarket Café Group
10 cases of cola 6 cases lemonade 4 of the sparkling water 2 kegs of the pale ale for tues
The original message stays attached to the order — permanently.
| Product | Unit | Qty | Line |
|---|---|---|---|
| Cola Classic 330ml — 24pk24 × 330 or 12 × 500? Both are stocked for this account | CS | 10 | $112.00 |
| Lemonade 330ml — 24pk | CS | 6 | $62.40 |
| Sparkling Water 750ml — 12pk | CS | 4 | $35.60 |
| Pale Ale — 30L kegDeposit applies — returnable | KEG | 2 | $176.00 |
- Order value
- $386.00
- Minimum
- $150.00
- Status
- Minimum met
"10 cases of cola" is not enough to pick from. ManualOut flags the pack ambiguity instead of guessing — a wrong pack size is a credit note, a second trip and a phone call.
This is a real project, not a setting. You need a verified business account, a number that is not already tied to a personal WhatsApp, and usually a provider who handles the connection. Budget a few weeks and expect the verification to be the slow part.
The customer notices nothing. They keep messaging the same number.
Step two: work out who is talking
Email carries an address that usually maps to an account. WhatsApp carries a phone number, which maps to a person — and that person might order for three sites, or be a chef who has changed employer twice.
So the account mapping has to be explicit, maintained, and able to handle one number ordering for multiple delivery points. Getting this wrong sends the right order to the wrong branch, which is a worse failure than not automating at all.
Step three: handle what actually gets sent
WhatsApp orders are not tidy text. They are voice notes recorded in a walk-in fridge. Photographs of a handwritten list. A message that says "same as Tuesday but no tea". Six messages over four minutes that together are one order.
That last one deserves attention. Message boundaries are not order boundaries. A system that treats each message as an order will create six orders, and a system that waits for a pause will sometimes cut one in half. This needs to be handled deliberately, and it is the part most integrations get wrong.
Step four: the same pipeline as everything else
Once the message is text, WhatsApp stops being special. Match the lines to the item master using the account's history. Apply their price list, minimum and cutoff. Write the sales order. Route the ambiguous line to a person with the original message attached.
If your WhatsApp orders take a different path from your email orders, you have built a second order desk. See Multi-channel order processing for why the pipeline should converge immediately after reading.
What not to build
The tempting version is a chatbot that walks the customer through a structured order — pick a product, pick a quantity, confirm.
Do not. You have just rebuilt the portal inside WhatsApp, and it will fail for the same reason the portal did: it asks the customer to do data entry for your benefit. They messaged you because it was faster than a form. A bot that turns the message back into a form has removed the only reason the channel worked.
Let them type what they want. Do the structuring on your side.