Strategy and Network Design

Network Optimisation and Tool Selection: A Practitioner's View After Fifteen Years

I have spent fifteen years designing and redesigning supply chain networks, across retail, FMCG, manufacturing, infrastructure, and government, first inside large consulting and planning firms and now at Trace. In that time I have built a lot of models, sat in a lot of steering committees, and watched a lot of network studies either change a business or quietly gather dust. This is not a textbook explanation of supply chain network optimisation. It is a point of view about what separates the network work that lands from the network work that does not.

The headline of that view is simple: the optimisation engine is the least interesting part of the problem. I have seen excellent tools produce useless answers and modest tools produce decisions worth tens of millions, and the difference almost never came down to the solver. It came down to three things that get far less attention than they deserve. Whether the baseline was properly calibrated. Whether the modelling genuinely grappled with uncertainty rather than optimising to a single forecast. And whether the network decision was made together with inventory and ordering mechanics, or in isolation from them. Get those three right and the choice of tool becomes a secondary question. Get them wrong and no platform will save you. What follows is how I think about each, and where tool selection actually fits once the priorities are straight.

What supply chain network optimisation actually is, and why it so often disappoints

Supply chain network optimisation, also called network design, is the discipline of deciding the structural shape of your supply chain: how many distribution centres or plants you should have and where, which customers and regions each should serve, where inventory should sit across the network, and how product should flow from source to shelf. These decisions set the fixed footprint within which all your day-to-day planning then operates. They shape cost and service for years, which is why getting them right matters and why getting them wrong is so painful to unwind.

Network studies disappoint more often than almost any other kind of supply chain work, and I have learned to recognise the pattern early. A study kicks off with energy, a tool is licensed, a model is built at pace, and a sensible-sounding recommendation emerges, to consolidate from four sites to two, or to add a node in a growth region. The deck is polished and the savings are quantified to a suspiciously precise number. Then the recommendation goes nowhere, because when the business looks closely it does not quite trust it. The numbers do not reconcile with what finance sees. The inventory implications were waved through. The model assumed a single demand future everyone knows will not eventuate. So the boldest structural moves get deferred, and the business carries on with a footprint it has half-suspected is wrong for years.

When I unpick why these studies fail, it is almost never the mathematics. The optimisation techniques at the heart of network design are mature, and the commercial tools solve them perfectly well. The failures sit upstream and downstream of the solver: a baseline nobody calibrated, a refusal to model uncertainty honestly, a network question divorced from inventory, and an absence of the executive ownership needed to act on a structural change. The tool gets blamed, or credited, far more than it deserves. So before tools, I want to talk about the things that actually determine whether the work is worth doing.

It begins and ends with the baseline: the calibrated digital twin

If you take one thing from this article, take this. A network model is only as good as the baseline it is built on, and the most common and most expensive mistake I see is teams rushing past the baseline to get to the scenarios. Everything you build on top inherits the flaws underneath.

The baseline is what the industry now calls a digital twin: a model of your current network that reproduces, as faithfully as the data allows, how your supply chain behaves today. The major platforms lean on this language heavily, Coupa, for instance, markets a true digital twin of the extended supply chain, and the concept is sound. But a digital twin is only useful if it is calibrated, and calibration is the step that gets skimped. By calibration I mean tuning the model until it reproduces last year's reality, your actual costs, volumes, flows, and service, within an acceptable tolerance, before you trust it to tell you anything about the future. If the model cannot reproduce what already happened, it has no business forecasting what should happen next.

This is harder and less glamorous than it sounds, which is why it gets rushed. Calibrating a baseline means reconciling the model's freight cost against the freight you actually paid, lane by lane and mode by mode. It means handling and warehousing costs that reflect your real operations, not a generic rate card. It means demand that matches what you actually shipped, and lead times that reflect the variable real world rather than a single number copied from an ERP field. It means finding the awkward reconciling items: costs in the wrong cost centre, inter-site transfers nobody accounts for cleanly, peaks the annual average hides. The test I apply is blunt. Fed last year's demand, does the model reproduce last year's cost and service to within a few per cent? If not, I do not move on. An uncalibrated baseline is worse than no model, because it carries the false authority of precision. A rough spreadsheet invites scrutiny. A polished optimisation model that is quietly wrong gets believed.

The baseline also earns you the right to be believed. When I can show a CFO that our model reproduces their actuals, that it tells them what they already know to be true about last year, the scepticism drains out of the room and every number on top is easier to trust. Skip that step and the whole analysis fights an undertow of doubt. The baseline is not a chore to get through on the way to the scenarios. It is where most of the value, and almost all of the credibility, is won or lost.

Scenario modelling: the value is in the questions, not the solver

Once you have a baseline you trust, scenario modelling is where the value gets created, and the craft is almost entirely in the questions. The solver will optimise whatever you point it at. Whether the exercise is worth anything depends on whether you framed the right decisions.

The scenarios that matter are rarely just "what is the lowest-cost footprint." That is the question everyone asks first and usually the least interesting, because lowest cost in isolation is almost never what the business actually wants. The valuable scenarios explore the real decision space: at what point does consolidation start to break service for which customers; how does the optimal network change if the business grows thirty per cent, shifts toward e-commerce, or wins a major customer in a region you barely serve; what does the network need to look like if a key site is lost to a lease expiry or a disruption; how does an acquisition reshape the answer. A good scenario set brackets the genuinely consequential questions and the genuinely plausible futures, rather than running twenty minor variations to manufacture the appearance of rigour.

The discipline I hold to most firmly is to resist optimising to a single point. It is tempting to take the base-case forecast, optimise to it, and present the result as the answer. But a network tuned perfectly to one forecast is, by construction, fragile to every other forecast, and we know with certainty the single forecast is wrong. The right question is not "what is the optimal network for the expected future" but "what is the network that performs well across the range of futures we might face." That leads into the two techniques that separate serious network work from the rest: sensitivity testing and Monte Carlo analysis.

Sensitivity testing and Monte Carlo: designing for a range of futures

A network recommendation that has not been stress-tested against uncertainty is incomplete, however elegant the optimisation. Structural decisions are ones you live with for years, through conditions you cannot foresee, so the question is never just "is this optimal today" but "how robust is this to what will change."

Sensitivity testing is the simpler layer. It asks how the answer moves as you flex the inputs that matter: fuel and freight, demand volume and mix, labour and property costs, lead times. Its value is in showing which assumptions the recommendation actually hinges on. Sometimes the optimal footprint is stable across a wide range of fuel prices, so you can stop worrying about fuel and act with confidence. Other times the whole recommendation flips on a ten per cent freight movement, which is vital to know before you commit capital. I have seen recommendations that looked compelling at the base case fall apart under sensitivity testing, and I would far rather discover that in the model than two years into a property lease.

Monte Carlo analysis goes further, and for high-stakes decisions it is where the real robustness work happens. Rather than flexing one variable at a time, it runs the network across thousands of randomised scenarios, drawing each uncertain input from a probability distribution and aggregating the results to show the full range of outcomes a design produces. This reframes the decision. Instead of "design A saves two million in the base case," you get "design A saves between half a million and three million across the plausible range and never performs worse than the status quo," against "design B has a higher expected saving but a real tail risk of underperforming today if demand softens." That is a far richer basis for a structural decision, because it lets you choose a network for resilience, the one that performs well across most futures and protects you in the bad ones, rather than the one perfectly tuned to a future that will not arrive.

This matters more now than when I started, because the environment is less stable. McKinsey's research, widely cited across the industry, finds that supply chain disruptions lasting longer than a month now occur every 3.7 years on average and can cost businesses up to 45 per cent of a year's profit over a decade. When disruption on that scale is near-certain over the life of a network decision, designing to a single benign forecast is not optimism, it is negligence. A network designed with uncertainty built in is one you can defend to the board in three years when conditions have moved and the design still holds. deloitte

The decision is strategic enablement, not cost minimisation

A conviction that has only hardened with experience: the best network studies start with "what are we trying to enable," not "how do we save money." A network is the physical expression of a business strategy, and if you design it purely to minimise cost you will often design something that undermines what the business is trying to achieve.

The clearest way to see this is through the customer value proposition, because the network encodes it whether you intend it to or not. The trade-offs in network design, fewer larger sites against more smaller ones, central inventory against forward-positioned inventory, lowest cost against fastest delivery against greatest resilience, are not abstract parameters. They are decisions about what promise you make to which customers. Consolidating to two large distribution centres might be the lowest-cost answer, but if it breaks the next-day promise your best customers buy from you for, you have optimised your way out of your own value proposition. A more distributed, slightly more expensive network might be exactly right if speed and availability are how you win. There is no universal answer, because it depends on what the business is for and which customers matter most.

So I push hard, at the start of every engagement, to get the strategy and the value proposition on the table before we touch the model. Who are we serving, and what do they value: price, speed, availability, breadth, reliability? Which segments are we willing to serve differently? Where is the business heading, into which channels and regions? What is our appetite for resilience versus efficiency, knowing the two genuinely trade off and the last few years have repriced that trade-off for most boards? And where does sustainability sit, because network structure drives a large share of transport emissions, and more of the businesses I work with now treat carbon as a real constraint. Only once those are answered does optimising make sense, because they define what "optimal" means. I would rather spend a day arguing about the value proposition than a month optimising against a goal nobody has examined.

The point too many people miss: network and inventory cannot be decided apart

If the baseline is the thing teams most often skimp, this is the thing they most often get structurally wrong, and it is the most expensive class of error I encounter. Network decisions cannot be made in isolation from inventory and ordering mechanics, because they are not separate problems. They are the same problem at different time horizons, and treating them separately is how businesses arrive at footprints that look optimal on the network model and prove uneconomic in reality.

Here is why they are inseparable. Where you hold inventory is simultaneously a network decision and an inventory decision. The moment you add or remove a node, you change the inventory the network must carry, through the pooling effect: consolidating stock into fewer locations reduces total safety stock, because aggregated demand variability is proportionally smaller, while spreading stock across more forward locations increases it. This is not a second-order detail. The inventory consequence of a footprint change can be large enough to outweigh the transport and facility savings the network model was optimising for. I have seen studies recommend consolidating to fewer sites on transport and overhead savings, only for the move to collapse once someone modelled the inventory, because the forward-positioning the service promise required, combined with the suppliers' ordering constraints, wiped out the saving. The network model said yes. The inventory reality said no. Nobody had put the two in the same room.

Ordering mechanics compound this. Replenishment frequency, minimum order quantities, batch sizes, container and pallet rounding, and order policies all determine how product actually flows through the network and therefore what it truly costs to operate. A network optimised as if product flows in smooth, perfectly divisible streams will mislead you, because real product flows in lumps governed by ordering rules, and those lumps drive inventory, handling, and space. Multi-echelon inventory optimisation, which decides how much buffer to hold at each tier, is really the operational expression of a network design choice, and the two should share one model and one set of assumptions. I have written before, in our guide to supply chain planning for Australia and our work on demand, inventory, and replenishment, about how much value leaks at the seam between disciplines that should be joined. Nowhere is that seam more expensive than between network design and inventory.

The organisational version of this mistake is the one I see most. A strategy team runs the network study and hands over a footprint, while a separate planning team owns inventory on its own assumptions, and the two never reconcile. The result is either a recommendation that ignores its own inventory implications or, worse, a structural change built on transport savings that the inventory reality then undermines. My firm rule is that a network study that does not model the inventory and ordering consequences of each scenario is not finished, however polished the footprint analysis. The network question and the inventory question must be answered together, in one model, by people who are talking to each other. This single discipline, more than any tool or technique, is the difference between network work that holds up and network work that embarrasses everyone a year later.

Choosing the tool: what actually matters

Only now, with the priorities straight, do I come to tools, because this is the order in which they matter. The tool is the last and least of the decisions, and teams routinely over-invest in platform selection while under-investing in the baseline, the uncertainty modelling, and the network-inventory integration that actually determine success. The tool is not irrelevant, though, and the market has shifted enough recently to be worth understanding.

The criteria I care about, in order, are these. Can the tool support a properly calibrated baseline without taking months to stand up. Does it bring optimisation, simulation, and uncertainty analysis together, because a network you cannot stress-test is a network you cannot trust. Can it model inventory and ordering policy alongside network structure, in the same environment, so you avoid the hand-off that causes the most expensive errors. Can the people who will own it after the consultants leave actually use it. And can you re-run it as conditions change, treating network design as a living capability rather than a one-off project.

On the landscape, the picture in 2026 is genuinely in flux. For years the reference point was LLamasoft's Supply Chain Guru, which Coupa acquired in 2020 before Coupa itself was taken private by Thoma Bravo. That product is now sold as Coupa Supply Chain Design and Planning. It remains capable and proven on complex global networks, though the common view is that design investment has slowed under successive owners and the architecture is showing its age, with model construction still tied to the desktop. The most notable newer entrant is Optilogic's Cosmic Frog, built by former LLamasoft people as a cloud-native platform that combines optimisation, simulation, and risk in a single environment with a risk rating on every scenario. Alongside them sit AIMMS, with decades of pedigree in mathematical optimisation and what-if modelling, and anyLogistix, which is built on a simulation engine and is strong where dynamic, stochastic behaviour matters more than pure optimisation. Tellingly, the better modern platforms are converging on exactly the integration I have argued for: policy optimisation, which optimises reorder points and safety stock rules alongside network structure in the same model, is becoming a defining capability. The market is catching up to the idea that network and inventory belong together.

That is the case for GAINS, which is the platform we most often recommend at Trace and the one we have the deepest experience implementing. Its strength for this problem is integration. Network design sits inside a single platform that also runs demand forecasting, multi-echelon inventory optimisation, lead-time prediction, and replenishment, built around decision engineering and designed to overlay your existing systems rather than replace them. That is precisely what stops the network question and the inventory question being answered by two different tools on two sets of assumptions, which is the failure mode that does the most damage. GAINS added dedicated network design through its 2023 acquisition of 3 Tenets Optimization, and pairs it with a mature planning suite and an overlay architecture that keeps implementation cost and disruption low. For the businesses I work with, whose network decisions are inseparable from ongoing planning and inventory, that integration is the thing that matters most, and it is why GAINS is usually my recommendation. The right tool always depends on the problem in front of you, and you should choose it last, against the criteria above, not first against a slick demonstration.

Why network studies fail

To pull the threads together, here is the list I carry in my head, every item of which I have watched happen more than once.

They skip baseline calibration and build sophisticated scenarios on a foundation that cannot reproduce last year. They optimise to a single forecast and produce a network fragile to every future except the one that will not happen. They divorce the network decision from inventory and ordering mechanics, and recommend footprints the inventory reality makes uneconomic. They treat the study as a one-off rather than a living capability, so the model is obsolete within a year. They fall for tool-first thinking, investing in the platform while neglecting what actually matters. They design for cost rather than the customer value proposition, and optimise the business out of its own strategy. And they lack an executive owner and a real decision forum, so the analysis surfaces the right questions but the organisation never finds the resolve to act. Almost none of these are technical failures. They are failures of discipline, framing, and organisation, which is why I spend so little energy on the solver and so much on everything around it.

How Trace Consultants can help

At Trace Consultants, this is core ground for us, and we approach network work the way I have described it, because it is the way it actually pays off.

We build network models on baselines we have genuinely calibrated. Through our strategy and network design work, we stand up a digital twin that reproduces your actual costs, flows, and service, and we earn the right to be believed before modelling a single scenario.

We model the network and the inventory together, never apart. We bring the footprint question and the inventory and replenishment question into one model with one set of assumptions, drawing on our planning and operations capability and our multi-echelon inventory work, so the recommendation holds up against the inventory reality rather than collapsing under it.

We design for uncertainty and for your strategy. We stress-test recommendations with sensitivity and Monte Carlo analysis so the network you choose is robust across the futures you might face, and we anchor the work to your customer value proposition and growth strategy, so we optimise toward what the business is actually for.

We help you choose and implement the right tools, on the right criteria. We select for the ability to calibrate, to model uncertainty, and above all to optimise network and inventory together as a living capability. The platform we most often recommend and have the deepest experience with is GAINS, for the integration reasons above, and our view on technology sits on our technology page. Because the realities differ by sector, we bring practitioners who have done this work in your industry, whether retail or FMCG and manufacturing.

Explore our Strategy and Network Design services →

Speak to an expert at Trace →

Where to begin

If you are contemplating a network study, interrogate two things before you engage anyone or license anything. First, ask whether you can build, or have built, a baseline that genuinely reproduces your current cost and service, because if you cannot, that is the first piece of work and everything else waits behind it. Second, ask whether your network conversation and your inventory conversation are happening in the same room, with the same people and assumptions, or running on separate tracks. If they are separate, fix that before you optimise anything, because the most expensive network mistakes live in that gap.

From there the sequence is straightforward. Calibrate the baseline until you believe it. Frame the scenarios around the strategic decisions and plausible futures that matter, not a single forecast. Stress-test with sensitivity and Monte Carlo so you are choosing a resilient network rather than a fragile one. Model the inventory and ordering consequences of every option alongside the footprint. Anchor the whole thing to your customer value proposition. And choose your tool last, with a clear preference for one that keeps network and inventory together. Do that, and the recommendation will be one your board can act on with confidence.

The bottom line

If I had to compress fifteen years into a sentence, it would be this: the network is the easy part to model and the hard part to get right, and the difference is almost never the software. It is the rigour of the baseline, the honesty with which you treat uncertainty, the refusal to separate the network from the inventory and ordering mechanics that determine its real cost, and the discipline to design toward what the business is for rather than the lowest number on a slide. The tools keep improving, but they remain instruments. They amplify the quality of the thinking around them; they do not substitute for it.

The businesses that get extraordinary value from network optimisation treat it as a strategic, ongoing capability, built on foundations they trust, integrated with their planning, and owned by people senior enough to act on what it reveals. The ones that are disappointed bought a tool and hoped it would do the thinking for them. The footprint of your supply chain shapes your cost and service for years. Design it with more rigour than a single forecast and more honesty than a cost-cutting exercise, and the tool you choose to support it will be the smallest of your worries.

If you are weighing a change to your network, Trace can help you build the baseline, model it properly, and make a structural decision that holds up.

Explore our Strategy and Network Design services →

Speak to an expert at Trace →

Frequently asked questions

What is supply chain network optimisation?

Supply chain network optimisation, or network design, is the discipline of deciding the structural shape of a supply chain: how many facilities to operate and where, which customers or regions each should serve, where to hold inventory, and how product should flow from source to customer. These decisions set the fixed footprint within which all day-to-day planning operates, and they shape cost and service for years, which is why they are made using optimisation, scenario modelling, and simulation rather than judgement alone.

What is a digital twin in network design, and why does calibration matter?

A digital twin here is a model of your current network that reproduces how it behaves today in cost, flow, and service terms. Calibration is the discipline of tuning that model until it reproduces last year's real costs and service within tolerance before you trust it to evaluate future scenarios. It matters because every scenario builds on the baseline, so an uncalibrated baseline produces unreliable answers that carry the false authority of a precise model, which is more dangerous than an obviously rough estimate.

Why can't network and inventory decisions be made separately?

Because they are the same problem at different horizons. Where you hold inventory is both a network and an inventory decision, and changing the footprint changes the inventory the network must carry through the pooling effect, where consolidating stock reduces total safety stock and dispersing it increases stock. That consequence can be large enough to outweigh the transport and facility savings a network study optimises for, so a footprint chosen without modelling its inventory and ordering implications can look optimal on the model yet prove uneconomic in practice.

What is the role of Monte Carlo analysis in network design?

Monte Carlo analysis runs a network design across thousands of randomised scenarios, drawing uncertain inputs such as demand, costs, and lead times from probability distributions rather than fixed values, to reveal the full range of outcomes a design produces. It lets you choose a network for robustness, one that performs well across most plausible futures and protects you in adverse ones, rather than one tuned to a single forecast. Given how frequently major disruptions now occur, designing with uncertainty built in has become essential.

How should I choose a network design tool?

Choose it last, after you have settled the baseline, the uncertainty modelling, and the network-inventory integration, and select on criteria that matter: speed to a calibrated baseline, optimisation and simulation and risk in one place, the ability to model inventory and ordering policy alongside network structure, usability for the team who will own it, and the ability to re-run it as a living capability. The 2026 landscape includes Coupa Supply Chain Design and Planning, the cloud-native Optilogic Cosmic Frog, AIMMS, anyLogistix, and GAINS. For businesses whose network decisions are inseparable from ongoing planning and inventory, an integrated platform such as GAINS, which optimises network and inventory together, is the strongest fit.

Related reading: Supply Chain Planning: A Guide for Australia · Demand, Inventory & Replenishment: Competitive Advantage · How Advanced Planning Systems Transform Supply Chain Planning · S&OP That Actually Works in Australia

‍

How to Build a Supply Chain Business Case That Gets Approved

Most supply chain investments do not fail because the idea was wrong. They fail because the business case never cleared the room. The warehouse automation that would have paid for itself in three years, the network redesign that would have stripped millions out of freight, the planning system that would have lifted forecast accuracy: plenty of these die not at the operational level but on a finance director's desk, marked up with the words "needs more detail" or "the numbers don't stack up."

A supply chain business case is the document that translates an operational opportunity into a financial decision the board can say yes to. It is not a project plan, a vendor pitch, or a wish list. It is an argument, built on evidence, that puts a defensible number against a problem and shows how spending capital today produces a better outcome than doing nothing. Get it right and you unlock funding, momentum, and the mandate to deliver. Get it wrong and the best idea in the business sits in a drawer for another budget cycle.

This guide is for Australian operations, supply chain, procurement, and finance leaders who need to take an investment to an executive committee or board and have it approved. It covers what a strong case contains, why so many of them get sent back, and how to build one that survives scrutiny and then actually delivers the value it promised.

Why supply chain business cases get rejected

Before building a case, it helps to understand why they fail, because the failure patterns are remarkably consistent. Industry research on capital proposals suggests a large share, by some estimates around 40 percent, never secure approval, and very often the underlying project had genuine merit. The case simply did not make a compelling argument to the people holding the cheque book.

The recurring failure modes are worth naming directly. Optimistic benefit projections with no evidence behind them. Incomplete cost accounting that hides the true investment, then blows the budget mid-delivery. Missing risk analysis that pretends the path to value is smooth. Weak strategic alignment that never connects the project to what the organisation is actually trying to achieve. And the quietest killer of all: no credible explanation of how a number on a slide becomes cash in the bank.

There is also a more uncomfortable pattern, sometimes called strategic misrepresentation, where costs get understated to improve the benefit-cost ratio and slip the project under an approval threshold. It works in the short term and creates a budget crisis later. Boards that have been burnt this way become sceptical of every case that follows, which makes life harder for the next person with a genuinely good proposal.

The lesson runs through everything below. A business case is not approved because it is long, polished, or full of charts. It is approved because the decision is clear, the logic is defensible, and the path from approval to realised value is credible.

What a strong supply chain business case actually contains

A good case answers a small number of questions in an order a busy executive can follow. Strip away the formatting and the structure is always the same.

The problem, stated plainly. What is the issue, how big is it, and what does it cost the business to leave it unsolved? This is the "cost of doing nothing," and it is the single most persuasive element of most cases. If your distribution network is adding two days to lead times and bleeding service penalties, quantify that. If fragmented procurement is leaving spend unmanaged across dozens of suppliers, size it. Executives fund problems they can see and measure, not solutions in search of a justification.

The strategic link. Every dollar of capital competes with every other dollar. A supply chain case that connects to a board-level priority, whether that is growth, margin recovery, resilience, customer service, or a sustainability commitment, will always beat one framed purely as an operational tidy-up. If the organisation is chasing growth, show how the current network constrains it. If the pressure is on margin, lead with cost-to-serve.

The options, not just the answer. Both the NSW Treasury Business Case Guidelines and the Commonwealth Department of Finance investment frameworks require an options analysis for a reason: it proves you considered alternatives rather than reverse-engineering a justification for a decision you had already made. A credible case sets out a realistic longlist, narrows it to a shortlist, and includes the base case of doing nothing or doing the minimum. Boards trust a recommendation far more when they can see what it was chosen over.

The numbers, built honestly. This is the financial heart of the case. Costs and benefits over time, expressed as ranges rather than false precision, with the assumptions visible. A net present value, a payback period, and an internal rate of return where they apply. Critically, the costs must be complete: not just the capital outlay but implementation, change management, system integration, training, and ongoing operating costs. The benefits must be the kind you can actually bank, not theoretical efficiencies that never reach the P&L.

The risks and how they are managed. Generic risk registers get cases sent back. What executives want are the decision-relevant risks: delivery risk, adoption risk, the chance benefits do not materialise, cost escalation, and how each is owned and mitigated. A case that names its own weaknesses is more trusted than one that pretends there are none.

The delivery and benefits-realisation plan. The most common reason a financially sound case still gets returned is the absence of a credible path to implementation. Milestones, resourcing, dependencies, decision gates, and most importantly, how the promised benefits will be tracked and who is accountable for them after the project closes. A business case is not a one-time approval exercise. It should become the live instrument against which the investment is measured for years.

Quantifying the benefits without overselling

The benefits section is where most cases either earn credibility or lose it. The temptation is to inflate. A spreadsheet full of optimistic savings assumptions is rarely persuasive, because experienced finance leaders have seen the gap between projected and realised value too many times to take it on faith.

The discipline is to separate benefits into tiers. Hard, bankable savings come first: freight reduction from network redesign, inventory release from better planning, labour productivity from process change, contract savings from supplier rationalisation. These hit the P&L or balance sheet and can be tracked. Soft benefits come second: improved service, reduced risk, better data, greater agility. They are real but harder to bank, so they support the case rather than carry it.

The single most powerful technique is to model in scenarios rather than point estimates. Present a conservative, base, and upside case. The conservative case should still clear the hurdle rate. If your investment only works in the upside scenario, you do not have a business case, you have a hope. Showing that the numbers hold even when you are pessimistic does more to build confidence than any amount of optimism.

Tie every benefit to a mechanism. Do not claim a 15 percent inventory reduction; explain that it comes from a specific lift in forecast accuracy, applied to a specific portion of the portfolio, releasing a specific amount of working capital. The path from insight to action to outcome must be visible. When a board can see how value becomes real, they fund it.

Getting the costs right

Underestimating cost is the fastest way to destroy credibility, both at approval and during delivery. A complete cost picture covers the full life of the investment, not just the capital line.

For a supply chain investment, that typically means the capital cost itself, implementation and integration, change management and training, any transition or dual-running costs while the old and new state coexist, and the ongoing operating cost once the solution is live. A new warehouse management system is not just the licence; it is the integration with your ERP and TMS, the process redesign, the training of every user, and the support cost that recurs forever after.

Contingency belongs in the case, visibly. Leaving it out to make the numbers look better is a false economy that catches up with you the moment the first unforeseen complexity appears. A case that includes a sensible contingency and explains it is more credible, not less, because it signals that the author understands how projects really behave.

Tailoring the case to the decision and the audience

Not every investment needs the same weight of analysis, and pretending otherwise wastes everyone's time. The Australian government frameworks build this in deliberately: the level of detail required is proportionate to the size and risk of the proposal. A minor process improvement does not warrant a hundred-page case; a multi-million dollar network transformation does. Match the rigour to the scale of the decision.

Audience matters just as much as size. A CFO reads a business case differently from a COO or a board. The CFO wants defensible numbers, complete costs, and a clear view of risk to capital. The COO wants confidence the thing can actually be delivered without breaking operations. The board wants the strategic logic and the headline decision. A strong case serves all three without burying any of them, usually through a tight executive summary that states the decision and the recommendation up front, with the supporting detail behind it for those who want to interrogate it.

Lead with the recommendation. Executives assess cases quickly and they look first for the clarity of the decision, the strength of the evidence, and the credibility of delivery. Making them hunt for the ask across thirty slides is how good ideas lose momentum.

Turning the business case into a live tool

The work does not end at approval. The most valuable thing a business case can become is the standard the investment is held to over its life. The benefits projected at appraisal should be tracked through delivery and measured at closure. Too often the original projections are quietly forgotten the moment funding is secured, and nobody ever checks whether the value showed up.

This is where benefits-realisation discipline separates organisations that consistently get a return on capital from those that do not. Define the benefits precisely, assign ownership, set the cadence for measurement, and keep the case alive as a steering instrument rather than filing it away. It protects the integrity of every future case too, because a track record of delivering what you promised is the most persuasive evidence you can bring to the next ask.

How Trace Consultants can help

At Trace Consultants, we build supply chain business cases that get funded and then deliver. As a senior-led Australian advisory firm, the people who build your case are experienced practitioners who have sat on both sides of the table, not junior analysts working from a template. That matters when the case has to survive a sceptical CFO or a board that has seen optimistic numbers before.

We quantify the opportunity with your own data. We build the analysis from your ERP, WMS, TMS, and financial systems, structured to your specific cost pools and operational drivers. Whether the opportunity is in network design, cost-to-serve, inventory, or procurement, we size it with evidence rather than assumption, so the benefits in your case are ones you can actually bank. Explore our Strategy & Network Design capability for how we approach this.

We model the financials in scenarios that hold up. Conservative, base, and upside cases with the assumptions visible, complete cost accounting across the full life of the investment, and a clear view of payback and return. The kind of analysis that earns credibility in the finance review rather than losing it.

We connect the case to delivery. A business case is only as good as the value it realises, so we build the implementation and benefits-realisation logic into the case from the start. Our Planning & Operations and Procurement teams have delivered the kinds of programmes your case will need to stand behind, from forecasting and inventory through to supplier rationalisation and contract consolidation.

We bring resilience and risk into the frame. A modern supply chain case has to account for disruption and risk, not just steady-state efficiency. Our Resilience & Risk Management work helps ensure the case reflects the real operating environment rather than an idealised one.

For larger physical investments, our Warehousing & Distribution practice covers the operational design and costing that underpins a credible facility or automation case. And our wider approach to client work is built on senior delivery, solution-agnostic advice, and a standard of returning many times the value of our fees.

Explore our Strategy & Network Design capability →

Speak to an expert at Trace →

Where to begin

If you have an investment you believe in but no approved case behind it, start with the problem, not the solution. Quantify the cost of doing nothing using the data you already have. That single number, more than any vendor demo or efficiency claim, is what opens the conversation with finance.

From there, set out your realistic options including the base case, model the financials conservatively before you model them optimistically, account for every cost across the full life of the investment, and build the delivery and benefits-tracking logic in from the start rather than bolting it on. Tailor the depth to the scale of the decision, lead with your recommendation, and be honest about the risks. A case built this way does not just get approved. It gives you the mandate, the resources, and the accountability framework to deliver the value you promised, which is the only outcome that actually matters.

The difference between a good supply chain idea and a funded one is rarely the idea. It is the case behind it.

‍

‍

What Is Cost-to-Serve?

Cost-to-serve (CTS) is the total cost of getting a product from your distribution network into the hands of a specific customer, through a specific channel, at a specific service level.

It sounds straightforward. In practice, most Australian businesses have never calculated it — and the ones that have are often surprised by what they find.

The standard formula aggregates costs across the full fulfilment chain: inbound freight, warehousing (receiving, storage, pick-and-pack), outbound transport, customer service, returns handling, and any channel-specific compliance costs such as retailer DIFOT penalties or promotional execution. Divide that total by volume — per case, per pallet, per order — and you have a cost-to-serve figure you can compare across customers, channels, channels, SKUs, and regions.

The insight that makes CTS powerful is this: your gross margin on a product tells you very little about whether you're actually making money on it. A customer buying at full price but demanding daily small-order drops, bespoke labelling, extended payment terms, and high return volumes can easily cost more to serve than the margin they generate. A customer on a discount but ordering full pallets, paying on time, and never claiming can be one of your most profitable accounts.

Without CTS visibility, you're flying blind on profitability — and most pricing, ranging, and service-level decisions are effectively guesswork.

Why Cost-to-Serve Matters More Now

Margin pressure in Australian retail and distribution has intensified sharply over the past three years. Input cost inflation, labour cost increases, fuel surcharges, and the structural shift toward e-commerce have all pushed up the cost side of the equation. At the same time, major retail customers have continued to demand faster replenishment cycles, higher service levels, and more promotional and compliance activity from their suppliers.

The result is a hidden profitability problem. Businesses that were marginally profitable on their full customer and SKU mix in 2021 may be loss-making on significant portions of that mix today — without it showing up in their headline P&L.

Several specific dynamics are accelerating this in Australia:

Omnichannel fulfilment complexity. Retailers are increasingly requiring suppliers to support multiple fulfilment modes simultaneously — bulk DC delivery, direct-to-store, click-and-collect top-up, and e-commerce pick. Each mode has a different cost profile. Suppliers who haven't modelled the cost difference between a full pallet DC replenishment and a store-by-store eaches delivery are systematically mispricing their service commitments.

Geographic dispersion. Australia's population spread creates legitimate cost-to-serve variation that is not always captured in standard pricing structures. Serving a customer in Perth or Darwin from an east coast DC has a materially different transport cost profile to serving the same customer from Sydney to Melbourne. Regional and remote service commitments made without CTS modelling frequently turn out to be loss-making.

Retailer compliance regimes. Major grocery and hardware retailers have tightened DIFOT requirements and compliance penalty frameworks over the past several years. Suppliers who absorb these penalties without attributing them to specific customer CTS models are distorting their profitability picture.

SKU proliferation. The range expansion that occurred through COVID — safety stock build, innovation acceleration, channel-specific variants — has left many suppliers carrying a long tail of SKUs that are expensive to warehouse, slow-moving, and ordered in small quantities. The true cost of maintaining these SKUs in the range is rarely visible in standard reporting.

The Whale Curve: Why the Top Line Lies

One of the most useful outputs of a cost-to-serve analysis is the profitability waterfall — sometimes called the whale curve.

The whale curve plots customers (or SKUs, or channels) ranked from most to least profitable, showing cumulative profit contribution. In most businesses, the shape is consistent: the top 20–30% of customers generate 150–200% of total profit. The middle tier is roughly break-even. The bottom 20–30% destroys 50–100% of the profit generated at the top.

The headline business is profitable. The CTS breakdown shows that a significant portion of that profit is being destroyed by customers, channels, or SKUs that cost more to serve than they contribute.

This pattern repeats across industries. In Australian consumer goods distribution, it is common to find that 20–30% of products show margin erosion before they've even been delivered — driven by inbound costs, warehousing complexity, and order profile inefficiency. In retail distribution, small-format independent accounts, long-tail SKUs, and promotional compliance activities are the most common culprits.

The whale curve is not an argument for firing your bottom-tier customers. It is an argument for understanding what's driving their cost to serve — and making conscious, informed decisions about whether to fix it, reprice it, or exit.

What Drives High Cost-to-Serve

Before you can reduce CTS, you need to understand what drives it. The major cost levers in Australian retail and distribution are:

Order Pattern and Order Size

Small, frequent orders are the single biggest CTS driver in most distribution businesses. Every order triggers a fixed transaction cost — order processing, pick labour, despatch documentation, transport — regardless of the number of cases involved. A customer who orders twice weekly in small drops costs structurally more to serve than a customer who orders fortnightly in full pallet quantities.

The economics here are stark. In a typical pick-and-pack operation, the fixed cost per order often exceeds the variable cost per case for small orders. A three-case order can cost as much to process as a 30-case order in transaction terms.

Transport Mode and Delivery Distance

Outbound freight is typically the largest single component of CTS for high-frequency retail replenishment. The cost difference between a full truckload (FTL) delivery, a less-than-truckload (LTL) consolidation, and a courier parcel is not linear — it's exponential on a per-unit basis.

Australian geographic realities amplify this. Delivering to regional WA, rural NSW, or remote QLD from an east coast DC often makes accounts structurally uneconomical at current pricing — a problem that becomes visible only when transport costs are attributed to individual customers rather than pooled.

Warehousing Complexity

SKUs that are slow-moving, require special handling, have short shelf lives, or are stored in non-standard locations carry a higher warehousing CTS than fast-moving, shelf-stable lines in standard racking. If your CTS model pools warehousing costs across all SKUs equally, you're subsidising your complex lines with your simple ones.

Pick path complexity also matters. An order that requires picks across multiple zones, multiple temperature environments, or multiple storage systems (ambient, chilled, frozen, hazmat) costs more to fulfil than a single-zone order of equivalent case count.

Returns and Reverse Logistics

Returns are consistently undercosted in standard P&L reporting. The true cost of a return includes inbound freight, receival labour, quality assessment, repackaging, restocking or disposal — and in many cases, the customer service and credit administration overhead. For categories with high return rates (grocery promotions, seasonal apparel, consumer electronics), returns can add 3–8% to the effective CTS.

Compliance and Promotional Requirements

Retailer-specific labelling, ticketing, promotional setup, and compliance documentation add cost that standard margin reporting typically ignores. Bespoke EDI integration, retailer-specific carton labelling, and promotional execution requirements are real costs — but they're often absorbed in overheads rather than attributed to the customers that drive them.

Customer Service and Account Management Overhead

High-touch accounts that require frequent contact, complex queries, dispute resolution, or intensive account management carry a CTS that pure logistics models don't capture. In B2B distribution, the cost of servicing a high-maintenance $500K account can exceed the cost of managing a low-touch $2M account.

How to Build a Cost-to-Serve Model

CTS analysis doesn't require a six-figure software investment. Most businesses can build a working model using their existing ERP data, a structured activity-based costing approach, and a reasonably detailed understanding of their operational cost pools.

Step 1: Define the Unit of Analysis

Decide what you're measuring CTS at. Common choices are: per customer, per channel, per SKU, per order, or per delivery zone. Most useful CTS models are multi-dimensional — capable of slicing by customer AND channel AND SKU simultaneously.

Step 2: Map Your Cost Pools

Identify the major cost categories that sit between the factory gate (or supplier) and the customer. Typical cost pools for a retail distribution business include:

• Inbound freight and receival
• Warehousing (storage, pick-and-pack, despatch)
• Outbound freight (primary transport, last-mile)
• Returns and reverse logistics
• Order management and customer service
• Compliance and promotional execution
• Account management overhead

Step 3: Define Cost Drivers for Each Pool

For each cost pool, identify the activity driver — the operational event that causes costs to be incurred. Warehousing costs are driven by picks, pallets, and storage days. Outbound freight costs are driven by weight, cubic volume, zone, and frequency. Order management costs are driven by order count and line count.

This is the activity-based costing (ABC) step. It's the most analytically intensive part of the model — but it's also where the insight lives. Pooling costs without activity drivers produces averages that obscure the actual variation.

Step 4: Attribute Costs to Customers, Channels, and SKUs

Once you have cost pools and cost drivers, you can attribute costs to individual customers based on their actual consumption of each activity. A customer who placed 104 small orders last year at an average of 3 cases per order gets a very different CTS attribution than a customer who placed 12 orders at an average of 60 cases.

Step 5: Build the Waterfall and Whale Curve

Plot gross margin minus CTS for each customer (or SKU, or channel) to produce a net contribution figure. Sort and chart. The whale curve will show you the profitability distribution across your portfolio — and the outliers that warrant immediate attention.

Step 6: Validate and Sense-Check

CTS models are only as good as their inputs. Before acting on the output, validate against operational intuition. If the model says your largest customer is loss-making, check the assumptions. If it says your most demanding small customer is profitable, check whether all their compliance costs have been captured.

How to Reduce Cost-to-Serve: Seven Levers

Once you've built the model and identified where cost is being generated, there are seven primary levers for reduction.

1. Order Consolidation and Minimum Order Incentives

The fastest lever for most businesses is reducing order frequency and increasing order size. Minimum order quantities (MOQs), minimum order values (MOVs), or frequency-based pricing (lower per-case cost for less frequent, larger orders) all shift the order profile toward better CTS economics.

This doesn't require unilateral customer mandates. Many customers will voluntarily adjust their ordering patterns when the economic trade-off is made transparent — particularly if the cost saving can be shared in the form of a price incentive.

2. Route and Zone Optimisation

A systematic review of transport routing and zone structure can yield 10–20% freight cost reduction without service level compromise. This includes: zone skipping (bypassing intermediate DCs for high-volume lanes), milk run consolidation (combining multiple small-drop customers on a single run), and carrier mix optimisation (matching carrier selection to shipment profile rather than applying a single carrier blanket rate).

3. SKU Rationalisation

CTS analysis typically reveals a long tail of SKUs that are slow-moving, expensive to warehouse, ordered infrequently, and generate negative contribution after costs. A disciplined SKU rationalisation programme — informed by CTS data rather than just sales velocity — can reduce warehousing complexity, improve pick efficiency, and free up working capital.

The threshold for rationalisation should be explicit: SKUs below a CTS-adjusted contribution floor, with no strategic reason for retention (ranging requirements, range defence, anchor product), are candidates for deletion.

4. Channel-Specific Pricing and Service Tiers

If different channels (wholesale, direct-to-store, e-commerce, export) have materially different cost-to-serve profiles, that difference should be reflected in pricing or service-level structures. Charging the same price for a full DC pallet and a single-unit ecommerce pick is a structural mispricing problem.

Service tier design — defining explicit service levels (frequency, lead time, minimum order, compliance requirements) and pricing them accordingly — is one of the most effective structural tools for CTS management. Customers who want high-frequency, small-drop, bespoke service pay for it. Customers who consolidate and standardise benefit from a lower cost base.

5. DC Network Optimisation

For businesses with multiple distribution points, CTS analysis often reveals that the DC network is not optimally positioned relative to the customer base. A DC located to minimise inbound freight may be suboptimal for outbound last-mile costs. Adding a spoke location, repositioning inventory closer to high-density customer clusters, or shifting to a cross-dock model for certain customer segments can each reduce outbound CTS materially.

This is a longer-term lever — DC network changes involve lease commitments, capex, and operational transitions — but CTS modelling provides the business case rigour to make the decision with confidence.

6. Returns Rate Reduction

Reducing return rates directly reduces CTS. The primary levers are: improving order accuracy (the right product, right quantity, right condition), reducing promotional over-ordering (better promotional forecasting and agreement on sell-through responsibility), and improving packaging quality (reducing transit damage returns).

Where returns are unavoidable, streamlining the reverse logistics process — consolidated return pickups, automated credit processing, rapid quality assessment and restocking — reduces the per-unit cost of handling them.

7. Customer Collaboration

For strategically important customers with high CTS, a collaborative approach often yields better outcomes than unilateral repricing. Sharing CTS data with the customer — showing them what their ordering patterns, compliance requirements, and return rates are costing — enables joint problem-solving.

Many major retailers and FMCG customers have incentive to participate in CTS reduction programmes because the savings flow both ways. A supplier who reduces their CTS can pass some of the saving through in pricing; a retailer who adjusts their ordering behaviour reduces their own receiving and processing costs. The model that works is explicit: savings are identified jointly, and the split is agreed in advance.

Australian-Specific Considerations

Several features of the Australian market shape how CTS plays out in practice.

Retail concentration. Two grocery majors account for around 65% of Australian grocery sales. For FMCG suppliers, these accounts are non-negotiable to serve — but they are also the accounts most likely to have high compliance costs, tight DIFOT requirements, and intensive promotional activity. Managing CTS on these accounts is about optimisation rather than exit: how do you structure the relationship to minimise avoidable costs while maintaining the ranging and promotional position you need?

Independent and foodservice channels. The independent grocery, foodservice, and convenience channels in Australia involve high delivery frequency, geographic fragmentation, and significant account management overhead. CTS analysis on these channels frequently reveals that the segment as a whole is marginal — but within it, there are clusters of accounts with strong fundamentals and clusters with genuinely negative economics. The insight from CTS modelling allows selective focus rather than blanket withdrawal.

3PL relationships. Many Australian mid-market businesses operate through third-party logistics providers. CTS modelling in a 3PL environment requires integrating the 3PL's cost data — typically through open-book arrangements or detailed activity reporting — into the CTS model. Businesses that rely on 3PL summary invoices without activity-level detail are almost certainly missing significant CTS insight.

E-commerce growth. The continued growth of e-commerce in Australian retail has created CTS complexity that most traditional FMCG and retail distribution businesses are still working through. The per-unit cost of fulfilling an e-commerce order from a warehouse designed for pallet-level replenishment is typically 4–8x the per-unit cost of a DC-to-DC pallet move. Without explicit CTS modelling of the e-commerce channel, these costs are absorbed in the blended rate — and the e-commerce P&L is systematically overstated.

Common Mistakes in CTS Programmes

Building the model but not acting on it. CTS analysis is intellectually satisfying. It's also easy to use as a reason to keep analysing rather than making hard decisions. The businesses that extract value from CTS work are the ones that set a clear decision framework before they start — and commit to acting on the output.

Treating CTS as a one-time exercise. CTS changes as your business changes. Customer ordering patterns shift. Transport costs move. SKU mix evolves. A CTS model that was accurate two years ago may be materially wrong today. The businesses that get sustained value from CTS have embedded it as an ongoing operational metric — not a project.

Pooling costs too broadly. A CTS model that allocates warehousing costs equally across all SKUs, or splits transport costs evenly across all customers in a zone, will produce averages that obscure the variance. The whole point of CTS is to surface that variance. If your model produces a tight, normally distributed result across your customer base, the model probably isn't granular enough.

Failing to include all cost pools. The most commonly missed cost pools in Australian CTS models are: promotional execution labour, customer-specific compliance costs, EDI and systems integration costs, and customer service overhead. Omitting these systematically understates the CTS of your most demanding accounts.

Using CTS to justify price increases without a conversation. Informing a major customer that you're repricing because your CTS analysis shows they're unprofitable is a relationship risk. The more effective approach is to lead with the data, propose a joint problem-solving process, and frame repricing as a last resort rather than a first move.

How Trace Consultants Can Help

Cost-to-serve analysis is one of the highest-ROI supply chain engagements available to Australian retailers and distributors — but only if the model is built with sufficient rigour, validated against operational reality, and connected to a clear decision and implementation framework.

Trace Consultants works with retailers, FMCG businesses, and distributors to design and execute CTS programmes from the ground up. Our work typically spans three phases:

Diagnostic. We build the CTS model using your ERP, WMS, TMS, and financial data — structured to your specific cost pools and operational drivers. We produce the whale curve, identify the high-CTS segments, and quantify the opportunity.

Strategy. We work with your commercial and operations teams to design the response: which levers to pull, in what sequence, with what customer engagement approach. We model the financial impact of each lever under conservative, base, and upside assumptions.

Implementation. We support execution — whether that's carrier renegotiation, SKU rationalisation, service tier redesign, or DC network review — and establish the ongoing CTS reporting framework so the improvement is sustained.

Typical outcomes from Trace CTS engagements range from 10–25% reduction in cost-to-serve for target customer and SKU segments, with payback periods of six to eighteen months depending on the lever mix and business scale.

If your business is feeling margin pressure but can't identify where it's coming from — or if you suspect your pricing and service model hasn't kept pace with your cost structure — a CTS diagnostic is a logical starting point.

Explore our Warehousing & Distribution services →
Talk to our supply chain team →

Trace Consultants is an Australian supply chain and operations consultancy with offices in Sydney, Melbourne, Brisbane, and Canberra. We work with retailers, FMCG businesses, distributors, and government clients to improve supply chain performance, reduce cost, and build operational resilience.

‍Learn more about our work →