A branded iOS and Android self-service app that gives your employees a mobile front-end to ERPNext for leave requests, expense claims, payslips and check-in. Built to your scope by ECOSIRE, installed on your ERPNext v15/v16 instance and supported after go-live. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A branded iOS and Android self-service app that gives your employees a mobile front-end to ERPNext for leave requests, expense claims, payslips and check-in. Built to your scope by ECOSIRE, installed on your ERPNext v15/v16 instance and supported after go-live.
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Most ERPNext HR rollouts stall at the same place: the back office loves the ERP, but frontline and field employees never touch it. Filing a Leave Application, submitting an Expense Claim, checking a payslip or recording an Employee Checkin all mean logging into the ERPNext desk on a laptop or squinting at a responsive web view that was never designed for a phone. ERPNext HR is complete as a system of record, but out of the box it gives you no native mobile app, no push notifications for approvals, and no camera-first receipt capture or GPS-stamped attendance. That gap is where adoption dies and where HR ends up re-keying paper forms.
Native iOS and Android app with your branding, icon, splash and app-store/Play-Store listing metadata
Leave & time-off requests that create real `Leave Application` records honoring `Leave Type`, `Leave Allocation` balances and your existing approval workflow
Expense claims with in-app camera receipt capture, attached as `File` records against the `Expense Claim` DocType
Payslip viewing that reads submitted `Salary Slip` documents, permission-scoped so each employee sees only their own
Check-in/out writing `Employee Checkin` records with GPS latitude/longitude, device timestamp and optional geofence validation
Push notifications for pending approvals via Firebase Cloud Messaging, triggered by `hooks.py` doc events and `scheduler_events`
We build a branded native mobile app — your name, logo, colors and app-store listing — that sits on top of your existing ERPNext instance and talks to it through the Frappe REST API and a small set of @frappe.whitelist() server methods we ship as a proper Frappe app. Nothing is a separate database: a leave request from the phone creates a real Leave Application DocType record, respects your existing Leave Type, Leave Allocation and approval workflow, and flows through the same hooks.py doc events (on_submit, on_update) your ERPNext already runs. Expense claims capture receipt photos and attach them as File records against the Expense Claim; payslip viewing reads submitted Salary Slip documents scoped by permission; and check-in/out writes Employee Checkin rows with latitude/longitude, optional geofence validation and device time.
Technically the app authenticates each employee against their own ERPNext user, so every read and write is enforced by ERPNext's native role permissions and role profiles — an employee only ever sees their own records, and approvers see their queue. Push notifications for pending approvals are driven by Frappe scheduler_events and doc-event hooks that fan out to Firebase Cloud Messaging when a document needs a manager's action, so approvals happen from the lock screen instead of an unread email. Client-side validation mirrors the server rules, and all business logic that must be trusted lives in whitelisted methods and server scripts on ERPNext — the app is a thin, well-behaved client, not a second source of truth. We target Frappe/ERPNext v15 and v16.
Because this is build-to-order, we do not hand you a generic binary off a marketplace. After a short scoping call we confirm exactly which flows you need, your branding, your approval hierarchy and any custom fields, then design, build and test the app against a staging copy of your ERPNext. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source code for your version, we install and configure the companion Frappe app on your instance, run UAT on staging with a documented rollback plan, and stay with you through a post-go-live support window. It is your app, your data and your ERPNext — we just make it reachable from every employee's pocket.
Owns the ERPNext HR module and is tired of paper leave forms and re-keying. Needs employees to self-serve leave, expenses and payslips from a phone while every record still lands correctly in ERPNext under the existing approval workflow.
Responsible for the Frappe instance and wary of shadow systems. Wants a clean companion Frappe app with whitelisted methods and native permission enforcement, source code in a git repo they control, and compatibility with their v15/v16 upgrade plan.
Manages employees who rarely sit at a desk — technicians, drivers, retail or site staff. Needs GPS or geofenced check-in/out and photo-based expense capture so attendance and reimbursements are accurate without office visits.
Wants employees to view their own submitted salary slips securely and file expense claims with attached receipts, reducing payroll queries and reimbursement disputes while keeping approvals and permissions strictly enforced by ERPNext.
Compre la licencia en ecosire.com y descargue la aplicación ZIP de Employee Self-Service Mobile App desde el panel de su cuenta.
Extraiga el ZIP en la carpeta de aplicaciones de su banco o ejecute `bench get-app` con la ruta a la aplicación extraída.
Ejecute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench migrar` para instalar Employee Self-Service Mobile App y aplicar su esquema.
Abra la configuración de licencia de ECOSIRE en su sitio y active su clave de licencia. Requiere las aplicaciones gratuitas ecosire_connect y ecosire_license_client.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Mobile experience | Native iOS/Android app, your branding | Whatever you build in-house | Generic app, limited branding | |
| ERPNext integration | Real DocTypes via REST + whitelisted methods | Depends on your team's Frappe depth | Fixed schema, may not fit your setup | |
| Fits your workflows | Adapted to your approvals and custom fields | Fully custom but you own the effort | Take it as shipped | |
| GPS / geofence check-in | Built in, writes `Employee Checkin` | Build and maintain yourself | Sometimes, varies by vendor | |
| Push approval notifications | FCM via hooks and scheduler events | Wire up FCM yourself | If offered, often generic | |
| Source code ownership | Full source + git repo handover | You own it, you built it | Closed binary, licensed | |
| Delivery time | 2-4 weeks from confirmed scope | Months, plus hiring/ramp | Instant install, generic fit | |
| Support & upgrades | Post-go-live window + optional plan | Your team maintains it | Vendor SLA, may lag v15/v16 |
No. This is a build-to-order product. ECOSIRE designs, builds and installs a branded app tailored to your ERPNext instance and workflows. It is not a pre-published Frappe Cloud Marketplace download — after a scoping call we build your version and deploy it to you.
Typical delivery is 2 to 4 weeks from confirmed scope. The clock starts once we have agreed the flows, branding, approval hierarchy and any custom fields on a scoping call. Larger customizations or additional flows can extend that, and we tell you the impact before you commit.
Yes. The app writes to real DocTypes — `Leave Application`, `Expense Claim`, `Employee Checkin`, `Salary Slip` — so it respects your existing `Leave Type`, allocations, approval workflows and custom fields. We adapt the companion Frappe app to your customizations during the build rather than forcing a fixed schema.
We build and test against Frappe/ERPNext v15 and v16. If you are on an older version we will flag it during scoping and recommend an upgrade path, since the app relies on the v15/v16 REST API and permission behavior.
Each employee authenticates as their own ERPNext user, so all reads and writes are enforced by native ERPNext role permissions and role profiles. Trusted logic lives in `@frappe.whitelist()` methods and server scripts on your instance. There is no separate database — your ERPNext remains the single source of truth.
Every engagement includes a post-go-live support window for defect fixes and configuration questions. Because you receive the full source code and git repository, you can maintain it yourself or contract ECOSIRE for ongoing updates, ERPNext version upgrades and new flows under a separate support arrangement.
Yes. You receive the full installable source for both the mobile app and the companion Frappe app, handed over via a git repository with a tagged release. It is your app on your Apple and Google developer accounts, running against your ERPNext data.
A branded iOS and Android self-service app that gives your employees a mobile front-end to ERPNext for leave requests, expense claims, payslips and check-in. Built to your scope by ECOSIRE, installed on your ERPNext v15/v16 instance and supported after go-live.