Clock-ins you can trust, roles you build permission by permission, and a staff file that holds the documents an inspector asks for. Quickbuy does not run payroll; it produces the hours payroll needs.
Staff clock in and out through the day, and a split shift is two records rather than one estimate. Managers can close a clock-out someone forgot, so the totals stay honest, and the whole period exports as CSV for whoever runs your payroll.
Today's clock-ins
Shift History
Export Shifts
14
Total shifts
5
Active shifts
86.5
Total hours
6.2h
Avg. Shift
Amir H.
Waiter
09:0213:304.5
Amir H.
Waiter
18:00Not clocked out—
Sara K.
Cashier
11:00Not clocked out—
Tariq M.
Chef
07:4516:108.4
A split shift is two records, not one estimate. Managers can close a clock-out staff forgot.
Activity Throughout Operating Hours
Total Active Hours: 86.5
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Peak 6 on at 18:00Quickbuy produces the hours; it does not run payroll.
Today's clock-ins
Shift History
Export Shifts
14
Total shifts
5
Active shifts
86.5
Total hours
6.2h
Avg. Shift
Amir H.
Waiter
09:0213:304.5
Amir H.
Waiter
18:00Not clocked out—
Sara K.
Cashier
11:00Not clocked out—
Tariq M.
Chef
07:4516:108.4
A split shift is two records, not one estimate. Managers can close a clock-out staff forgot.
Activity Throughout Operating Hours
Total Active Hours: 86.5
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Peak 6 on at 18:00Quickbuy produces the hours; it does not run payroll.
A shift screen showing 14 total shifts, 5 active, 86.5 total hours and a 6.2 hour average, above today's clock-ins. Amir H. appears twice, a 09:02 to 13:30 shift of 4.5 hours and an 18:00 shift still open. Sara K. is clocked in at 11:00 and not yet clocked out. Tariq M. worked 07:45 to 16:10. Beside them a bar chart shows headcount across operating hours, peaking at 6 people on at 18:00.
There is no rota builder and no shift swapping. Quickbuy records what actually happened, which is the part payroll and disputes depend on.
Role customizations
Built permission by permission, not from three presets
A role is assembled from individual permissions, module by module, so you grant exactly what a job needs. Anything the role is not given simply does not appear on that person's dashboard, rather than sitting there greyed out.
Floor Supervisor
Permissions set per module
Orders
Partial
Menu
Partial
Items
Partial
Employees
Partial
Tables
Full access
Inventory
No access
Branches
Partial
Analytics
No access
Accounting
No access
Settings
No access
Customers
Partial
Reception
No access
What a role cannot do is not greyed out, it is simply absent from that person's dashboard.
Orders
Amending an order and erasing one are separate permissions.
LIST_ORDER
CREATE_ORDER
UPDATE_ORDER
VOID_ORDER
REFUND_ORDER
The same split exists on wallets: adjusting a balance and refunding one are separate grants.
Floor Supervisor
Permissions set per module
Orders
Partial
Menu
Partial
Items
Partial
Employees
Partial
Tables
Full access
Inventory
No access
Branches
Partial
Analytics
No access
Accounting
No access
Settings
No access
Customers
Partial
Reception
No access
What a role cannot do is not greyed out, it is simply absent from that person's dashboard.
Orders
Amending an order and erasing one are separate permissions.
LIST_ORDER
CREATE_ORDER
UPDATE_ORDER
VOID_ORDER
REFUND_ORDER
The same split exists on wallets: adjusting a balance and refunding one are separate grants.
A role called Floor Supervisor, with permissions set module by module. Tables shows full access, orders, menu, items, employees, branches and customers show partial access, and inventory, analytics, accounting, settings and reception show no access. Beside it the orders module is opened, showing LIST_ORDER, CREATE_ORDER and UPDATE_ORDER granted while VOID_ORDER and REFUND_ORDER are refused.
Amending an order and erasing one are separate permissions, as are adjusting a customer wallet and refunding it. That separation is the ordinary control against shrink.
The staff file
The documents an inspector asks for, on the employee
An employee record is more than a login. It holds the contract type, start date, shift window, reporting line, salary and next of kin, plus a list of named documents kept against the person rather than in a drawer or a WhatsApp thread.
AH
Amir H.
Waiter · Floor 1
Active
Contract
Full time
Start date
04 Mar 2025
Shift window
09:00AM-5:00PM
Reports to
Sara K.
Salary
AED 4,200
Emergency contact
+971 50 ••• ••••
Contract, start date, reporting line and next of kin sit on the record, not in someone's phone.
Documents
Named files kept on the employee, not in a drawer.
Residency visaAttached
Emirates IDAttached
Labour cardAttached
Food handler certificateAttached
Quickbuy stores the file against the employee. It does not read expiry dates or send renewal reminders.
AH
Amir H.
Waiter · Floor 1
Active
Contract
Full time
Start date
04 Mar 2025
Shift window
09:00AM-5:00PM
Reports to
Sara K.
Salary
AED 4,200
Emergency contact
+971 50 ••• ••••
Contract, start date, reporting line and next of kin sit on the record, not in someone's phone.
Documents
Named files kept on the employee, not in a drawer.
Residency visaAttached
Emirates IDAttached
Labour cardAttached
Food handler certificateAttached
Quickbuy stores the file against the employee. It does not read expiry dates or send renewal reminders.
An employee record for Amir H., a waiter on Floor 1, marked active. Fields show a full time contract, a 04 March 2025 start date, a 09:00AM to 5:00PM shift window, reporting to Sara K., a salary of AED 4,200 and a masked emergency contact. Alongside, four documents are attached: residency visa, Emirates ID, labour card and food handler certificate.
Quickbuy stores the file against the employee. It does not read expiry dates off a document or send renewal reminders, so keep your own diary for those.
What Quickbuy's employee management covers, and what it does not
Employee management in a restaurant system usually means three separate promises: planning who works when, recording who actually worked, and paying them. Quickbuy does the middle one properly and does not pretend to do the other two.
There is no rota builder, no published schedule, no shift swapping, no time-off workflow, and no payroll run. What there is: accurate clock-in and clock-out records, roles built from individual permissions, and an employee file that holds the paperwork. If planning rotas or producing a WPS file is what you are shopping for, Quickbuy will not do it, and finding that out on this page is better for both of us than finding it out in month three.
How shift tracking works
Staff clock in and out through the day. A split shift is stored as two separate records rather than being averaged into one, so the morning and the evening are each visible with their own times. Where someone forgets to clock out, the record shows Not clocked out and a manager can force the clock-out, which is the only reason the totals underneath can be trusted at all.
From those records you get total shifts, active shifts, total hours and average shift length, a per-employee history of every clock-in and clock-out, and a chart of how many people were actually on across your operating hours. The whole period exports as CSV. Quickbuy produces the hours; whoever runs your payroll takes them from there.
Roles, and why the separation matters
A Quickbuy role is not a preset. It is assembled from individual permissions, set module by module, and anything you do not grant is simply absent from that person's dashboard rather than sitting there greyed out and inviting a request.
Permissions are set module by module across orders, menu, items, employees, tables, inventory, branches, analytics, accounting, settings, customers and reception.
Accounting is the deepest of them, so a bookkeeper can be given the ledger without being given the floor.
Updating an order, voiding an order and refunding an order are three separate grants, which is the ordinary control against shrink.
Viewing a customer wallet is separate from adjusting it and from refunding it.
The dashboard adapts
a waiter signing in on a phone sees the order screen and nothing else.
Roles are reusable across your team, and branches are themselves a permission, so a manager can be scoped to one site.
The employee record
The third piece is the file itself, and it is the one most restaurant systems skip. An employee in Quickbuy is not just a login and a role.
For a UAE operator the document list is the part that earns its place. A residency visa, an Emirates ID, a labour card and a food handler certificate all get asked for, and they are usually in a drawer or somewhere in a WhatsApp thread.
Contract type, full time or part time, with a start date.
Salary held on the record as a reference figure, and an expected shift window.
A reporting line, so who answers to whom is written down rather than assumed.
Emergency contact and next-of-kin details, which matter exactly once and matter enormously.
A list of named documents attached to the person, kept with the record rather than in a drawer.
Note the limit
Quickbuy stores the file. It does not read an expiry date off it and does not send renewal reminders, so keep your own diary for those.
Getting started
Setup is short. Create your roles first, because that decides what everyone sees, then add your team against them and attach whatever documents you already hold. Clock-ins start the same day.
The honest case is narrow and, we think, more useful for it. Quickbuy will not plan your rota and will not pay your staff. It will tell you exactly who was on, for how long, with a manager able to correct the clock-outs people forget, and it will make sure the person who can take an order is not automatically the person who can void it. If you also need scheduling or payroll, say so on the call and we will tell you where Quickbuy stops.
Frequently Asked Questions
Everything you need to know about managing your restaurant team with Quickbuy.
See it with your own team
Bring your roles and a week of real shifts, and we will show you the permission grid and the hours export on your own data.