Gym biometric attendance: how the setup works

We have an ESSL fingerprint reader at my own studio, a personal-training studio I run in Hyderabad. When I was on FitnessForce, each reader was a five-figure bill to get installed, which made no sense for a box that mostly needs power, a network cable and a member list.

In July we got that reader talking straight to the cloud instead of going through a desktop app. Most of what's below comes from that move, and from the small things that went wrong after it.

#The three parts of a setup

Every setup has three parts, whatever the brand. There's the reader on the wall, which recognises a finger or face and stores a time-stamped record called a punch. There's the software, which collects those punches and shows them as attendance and expiry. And there's the member list, where every enrolled person has a user ID that the software holds too.

When someone says "the machine isn't working", it's usually the second or third part.

#Where the fingerprint lives

When a member enrols, the reader scans the finger and turns it into a template, a block of numbers made from the print, and stores that next to the user ID. Makers list the capacity on the product page. The eSSL X990 page lists 10,000 fingerprints, 10,000 cards and 100,000 transactions, as of 2 Nov 2026.

So the software doesn't need a copy of anyone's fingerprint to record a punch, because the reader does the matching and sends out only the user ID and the time. The flip side is that templates don't move by themselves if you replace the reader, so ask the reseller how enrolment gets copied, or plan to enrol everyone again.

A fingerprint is sensitive personal data, so the reader is the right place for it, and a spreadsheet or a WhatsApp group isn't.

#Push or pull: how punches reach the software

A reader can hand its punches over in two ways.

The X990 page lists "Push data" support with static IP and domain server, and TCP/IP and USB for connection. The exact model you buy, in its India variant, is the one that matters.

We started on pull, through a desktop app at the front desk, and that app cleared the reader's log after reading it, which sounds tidy until something goes missing. Since July we've been on push, and a scan reaches the cloud in about three seconds.

It wasn't plug and play, though. Our reader had never been on the internet, so it needed its gateway and DNS set, and its server port was locked to one our host doesn't accept, so we had to route it through the reader's proxy setting.

And then the one I didn't see coming. About a week of punches from mid-July never came across, because the reader considered them delivered and wouldn't send them again, even after a reboot. Getting them back needs a full read from a PC on the same network. People will tell you the reader's own log is your safety net, and it is, but I wouldn't count on it until I've seen that log come back out.

#Software on a PC or in the cloud

Most gyms meet one of two kinds of software. One is desktop software on a front-desk PC, like eSSL's own eTimeTrackLite. It's built for office time and attendance, so it speaks in shifts and leave, and it does that job fine, but it has no idea who owes fees. The other is gym software that reads punches and matches them to a member's plan, so expiry and attendance sit in one place.

The question I'd put to any vendor is simple. Does anything have to stay switched on at my gym for this to work, and what happens when it's off?

Honestly, we've only half finished this ourselves. Our punches don't need a PC any more, but enrolment at my desk still mostly runs through the old desktop app, because that's what the front desk is used to. The new way from the portal works fine. I just haven't won that one yet.

#User IDs: the one thing you can't lose

Each person on the reader has a user ID, usually a number, and punches are recorded against that ID, not a name. So if a new system hands out new IDs, old punches stop matching the right member, and if two people end up with the same ID, one person's punches land on the other's account. That's why we give each person the next number up and never reuse one, even after they've left, and why the reserved master user stays on the reader, always. If you're changing software, the switch guide lists what to export first.

There are two ID problems I've actually run into. The first is what I call a phantom member. When enrolment breaks halfway on our desktop app, the reader can end up with a new user and no finger on it, and that number is gone. You spot it in the counts, because users go up and fingerprints don't.

The second was our own mistake. In October I found two of our housekeeping staff had been showing up as expired members for about two weeks, because housekeeping was missing from the list of staff roles in our code. The nightly clean-up, which was still in dry run, would have lined them up for deletion. So when you add a new kind of person to your gym, check how the software treats them.

#Wet hands, sweat and worn fingers

A gym is a hard place for a fingerprint reader. People arrive sweaty, leave with wet hands, and use chalk or gloves, and optical sensors can struggle with wet, oily, dry or worn fingers.

What usually helps is a towel next to the reader, two fingers enrolled per member, and enrolling at rest with a clean finger pressed flat and firm. If you're buying, test with your sweatiest regulars at peak hour, and ask the reseller for a return window. And keep a card, PIN or QR code as another way in, so a bad read doesn't block a paying member.

#When enrolment silently fails

Last month a new member's enrolment just didn't start. The app said it had gone out, the reader's screen showed nothing, and it looked like a broken app. It wasn't. Someone had scanned in on the reader at almost the same moment, so the reader was busy and dropped the prompt. We tried again half an hour later and it came up within three seconds.

A normal enrolment on ours finishes in 11 to 35 seconds. If it goes past a minute with nothing on the screen, someone was probably using the reader, so wait until it's free and try again.

#Fingerprint, face or QR

Fingerprint readers are common and usually hold more members per rupee. Face readers avoid the wet-hand problem and keep the queue moving, but they need decent light and may hold fewer members. QR, scanned from the member's phone, has no shared surface and no template at all. Our comparison of fingerprint, face and QR goes through the trade-offs.

#Locking the door when membership expires

Plenty of gyms want the door to refuse an expired member, and two things have to be true for that. The reader needs a relay or Wiegand output to drive a lock or turnstile (the X990 page lists a 12 V relay and Wiegand input and output). And it has to learn who has expired, either because software removes the person from the reader or because the reader holds a validity date. Ours holds only active people, so expired members come off it.

Mistakes will happen here. A member who paid at 8 pm and gets blocked at 6 am isn't going to be happy, right? So the front desk needs a quick override, and grace days if you want them.

#When the reader is down

Power cuts, a pulled network cable, a stuck sensor: it'll happen. It's worth having these written down before it does.

• How many punches the reader holds in its own memory while the network is out
• A paper or tablet sign-in sheet at the desk, which covers a day
• A USB drive, and how to export the log from the reader's menu
• QR or a card as another way in
• The reader's IP address, admin password and reseller's phone number, kept away from the reader itself

One small thing from ours: some nights it goes quiet around closing and other nights it keeps checking in till midnight, so a quiet evening doesn't mean it's down.

#What a biometric machine costs in India

Most makers don't publish a price, and eSSL's X990 page shows none. One IndiaMART seller listed the X990 at ₹15,580 per piece, excluding taxes, on the marketplace page, as of 2 Nov 2026. Other sellers, models and installers will differ, so get a written quote that separates the reader, GST, installation, the software licence and any yearly fee.

Our list of seven machines shows what each maker's page says. For the two big brands side by side, see eSSL vs ZKTeco for gyms, and for one model in detail, the eSSL X990 in a gym.

#Where Helmr fits

It feels a little funny to pitch after all that, but this is why I'm building it. Helmr, gym management software for India, is being built to connect ESSL and ZKTeco readers through a bridge, with fingerprint templates staying on the reader and QR check-in always there as another way in. Helmr is in early access.

If you'd like to be among the first to use it, message us on WhatsApp.