Capability table
The difference between QRFlow and a plain QR attendance system
No company is named on this page. The right-hand column describes the general approach widespread on the market; every line in the left column is a capability of the product that really works today. One row goes to the simple systems — we kept it in the table.
How to read this table
- The right-hand column is not a product, it is an approach: "a plain QR attendance system" means the structure you meet most often on the market.
- You can check every capability in the left column yourself — in the no-signup demo and in your own workspace.
- No cell says "they do not have it". The generalisation is carried by "usually", "most often" and "as a rule", because it is not a verdict on any particular product.
- If we got a line wrong, tell us: we correct it and keep the correction on this page.
Money first
Two different models. Per-employee billing grows the invoice with every new hire; our plan price is fixed and headcount moves freely inside the plan limit.
| Headcount | QRFlow — plan | QRFlow — plan + cleaning | Per-employee billing model | Difference (plan only) |
|---|---|---|---|---|
| 10 employees | 390 ₼ Starter | 570 ₼ | 582 ₼ | 192 ₼ less |
| 25 employees | 390 ₼ Starter | 570 ₼ | 1 482 ₼ | 1 092 ₼ less |
| 50 employees | 990 ₼ Business | 1 338 ₼ | 2 982 ₼ | 1 992 ₼ less |
| 100 employees | 990 ₼ Business | 1 338 ₼ | 5 982 ₼ | 4 992 ₼ less |
| 200 employees | 2 990 ₼ Pro | 3 698 ₼ | 11 982 ₼ | 8 992 ₼ less |
- 1. The comparison uses 5 ₼ per employee per month — the level commonly seen on the market. The sum is: 8.50 ₼ a month as a floor (the first 2 people included) plus 5.00 ₼ a month for every further employee, billed annually.
- 2. This column is not any company's price list. It shows how a per-employee model grows as headcount grows — every figure can be reproduced with the same formula.
- 3. The QRFlow column is the annual plan price. The next column adds one light module — cleaning — as a worked example (light module: 15 / 29 / 59 ₼ a month depending on plan, heavy module 19 / 39 / 79 ₼).
- 4. QRFlow plans cover sites and active QR codes as well as headcount: Starter 25 employees / 2 sites / 3 QR, Business 100 / 5 / 10, Pro 500 / 20 / 50, unlimited on Enterprise.
Row by row
Left column: the criterion. Middle: our code. Right: the common market approach.
| Criterion | QRFlow | Plain QR attendance systems |
|---|---|---|
| Scope and price | ||
| What you get | check_circle Attendance (included in every plan) and seven modules — cleaning, inspections & patrols, assets & maintenance, visitors & events, customer satisfaction, work schedule, team communication — are live today. Each is switched on separately; nothing unfinished is sold. | Usually a single product: attendance and access control. A module store is, as a rule, not part of the idea. |
| How the price grows | check_circle A fixed annual plan: Starter 390 ₼, Business 990 ₼, Pro 2 990 ₼, Enterprise from 5 990 ₼; monthly 49 / 119 / 359 / 719 ₼. Going from 24 employees to 25 does not change the invoice — the price holds until the plan limit is full. | Most often a monthly fee per employee: every new hire grows the invoice, and the gap widens as the team grows. |
| Paying by the number of QR codes | check_circle Included in the plan: 3 / 10 / 50 active QR codes, unlimited on Enterprise. Nothing extra per door. | The number of doors or gates is usually a separate line on the invoice. |
| Extra modules: price and trial | check_circle Module prices are published: a light module is 15 / 29 / 59 ₼ a month by plan, a heavy one 19 / 39 / 79 ₼; on Enterprise they are all included. And every module can be tried free for 14 days, no card, before you buy. | Usually there is no notion of modules: whatever exists sits inside one tariff, and a per-module trial is, as a rule, not provided either. |
| Trusting the scan | ||
| Can an employee clock in from home? | check_circle No. An employee can check in only on the site's grounds (100 metres by default, set separately per site). Even if the phone hides its location the outcome is the same — the check-in is refused. | An area check is usually offered; what happens when no location data arrives is most often not stated. |
| Can they scan in for a friend? | check_circle No. Check-in is tied to the employee's own approved phone — a code scanned from somebody else's phone is refused. A lost phone is removed in one click and never works again. | Phone binding usually exists; what becomes of a removed phone, and how re-binding works, is most often not explained. |
| Only from the workplace network | check_circle If you wish, check-ins are accepted only from the site's own internet (the office Wi-Fi, for example). An attempt from an outside network is refused together with its reason. | A network restriction is usually a simple list, and the finer cases are, as a rule, not called out separately. |
| Sharing a photo of the QR code | check_circle It gets nobody anywhere: the code shown on screen refreshes itself and the old one becomes invalid at once. Nor can a future code be built from a photo of the printed code on the wall. | A self-refreshing QR is usually offered; how quickly it refreshes, and what becomes of the old code, is most often not shown. |
| Repeat scans and double entries | check_circle After a successful check-in a pause set separately for each QR code kicks in — a code accidentally scanned twice does not create a double entry. Even if two attempts arrive at the same moment, one entry lands in the timesheet. | A pause against repeat scans usually exists, but most often as one value for the whole system; what becomes of two attempts arriving at once is, as a rule, not said. |
| Time and shifts | ||
| Past reports stay untouchable | check_circle The shift rule (start, end, allowance, break) is stored inside each record itself. Change the rule tomorrow and yesterday's and last month's reports stay as they were — in an inspection you are covered. | Shift settings are usually read from their current value; changing a rule can change the numbers in past reports as well. |
| Night shifts and clock changes | check_circle Overnight shifts, several check-ins and check-outs in one day and seasonal clock changes are all supported — the report does not get confused, and lateness is counted only against the first arrival of the day. | Night shifts are usually supported; several sessions a day, the closing of a shift left open and the effect of clock changes on reports are most often not shown. |
| Everyday work | ||
| Who sees what, who can do what | check_circle Alongside ready-made roles you can build your own — each permission is granted separately. Admin sign-in is protected with two-step confirmation, and every important change is logged: who changed what, and when. All of it in every plan. | Usually a handful of ready-made roles. Custom roles, two-step sign-in and a change history are most often offered on the upper tiers only. |
| On the phone in your name | check_circle Your team adds the app to their phones with YOUR name and logo — from a single link, with no App Store or Google Play search. | Usually one shared mobile app: the same name, the same icon and the same splash screen for every company. |
| Interface in three languages | check_circle AZ / EN / RU — the panel, the scan screen, the reports and the export files. Each company chooses which languages are open. | The website is often multilingual; the panel and the mobile app do not usually cover the same set of languages to the same depth. |
| Reports and Excel/PDF export | check_circle Employees, attendance, timesheets and reports export to Excel and CSV in the language you choose. In PDF reports the Azerbaijani letters (ə, ş, ğ, ı, ö, ü, ç) come out correctly, as real text. | CSV or Excel export is usually there. Whether diacritics survive in a PDF report depends on the font and is most often not stated. |
| Moving your employee list over | check_circle Import from Excel and CSV files: columns are recognised automatically under Azerbaijani, English and Russian headings, a preview comes first, and faulty rows are listed with their reason — nothing is lost silently. | Excel import usually exists; column mapping and a row-by-row error report are, as a rule, not shown separately. |
| The employee's own cabinet | check_circle Every employee has their own cabinet: timesheet, attendance history, leave and time-off requests, attendance correction requests — with an approval flow and notifications. | The employee side is usually limited to the scan screen; leave and correction requests most often live in another system or on paper. |
| Wall display (kiosk) | check_circle A tablet or monitor works as a wall display: it shows the self-refreshing QR and gives no access to the admin panel. No extra hardware or licence is needed. | A kiosk or terminal mode is usually offered, most often with dedicated hardware or a separate licence. |
| How payment works | check_circle Settlement runs on official invoices and bank transfer — the documented, familiar route for company accounting. | Online card payment is widespread on the market. |
| Simplicity flagThe simple system wins this row | More choice means more decisions. Plan, module store, roles, trusted networks, shift rules — the initial setup usually takes 20–30 minutes. | If attendance is all you need, a simple system starts up with fewer settings — we have more choice, and that adds to setup time. |
Scroll the table sideways to see every column.
Who QRFlow is not for
One site, one shift, up to 15 people — and all you need is who came and went? Then a single product with a single price and a single screen takes less of your time.
QRFlow starts paying off when a second site opens, a night shift appears, cleaning or patrol rounds need to run on the same QR codes, or headcount grows until per-employee pricing starts inflating the bill.
How to check us
Do not take a single figure on this page on our word.
The price: put your own headcount into the calculator on the pricing page. Both models are worked out side by side, and it says plainly where we lose on small teams.
The limits: every plan's employee, site and QR caps are read from the product's own rules — when reality changes, this page changes with it.
The behaviour claims: in the rule sandbox on the demo page, switch the four checks off one at a time — and see with your own eyes how the system answers.
No company name, mark or quotation appears on this page. The right-hand column is not a claim about any particular product — it describes the general approach widespread on the market, which is why it says "usually", "most often" and "as a rule". Every line in the left column is a capability of the product that works today.