HR & Payroll Software for Retail Chains in Nepal
One attendance log across every outlet, a store manager who approves only their own team, geofenced field visits for merchandisers, festive leave blackouts, and PF/CIT/SSF/eTDS payroll that reads payable days from all of it.
Twelve Outlets, One Attendance Log, One Payroll Run
Retail HR is not complicated, it is distributed. NepalHRM puts the approval where the staff are and the reporting where the management is.
A Retail Chain's HR Problem Is a Distance Problem
The work is not hard. It is happening in fourteen places at once, and the record has to arrive at head office before payroll closes.
Twelve outlets means twelve places a punch happens and one place it has to be counted. Chains usually solve this with twelve WhatsApp groups and a monthly reconciliation.
Push approvals to head office and month-end becomes a bottleneck. Push them to store managers without a boundary and everyone can see everyone else's roster and pay.
Merchandisers, sales officers and distribution staff spend the day at client sites. Neither a fixed device nor an honour system produces a record anyone trusts.
The festive weeks that carry the year's revenue are exactly the weeks staff ask to be away, and refusing case by case turns a policy question into twenty arguments.
The Shop Floor, the Road and the Head Office
Outlet attendance, scoped approvals, field work with a location on it, and a payroll run that reads all three.
Every outlet as a branch
Each store carries its own staff, its own biometric devices and its own reporting, while payroll, leave and headcount still close once for the whole chain.
Approval scoped to one store
A branch manager assignment authorises one person to view and approve attendance for one branch and nowhere else. It is an approval grant, deliberately separate from the org chart.
Readers at the shutter, one log
ZKTeco and Hikvision devices are added per outlet by vendor, model, IP, port and serial, and an edge agent on the store network keeps collecting punches when the link drops.
Import the readers you already bought
For a device NepalHRM does not talk to directly, map its monthly export once (header row, Time In column, BS or AD dates) and reuse that profile every month across the chain.
Geofences for field work
Named client, office, home and site geofences, capped at 500 m for pin-point kinds and 5 km for a warehouse or yard, so a check-in means a place rather than a district.
Field visits with a status and a photo
A visit moves through Planned, En route, Arrived and Completed, carries photos and a label, and mileage is computed from the start and end geofences for reimbursement.
Rosters per outlet, published weekly
Opening, closing and split shifts per store, assigned in bulk with a date range and a rotation. Changes stay a Draft until you publish the week to staff.
Blackout dates for the festive peak
Name the range when leave is unavailable and the policy carries the decision. Dashain, Tihar and your own sale weeks sit on the same calendar as the public holidays.
Allowances priced per day worked
A field or duty allowance can be a per-day rate rather than a monthly figure, paid for the days actually earned, with payable days coming from approved attendance.
A day on the road that leaves a record.
Merchandisers and sales officers are the hardest people in a trading company to manage fairly, because the honest ones and the rest produce identical paperwork. NepalHRM gives the day a shape instead: client sites are named geofences, held to 500 m so arriving means arriving, with a wider 5 km allowance for a warehouse or yard. A visit moves through Planned, En route, Arrived and Completed, carrying its label and its photos. The distance between the start and end geofence is measured rather than claimed, which turns the monthly mileage conversation into a reading exercise.
- Client, office, home & site geofences
- 500 m pin-point cap, 5 km for a site
- Planned 路 En route 路 Arrived 路 Completed
- Mileage measured from the geofences
The three modules a retail chain switches on first
Attendance across the outlets is the whole problem. Rosters and payroll are what it feeds.
Devices per branch, edge agents, import profiles, the punch log and regularisation.
Opening and closing shifts per outlet, bulk assignment, rotations and the weekly publish.
Payable days from attendance, per-day components, PF, CIT, SSF and eTDS on IRD slabs.
Questions from Chain HR and Operations Managers
Yes. A branch manager assignment authorises one employee to view and approve attendance for one branch, and it is deliberately separate from the reporting line in the org chart. So a store manager clears their own team's attendance and regularisation requests without seeing another outlet's roster or pay, while head office keeps the consolidated view across the chain.
Each outlet is a branch with its own devices. ZKTeco and Hikvision readers are added per branch by vendor, model, IP, port and serial, and an edge agent on that store's network collects punches and posts them upstream in signed batches, continuing to read the device while the internet is down. Every outlet's punches land in one attendance log, which is what payroll reads.
Usually not. If the device is not one NepalHRM talks to directly, import its own monthly export instead: you map the file once, recording which row is the header, which column is Time In and whether the date column is Bikram Sambat or AD, and save that as an import profile. The same file then imports every month without remapping, across every outlet using that model.
With geofences and field visits. A geofence is a named client site, office, home or site area, capped at 500 m for pin-point kinds and 5 km for a warehouse or yard. A visit moves through Planned, En route, Arrived and Completed with photos and a label attached, and travel between the start and end geofence is measured for mileage reimbursement rather than claimed from memory.
Yes. Blackout dates hold the ranges when leave is not available, so the policy carries the refusal instead of a store manager repeating it twenty times. They sit alongside Nepali public holidays and your own closures on the Bikram Sambat calendar, and leave balances, accrual and the fiscal year close all read from the same calendar.
From attendance. Approved attendance sets payable days for the period, and allowances or deductions can be priced per day worked rather than as a monthly figure, so a field allowance or a staff-meal deduction reflects the days actually earned. Employment types cover full time, part time, contract, intern and probation, each with its own contract record and end date where one applies.
Yes. PF, CIT, SSF and eTDS calculate on the current IRD slabs for every employee across every outlet in one run, with approved overtime priced at its rate tier. Payslips are bilingual in Nepali and English, bank transfer files are generated for the disbursement, and reports export to Excel, PDF and CSV per branch or for the whole chain.
Get Every Outlet's Attendance Into One Month-End
Bring two outlets and one month of punches, including the machine you already own. We will import it, scope the approvals to each store, and run the payroll.
- One log across every outlet
- Store-scoped approvals
- Geofenced field visits
- Free onboarding