Warehouse systems engineering · WMS optimisation
Your WMS, aligned to how the floor actually works.
The picks are slow, the counts drift, and operators build workarounds instead of following system logic. In most cases the platform is not the problem — the configuration is. 1722 is independent, vendor-neutral WMS configuration and optimisation: pick and put path design, slotting, wave planning, directed put-away, allocation, batching, replenishment and returns, aligned to your floor rather than a vendor default.
We do not sell a WMS and take no vendor commissions. We configure and optimise the system you already run.
What it is
What WMS optimisation covers.
Independent configuration work on the WMS you already own, scoped to the mechanics that actually move product through your building.
- 01
Pick & put path design
Travel paths, zone logic and pick sequencing reworked around your actual floor layout and order profile, not a generic default.
- 02
Slotting
Item placement aligned to velocity, order affinity and pick method — the single change with the largest effect on travel time in most warehouses.
- 03
Wave planning
Wave logic, release timing and sizing tuned to labour availability and order cutoffs, so waves land work operators can actually execute.
- 04
Directed put-away & allocation
Put-away rules and allocation logic set to match how stock is actually received and picked, closing gaps between system direction and floor behaviour.
- 05
Batching & replenishment
Batch sizing and replenishment triggers configured against real demand patterns, reducing both stockouts on the pick face and excess replenishment trips.
- 06
Returns configuration
Returns processing and disposition logic set up to close the loop back into inventory without a manual workaround.
When you need it
When to look at the configuration first.
Four patterns come up repeatedly: picks running slower than the system was rated for; operators building manual workarounds instead of following system logic; a configuration that has drifted since go-live as processes changed underneath it; and growth — new SKUs, new volume, a new building — that has outpaced the original setup. Each is a configuration signal before it is a platform signal.
What you get
Deliverables you own.
Every engagement ships concrete artefacts your team keeps and can act on — never advice alone.
- KPI baseline across picking, put-away and replenishment, with the current-state read
- Documented configuration changes — exactly what changed and why, for pick paths, slotting, waving, put-away, allocation, batching, replenishment and returns
- Process design aligned to the floor, not a vendor default
- Before/after read against the baseline, so the effect of the work is measurable
- Handover pack — documentation and training so your team owns the configuration
Out of scope
What this is not.
This is not a WMS product, a resale of any vendor’s platform, or a subscription — we take no vendor commissions and sell no licences. It is also not managed operations: the engagement has a defined end point, and your team runs the configuration afterwards. Where the floor problem turns out to be automation integration or reporting rather than WMS configuration, that is scoped separately and named plainly, not folded in.
How we engage
A project, not a ticket queue.
| 1 · Assess | Warehouse walk & KPI baseline across picking, put-away and replenishment. |
|---|---|
| 2 · Design & configure | Pick/put path, slotting, waving, put-away, allocation, batching, replenishment and returns configuration. |
| 3 · Validate | Before/after read against the baseline; staged rollout with rollback criteria agreed up front. |
| 4 · Handover | Documentation and training so your team owns the configuration without us. |
Point the WMS at your actual floor.
Tell us where picks, slotting or waving are fighting the system. A short discovery call, then a scoped plan.
FAQ
WMS optimisation, answered.
Do you sell or replace our WMS?
No. We do not sell a WMS, take no vendor commissions, and in most cases do not recommend replacement. The great majority of WMS problems are configuration problems, not platform problems — we align the system you already own to how your floor actually works before a replacement conversation is ever warranted.
How is WMS optimisation different from a WMS implementation?
An implementation configures you onto a new platform. Optimisation works inside the platform you already run — pick and put path design, slotting, wave planning, directed put-away, allocation, batching, replenishment and returns — closing the gap between how the system is set up and how the floor moves.
What are the signs we need this?
Slow picks that do not match rated throughput, operators building workarounds instead of following system logic, a configuration that has drifted since go-live, or growth and SKU count that have outpaced the original setup. If any of those sound familiar, the configuration is the first place to look.
Which WMS platforms do you work with?
The method is platform-independent by design. Engagements start from your pick logic, slotting rules, wave strategy and put-away configuration, not from a vendor playbook. Tell us what you run on the discovery call and we will be specific about fit.
What do we get at the end of the engagement?
A documented KPI baseline, the specific configuration changes made and why, a before/after read against that baseline, and a handover pack so your team owns the configuration going forward — not a set of recommendations left for someone else to implement.
Will this disrupt live operations?
Changes are staged and validated against the KPI baseline before and after each change set, with go-live and rollback criteria agreed up front. The intent is a measured before/after read, not a live experiment on your floor.
Do you run the WMS afterwards?
No. This is project engineering with a defined end point, not ongoing operations. We document the configuration and train your team so they run it without us. A follow-on retainer is available if wanted, but it is never the lead offer.