Field-delivery teams running on ERPNext hit the same wall: the Delivery Trip DocType is a solid back-office plan, but it stops at the warehouse door. Drivers still work from printed manifests or WhatsApp messages, proof of delivery arrives as a shoebox of paper signatures, and cash-on-delivery money is reconciled by memory at end of day. ERPNext core has no driver-facing mobile surface, no structured capture of who received a parcel, and no way to know in real time whether stop 7 of 12 succeeded or failed. That gap is exactly where deliveries leak — disputed drop-offs, unaccounted COD cash, and a back office that is blind until the van returns.

We build a proper Frappe app — installed on your own bench alongside ERPNext — that adds a mobile-first driver workflow on top of the objects you already use. The app reads each driver's assigned Delivery Trip and its Delivery Stop child rows through the Frappe REST API and whitelisted methods (frappe.whitelist()), so the manifest a driver sees is the same record accounting and inventory see. Each stop links back to its Delivery Note and Sales Order, launches turn-by-turn navigation via the stop's geolocation, and on arrival captures a structured proof of delivery: an on-glass e-signature, one or more photos stored as File attachments, the receiver's name, and a timestamp with GPS coordinates. Failed attempts are recorded against a configurable set of reason codes (customer absent, refused, wrong address, damaged) rather than a free-text guess, so exceptions become reportable data instead of anecdotes.

Technically, the app ships as a versioned Frappe module with its own DocTypes (for POD records, reason-code masters, and COD cash sessions), hooks.py document events that fire on submit to stamp the linked Delivery Note and post the delivery status back, and client scripts that drive the on-device capture flow. COD collection is first-class: each cash payment is recorded against the stop, rolled into a driver cash session, and reconciled at handover so the amount received matches the amount banked — with a clear variance if it does not. Server scripts and scheduler events push live location and stop status to the back office and can trigger notifications, while Frappe's permission model and role profiles (a Delivery Driver role that sees only its own trips) keep drivers scoped to their own data. The build targets Frappe/ERPNext v15 and v16 and follows framework conventions throughout, so it survives bench update and standard site migrations.

Because this is build-to-order, nothing is a black box you download blind. After a short scoping call we confirm your exact stop lifecycle, reason codes, COD rules, and role model, then build against that specification. You receive the full installable source, we install and configure it on your staging site, you sign off through UAT, and we deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope, and you own the git repository at the end.