In this guide 6 sections
Keep taking orders on WhatsApp while one person can read every message, type each order into billing and still remember each dealer’s rate. Build a dealer ordering portal once orders arrive in volume, price lists differ by dealer, credit limits need checking before dispatch, or dealers keep asking what is in stock.
What WhatsApp does well for dealer orders
Dealers already have it. Nobody needs a password, a training session or an app install, and a voice note from a shop counter reaches the coordinator in seconds. For a distributor with twenty or thirty dealers, that low friction, plus a photo of an empty shelf gap, beats any dashboard early on.
Chat is a conversation, not a record. An order lives inside a thread between a sales coordinator and a dealer, mixed with photos of damaged cartons, payment screenshots, forwarded greetings and a half-finished scheme query.
That arrangement can run for years. It holds only while one person types every order into the billing package on the day it arrives, without a backlog or a guessed pack size. The real test is festival week. Volume doubles, and two dealers demand the same scheme on the same afternoon while the forklift driver idles at the loading bay waiting for a confirmed pick list.
- No onboarding for dealers
- Voice notes and photos of the shelf gap
- Easy to negotiate a special rate in the thread
- Zero build cost on day one
Where chat orders start to break
The first crack is transcription. A dealer writes “10 box 6mm, 5 box 8mm, same as last time” and the coordinator guesses what last time meant, then types a pack the picker cannot find. The wrong carton ships. A credit note and a re-dispatch follow.
Pricing breaks next. Dealers on different slabs get different rates. A rate promised in a thread in March gets quoted back in August with a screenshot as proof, and nobody can show which price list was current then.
Credit is the third crack. A dealer over the limit still orders. Nobody checks the ledger until the invoice is raised, so dispatch waits while sales and accounts argue over a cheque that has not cleared. Late evening is the worst time. Orders land after the coordinator leaves, and the morning begins with ninety unread chats, each needing a decision before the first truck is loaded.
- Orders retyped from free text into billing
- Price slab remembered rather than looked up
- Credit limit checked after the order, not before
- Stock questions answered from memory
- Order history buried in scrolling threads
What a portal has to do that chat cannot
A portal is a form with rules. The dealer logs in, sees only their own price list, picks items from the live catalogue, and watches the running total creep toward their credit limit.
Stock visibility matters more than it sounds. Showing available, reserved and expected-by-date quantities removes the daily “is the 8mm coming this week?” message, and stops dealers ordering SKUs that sit on backorder until the scheme ends.
Each order lands in billing as a structured sales order with a number, a dealer code and line items, so nothing is retyped. Status moves from placed to confirmed to dispatched. The dealer sees where it stands.
Weigh the decision with your own numbers
Take one normal week and be honest. Count orders received, minutes spent retyping each, corrections raised after dispatch and stock queries answered by phone, because those four figures show whether chat has become a hidden job.
Then list the rules you apply by hand. Slab rates, scheme discounts, minimum order quantities, credit holds and tax codes by item all count, and a portal pays off when several need checking on nearly every order.
Also ask how dealers behave. Younger staff use a phone form, while an older proprietor who dictates orders by voice may keep calling, so plan a sales desk that keys orders in for them.
- Orders per week and per busy day
- Minutes to enter one order
- Corrections after dispatch
- Dealers over their credit limit
- Stock queries per day
A middle path before the full build
You do not have to choose all at once. Many distributors move only the order off chat. The dealer receives a link, fills a form against their own price list, and gets a confirmation back in the WhatsApp thread.
Start small. Pick the ten dealers who send the most orders and run the portal beside chat for one month, then compare corrections and entry minutes between the two channels.
Write down what version one must do. Price list per dealer, credit check, stock display and order number make a fair first scope, and you can ask any builder for a quote against those four items.
Dealer order channel scorecard
Print one sheet in three blocks. The first block logs a week of orders by dealer with columns for channel, lines, minutes to enter and corrections after dispatch. The second lists each pricing and credit rule applied by hand, ticked by how often it applies, and the third scores five readiness questions. It ends with a stay-on-chat or build-a-portal note.
Open a blank worksheet to printQuestions owners ask
How many dealers do I need before a portal makes sense?
There is no fixed number. Fifteen dealers with slab pricing, scheme discounts and credit holds can justify a portal, while eighty dealers buying one product line at one rate may not. Count rules per order, not heads.
Will dealers actually use a portal?
Most will, once it saves a call. A portal showing stock and the dealer’s own rate gets used, and a phone line for holdouts, with the sales desk keying their orders in, keeps reporting complete.
Can we link the portal to our billing software?
Usually yes. An export file or an API can carry sales orders and customer codes into the package, so check what your billing software accepts before the build. That decides how clean the handover is.
Can WhatsApp stay as the support channel?
Yes, and most teams do. Chat stays for questions, complaints and photos of damaged cartons, and it also carries order confirmations and dispatch updates sent from the portal. Only the order itself moves.