Chatea en whatsapp

Los detalles del producto se muestran en inglés. Próximamente traducciones.

Precio: $399.00 USD
Versiones de ERPNext: —
tiempo de configuración: 30 minutos
Licencia: Perpetuo único
Idiomas: 11 idiomas

Compra única

Android / Mobile POS for ERPNext

Name: Android / Mobile POS for ERPNext
Brand: ECOSIRE
SKU: erpnext-android-mobile-pos

A native Android POS app for handheld terminals and tablets that bills, prints receipts and takes payments directly against ERPNext. ECOSIRE scopes, builds, installs and supports it for your hardware and workflow — this is a build-to-order engagement, not an instant download.

$399.00USD

Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.

Características clave

Native Android client for handheld terminals and tablets — not a wrapped web view of the ERPNext desktop POS

Packaged as a proper Frappe app (installed via `bench get-app` / `bench install-app`) plus the companion Android build, versioned in git

Custom DocTypes and whitelisted REST methods for catalogue sync and invoice submission, all inside your ERPNext bench

Creates and submits `POS Invoice` / `Sales Invoice` records against the correct POS Profile, warehouse and price list

Offline-first: encrypted local store lets staff bill, scan and print with no connection; queued sales auto-submit on reconnect

Idempotency keys and server-side validation on the submission method so a dropped signal never double-posts an invoice

Bluetooth barcode scanner pairing for fast SKU lookup against `Item` and `Item Barcode`

Bluetooth/USB thermal (ESC/POS) receipt printing mapped to your ERPNext Print Format

Mobile card-reader and QR payment support wired to your chosen provider, reconciled into ERPNext Mode of Payment

`hooks.py` doc events keep mobile prices and on-hand stock current when `Item Price` or `Stock Entry` changes

Scheduler events reconcile out-of-sync devices and flag stale or offline terminals

Dedicated role profile and permission rules so cashiers ring sales without access to the general ledger

Client scripts and server scripts for till-specific logic — loyalty, tax overrides, per-branch defaults, discounts

Token-authenticated Frappe REST API integration, built and tested against Frappe/ERPNext v15 and v16

Sobre este producto

ERPNext ships a capable Point of Sale, but it is a browser-based screen built for a fixed counter with a mouse and keyboard. The moment your selling happens on the move — a market stall, a delivery van, a trade-show booth, floor staff walking the shop with a handheld — that model runs out of road. The web POS assumes a reliable connection, does not natively pair with a Bluetooth barcode gun or a pocket thermal printer, and stalls the instant Wi-Fi drops. Vendors fall back to paper and re-key sales into ERPNext at day's end, which breaks stock accuracy and delays cash reconciliation.

Por qué elegir Android / Mobile POS for ERPNext

Native Android client for handheld terminals and tablets — not a wrapped web view of the ERPNext desktop POS

Packaged as a proper Frappe app (installed via `bench get-app` / `bench install-app`) plus the companion Android build, versioned in git

Custom DocTypes and whitelisted REST methods for catalogue sync and invoice submission, all inside your ERPNext bench

Creates and submits `POS Invoice` / `Sales Invoice` records against the correct POS Profile, warehouse and price list

Offline-first: encrypted local store lets staff bill, scan and print with no connection; queued sales auto-submit on reconnect

Idempotency keys and server-side validation on the submission method so a dropped signal never double-posts an invoice

We build a native Android application that turns any supported Android handheld or tablet into a first-class ERPNext till. It ships as two coordinated pieces: a proper Frappe app installed on your bench (bench get-app / bench install-app), plus the companion Android client. The Frappe side adds the DocTypes and whitelisted API methods the device needs — a lightweight sync endpoint that pulls Item, Item Price, POS Profile, Customer and stock levels, and a submission method that creates and submits POS Invoice / Sales Invoice records against the correct POS Profile, warehouse and price list. Every write flows through ERPNext's own permission engine via a dedicated role profile, so a floor cashier can ring sales without ever touching your general ledger.

Technically, the app is anchored in native ERPNext concepts rather than a bolt-on side database. hooks.py doc events keep the mobile catalogue, prices and on-hand quantities current whenever an Item Price or Stock Entry changes; scheduler events reconcile any device that fell out of sync and flag stale terminals. The Android client talks to the Frappe REST API and your whitelisted methods over token auth, and holds an encrypted local store so it can bill, scan and print entirely offline — queued invoices submit automatically on reconnect, with idempotency keys and server-side validation so a flaky signal never double-posts a sale. Bluetooth barcode scanners, Bluetooth/USB thermal receipt printers (ESC/POS), and mobile card readers / QR payment flows are wired to the specific hardware you run, and receipt layouts map to your ERPNext Print Format. Client scripts and server scripts cover any till-specific rules — loyalty, tax overrides, per-branch defaults — you need on top.

Because this is build-to-order, nothing is pretended to be a shrink-wrapped download. We start with a short scoping call to confirm your ERPNext version (v15 / v16), hardware models, payment providers and offline requirements, then quote a fixed scope. Typical delivery is 2–4 weeks from confirmed scope. You get the app built to your bench, installed and configured, tested on a staging site with UAT before anything touches production, and a git repo handover plus a post-go-live support window so your team is never left holding an unsupported binary.

lo que obtienes

Installable source code for your ERPNext version (the Frappe app plus the Android client build)
On-bench installation and configuration on your ERPNext instance, wired to your POS Profiles, warehouses and payment modes
Technical documentation: architecture, DocTypes, API methods, hooks and scheduler events
End-user guide plus a live training session for cashiers and floor staff
UAT on a staging site before go-live, with a documented rollback plan
Post-go-live support window for defect fixes and configuration questions
Git repository handover with full commit history so you own the code
Signed Android APK / build artifacts and a documented device-provisioning checklist

¿Para quién es esto?

Market-stall and mobile vendor

Sells from a stall, van or pop-up with no fixed counter and patchy connectivity. Needs to scan, bill and print on a handheld, take card or QR payments, and have every sale land in ERPNext stock and cash accounts without end-of-day re-keying.

Retail floor staff on tablets

Store associates who ring sales while walking the floor with a tablet and Bluetooth scanner, so customers skip the counter queue. Needs fast SKU lookup, thermal receipts and correct POS Profile / warehouse posting into ERPNext.

Multi-branch retail operations manager

Runs several outlets on one ERPNext instance and wants consistent mobile tills across locations, per-branch defaults, cashier-scoped permissions, and reliable offline behaviour so a dropped connection never loses a sale or corrupts stock.

ERPNext implementation partner or in-house admin

Owns the ERPNext deployment and needs a clean, git-handed-over Frappe app that respects native DocTypes, permissions and print formats — installable on their own bench and maintainable against v15/v16 upgrades, not a black-box binary.

Descripción general de la instalación

Descargar desde ECOSIRE
Compre la licencia en ecosire.com y descargue la aplicación ZIP de Android / Mobile POS for ERPNext desde el panel de su cuenta.
Añade la aplicación a tu banco
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.
Instalar en su sitio
Ejecute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench migrar` para instalar Android / Mobile POS for ERPNext y aplicar su esquema.
Activa tu licencia
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.

Cómo se compara Android / Mobile POS for ERPNext

Criterio	ECOSIRE	Construcción personalizada	Competidor
Delivery model	Build-to-order: scoped, built and installed for your bench in 2–4 weeks	You hire and manage a mobile + Frappe team from scratch	Instant download, but generic and not fitted to you
Mobile experience	Native Android app for handhelds and tablets	Whatever you have the skills to build	Usually a wrapped web view, not truly native
Offline mode	Encrypted offline store with auto-sync and idempotent submission	Hard to get right; easy to lose or duplicate sales	Often online-only or shallow offline support
Hardware integration	Bluetooth scanner, ESC/POS printer, card reader / QR wired to your models	Per-device driver work you own and maintain	Supports a fixed list that may exclude your gear
ERPNext integration	Proper Frappe app: DocTypes, whitelisted API, hooks, scheduler, role profile	Depends entirely on your team's Frappe depth	Varies; may sync via a side database rather than native docs
Permissions and security	Dedicated cashier role profile, writes via ERPNext permission engine	You design and audit the security model	Generic roles, may over-expose data
Ownership	Git repo handover and signed build — you own the source	You own it, but also all the risk and cost	Closed binary; typically no source access
Support and updates	Post-go-live support window plus optional v15/v16 upgrade retainer	Only what your internal team can sustain	Vendor SLA that may not cover your customizations

Preguntas frecuentes sobre Android / Mobile POS for ERPNext

+Is this an app I can download and install myself right now?

No. This is a build-to-order engagement. ECOSIRE scopes, builds, installs and configures the Android POS for your specific ERPNext instance, hardware and payment providers. There is no instant marketplace download — we hand over the built app and its git repository once it is tested and live on your bench.

+How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. We start with a short scoping call to lock down your ERPNext version, device models, payment methods and offline requirements, then quote a fixed scope. Complex payment integrations or unusual hardware can extend the timeline, and we tell you that up front rather than after.

+Which ERPNext and Frappe versions are supported?

We build and test against Frappe/ERPNext v15 and v16. The Frappe app installs on your bench with `bench get-app` / `bench install-app`, and we confirm your exact version and any custom apps during scoping so there are no surprises at install time.

+How does it work offline, and can it lose or duplicate sales?

The Android client keeps an encrypted local store so staff can scan, bill and print with no connection. Queued invoices submit to ERPNext automatically on reconnect. Each submission carries an idempotency key and is validated server-side, so a flaky signal will not double-post an invoice or corrupt your stock.

+What Android devices, scanners, printers and payment methods does it support?

It runs on Android handhelds and tablets, pairs with Bluetooth barcode scanners, prints to Bluetooth/USB thermal (ESC/POS) receipt printers, and supports mobile card readers and QR payment flows. Because hardware varies, we wire the app to the exact models and payment provider you run — confirmed during scoping — rather than promising universal compatibility.

+How does it keep cashiers out of sensitive ERPNext data?

Sales are submitted through a dedicated ERPNext role profile with tightly scoped permissions. A cashier can ring and print sales but cannot see the general ledger, other branches' data or admin settings. All writes go through ERPNext's own permission engine — the mobile app never bypasses it.

+What happens after go-live for support and updates?

Every engagement includes a post-go-live support window for defect fixes and configuration questions, and you receive the full git repository so your team or partner can maintain and extend the app. Beyond the included window, we offer ongoing support and version-upgrade retainers, and because you own the source there is no lock-in.

Solicitar presupuesto