Pesticide and Crop Protection Distribution in Nepal: A Crop-Calendar Playbook
Crop protection sales come in short, intense windows set by the crop calendar. How to prepare before, run during and close out after each season.
gamitrack team · · 6 min read
On this page
For a crop protection company in Nepal the year is not twelve even months. It is a handful of short windows, set by the crop calendar and the weather, when pests and diseases spread, farmers crowd the agro-dealer's counter and the right product is either on the shelf or not. Between those windows there are long quiet stretches. The companies that do well treat the quiet stretches as preparation time: stock positioned near demand, every dealer visited, credit agreed, batches clean. This guide is organised around that calendar. It is operational guidance only; follow the rules that apply to your product registrations and licences.
How the chain is built
Manufacturers, importers and formulators sell to national or regional distributors. Distributors supply agro-dealers and agrovet shops in district headquarters and market centres, and those dealers sell to farmers. Company representatives and technical staff visit dealers, and sometimes farmer groups, to explain products and take orders. Cooperatives and projects also buy in volume through their own processes.
Three features make this chain unusual:
- Demand arrives all at once. When a pest is spotted in an area, every dealer there wants the same products in the same week.
- Credit runs backwards. Farmers pay dealers after harvest, so dealers pay distributors late, and distributors pay the company late. Credit across the chain peaks after the season, not during it.
- Batches matter. Every product carries a batch number, manufacture date and expiry. When a farmer complains, the first question is which batch.
The crop protection calendar
The windows below are a rough guide for the main crops. Timing varies by region and altitude, and between Terai, hill and mountain districts, so adjust it using your own recorded orders by branch.
| Crop and period (approx.) | Typical demand | Prepare by |
|---|---|---|
| Rice: transplanting around Asar to Shrawan | Herbicides and early insect control | Jestha |
| Rice: growing season, Shrawan to Ashwin | Insecticides and fungicides as pressure builds | Asar |
| Wheat: sowing around Kartik to Mangsir | Seed treatment, weed control | Ashwin |
| Wheat: Magh to Falgun | Insect and disease control in the field | Poush |
| Maize: spring sowing in Terai, later in hills | Insect control, for example against fall armyworm | Magh to Falgun |
| Vegetables: year-round, heavier in winter and pre-monsoon | Wide range of small packs | Ongoing |
Treat this as a planning frame, not advice on what farmers should apply. After one season in gamitrack, your own data replaces it: orders by dealer, by product and by month, for each branch.
Three phases of every season
| Before (4 to 8 weeks ahead) | During (the surge) | After (season close) | |
|---|---|---|---|
| Stock | Move stock to branches nearest demand | Daily dispatch plan, watch low stock | Dealer counts show leftovers |
| Dealers | Visit every key dealer, agree orders and terms | Reorders, complaints, out-of-stocks | Returns and credit notes |
| Credit | Set limits and due days before first dispatch | Track new sales against limits | Weekly collection drive |
| Targets | Set dealer and officer targets | Daily pace review | Compare achievement by quarter |
Before: position stock and decide credit
Model your central warehouse and each regional depot as branches. Use last season's orders by branch to decide what to move where, and set low-stock levels on the products that sell out first. Transfers between branches are recorded as stock movements, so you can see what was sent where and when.
Credit is a pre-season decision. Once the surge starts, nobody wants to refuse a dealer. Set each dealer's terms before the first dispatch; in gamitrack, payment due days are fixed from the dispatch date, so the due date is never in doubt.
During: coverage and speed
Representatives tend to visit the big dealers and skip the rest. In a surge, many small agro-dealers together sell as much as a few large ones, and an unvisited dealer buys from someone else.
Build routes with ordered stops by market centre. Each visit is checked against the dealer's geofence and recorded with a photo and outcome: an order, a no-order reason or a note, such as a pest reported in the area or a competitor out of stock. Visits outside the geofence, too short or without a photo are flagged, so a manager reviews exceptions rather than every entry. A daily integrity score per person shows whose records can be trusted at a glance.
Orders are priced from price lists, with party overrides, then party type, then the default list. VAT applies only to taxable lines, and invoices are numbered per fiscal year in IRD format. Check the current IRD rules for how your products are taxed.
Where you sell through distributors to agro-dealers, use via-dealers mode. Officers book the dealer's shop orders, the distributor sees them in the dealer app with a timeline and reminders, and fulfilled sales count toward schemes and targets.
After: count, return, collect
When the season ends, three jobs start at once.
- Dealer stock counts. The monthly dealer stock report compares expected closing stock with the dealer's count. It shows which dealers sold through and which only bought.
- Returns. Leftover or near-expiry stock may come back under your return policy. Each return carries a reason (damaged or expired), goes through review and returns to a branch with a credit note once approved.
- Collections. Aging by dealer shows the credit position. Weekly collection plans give each officer a list, and the plan shows planned against collected. Payments by cash, eSewa, Khalti, Fonepay, bank or cheque are allocated to the oldest invoices first.
When a complaint arrives
Q: A farmer says a product did not work. Where do I start? A: With the batch. Receive every product into stock with its batch number and expiry date. Because every movement is recorded and append-only, you can trace which batches went to which branch and onward to which dealer.
Q: A dealer has damaged containers from transport. What do I record? A: A return with the reason "damaged", with photos, so the loss is visible and can be raised with the transporter.
Q: A dealer is holding a batch close to expiry. A: Check batch expiry across branches every month during the quiet period. Moving near-expiry stock to where demand is coming next is better than taking it back after the season.
A worked season (hypothetical)
Suppose a distributor covers three districts from one central warehouse and two depots. In Jestha, the manager reviews last year's rice season orders by depot and moves stock accordingly. Representatives receive route lists covering every agro-dealer, including the small ones, and each visit is recorded with a photo and an order or reason.
In Shrawan, a pest is reported in one area. Visit notes show it first; the depot's low-stock alert follows two days later and a transfer goes out. In Kartik, dealer counts show two dealers still holding significant stock. One agrees to carry it into the next window; the other's near-expiry batch comes back as a return with a credit note. By Mangsir the collection plan has worked through the aging list.
Every detail here is invented to show the routine, not a measured result.
Mistakes to avoid
- Deciding credit during the surge. Set limits and terms before the first dispatch.
- Adding batch details later. Capture them at receipt, or traceability is lost.
- Visiting only large dealers. Small agro-dealers together carry the season.
- Waiting for year-end to check targets. Review dealer achievement by quarter.
Related reading
For the same dealers' other lines, see seed companies in Nepal and fertiliser dealers in Nepal. For expiry, read batch and expiry control. Industry page: Agro inputs.
Next step
Set up your key dealers and one depot before the next season starts, and run the full before, during and after cycle once. See the pricing page for plans and the free trial, or contact us.
Frequently asked questions
Can gamitrack track batches and expiry for agrochemicals?
Yes. Stock can be received into each branch as batches with expiry dates, and every movement is recorded, so you can trace which batch went to which dealer. Keep any regulatory records your licences require separately.
How do I handle season-end returns from agro-dealers?
Returns are raised with a reason, reviewed and, once approved, come back into a branch with a credit note. In via-dealers mode, a shop's return is accepted or rejected by its dealer.
Can I give distributors seasonal or annual targets?
Dealer targets can be set quarterly or annually by Nepali fiscal year, in amount or kg, and officers get monthly targets with a daily pace.
How do I see which agro-dealers have not been visited before the season?
Every visit is recorded per outlet with a geofence check, photo and outcome, so a coverage review shows dealers without a recent visit.
Put this playbook to work
gamitrack gives your salespeople, delivery staff and dealers one app — and you one place to see sales and stock.