Replacing Paper Order Books, Excel and WhatsApp Orders in Nepal

Walk into the office of a mid-sized distributor in Nepal at 7 pm. One person copies orders from the salesmen's pocket books into an Excel sheet. Another reads WhatsApp voice notes from shopkeepers. A third phones the warehouse to ask whether there is enough stock. By 9 pm the day's orders are somewhere in the system, mostly.

It works until the business grows past the capacity of its people. This article explains the hidden costs of paper, Excel and WhatsApp, and how to move to one system without a painful transition.

The hidden costs

Re-typing errors

Every time an order moves from paper to Excel it can be misread: 12 becomes 72, a product code is confused, a shop name is spelled two ways. Each error becomes a wrong delivery, a credit note and an unhappy customer.

Delay

Orders written at 11 am may be typed at 8 pm and dispatched the next day. In perishable categories like dairy and bakery that delay is expensive; in all categories it slows cash.

No live stock check

A salesperson on a route cannot know whether the product is available, so he promises what the warehouse cannot deliver.

Price confusion

The same shop gets different prices depending on who took the order and which price sheet was in their bag.

Lost history

Paper books fill up, get wet in the monsoon, and disappear when someone leaves. WhatsApp chats are impossible to search properly across hundreds of customers.

Weak credit control

If orders and payments live in different places, nobody sees at the time of the order that the shop is already overdue. See collecting payments on time.

No proof

A disputed order is one person's memory against another's. A timestamped record settles it.

When Excel is still fine, and when it is not

Situation	Excel works	Needs a system
Customers	Under 30	Hundreds or thousands
People entering data	One	Several, including field staff
Stock	Single store	Multiple depots, batches, expiry
Invoices	Few per day	Many, with VAT and numbering rules
Reports	Occasional	Daily or live

What one system should do

For orders, a good system lets a salesperson or dealer:

1. Select the customer and see price list, outstanding and credit limit.
2. Add products by pack size with correct prices and VAT lines.
3. See stock availability, or at least low-stock warnings.
4. Show a clear error when there is no signal, so the order can be retried or entered as soon as there is coverage.
5. Submit once, so the office sees it immediately.

Then the office can approve, dispatch, invoice and track delivery from the same record. See delivery and dispatch.

A migration plan in six steps

1. Clean your data

Prepare the product list (names, pack sizes, prices, tax treatment), the customer list (name, PAN, phone, location, type, region), and opening balances for each customer. This is the longest step. Resist the urge to import everything dirty; duplicates will follow you into the new system.

2. Choose a pilot

Pick one team, one region or one dealer group with a mix of enthusiastic and sceptical people. Success stories from colleagues persuade better than management memos.

3. Train briefly and practically

A short session on a real route is better than a long classroom lecture. Teach the five actions: day start, check in, take order, collect payment, day end.

4. Run in parallel for a short time

Allow paper for a couple of weeks, but set a firm date to stop. Parallel running forever is double work.

5. Move the WhatsApp channel

Do not ban WhatsApp; change what happens next. Shopkeepers who message orders can still do so, but your staff enters them as orders in the system, or, better, the dealer or shop orders via the dealer app. Gradually teach the biggest customers to order directly.

6. Review and extend

After a month, compare orders, collections and complaints with the previous month. Expand to the next team once the first one is stable.

Keeping the team on board

People fear that new tools mean more control and more work. Address both:

• Show how it removes the evening re-writing of orders.
• Explain what is tracked and what is not.
• Appoint a respected field person as a champion.
• Provide Nepali language screens to remove the language barrier.
• Fix teething problems quickly; an unanswered complaint kills adoption.

Mistakes to avoid

• Starting with every feature at once. Begin with orders and collections.
• Importing dirty data. Clean it first.
• No owner. Assign one person responsible for the roll-out.
• Forgetting dealers and shops. Their ordering experience affects adoption.
• Not planning for poor signal. Test saving orders on your worst route and agree what staff do when there is no connection.

What to measure after the switch

• Time from order to dispatch.
• Order errors and credit notes for wrong items.
• Percentage of orders entered by field staff at the shop.
• Outstanding days.
• Staff hours spent on data entry.

These numbers show the benefit in plain terms. Do not expect miracles in week one.

A realistic first month

Here is what a gentle roll-out can look like for a hypothetical distributor with twelve salespeople.

Week	Focus
1	Clean product and customer lists; set up price lists; load opening balances
2	Train a pilot team of three; they take orders in the app alongside paper
3	Fix problems found; pilot team stops using paper; office processes orders only from the system
4	Train the remaining nine in two groups; announce the date paper stops

By the end of the month everyone is on the system, but the pilot team has already found most of the problems. This is slower than flipping a switch, and much safer.

Answering the objections

• "The app takes more time than writing." Entering an order should take under a minute with a saved product list, and it removes the evening rewrite. Measure it during the pilot.
• "My shopkeepers prefer WhatsApp." Keep the channel and enter the order yourself, or invite the shop to try the dealer app. Many will, once they can see their own balance and order history.
• "What if the phone breaks?" Orders are saved on the server the moment they are placed, so a lost phone does not lose the books, unlike a lost notebook.
• "We are too small." If you have more than a handful of customers and more than one person touching orders, the errors are already costing you.
• "What about staff who are not comfortable with phones?" Pair them with a colleague, use Nepali screens and give them time. Often the older salespeople have the best customer knowledge and learn the app within a couple of weeks.

Keeping the books after the switch

Digital is not a magic cure. Review exceptions weekly: orders waiting for approval, orders with no dispatch, payments not allocated, customers over limit. A system makes these lists easy to produce, but someone must read them.

What to keep from the old way

Not everything about the old system is bad. Salespeople's personal knowledge of shops, the habit of recording notes about owners, and the personal relationship with the shopkeeper are valuable. Good software should capture these as notes and history, so that knowledge survives staff changes instead of leaving with the notebook.

How gamitrack handles it

gamitrack replaces order books and sheets with one app for salespeople and dealers. Orders are priced from price lists (with customer-specific overrides), VAT applies only to taxable lines, and dispatch checks stock. Salespeople take orders in English or Nepali; dealers and shops can place and track orders in the dealer app; the office gets orders, invoices, payments and the party ledger in one place.

Try it with a pilot team: start a free trial. For buying advice see choosing sales force software in Nepal.

Key takeaways

• Paper, Excel and WhatsApp cost you in errors, delay and lost history.
• Clean data first; pilot with one team; set an end date for parallel running.
• Keep customer channels, but enter every order once in one system.
• Measure order-to-dispatch time and errors to prove the benefit.