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.

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 one working week 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.