Warehouse Management — offline-first Android scanner

Bin-level stock, directed putaway,
FEFO picking, cycle counts.

Bolt on to Business Central, SAP B1, or Solvexa Retail. Your operators keep scanning even when the warehouse Wi-Fi dies. Every scan lands exactly once, whenever the network settles.

Start free — 30-day trial Download scanner APK
SUB-WMS-STARTER · ₹12,000/month · 1 warehouse · 25 operators · all four flows

Receive

Scan barcode pick receiving bin qty. Enqueue instantly; never wait for the server. Optional lot + expiry for perishables.

/Warehouse/Receipt

Putaway

Every positive quantity in a Receiving bin becomes a task. Scan target confirm. Directed-putaway rules (cold-chain enforcement) coming next.

/Warehouse/Putaway

Pick

Item lookup shows every bin holding stock, FIFO-ordered. Cap on over-pick both client + server. Wave picks + order-driven tasks in a later slice.

/Warehouse/Pick

Cycle Count

Pick a bin System qty next to Counted qty per line. Server posts the signed delta as one adjustment ledger row. Variance thresholds + supervisor approval next.

/Warehouse/CycleCount

Offline round-trip, guaranteed once

Every mutating endpoint takes an Idempotency-Key. A replayed scan after the network settles hits the server's WMS_Idempotency cache and returns the same movement id — never a double post.

Scanner: scan item pick bin qty Submit │ drift.pending_actions enqueue with fresh clientGuid │ (SyncEngine tick — 60s / connectivity / resume) │ POST /Warehouse/Receipt header: Idempotency-Key: {clientGuid} │ Server IdempotencyService.GetOrExecute │ ├─ cache hit return cached response, NO re-execute └─ cache miss MovementService (atomic +/- ledger + BinContent) │ 200 local pending row deleted

ERP-agnostic

Solvexa WMS ships an IErpAdapter interface with connectors that plug into your existing books-of-record. Same product either way.

Solvexa Retail (in-process)
Microsoft Dynamics 365 Business Central (Day 12)
SAP B1 · Tally · Zoho (backlog)

How Solvexa WMS is different

Three concrete things you won't find in a stock WMS.

Offline-first is the DEFAULT

Not "sync when convenient" — local drift SQLite mirror + server-side idempotency cache. Metal racks and freezer Faraday cages don't stall the shift.

One app across the tenant

Same login, same tenant DB, same Saathi assistant. Retail + WMS operators share the item master and see one another's stock adjustments in real time when the module gate opens both sides.

Saathi speaks WMS out of the box

16 how-to chunks seeded on every WMS-enabled tenant. Ask "how do I receive stock" or "what happens if Wi-Fi drops mid-pick" and get an inline answer, no doc-hunting.