Handheld and phone barcode scanning for receiving, picking, packing, transfers, and stock counts, wired directly into ERPNext's Stock DocTypes. ECOSIRE builds it to your workflow, installs it on your bench, and supports it after go-live. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $399.00 USD; request a quote for a scoped proposal.

Handheld and phone barcode scanning for receiving, picking, packing, transfers, and stock counts, wired directly into ERPNext's Stock DocTypes. ECOSIRE builds it to your workflow, installs it on your bench, and supports it after go-live.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Warehouse teams running ERPNext quickly hit the limits of manual data entry. Stock Entry, Purchase Receipt, and Delivery Note forms were designed for a desk, not for a picker walking aisles with a scan gun. Item codes get keyed wrong, Pick Lists are worked off printed paper and reconciled hours later, and cycle counts mean someone transcribing shelf tallies into a spreadsheet before a Stock Reconciliation is ever created. ERPNext core does support a barcode field and the built-in Point of Sale scan box, but there is no purpose-built mobile flow for receiving against a PO, picking against a Pick List, bin-to-bin transfers, or blind counts — and nothing that keeps working when the warehouse Wi-Fi drops behind a rack of steel shelving.
Camera-based scanning via an on-device JS barcode decoder (1D and 2D/QR), no native app-store install required
Bluetooth and USB HID scan-gun support, so existing handheld terminals keep working as keyboard-wedge input
Scan-to-pick against an ERPNext `Pick List`, validating each scan for item, remaining qty, and batch/serial where configured
Scan receiving that matches units against open `Purchase Order` / `Purchase Receipt` lines with over-receipt guards
Bin-to-bin and warehouse-to-warehouse transfers that post real `Stock Entry` documents through the standard submit flow
Cycle counts and blind counts that generate `Stock Reconciliation` documents with variance flagged before submit
We build a proper Frappe app — its own module with custom DocTypes, hooks.py doc events, whitelisted API methods, and a mobile-first UI — installed on your own ERPNext bench. Scanning happens through the device camera (using a JS barcode decoder) or any Bluetooth/USB HID scan gun, and every scan resolves against your existing Item, Item Barcode, Batch, and Serial No records via whitelisted @frappe.whitelist() methods over the Frappe REST API, so there is no shadow inventory and no second source of truth. Scan-to-pick walks the operator through an ERPNext Pick List line by line, validating each scan against the expected item, quantity, and (where used) batch/serial. Scan receiving matches units against open Purchase Receipt / Purchase Order lines. Transfers and cycle counts post real Stock Entry and Stock Reconciliation documents through the standard submit workflow, so ledger entries, valuation, and audit trail stay exactly as ERPNext expects.
Reliability is designed in. Server-side hooks.py doc events enforce your posting rules, client scripts drive the on-device validation, and an offline queue buffers scans in local storage when connectivity drops and replays them through an idempotent sync endpoint once the device is back online — with conflict handling so a stale queue can't double-post. Permissions ride on ERPNext's own role and Role Profile model plus Warehouse-level restrictions, so a picker only ever touches the documents and stock locations they are entitled to, and every posted document carries the operator's user and timestamp. Optional scheduler events can reconcile the queue, flag stuck scans, or push a daily count-variance report. The app is built and tested against Frappe/ERPNext v15 and forward-compatible with v16.
Because this is build-to-order, nothing ships until we understand your warehouse. We start with a scoping call to map your receiving, picking, and counting flows, your scanner hardware, and whether you use batches, serials, or multi-warehouse bins. From confirmed scope, typical delivery is 2 to 4 weeks: we build against a staging copy of your bench, run UAT with your operators on real documents, then install on production with a rollback plan. You receive the full source, the git repository, install and configuration docs, and a post-go-live support window — no black box, no lock-in.
Runs receiving, picking, and dispatch on ERPNext and needs floor operators to scan instead of key data, cutting mis-picks and eliminating the lag between physical movement and a posted Stock Entry.
Owns stock accuracy across batches, serials, and multiple warehouses. Wants blind cycle counts that post `Stock Reconciliation` documents directly, with variances surfaced before submit rather than found at year-end.
Maintains the bench and integrations. Needs a clean Frappe app installed the right way — whitelisted methods, doc-event hooks, role-based permissions — with source, git repo, and docs so nothing is a black box on upgrade.
Wants faster, more reliable warehouse throughput without ripping out ERPNext for a separate WMS, and a build-to-order path with defined scope, UAT, and support rather than an unsupported marketplace gamble.
Buy the license on ecosire.com and download the Mobile Barcode Scanning for ERPNext Warehouse app ZIP from your account dashboard.
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Mobile Barcode Scanning for ERPNext Warehouse and apply its schema.
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fit to your warehouse flow | Built to your exact receiving, picking, transfer, and count workflows | Fully bespoke but you scope and manage it | Fixed flows you must adapt to | |
| Offline scanning | Local queue with idempotent replay on reconnect | Only if you design and build it | Often online-only or limited | |
| ERPNext integration | Native DocTypes, hooks, whitelisted REST methods | Depends on developer discipline | Varies; some bolt on a shadow store | |
| Scanner hardware | Camera plus Bluetooth/USB HID scan guns | Whatever you choose to support | Usually one input mode | |
| Delivery model | Build-to-order, 2-4 weeks, UAT and rollback | Your timeline and project risk | Instant install, no tailoring | |
| Support and ownership | Post-go-live support plus full git handover | You own and staff it | Vendor SLA, closed source common | |
| Cycle / blind counts | Scan-driven `Stock Reconciliation` with variance flags | Build it yourself | Sometimes, quality varies | |
| Total cost of ownership | Fixed build price, you keep the code | Higher and open-ended | Recurring license fees |
This is a build-to-order app, not an instant download. After a scoping call to confirm your workflows and hardware, typical delivery is 2 to 4 weeks from confirmed scope. That includes building against a staging copy of your bench, UAT with your operators, and a monitored production install with a rollback plan.
Both work. Any modern phone or tablet can scan through its camera using the on-device barcode decoder, and any Bluetooth or USB HID scan gun works as keyboard-wedge input. During scoping we confirm your exact devices so the flows are tuned to them.
Scans are buffered in an offline queue in device local storage and replay through an idempotent sync endpoint once connectivity returns, with conflict handling so a stale queue cannot double-post. Operators keep working; nothing is lost and nothing is posted twice.
No. Every action posts standard ERPNext documents — `Stock Entry`, `Purchase Receipt`, `Stock Reconciliation` — through the normal submit workflow, so ledger entries, valuation, batch/serial tracking, and audit trail behave exactly as ERPNext core does. Barcodes resolve against your existing Item and Item Barcode records; there is no separate inventory database.
The app rides on ERPNext's own role and Role Profile system plus Warehouse-level restrictions. An operator only touches the documents and stock locations they are entitled to, and every posted document carries the operator's user and timestamp for a full audit trail.
The app is built and tested on Frappe/ERPNext v15 and is forward-compatible with v16. You receive the full source and git repository, so your team can maintain it. During the post-go-live support window we fix defects and adjust configuration; version upgrades or new features beyond that window can be scoped as follow-on work.
You own it. We hand over the complete git repository and installable source along with technical docs. It is a standard Frappe app on your bench — no license server, no runtime lock-in, and any competent ERPNext developer can extend it.
Handheld and phone barcode scanning for receiving, picking, packing, transfers, and stock counts, wired directly into ERPNext's Stock DocTypes. ECOSIRE builds it to your workflow, installs it on your bench, and supports it after go-live.