Warehouse management system
Goods in, goods out and stocktakes are entered where they happen, from a scanner, and the figure moves at the moment of the operation.
- Buildfrom $2,850
- Timeline4–7 weeks
- Supportfrom $570/mo
Who this suits: Warehouses where the stock figure lives in a spreadsheet updated in the evening, orders are picked from a printout, and a shortfall surfaces once a quarter.
What is in the first version
- receiving by document
- barcodes and handhelds
- picking and shipping
- rolling stocktakes
The figures above are the package this sits on: CRM or client portal. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
Goods become stock at the gate
The storeman scans at the gate and checks against the supplier's document while the lorry is still standing.
- 02
Picking follows a task
The picker follows a route through the bins and confirms every line with a scan, catching a wrong item.
- 03
A reservation takes stock before shipment
A confirmed order stops the quantity being available, and the same figure goes outward to a portal or a storefront.
What decides whether this works or annoys people
The network drops in the aisles
The handheld works offline, holds operations and sends them later, and a conflict on that send is resolved by a stated rule.
A stocktake that stops the work
A rolling count by zone freezes only the zone being counted, and a discrepancy closes with a document and an author.
A negative figure is a symptom
Forbidding it pushes a storeman to enter a receipt that never happened, so the operation goes through, gets flagged and queued.
What to measure once it is live
- gap between system and shelf
- time from receiving to the figure
- lines picked without a wrong item
- operations entered after the fact
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Warehouse screens and the handheldTypeScriptReactNext.jsKotlin
- Server and dataNode.jsPostgreSQLPrismaRedisDocker
- Exchange and watchingn8nTemporalTelegram Bot APIS3Grafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- handhelds, scanners and label printers
- access points and their installation
- labels, ribbons and printing consumables
- hosting and an on-site server
Asked before the first call
- Why not 1C or a ready-made WMS?
- If a ready-made one fits your warehouse, take it. Your own earns its place on a non-standard process, and often the right answer is a warehouse alongside the accounting system rather than instead of it.
- What about several warehouses and moves between them?
- The ordinary case, and goods in transit are counted separately: written off one warehouse and not yet received at the other, otherwise they double or vanish for the journey.
- Will the warehouse staff actually use it?
- They use it when the scanner beats paper: one task per screen, large targets, one-handed work in a glove. We check that in your warehouse before launch, not on a big monitor.