Every branch has its own roster
Shifts and rosters per group, and a shift swap that runs as an approved request rather than a verbal arrangement between staff.
An HR system for retail and multi-branch companies
Many branches on different schedules, branch managers who must not see each other's data, and one payroll run that pulls them all together at month-end. That is what retail specifically needs.
app.barez.sa/employees
The pain, and what the system does
A branch manager must see only their branch
Granular permissions per role, department and branch. The branch manager sees their own staff, requests and attendance — management sees everyone.
Staff checking in at the wrong branch
Geo check-in is bound to the branch radius and rejects anything outside it, and face verification stops buddy-punching.
Requests get lost between branches
Thirteen request types raised from the employee's phone, running a clear approval route, with delegation when the approver is away.
Payroll pulls scattered branches together
One payroll run covering every branch, fed by attendance itself, then staged approval and a freeze once signed off.
High staff turnover
The recruitment engine receives applicants via a public link and ranks them by match score, and a hire becomes an employee in one click — shortening the replacement cycle.
Frequently asked questions
Can a branch manager approve only their own team's requests?
+
Yes. Permissions are scoped by branch, department and role, so they neither see nor approve outside their scope.
How do two employees swap shifts?
+
Through a shift-swap request that runs approval, so the swap stays documented in the record rather than being a verbal arrangement.
Does the system block check-in from another branch?
+
Yes, if you bind the employee to their branch radius. And it accepts multiple branches when the role requires moving between them.
Is payroll one run for all branches, or one per branch?
+
Either works: a run that covers all branches, or a split by branch with a unified board showing the total.