Time Clock for Retail Stores: Lock the Register

Retail runs on hourly, on-site staff, and that makes it one of the worst-hit industries for time-clock leakage. A cashier clocks in from the bus so their shift “starts” before they arrive. A coworker punches in a friend who’s running ten minutes late. Someone clocks in the moment the schedule allows, even though the doors don’t open for another half hour. None of it feels like theft to the people doing it — but across a floor of hourly staff, it quietly inflates every payroll run.

If you’re shopping for a time clock for a retail store, the feature that matters most isn’t fancy scheduling. It’s the ability to make a punch only count when the person is actually in the store. The cleanest way to do that is to lock clock-in to the building’s own network — and that’s exactly what Punchwell’s office-IP clock-in lock does.

Why retail is especially exposed

A few things about retail work stack up against you:

  • The workforce is hourly and on-site. Minutes map directly to dollars, and everyone is supposed to be physically present — so an off-site punch is almost always wrong.
  • Shifts have hard edges. The store opens at a set time. Clocking in 25 minutes early “because I was here” adds up fast across a season.
  • Turnover and seasonality are high. You staff up for the holidays, then wind down. Every new hire is another punch to trust.
  • The clock is often a shared terminal. A POS station or back-office tablet gets used by everyone, so a PIN alone doesn’t prove who pressed the button.

Most affordable time clocks respond to this with GPS geofencing — check the employee’s phone against the store’s location. It’s better than nothing, but it needs an app on every personal phone, and a phone’s GPS can be spoofed from a couch at home. GPS tells you where a phone says it is. For a store where everyone is meant to be behind the counter, that’s a soft answer to a question that has a hard one.

The hard control: lock the register to the building

Every store’s internet connection has a public IP address — the single address your whole shop shares when it connects out. An office-IP lock says: this employee can only clock in or out from the store’s network. A punch from home, the parking lot, a bus, or a spoofed phone is refused server-side — not quietly logged with a note about the location. Refused.

That’s the difference that actually stops buddy punching in a shop: a phone on someone’s home Wi-Fi cannot borrow your store’s public IP. To punch in, you have to be on the store network — which means being in the store.

For a retail floor, the depth is what makes it livable day to day:

  • Per employee. Lock your cashiers and sales staff to the building, while a district manager who covers three stores can be allowed to clock in from any of them. One setting per person — you’re not choosing between “lock everyone” and “lock no one.”
  • The whole store network in one entry. Enter a single IP, an address range, or a CIDR block (like 203.0.113.0/24) so the entire shop’s network is covered without listing devices. A “Use this IP” button captures the store’s public address while you’re standing in it.
  • Block, warn, or flag. Roll it out in warn mode first — punches still go through but off-network ones get noted — then switch on hard block for the roles that need it once you’ve spotted the real exceptions.
  • A clock-in time window. Optionally only accept punches around shift start, so nobody clocks in half an hour early to pad the timesheet. It’s direction-aware: it won’t block clock-out, so no one gets stuck on the clock at close.
  • A blocked-attempt email. When an off-site punch is refused, a manager gets a heads-up — so it’s a visible event, not a silent mystery.

The shared terminal problem, solved

Because retail so often clocks in on one shared device, Punchwell includes a kiosk / wall-tablet clock plus a mobile punch screen. Mount a tablet by the back office or the register and each employee clocks in with a short code and a 6-digit PIN — no individual logins on the shared device, and the tablet’s own connection has to match your store’s allowlist to work. That gives you one obvious place to punch, tied to the building, without handing everyone a personal login for the POS.

Flat price beats per-seat — especially with seasonal staff

Retail is the clearest case against per-seat billing. You hire a wave of seasonal help, and a per-head time clock bills you for every one of them — then you’re paying for empty seats when the season ends.

Punchwell is priced per site, not per seat, with unlimited employees on every tier: a free community version on WordPress.org, then Pro at $99/year per site. Hire your tenth seasonal cashier and your bill doesn’t move.

For contrast, here’s roughly what a 25-staff shop pays the per-head SaaS clocks (approximate, as of June 2026 — confirm current rates before deciding): Buddy Punch around $1,520/yr, Deputy around $1,950/yr, When I Work around $2,100/yr. Most of those, and the popular budget options, do GPS-only location checks rather than a true store-network lock. Punchwell gives you the hard IP lock and an optional GPS geofence, at a flat annual price — and because it’s self-hosted inside the WordPress site you may already run, your staff and attendance data stays in your own database instead of a vendor’s cloud.

Running more than one store

If you operate several locations, each store’s network gets its own entry, and the allowlist levels combine so staff are locked to their own building while a roving manager can be allowed everywhere. A location without a fixed public address can lean on the GPS geofence or the kiosk instead. It scales from a single shop to a small chain without changing how the lock works.

The bottom line for retail

Retail’s attendance problem is specifically a presence problem: everyone is supposed to be in the store, so a punch that isn’t should never count. GPS can be faked; a shared PIN proves nothing on its own. Locking clock-in to the store’s network refuses the off-site punch outright, applied per employee, with a clock-in window to stop early padding and a kiosk for the shared terminal — at a flat price that doesn’t punish you for staffing up.

If that’s the control your shop floor needs, the calm next step is the Punchwell product overview to see how the pieces fit together for a store.


Punchwell is an independent, third-party maintained fork of the GPL-licensed “WP Human Resource Management” plugin. Sturdyhaus is not affiliated with, endorsed by, or sponsored by wpspear, weDevs, or the original author. Competitor names (Buddy Punch, Deputy, When I Work) are referenced descriptively only; all trademarks belong to their respective owners. Competitor pricing and capabilities are approximate, as of June 2026 — confirm current rates before relying on them.


Punchwell is an independently maintained GPL fork. Not affiliated with the original “WP Human Resource Management” plugin or its authors. Competitor names and figures are nominative and approximate (as of the date noted) — confirm current rates.