Receiving, picking and dispatch on a scanner that survives the floor.
The ERP has a warehouse module, but nobody uses it on the floor because it assumes a desk and a mouse. So goods move first and get recorded later, from memory, and the discrepancies surface a week after they happened.
What we build
- Receiving against a purchase order, with over- and short-receipt handling
- Internal transfers and put-away, scanned at both ends
- Picking with short-pick and backorder handling built in, not bolted on
- Dispatch confirmation, and fixed-reader portals at the dock door where reads must be hands-free
Hardware it runs on
- Zebra TC21
- Enterprise handheld, barcode via DataWedge
- Chainway C72
- UHF handheld for pallet-level reads
- Zebra FX9600
- Fixed reader for dock-door portals
Every device listed here is one we have written about or shipped against. If yours isn't on the list, the feasibility read covers whether it can be.
How it reaches your system of record
The app talks to your ERP directly rather than through an export file — session-authenticated calls into Odoo, or a service against ERPNext, SQL Server or a custom API. Fixed readers speak LLRP into a middleware layer that filters false reads and infers direction before anything is written.
What you get
- Android application for the floor
- ERP module or integration service
- Device provisioning profile for fleet rollout
- RF and antenna placement notes where fixed readers are involved
What it costs
A fixed fee, scoped after the feasibility read. You see the number before any work starts, and it doesn't move.
How an engagement runsThe work behind it
We publish the engineering, not just the sales page.
Send us the device and the error
Model, SDK version, and what's failing. A written read within 24 hours, and nothing owed if it's a no-go.
Get a feasibility read