Warehouse Management software
A warehouse system is a walking-distance problem wearing a software costume.
Inventory software tells you what you have. A warehouse system tells a specific person where to walk next, in what order, and proves what they picked. The whole return on it is measured in steps not taken and lines picked per hour, so that is what we design against.
What it replaces
- Pick lists printed in order-entry sequence, sending pickers back and forth across the same aisles all day.
- Putaway by habit, so fast movers end up at the back and the new starter cannot find anything.
- Mispicks discovered by the customer, with no record of who picked or packed the carton.
- Dispatch cut-offs missed because nobody can see, at three o'clock, which orders will not make the van.
What we build
The parts that make it a system.
Scoped to what you run. A module you do not need is not a discount we withhold — it is work nobody does.
Receiving and directed putaway
ASN or PO-matched receipt, quality hold, and putaway suggested by velocity, size and zone rather than by where there happens to be a gap.
Picking strategies
Single, batch, zone and wave picking with routes ordered by physical layout, short-pick handling that reallocates rather than stalls, and replenishment triggered from pick faces automatically.
Pack, verify and dispatch
Scan verification at pack, carton and weight capture, carrier label generation, and manifesting against the cut-off with a live view of what will not make it.
Labour and throughput visibility
Lines per hour by person, task and zone; the queue ahead of each cut-off; and the bottleneck named rather than felt.
Where AI actually helps
And where it does not.
Slotting is the real one — which SKU belongs in which location given current velocity and affinity, re-run as the mix changes rather than once at fit-out. Forecast-driven labour planning is the second. Both are optimisation problems where a model beats a rule of thumb, and neither is a chatbot, which is the thing most vendors will show you instead.
Integrations
What it has to talk to.
A system that does not reach the ones you already run creates a second place to type things, which is the problem you started with.
- Handheld scanners and mobile devices, tested on the units on your floor
- Carrier and courier APIs for labels, manifests and tracking
- Your ERP or order management system as the source of orders and stock ownership
- Weighbridge, dimensioners and label printers where they exist
The limits
What we do not do here.
Including, on several of these pages, telling you not to buy a build at all. That advice has cost us work. It has also stopped projects that would have failed in month three, which is cheaper for everyone.
- We do not integrate automation hardware — conveyors, sorters, AS/RS, robotics. That is controls engineering with a safety envelope, and it belongs to the vendor who supplied it.
- We do not do warehouse design or slotting consultancy as a standalone service. We will build the system that measures and executes a layout; deciding the layout is a different profession.
- A WMS on a building with no addressed locations is not a project we will start. Bin addressing and labelling comes first, and it is physical work.
In practice
Where this shows up.
E-commerce fulfilment
High line counts, small orders, and a cut-off that decides the customer promise. Batch picking and pack verification carry the whole operation.
Cold chain and pharma
Temperature zones, FEFO and full traceability are not features here, they are the licence to operate — and a manual exception process is the audit finding.
How it runs
Fixed scope, fixed price, working software each sprint.
01
Discovery
A call, then a written read of the problem — what it costs today, what would have to be true for software to fix it, and whether we're the right people.
02
Proposal
Fixed scope, timeline and price. No open-ended discovery phase billed by the hour.
03
Build
Agile sprints with something running at the end of each one. You see progress in the product, not in a status deck.
04
Ship & support
Cloud deployment, production monitoring and a maintenance arrangement that starts before launch, not after the first incident.
Related
Systems that usually come up in the same conversation.
Most of these share data with each other. Where two are in scope we would rather build one system than two that sync.
Inventory Management
Stock numbers you can act on — because the system knows what is reserved, what is in transit and what was miscounted.
Supply Chain Management
Visibility across suppliers, shipments and documents — so a delay is something you handle rather than discover.
Fleet Management
Vehicles, drivers, maintenance and fuel in one record — so cost per kilometre is a number rather than an argument.
Tell us what your Warehouse Management system would have to handle.
Pick a time that suits you. Tell us the problem, and we'll tell you honestly whether we're the right people to solve it.