HR management for stores & chains: clock in with a QR code, auto-calculate overtime and late penalties, build flexible schedules and compute staff commissions — no more manual Excel.
Staff clock in with a QR code, an attendance device or manually. Record clock-in/out times accurately, with flexible support for split shifts and half-day attendance.
| Staff | In | Out |
|---|---|---|
| Minh | 07:58 | 17:02 |
| Lan | 08:15 | 17:00 |
| Hùng | 07:45 | 19:30 |
Automatically total attendance and calculate pay by hour / shift / month, add overtime, deduct late and early-leave penalties, and include allowances. Clear payslips with fewer errors.
| Staff | Days | Net pay |
|---|---|---|
| Minh | 26 days | 9.8M |
| Lan | 24 days | 8.4M |
| Hùng | 27 days | 11.2M |
Plan work shifts, let staff register for shifts, and approve leave right in the system. Track staffing surplus or shortage for each time slot and branch.
Calculate commissions based on sales revenue and track each employee's KPI. Connect sales data directly for fair rewards and penalties that keep staff motivated.
With so many staff, calculating attendance and payroll at month-end used to be exhausting and error-prone. Now everyone clocks in by QR, the software generates the payslips automatically, and I just review and approve.
It is all HR, but a restaurant counts hours differently from a shop, and differently again from a salon. Ordersys is configured to your model rather than forcing one calculation on everyone.
Split shifts are normal: a few hours in the morning, a few at night, a break in between. Part-timers swap shifts constantly and some only work weekends. Time has to be counted from hours actually worked, not from days present.
Shifts are more fixed, but the variable part of pay is sales commission. Getting it right means sales data and attendance data have to live in one system — copying between two files is exactly where the errors start.
Technicians are paid for services performed, not for hours sitting in the shop. One customer often passes through two people, so the split has to follow each service ticket. Attendance here is for knowing who is in and building the roster; the money comes from work done.
Staff moving between locations is routine, and that day’s hours must be booked to the branch where the work happened, so you can see which branch carries a high labour cost. Each manager sees their own people; the owner sees everything.
These four steps repeat every month. The software changes only one thing: each step is recorded as it happens instead of being reconstructed from memory at month end.
Scanning records the start time, the system matches it against the rostered shift and immediately shows who is on time, who is late and which shift is short-staffed. Nobody has to watch the door to know whether the shop is fully manned.
Shift swaps, early leave, staying on for overtime — every change is recorded with who approved it, right then. This is the step most often skipped because nobody wants to write things down when busy, and it is precisely the step that causes the most argument at payday.
At period end the timesheet is already built from the month’s records. What is left is reviewing the unusual lines and approving, instead of adding everything up from a notebook. Any edit is stored with who made it and when.
Each person gets a payslip that separates base pay, overtime hours, allowances, commission and deductions. Staff can see where the final number comes from, so questions are quicker and calmer.
Most pay disputes are not caused by a wrong formula. They come from nobody remembering exactly what happened three weeks ago: who covered whose shift, whether that overtime was agreed in advance, which day the fifteen-minute lateness was.
The owner remembers one version, the employee another, and both believe themselves because neither has anything to check against. The usual outcome is the owner deducting less to keep the peace — do that a few times and the people who follow the rules feel shortchanged.
The fix is not in the pay formula but in recording events as they happen, with the person and the timestamp attached. With that record, the month-end conversation shifts from arguing about memory to looking at the same line of data — and usually ends within minutes.
A fixed QR code taped to the wall can be scanned by anyone with a phone, including someone at home asking a colleague to do it for them. That kind of attendance records a time but does not show the person was actually there, so the numbers look fine and cannot be used to decide anything.
Ordersys lets you tighten it as far as you need: codes that rotate over time so a photo is useless, clock-in only on the device kept in the shop, or location captured at the moment of scanning. How strict to be is the owner’s call — the software just has to make the number trustworthy.
Read more: signs of staff fraud that shop owners often miss →
Experience the full feature set with no setup fee. The Ordersys team supports on-site installation & training.