Skip to content
Shyenova

Supply Chain & Analytics

Network Design

Most networks are the fossil record of old decisions. Ours is a model you can re-run.

A distribution footprint is rarely designed. It accumulates. A warehouse opens because a large customer asked for it, a plant stays because closing it is politically expensive, a lane persists because nobody has re-tendered it since the contract was signed. Five years later the network is a set of answers to questions nobody is asking any more.

Network design is the highest-leverage structural decision in a supply chain because it fixes the cost floor for everything downstream. No amount of freight negotiation recovers the cost of a badly placed distribution centre. We treat it as an optimisation problem with a defensible objective function, not as a site-selection beauty contest.

How the work runs

Four phases, and what comes out of each.

Durations are indicative and assume reasonable data availability. Where data is poor we say so in the first fortnight rather than modelling on sand.
01

2–3 weeks

Baseline the network you actually have

Before modelling anything we reconstruct the current network from transactional data, every shipment, lane, rate and storage cost for a full seasonal cycle. This almost always surfaces facts that contradict the internal narrative: lanes running at a fraction of assumed utilisation, customers being served from the third-nearest node, cross-flows that exist only because of an old allocation rule.

Outputs

  • Flow map of every origin–destination pair by volume and cost
  • Cost-to-serve by customer, channel and SKU family
  • Reconciliation of modelled baseline against the general ledger
02

3–4 weeks

Build the optimisation model

We build a mixed-integer model of the candidate network: sites that could open, sites that could close, capacity steps, transport modes, and the service constraints that genuinely bind. The discipline here is in the constraints. A model that can produce any answer produces no answer. We spend most of this phase agreeing what is actually fixed and what is genuinely open.

Outputs

  • Candidate site universe with capacity and cost curves
  • Calibrated transport rate structure by mode and lane
  • Model validated against the baseline within an agreed tolerance
03

2–3 weeks

Run the scenarios that matter

Single-point answers are fragile. We run the network against demand growth cases, fuel and rate shocks, service-level tightening, and the loss of any single node. The output is not one recommended network but a map of which decisions are robust across every scenario and which only work under a specific forecast. Those are the ones that need a hedge, not a commitment.

Outputs

  • Scenario matrix with cost, service and carbon outcomes
  • Robustness ranking of each structural decision
  • Breakeven analysis for every proposed open or close
04

2 weeks

Sequence the transition

The optimal network and the path to it are different problems. Moving inventory, transferring licences, running parallel operations and re-papering customer service agreements all consume cash and attention. We build the migration sequence, quantify the transition cost honestly, and identify the point at which the change becomes cash-positive.

Outputs

  • Phased migration plan with dependencies
  • Transition cost and cash-flow profile
  • Risk register with mitigations per phase

What good looks like

The ranges we design toward.

These are the improvement ranges these levers are known to produce where the underlying practice has not been examined recently. They are targets to test against your baseline, not promises.

8–15%

Total landed cost

Typical reduction range when a footprint has not been re-optimised in five or more years.

20–35%

Lanes eliminated

Cross-flows and redundant lanes routinely found once true origin–destination data is reconstructed.

1–2 days

Order-to-delivery

Service improvement typically available at neutral cost purely from better node placement.

Deliverables

What you are left holding.

All of it handed over, documented, and with a session for whoever inherits it.
  1. 01A working optimisation model, handed over with documentation and a training session, not a black box we take home
  2. 02Cost-to-serve baseline down to customer and SKU-family level
  3. 03Recommended network with scenario robustness testing
  4. 04Transition plan sequenced by cash impact and operational risk
  5. 05Board-ready decision paper stating the recommendation, the evidence and the dissent

What an engagement looks like

A representative shape.

Illustrative. This is the shape of work in supply chain & analytics, not an account of a specific client. We do not publish named results, and we would be wary of a firm that publishes them without the client in the room.

12 weeks

  1. 01Situation

    A consumer goods manufacturer was opening a third distribution centre on the strength of a regional sales forecast, with freight cost per unit rising and no cost-to-serve view below channel level.

  2. 02What we did

    Reconstructed eighteen months of shipment data into a true origin–destination model, built cost-to-serve to customer level, and tested the proposed footprint against demand growth, rate shock and node-loss scenarios.

  3. 03Where it landed

    The third site turned out to be robust only under the most optimistic growth case. Redrawing catchments and re-tendering two lanes captured most of the projected saving without the capital, and the site decision was deferred rather than cancelled.

Where this connects

Rarely a self-contained problem.

These are the adjacencies that come up most often on this kind of work. Naming them is usually cheaper than discovering them halfway through.

Questions

The ones we get asked.

How much data do you need before you can start?

Twelve to eighteen months of shipment-level transactional data, a rate card or freight invoice extract, storage and handling costs by site, and a customer master with delivery locations. If some of that is missing or unreliable we will tell you in the first fortnight rather than modelling on sand, reconstructing a defensible baseline is part of the work, not a prerequisite for it.

Do we need to buy network optimisation software?

No. We build in open solvers and hand the model over with the engagement. If you already own a commercial platform we will build inside it so your team can maintain the model afterwards. Buying a licence to answer a one-time question is usually the wrong order of operations, decide the network first, then decide whether ongoing re-optimisation justifies a tool.

What if the answer is that our network is fine?

Then we say so, in writing, with the evidence. That has happened. A study that confirms the current footprint is robust across scenarios is a legitimate and valuable outcome. It converts an open argument into a closed decision and frees management attention for the constraint that actually binds.

How is this different from a 3PL's network study?

A logistics provider's study is competent and free, and its solution space is bounded by what that provider can sell you. Ours is not. We have no freight to place, no warehouse to fill and no software to licence, which is the entire reason the recommendation is worth reading.

Start a conversation

Talk to us about network design.

Most useful first conversations are thirty minutes and involve no proposal. Describe the problem you are looking at and we will tell you honestly whether it is one we can help with.

Or write directly to hello@shyenova.com