Instant Noodles Distribution in Nepal: Sales Tracking and Stock Control Playbook

Instant noodles look simple from the outside: a cheap packet, sold everywhere, bought every day. Inside a distribution company the picture is harder. Margins per packet are thin, so profit depends on volume, on never running out at the dealer, and on not writing off cartons that sat too long in a damp godown. This guide describes how the trade typically works in Nepal, where it goes wrong, and how to run sales tracking and stock management together so each one supports the other.

How the noodle trade works in Nepal

A typical noodle brand sells through layers. The manufacturer or importer holds stock in a central warehouse and one or more branch godowns. From there, goods move to dealers or distributors who cover a town, a valley or a Tarai district. Dealers supply wholesalers and retail shops, from the large supermarket to the single-room pasal at a village junction. Company sales officers walk or ride the routes, book orders from shops, and push the dealer to fulfil them.

Some companies supply shops directly in the core market and use dealers for outer districts. Others run everything through dealers. Either way you have two kinds of sale to track: the primary sale from the company to the dealer, and the secondary sale from the dealer to the shop. Most reporting problems start because people only measure the first.

Route types

• Urban beats: dense shops visited weekly or twice a week, mostly small orders in cartons or half-cartons.
• Highway and town-to-town routes: fewer shops, larger orders, long travel, a dealer or sub-dealer holding local stock.
• Hill and remote routes: fortnightly or monthly visits, orders bundled with other products, high transport cost.
• Modern trade and institutional: supermarkets, canteens, hostels and trekking-route lodges with their own terms.

Credit and schemes

Dealers usually buy on credit with a due date, often tied to dispatch. Shops buy cash or short credit. Schemes are constant: a free packet per carton, a price-off during a campaign, or a quarterly target reward for dealers. A scheme without a record is a leak, because nobody can say later which dealer earned what.

Seasonality, expiry and damage

Demand rises with trekking and travel seasons, festivals and cold weather, and softens when fresh food is abundant. Noodles have a shelf life, so slow stock near the end of life must be pushed or returned before it expires. Humidity, rough handling on long truck runs and rat damage produce broken cartons. Returns and damage claims need a trail or they turn into arguments.

The typical problems

1. Primary numbers look good, secondary numbers are unknown. The dealer bought a truck, but how much reached shops?
2. Phantom visits. Officers report covering a beat they did not fully walk.
3. Stock-outs at dealers because reorders depend on memory and phone calls.
4. Old batches stuck at a branch or a dealer while new batches ship out first.
5. Collections slip because due dates are tracked in a notebook.
6. Scheme disputes at quarter end with no clean basis for calculation.
7. Damage and returns accepted informally, with no matching stock or credit entry.

A practical playbook

Weekly rhythm

Day	Sales side	Stock side
Monday	Review last week visit and order numbers per officer	Review low-stock list per branch, plan replenishment
Tue to Fri	Officers run beats, book shop orders	Dispatch dealer orders, record every movement
Saturday	Follow-ups on pending dealer fulfilment	Check expiry list, plan pushes for near-expiry batches
Month end	Targets vs achievement, collections vs plan	Dealer stock count against expected closing

Checklist for a healthy noodle route

• Every shop on the beat is a named outlet with a location, not a nickname.
• Beat days are fixed and the order of stops is planned.
• Each visit ends in an outcome: order, no order with a reason, or closed.
• Closing stock at the shop is noted so the next order is sized properly.
• Damaged cartons are recorded as returns, not absorbed silently.

Questions to ask every month

• Which dealers sold out to shops, and which only bought in?
• Which beats have the lowest productive-call ratio?
• Which batches are the oldest on hand, and where?
• Which scheme paid out, and did the target actually get met?

How to run it in gamitrack

gamitrack combines field sales and stock management for companies like this. These are the workflows that map to the noodle trade.

1. Set up the outlet and dealer structure. Add dealers and shops as parties with geolocation. New outlets added in the field go through an approval step, so your master list stays clean. Link shops to the dealer that supplies them so secondary sales are attributed correctly.

2. Build routes and beats. Create routes with ordered stops and assign them to officers. Each officer starts the day with GPS, sees today's stops, and ends the day when the beat is done. Attendance is derived from the day start and end, including late and early leave, using Nepal time.

3. Verified visits. A visit is geofenced and needs a photo as proof, uploaded from the shop. Inconsistencies such as visits outside the geofence, very short visits or missing photos are flagged for a manager to resolve. This addresses phantom visits without a lecture.

4. Book orders with real prices. Orders are priced from price lists, with overrides by party, then by type, then the default. In via-dealers mode an officer books a secondary order that the dealer fulfils in the dealer app, and the dealer can see the progress timeline. Weights in kg are tracked on products and orders, which helps when trucks are loaded by weight.

5. Stock by branch, batch and expiry. Define products and SKUs with batches and expiry dates. Every stock movement is appended to a ledger and cannot be silently edited. Low-stock and expiry views tell you what to reorder and what to push first. Use branches to mirror your central warehouse and regional godowns.

6. Dealer stock counts. At month end, record each dealer's physical stock. gamitrack compares it with the expected closing figure and shows the variance, so you see which dealers hold more than they report or less than they should.

7. Returns with a trail. Sales returns are approved into a branch, put stock back and raise a credit note. For via-dealers sales, a shop's return goes to its dealer, who accepts or rejects it in the app.

8. Schemes, targets and collections. Configure schemes with tiered rewards on fulfilled secondary sales, and approved rewards credit the dealer ledger. Set monthly officer targets with a daily pace, annual dealer targets by Nepali fiscal quarter, and weekly collection plans against actual payments. Payment due days run from dispatch and stay fixed once set.

9. Commissions and expenses. If you pay officers commissions on secondary sales, rates and the minimum achievement rule are configured in the system, with month-end drafts. Field expense claims with receipt photos go to a manager for approval.

A hypothetical example

Imagine a noodle company with one central godown and two dealers in different towns. An officer visits a shop in town A, notes closing stock of two cartons, and books a six-carton secondary order. The dealer sees the order in the app, fulfils it, and stock leaves the dealer's side of the chain. At month end the dealer's count is compared with expected closing. This is only an illustration to show the flow, not a real result.

Related reading

If you also sell biscuits and snacks through the same dealers, read Biscuits and snacks distribution in Nepal. For the broader category, see FMCG and packaged food, and for bakery-adjacent lines see Bakery and confectionery.

Where to start

Do not try to digitise everything in week one. Start with one region: load its dealers and shops, build five routes, and run them for a month while recording stock movements at the branch. When the numbers feel trustworthy, add targets and schemes. You can see plans and what is included on the pricing page.