The choice at a glance
A terminal is shared equipment; a mobile app travels with the person. An organization can combine both. Biometrics describes the identification method: it is separate from the device and the attendance software.
What changes in everyday use
In a café or shop, start with the simplest process for opening, closing and shift changes. In a factory, test simultaneous arrivals. For service teams or construction sites, examine travel between locations and approval responsibilities. These are illustrative scenarios, not customer results.
Do not assume a mode works offline. Ask for a demonstration of the exact behaviour: stored or rejected events, synchronization, duplicates, recorded time and missed punches. For existing terminals, provide the model and version before assuming compatibility.
With 7odor: choose the capture method, keep the HR context
7odor connects attendance events with employees, sites, schedules and absences. Managers review exceptions and corrections; HR accesses reports and time exports. Test the chosen clock-in method all the way through to the period-end report.
The mobile workflow provides separate face-verification and location policies. Depending on the deployed version and services, face verification can be required or optional, and location can use GPS or selection of an authorized site. Confirm the available configuration for your team during the demo.
Location captured at clock-in and continuous route tracking are different functions. The continuous tracking presented by 7odor requires an upcoming mobile version and associated services: do not assume it is included in every existing installation.
Compare the project cost, not just the device
Request quotes for the same workforce, sites and features. Hardware, installation, subscriptions, connectivity, data migration, configuration and support can change the total cost. A mobile app is not automatically free, and keeping a terminal does not eliminate integration costs.
- Who supplies and maintains the equipment?
- Which modules, sites and users are included?
- What support is included after the pilot?
Biometrics and location: define the data scope
Define the purpose, necessary data, authorized users, retention and employee information before rollout. In Morocco, consult the CNDP procedures applicable to your processing, particularly for biometrics. A technical capability or phone permission is not legal approval of your setup.
Your pilot: five situations to check
Choose a representative site or team and have an operational manager and HR validate the result. Use anonymized scenarios in the demo. A useful pilot confirms that people can clock in, resolve an exception and find the right data in the report.
- Arrival and departure on a regular working day.
- A late arrival, a missed punch and a correction request.
- An overnight shift or a change of site.
- Lost connectivity or an unavailable device.
- A period export compared with the expected result.
Your questions
Does every employee need a smartphone?
Not for a shared-terminal workflow. For individual mobile attendance, check available equipment and plan an alternative for people who cannot use the app.
Can we combine terminals and the app?
Yes, subject to compatible devices and the chosen configuration. Verify employee identity mapping, event processing and reports in a representative pilot.
Does mobile attendance mean permanent tracking?
No. A location recorded at clock-in is separate from continuous tracking. Confirm active features, their version and collection rules for your rollout.
Let’s start with your working day.
Tell us about your organization to discover the functions useful to your teams.
Book a demo