Geofencing API for last-mile delivery in India

India's delivery networks run on a mix of hub-and-spoke courier chains — Delhivery, Shiprocket-integrated sellers, hyperlocal quick-commerce riders — all converging on the same last stretch: the final few kilometers where an order actually reaches a doorstep. That's where geofencing earns its keep. Not as a map feature, but as the trigger layer that tells your ops stack the moment a rider enters a delivery zone, the moment they dwell too long outside it, or the moment a package leaves a hub's boundary before it should.

Fencemaker handles that trigger layer directly. You define delivery zones — a housing complex, a pincode cluster, a dark-store radius — and Fencemaker fires a webhook the instant a tracked device crosses the boundary. No polling loop checking rider coordinates every 30 seconds and hoping you didn't miss an event; the geofence engine watches continuously and pushes only when something actually happens.

Why this matters specifically for Indian delivery ops

Two things make the Indian delivery market a harder geofencing problem than it looks:

Density and address ambiguity. A single housing society can have hundreds of geographically overlapping delivery points with inconsistent address formatting. Zone boundaries need to be precise polygons, not radius-based circles, or you get false triggers every time a rider passes an adjacent building.

Data residency expectations. With RBI and MeitY guidance pushing toward local data handling for operationally sensitive systems, teams increasingly want geofencing infrastructure they can point at a server they control — not a black-box SaaS holding rider location history in a jurisdiction they can't audit. Fencemaker runs self-hosted, so location data and event history stay on infrastructure you own.

How the trigger flow works

POST https://your-app.com/webhooks/fencemaker
{
  "event": "geofence.enter",
  "zone_id": "zone_hsr_layout_sector2",
  "device_id": "rider_8841",
  "timestamp": "2026-08-18T09:14:02Z",
  "coordinates": { "lat": 12.9121, "lng": 77.6446 }
}

That payload lands wherever you route it — a Slack channel for ops visibility, a Telegram bot for rider-facing alerts, or directly into your dispatch system to trigger the next step in a delivery workflow. No custom polling infrastructure, no separate location-tracking database to maintain.

What you get out of the box

Polygon and radius-based zone definitions, so you can match actual housing-society or dark-store boundaries instead of approximating with circles
Native Slack and Telegram webhook delivery for ops teams who already live in those tools
Device tracking with dwell-time detection, useful for flagging riders stalled outside a delivery radius
Self-hosted deployment, so location data never leaves infrastructure you control
An ops portal for defining and editing zones without touching code

If your delivery stack is currently stitching together a geolocation library and a cron job to approximate this, Fencemaker replaces that with a purpose-built trigger layer — built for exactly this kind of high-density, high-event-volume delivery operation.