Operations depend on oral habits, local experts and manual inventory corrections.
Warehouse manager guide
Prepare the warehouse for a WMS: flows, data, teams and acceptance
Turn actual practices into testable rules without losing the exceptions that keep operations running.
For: Warehouse managers, team leaders, methods, logistics and ITWhat to clarify before discussing a solution
Which scenarios prove the future operating model can handle a real working day?
The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.A shop-floor pack of scenarios, data, exceptions, equipment and acceptance criteria.
Four decisions to make before configuration
These decisions make the scope testable and prevent structural choices from being discovered during the project.
Choose representative days and flows
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Define priority and substitution rules
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
List equipment and shop-floor conditions
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Build acceptance run by future users
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
A readable end-to-end flow
Scope is not a list of modules. It is a chain of events, ownership and decisions.
1Receiving
2Put-away
3Replenishment
4Picking
5Shipping and inventory
In the first scoping
- One representative flow and its useful variants
- Authoritative events and minimum data
- Roles, decisions and escalation times
- Acceptance criteria and baseline measurement
To sequence in waves
- Additional sites, activities or populations
- Rare variants that do not condition the pilot
- Automations whose rule is not yet stable
- Advanced dashboards after source reliability
To decide explicitly
- Choose representative days and flows
- Define priority and substitution rules
- List equipment and shop-floor conditions
- Build acceptance run by future users
From direction to measured improvement
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.
Measure to decide, not to fill a dashboard
Every KPI needs a definition, a source, a cadence and an associated decision.
KPIFormulaSourceDecision
Inventory accuracyItems without variance ÷ items checkedSystem inventory, counts and movementsCorrect the flows that create variances
Dock-to-stock timeAvailability time − arrival timeAppointments, receiving, checks and put-awayRemove receiving bottlenecks and improve priorities
Picking productivityOrder lines picked ÷ productive hoursTasks, time, zones and operatorsReview methods, travel and workload by zone
Order cycle timeAvailability time − validation timeOrder, allocation, picking and shippingIdentify the link slowing the promise
06 · Business scenario
A working day as the acceptance scenario
- Situation
- The warehouse performs correctly thanks to adjustments known by a few people.
- Approach
- Teams replay receiving, inventory, picking, exceptions and counting with representative data and volumes.
- Target outcome
- Tacit rules become visible and can be configured, trained or removed.
Useful answers before the first discussion
01Where should we start in practical terms?
Choose a representative scope spanning “Receiving” and “Put-away”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.
02Do all existing systems need replacing?
No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.
03What data should be prepared before a workshop?
Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure Inventory accuracy. The quality of examples matters more than the quantity of documents.
04How should the right pilot scope be chosen?
Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.
05How can scope changes during the project be limited?
Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.
Next step
Turn this guide into a personalised review
Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Complementary guides
Guides by suite
EMS Logistics suite
Transform transport & logistics
Connect order, warehouse, transport, delivery and invoicing around the same events and responsibilities.
- Service promise
- Warehouse execution
- Transport plan
Guides by suite
EMS Industry suite
Connect planning to the shop floor
Build decision continuity across demand, materials, capacity, execution, quality, maintenance and cost.
- Demand and schedule
- Materials and capacity
- Execution and WIP
Guides by suite
EMS Commerce suite
Unify omnichannel commerce
Connect catalogue, availability, order, payment, fulfilment, delivery, return and customer relationship.
- Catalogue and pricing
- Available-to-promise inventory
- Order and allocation