产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $399.00 USD
- ERPNext 版本
- —
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Last-Mile Driver & Proof-of-Delivery App for ERPNext
A mobile driver companion for ERPNext Delivery Trips: turn-by-turn navigation, e-signature and photo proof of delivery, COD collection with cash reconciliation, and live status back to the office. Built to your workflow, installed on your bench, and supported by ECOSIRE.
$399.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Reads each driver's assigned `Delivery Trip` and `Delivery Stop` child rows over the Frappe REST API so the mobile manifest is the same submitted record the back office sees
Turn-by-turn navigation launched from each stop's stored geolocation, with stops ordered by the trip's planned sequence
On-glass e-signature capture plus one or more delivery photos, persisted as Frappe `File` attachments linked to a POD DocType
Structured failed-delivery reason codes backed by a reason-code master DocType (customer absent, refused, wrong address, damaged, rescheduled) instead of free text
COD collection recorded per stop, rolled into a driver cash-session DocType and reconciled at handover with an explicit variance line
`hooks.py` doc events on POD submit stamp the linked `Delivery Note`/`Sales Order` and advance delivery status automatically
Whitelisted server methods (`frappe.whitelist()`) expose only the driver-scoped actions the mobile client needs — no broad table access
Live location and stop status pushed to the back office via server scripts and scheduler events, with optional customer/dispatcher notifications
Dedicated `Delivery Driver` role profile and permission rules so a driver sees only their own trips, stops and cash sessions
Offline-tolerant capture: signatures, photos and COD entries queue on-device and sync when connectivity returns
GPS coordinates and server timestamp stamped on every delivery and failed attempt for dispute resolution and audit
Configurable stop lifecycle (assigned → en route → arrived → delivered/failed) implemented as controlled status transitions
Back-office dashboard and report views over POD records, reason-code breakdown and COD variance built on Frappe report/query tools
Built and tested against Frappe/ERPNext v15 and v16, following framework conventions so it survives `bench update` and site migrations
关于此产品
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.
为什么选择 Last-Mile Driver & Proof-of-Delivery App for ERPNext
Reads each driver's assigned `Delivery Trip` and `Delivery Stop` child rows over the Frappe REST API so the mobile manifest is the same submitted record the back office sees
Turn-by-turn navigation launched from each stop's stored geolocation, with stops ordered by the trip's planned sequence
On-glass e-signature capture plus one or more delivery photos, persisted as Frappe `File` attachments linked to a POD DocType
Structured failed-delivery reason codes backed by a reason-code master DocType (customer absent, refused, wrong address, damaged, rescheduled) instead of free text
COD collection recorded per stop, rolled into a driver cash-session DocType and reconciled at handover with an explicit variance line
`hooks.py` doc events on POD submit stamp the linked `Delivery Note`/`Sales Order` and advance delivery status automatically
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 2 to 4 weeks from confirmed scope, and you own the git repository at the end.
你得到什么
- Installable source code for your version of the app as a proper Frappe module (DocTypes, hooks.py, server and client scripts)
- Installation and configuration on your bench: app install, role profiles, reason-code and COD masters wired to your workflow
- Technical documentation: DocType schema, whitelisted method contracts, doc-event/scheduler map and REST endpoints
- End-user guide plus a live training session for drivers and back-office/dispatch staff
- UAT on a staging site with a documented rollback plan before production cutover
- Post-go-live support window for defect fixes and configuration questions
- Handover of the full git repository so your team can maintain or extend the app
- Version-compatibility notes and upgrade guidance for Frappe/ERPNext v15/v16 and future bench updates
这是给谁的
Logistics / Dispatch Manager
Runs daily delivery trips in ERPNext and needs real-time visibility into which stops succeeded, which failed and why, without waiting for the van to return. Buys this to replace paper manifests and phone check-ins with live, reportable status.
Finance / Accounts Controller
Owns COD cash integrity. Needs every cash-on-delivery collection recorded against the stop, rolled into a driver session, and reconciled at handover so banked cash matches collected cash with a clear variance trail.
Operations / IT Lead on ERPNext
Maintains the company's ERPNext bench and wants a driver app built as a clean Frappe module — proper DocTypes, hooks and permissions — that survives bench updates rather than a fragile external integration or spreadsheet workaround.
Field Delivery Team Lead
Manages the drivers themselves and needs a simple mobile flow: see my stops, navigate, capture signature and photo, log a failure reason, take COD. Buys this so drivers stop juggling WhatsApp, printouts and cash notes.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Last-Mile Driver & Proof-of-Delivery App for ERPNext 应用程序 ZIP。
将应用程序添加到您的工作台
将 ZIP 解压到您的 bench 的 apps 文件夹中，或者使用解压缩的应用程序的路径运行“bench get-app”。
安装在您的网站上
运行 `bench --site SITE_NAME install-app APP_NAME`，然后运行 `bench migrate` 以安装 Last-Mile Driver & Proof-of-Delivery App for ERPNext 并应用其架构。
激活您的许可证
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
Last-Mile Driver & Proof-of-Delivery App for ERPNext 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Fit to your delivery workflow | Built to your exact stop lifecycle, reason codes and COD rules | Fully bespoke but you carry all design decisions | Fixed feature set; you adapt to its assumptions | |
| Proof of delivery capture | E-signature + photos + receiver + GPS/timestamp as linked POD records | Possible, but you specify and build it all | Often signature-only, loosely linked | |
| COD cash reconciliation | Per-stop capture, driver cash session, variance at handover | Build it yourself from scratch | Basic COD flag, rarely reconciled | |
| ERPNext integration depth | Native Frappe module: DocTypes, hooks.py events, whitelisted API | Depends on your team's Frappe skill | Frequently an external app syncing over API | |
| Version safety (v15/v16) | Framework-conventional, survives bench update; upgrade guidance included | Only as disciplined as your build | Depends on vendor's upgrade cadence | |
| Delivery time & cost | 2–4 weeks from confirmed scope, fixed quote | Longer; open-ended internal effort | Instant install but rework to fit | |
| Code ownership | Full source + git repo handover, no lock-in | You own it outright | Usually closed source / licensed | |
| Support after go-live | Included support window + optional retainer | Your team supports it | Vendor SLA, variable quality |
关于Last-Mile Driver & Proof-of-Delivery App for ERPNext的常见问题
+Is this an existing app I can download and install today?
No. This is a build-to-order app that ECOSIRE builds, installs and supports for your specific workflow. It is not an off-the-shelf Frappe Cloud Marketplace download — we scope your stop lifecycle, reason codes, COD rules and roles first, then build against that specification.
+How long does delivery take?
Typical delivery is 2 to 4 weeks from confirmed scope. The clock starts once we have agreed the requirements in writing after the scoping call — not from the day you enquire. Larger or heavily customised builds are estimated during scoping.
+Which versions of ERPNext does it support?
We build and test against Frappe/ERPNext v15 and v16, following framework conventions (proper DocTypes, hooks.py doc events, whitelisted methods, permissions) so the app survives `bench update` and standard site migrations. Tell us your exact version during scoping.
+How does it fit with the native Delivery Trip and Delivery Note?
It builds directly on them. The driver app reads the assigned `Delivery Trip` and its `Delivery Stop` rows via the Frappe REST API, and on proof-of-delivery submit, `hooks.py` doc events stamp the linked `Delivery Note`/`Sales Order` and advance status. Your existing ERPNext data stays the source of truth.
+How is COD cash reconciled?
Each COD payment is recorded against its stop and rolled into a driver cash-session DocType. At handover the app compares total collected against total banked and shows an explicit variance, so finance gets an auditable trail instead of end-of-day estimates.
+What about support and updates after go-live?
Every build includes a post-go-live support window for defect fixes and configuration questions, plus full git repository handover so your team can maintain it. Ongoing enhancements, new features or version upgrades beyond the window are available as a separate support/retainer arrangement.
+Do we own the code?
Yes. You receive the full installable source and the git repository is handed over to you, so you are never locked in. You can maintain, extend or re-host the app with your own team or another vendor.
相关模块
申请报价
Last-Mile Driver & Proof-of-Delivery App for ERPNext
A mobile driver companion for ERPNext Delivery Trips: turn-by-turn navigation, e-signature and photo proof of delivery, COD collection with cash reconciliation, and live status back to the office. Built to your workflow, installed on your bench, and supported by ECOSIRE.
- Reads each driver's assigned `Delivery Trip` and `Delivery Stop` child rows over the Frappe REST API so the mobile manifest is the same submitted record the back office sees
- Turn-by-turn navigation launched from each stop's stored geolocation, with stops ordered by the trip's planned sequence
- On-glass e-signature capture plus one or more delivery photos, persisted as Frappe `File` attachments linked to a POD DocType
- Structured failed-delivery reason codes backed by a reason-code master DocType (customer absent, refused, wrong address, damaged, rescheduled) instead of free text