GPS Geofence Field Attendance

Key Features

`Geofence Site` DocType with center lat/long, enforcement radius, and optional link to `Customer`, `Warehouse` or branch

Server-side haversine distance check in a `hooks.py` `validate`/`before_insert` doc event — punches outside the radius are rejected or flagged, never trusted client-side

GPS selfie check-in capturing browser Geolocation coordinates, accuracy metres, device and an `Attach Image` selfie with server timestamp

`Field Punch` DocType storing raw coordinates, matched site, computed distance, punch type (IN/OUT) and reverse-geocoded address

Auto-promotion of valid punches into native ERPNext `Attendance` + `Employee Checkin` records via a daily `scheduler_events` job so payroll and shift logic keep working

Live field-staff map (Leaflet/OpenStreetMap) rendered from a whitelisted REST endpoint, showing current positions and the day's visit trail

Whitelisted `frappe.whitelist()` methods for mobile/PWA punch submission and daily route retrieval over the Frappe REST API

Role profiles and permission rules — Field Supervisor sees team map and exceptions, salesman sees only own punches, enforced server-side on every endpoint

Route / visit-history and geofence-violation Query Reports with per-site visit counts and out-of-fence exception lists

GPS accuracy threshold guard — low-accuracy or spoof-suspect fixes (mock-location flag, implausible jump) are flagged for supervisor review

Configurable 'present day' rule mapped to your shift definitions (minimum on-site punches, first-in/last-out, minimum minutes)

Per-employee assignable routes / target sites so a salesman's expected visits can be compared against actual punches

Client Script-driven mobile-friendly punch form with graceful handling of denied location permission and offline queueing option

Built and tested against Frappe/ERPNext v15 and v16, packaged as a standard installable Frappe app on your bench

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Distributed teams are where ERPNext attendance quietly breaks down. Field-sales reps, delivery riders and site technicians never touch the office biometric device or the desk kiosk, so their attendance is either back-filled manually or trusted on faith. ERPNext core gives you the Employee Checkin and Attendance DocTypes and a shift framework, but out of the box a check-in is just a timestamp — there is no location proof, no radius enforcement around a customer site or branch, and no live view of where your people actually are. Employee Checkin can log a latitude/longitude if a client sends one, but nothing stops a punch from a couch ten kilometres away, and nothing reconciles a day of valid field punches into a single Attendance record with route context. Standard geofencing add-ons live in a separate HR SaaS, forcing a fragile two-way sync back into ERPNext.

ECOSIRE builds a proper Frappe application — its own module, installed onto your bench — that closes those gaps natively. We define new DocTypes such as Geofence Site (a named location with center coordinates and an enforcement radius, optionally linked to a Customer, Warehouse or branch) and Field Punch (the raw punch carrying GPS coordinates, accuracy, device, a selfie Attach Image, and a server-computed distance-to-site). A mobile-friendly check-in surface — delivered as a Frappe web page or a Client Script-driven form using the browser Geolocation API — captures the salesman's live coordinates and selfie at punch time. On save, a hooks.py doc_events handler (a validate/before_insert server script) computes the haversine distance from every candidate Geofence Site, rejects or flags punches that fall outside the allowed radius, and stamps the matched site. Whitelisted methods (frappe.whitelist()) exposed over the Frappe REST API let a companion mobile view or PWA submit punches and pull the assigned route for the day.

Valid punches are promoted into ERPNext's own HR flow rather than a parallel silo. A scheduler event (a scheduler_events cron/daily hook) rolls each employee's first and last valid Field Punch of the day into a native Attendance record with IN/OUT Employee Checkin entries, so payroll, shift, and leave logic keep working unchanged. A live map — a Frappe Dashboard page or workspace using a Leaflet/OpenStreetMap tile layer fed by the REST API — plots current field-staff positions and the day's visit trail, and Query/Report DocTypes deliver route history, visit-per-site counts, and geofence-violation exceptions. Access is governed by ERPNext permissions and role profiles: a "Field Supervisor" sees the map and exceptions for their team, a salesman sees only their own punches, and the whitelisted endpoints enforce the same permission checks server-side.

Because this is build-to-order, you are not downloading a fixed marketplace app and hoping it fits. After a short scoping call we confirm your geofence sites, radius policy, selfie/liveness requirements, how a "present" day is defined for your shifts, and which ERPNext version you run (we support Frappe/ERPNext v15 and v16). We build against that scope, run UAT on a staging bench, and only then install on production. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the installable source, install and configuration, technical and user documentation, a training session, and a post-go-live support window — and the git repository is handed over so the code is genuinely yours.

What you get

Installable Frappe app source code for your ERPNext version (v15 or v16), packaged for your bench

Installation and configuration on your site — geofence sites, radius policy, roles and the scheduler job set up and running

Technical documentation: DocType schema, hooks and doc events, whitelisted API methods, scheduler jobs and permission model

End-user and supervisor guide plus a live training session for admins and field staff

UAT on a staging bench with sign-off, plus a documented rollback plan before production install

Post-go-live support window for defect fixes and configuration adjustments

Git repository handover so the source is genuinely yours to keep and extend

Version-compatibility notes and upgrade guidance for future Frappe/ERPNext point releases

Who this is for

HR / Operations Manager

Owns attendance integrity for a workforce that is rarely in the office. Needs verifiable proof that field staff were physically on-site, with valid punches flowing automatically into ERPNext Attendance so payroll and leave stay correct without manual back-filling.

Field-Sales / Distribution Lead

Runs a team of salesmen or delivery reps covering assigned customer routes. Wants a live map of where the team is, per-site visit counts, and out-of-fence exceptions to confirm reps actually reached their scheduled outlets.

ERPNext System Administrator

Maintains the bench and the site. Needs a clean, standard Frappe app that installs onto v15/v16, uses native DocTypes, hooks and scheduler events rather than external SaaS, respects permissions and role profiles, and ships with source and docs they can support in-house.

Logistics / Site Operations Supervisor

Coordinates technicians or drivers across multiple sites and warehouses. Needs radius-enforced check-in at each geofenced location and route history to reconcile where crews spent their day.

How GPS Geofence Field Attendance Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Geofence enforcement	Server-side radius check in a Frappe doc event, per-site radius	Possible but you design and test the haversine/validation yourself	Often client-side only or a fixed single radius	None — a checkin is just a timestamp
Attendance integration	Auto-rolls valid punches into native Attendance + Employee Checkin	You wire the scheduler job and mapping yourself	Frequently a separate silo needing sync back to ERPNext	Manual Employee Checkin / Attendance entry
Live location map	Leaflet/OSM map fed by whitelisted REST endpoints	Build the map, API and permission layer from scratch	May be web-portal only, outside ERPNext	No live field-staff map
Fit to your process	Scoped to your sites, radius, shift and present-day rules	Fully bespoke — highest effort and cost to you	Fixed feature set, adapt your process to the app	Generic HR framework only
Version support	Built and tested for Frappe/ERPNext v15 and v16	You own version testing and upkeep	Depends on publisher's maintenance cadence	Ships with your ERPNext version
Source & ownership	Git repo handover — the code is yours	Yours, but you built and must maintain all of it	Usually licensed/closed, no source handover	Core code, not attendance-geofencing specific
Time to value	2-4 weeks from confirmed scope, UAT on staging first	Longer — full dev cycle from zero	Instant install but generic fit and rework	Immediate but the gap is never actually filled
Support model	Post-go-live support window + optional ongoing retainer	Self-support or hire developers	Vendor tickets, roadmap not yours to steer	Community / your ERPNext partner

Frequently Asked Questions about GPS Geofence Field Attendance

How long does delivery take?

This is a build-to-order app, not an instant download. Typical delivery is 2 to 4 weeks from confirmed scope — that clock starts after the scoping call where we agree your geofence sites, radius policy, selfie/liveness needs, present-day rule and target ERPNext version. Simpler scopes land closer to two weeks; heavier route-planning or offline requirements closer to four.

Which ERPNext and Frappe versions do you support?

We build and test against Frappe/ERPNext v15 and v16, packaged as a standard installable app on your bench. Tell us your exact version and hosting (Frappe Cloud, self-hosted, or ECOSIRE-managed) during scoping and we build against that target.

How does it stop someone punching in from home?

The geofence check runs server-side in a `hooks.py` doc event, not in the browser. On every punch we compute the haversine distance from the device coordinates to each `Geofence Site` and reject or flag anything outside the allowed radius. We also flag low-accuracy fixes, mock-location signals and implausible location jumps for supervisor review.

Does it work with ERPNext's native Attendance and payroll?

Yes. Valid punches are promoted into native `Employee Checkin` and `Attendance` records by a daily scheduler job, so ERPNext shift, leave and payroll logic keep working unchanged. It augments core HR rather than replacing it with a parallel silo.

What about support and future updates?

Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because we hand over the git repository and full technical docs, your team can maintain it in-house — or you can retain ECOSIRE for version upgrades and enhancements under a support arrangement. We provide upgrade guidance for future Frappe/ERPNext point releases.

Do field staff need a special mobile app to check in?

No native app store install is required. The punch surface is a mobile-friendly Frappe web page / Client Script form that uses the browser Geolocation API and camera for the selfie, and it can be delivered as a PWA. If you already have a mobile app, our whitelisted REST endpoints let it submit punches and pull each day's route.

Can we customise the geofence radius, selfie rules and route assignments?

Yes — those are exactly the things we confirm during scoping. Radius is configurable per `Geofence Site`, the present-day rule maps to your shift definitions, selfie/liveness strictness is your call, and salesmen can be assigned target sites so expected visits are compared against actual punches. Anything outside the agreed scope becomes a follow-up change request.