Logstone WorksSupply chain management process improvement

How processes develop

Supply chain management processes improve step by step. These six levels describe increasing control, a clearer view of the work and more predictable results. Not every process needs all six. Different parts of a company may be at different levels.

Wide ink and watercolour drawing. A red thread leads from a tangle around an overloaded desk, through four orderly workstations, to a truck at a loading dock. Each level adds control, a clearer view of the work and more predictable results.
Fig. 1 Each level adds control, a clearer view of the work and more predictable results. Tap the drawing to enlarge it.

How do your processes work in practice today? If your best person is away for two weeks, what stops working?

Find the level that sounds most familiar. Start at Level 0 and read down. Even one statement that fits is a reason to look closer. It is not a judgment on the whole company.

Orders get fulfilled, but nobody can explain the whole process from start to finish.

What you see
  • Orders get fulfilled, but nobody can explain the whole process from start to finish.
  • The warehouse depends on what two or three people know and remember.
  • The ERP system is used mainly as a spreadsheet. The real decisions are made outside it.
The stage

Processes are not written down. Decisions depend on individuals, shared unwritten knowledge or reactions to problems.

What changes
  • Processes are written down, with a named person responsible for each one
  • The business stops depending on 2–3 irreplaceable people
  • You can answer basic questions about performance without a last-minute scramble

For the business Growth, financing or a sale no longer depend on two or three people.

Next step The SC Process Baseline. 4 to 6 weeks, with a fixed fee agreed before work starts. The baseline assessment explains the current situation and what to do next. Putting the improvements into practice is separate work.

More detail on this level
What you see
  • Orders get fulfilled, but nobody can explain the whole process from start to finish.
  • The warehouse depends on what two or three people know and remember.
  • Things go wrong when your best logistics person is on holiday.
  • The ERP system is used mainly as a spreadsheet. The real decisions are made outside it.
  • Finding out what it costs to serve a customer takes a week of Excel work.

If any one of these applies, it is worth looking closer.

What changes
  • Processes are written down, with a named person responsible for each one
  • New hires can be productive in weeks, not months
  • The business stops depending on 2–3 irreplaceable people
  • You can answer basic questions about performance without a last-minute scramble
What staying here costs
  • As the business grows, disruption grows at the same rate. The problems grow rather than the ability to handle the work
  • Checks by private equity investors, buyers or banks quickly expose the gaps and reduce the valuation
  • You cannot compare performance with others because you cannot measure your own
To distinguish this level from the next, ask
  • If your head of logistics or warehouse is away for two weeks, what stops working?
  • Can you say now what it costs to serve each customer segment?

Problems outside the normal process go to whoever is available, or to the boss. There is no agreed route.

What you see
  • Problems outside the normal process go to whoever is available, or to the boss. There is no agreed route.
  • Sales and operations, or procurement and the warehouse, have to negotiate how to pass work between them every day.
  • Management hears about problems after they happen, without an earlier warning.
The stage

Core processes are written down. Roles are clear. Basic performance measures are tracked.

What changes
  • There is an agreed way to handle exceptions, so they do not disrupt the whole operation
  • Passing work from sales to operations, or procurement to the warehouse, no longer needs daily negotiation
  • Management gets warnings instead of surprises

For the business Fewer problems catch you by surprise, and you spend less time dealing with urgent fixes.

Next step The Cost-to-Serve Reset. 3 to 6 months, with payments at agreed milestones set before work starts. The work covers the cost of serving customers, handling exceptions, passing work between teams and raising alerts. It ends with a period to stabilise the changes.

More detail on this level
What you see
  • Problems outside the normal process go to whoever is available, or to the boss. There is no agreed route.
  • People follow the processes when it is convenient, but set them aside when things get difficult.
  • Sales and operations, or procurement and the warehouse, have to negotiate how to pass work between them every day.
  • Management hears about problems after they happen, without an earlier warning.

None of the statements above applies, and at least one of these does.

What changes
  • There is an agreed way to handle exceptions, so they do not disrupt the whole operation
  • Passing work from sales to operations, or procurement to the warehouse, no longer needs daily negotiation
  • Management gets warnings instead of surprises
  • You move from having processes on paper to using them to run the business
What staying here costs
  • Processes are written down but not consistently followed. The same urgent problems remain, just with better labels
  • Growth adds people without adding capacity
  • Moving to a new ERP system carries the confusion into software because the processes are not clear enough to transfer
To distinguish this level from the next, ask
  • When an order goes wrong, is there an agreed route for raising the problem, or does it go to whoever is available?

Exceptions are handled by a rule. Nobody checks why the same ones keep returning or whether the threshold is right.

What you see
  • Exceptions are handled by a rule. Nobody checks why the same ones keep returning or whether the threshold is right.
  • Demand planning relies on experience: last year's figures plus an allowance.
  • The system flags a late order only after the deadline. It gives no early warning.
The stage

Processes work. Problems are spotted and handled consistently, without relying on individual rescue efforts.

What changes
  • You find out why the same exceptions keep returning and fix the cause.
  • You plan ahead using demand forecasts, capacity models and different possible scenarios
  • The system uses statistical methods to warn you before a deadline is missed.

For the business Less money is tied up in stock, and fewer bids are lost because of delivery-time commitments.

Next step The scope is agreed after a baseline assessment. There is no fixed-scope offer for this work yet.

More detail on this level
What you see
  • Exceptions are handled by a rule. Nobody checks why the same ones keep returning or whether the threshold is right.
  • Demand planning relies on experience: last year's figures plus an allowance.
  • Purchasing starts when an order arrives, rather than being planned from a forecast.
  • Stock covers uncertainty. Nobody can say in advance how growth of a third would affect capacity.
  • Promised delivery times are based on instinct rather than data.
  • The system flags a late order only after the deadline. It gives no early warning.

None of the statements above applies, and at least one of these does.

What changes
  • You find out why the same exceptions keep returning and fix the cause.
  • You plan ahead using demand forecasts, capacity models and different possible scenarios
  • Purchasing is planned from forecasts rather than starting only when orders arrive
  • Stock is managed to support business goals, rather than simply covering uncertainty
  • The system uses statistical methods to warn you before a deadline is missed.
  • You can model how growth of a third would affect the business before it happens
What staying here costs
  • Processes are stable, but planning is limited. You improve what you have without being able to prepare for what is coming
  • Stock is too high because planning reacts to events
  • You lose competitive bids because promised delivery times rely on instinct rather than data
To distinguish this level from the next, ask
  • How far ahead does your demand planning look: weeks, months or quarters?
  • Does planning use statistical methods or models, or does it rely on experience?

Sales and operations planning (S&OP) runs every month using real data.

What you see
  • Sales and operations planning (S&OP) runs every month using real data.
  • Demand forecasting uses statistical methods.
  • You model what could happen in different scenarios, rather than only discussing them in meetings.
The stage

Planning uses data and mathematical methods to forecast demand, model capacity and assess scenarios. It does not use AI.

What changes
  • Automated recommendations reduce the mental effort of making routine decisions
  • Machine learning finds patterns people miss: unusual demand, supplier risks and quality trends
  • A real-time view replaces reports produced at intervals

For the business As processes become more complex, planning effort grows more slowly.

Next step The scope is agreed after a baseline assessment. There is no fixed-scope offer for this work yet.

More detail on this level
What you see
  • Sales and operations planning (S&OP) runs every month using real data.
  • Supplier performance is measured and managed before problems arise.
  • Demand forecasting uses statistical methods.
  • Capacity planning covers 6–12 months ahead.
  • You model what could happen in different scenarios, rather than only discussing them in meetings.

None of the statements above applies, and all of these do.

What changes
  • Automated recommendations reduce the mental effort of making routine decisions
  • Machine learning finds patterns people miss: unusual demand, supplier risks and quality trends
  • A real-time view replaces reports produced at intervals
  • You move from accurate forecasts to a system that learns and adapts
What staying here costs
  • More manual analysis brings smaller gains. Progress is limited by how much people can pay attention to
  • For many processes, Level 3 is the right place to stay.
To distinguish this level from the next, ask
  • Which routine decisions does a model recommend today, and who checks them?

Machine learning models help forecast demand, optimise stock levels and score supplier risks.

What you see
  • Machine learning models help forecast demand, optimise stock levels and score supplier risks.
  • The system spots unusual patterns and flags them before they cause problems.
The stage

Machine learning helps people make decisions by finding patterns, spotting unusual changes and recommending actions.

What changes
  • Routine decisions are automated within agreed limits.
  • The system adjusts its own settings based on the results.

For the business Routine decisions take less management time.

Next step A direction, not a current offer.

More detail on this level
What you see
  • The system recommends an action. A named person approves it. The decision-making rules are written down.
  • Machine learning models help forecast demand, optimise stock levels and score supplier risks.
  • The system spots unusual patterns and flags them before they cause problems.

None of the statements above applies, and all of these do.

What changes
  • People focus on strategic oversight rather than day-to-day supervision.
  • Routine decisions are automated within agreed limits.
  • The system adjusts its own settings based on the results.
To distinguish this level from the next, ask
  • Which routine decisions happen without a person approving them, and who set the limits?

Ordering, routing, allocation and exception handling happen automatically.

What you see
  • Ordering, routing, allocation and exception handling happen automatically.
  • The supply chain improves its own performance within limits set by leadership.
The stage

Processes improve their own performance. People oversee strategy and exceptions only.

What changes
  • Routine decisions and exceptions are handled automatically, within limits set by leadership.
  • The system adjusts its own settings based on results and reports what it changed.

For the business Not every process needs this level. Named people remain responsible.

Next step A direction, not a current offer.

More detail on this level
What you see
  • People step in only for strategic decisions and situations not encountered before.
  • Ordering, routing, allocation and exception handling happen automatically.
  • The supply chain improves its own performance within limits set by leadership.

None of the statements above applies, and all of these do.

What changes
  • Routine decisions and exceptions are handled automatically, within limits set by leadership.
  • The system adjusts its own settings based on results and reports what it changed.
  • Named people remain responsible.

These are the changes usually seen. The result depends on where you start and the work that follows.

At any level Which work happens in your ERP system, and which still happens in Excel?

The red line shows the critical path at each level.

Not sure which level fits? The baseline assessment helps establish that.

The baseline assessment shows which level each function has reached and what to fix first.

See the baseline