Skip to content

Supply chain

Your supply chain was built for yesterday’s demand, suppliers and costs. A model redesigns it for today’s, as one connected plan.

  • Free 30-minute call
  • No commitment
  • You own the code
Typical decisions
inventory optimisation, replenishment planning
What you gain
Every decision shows its effect on your whole supply chain, in francs and delivery time
First step
A free 30-minute call

Typical problems in supply chain.

Many of your customers have moved since you chose your warehouse sites. Inventory, production and warehouse locations each get their own project, and each works against the others.

Designed for yesterday

Your main warehouse is where your biggest customers were when it was built. They have moved since, and your trucks drive further.

Separate plans miss savings

Three teams plan inventory, production and transport in three spreadsheets. Some savings only work when two teams change their plans together. Those savings never happen.

Forecasts drift

Last year’s forecast still drives this year’s plan. What you sell drifts further from the forecast. Months later, you pay for it with goods you can’t sell any more and with rush orders.

One disruption cascades

One supplier ships two weeks late. Production stalls, stock runs out and customers wait, because nobody modelled how supplier, production and stock depend on each other.

In short: Supply chain optimisation plans the sites, inventory and production of a supply chain together, in one model. It decides where warehouses go, which customers each one serves and how much stock each site holds for today’s demand.

A supply chain tuned for yesterday

A large customer moves its warehouse to the other end of the country, and nothing in your plan changes. Your trucks drive further, your stock is far from where it’s needed, and deliveries take a little longer each week. Your warehouse sites and delivery routes, your forecasts, your stock rules and your production plans were all set once, for the customers and suppliers you had back then.

Since then, customers have moved, suppliers have changed and costs have shifted. Inventory gets one project, production another and warehouse locations a third. Each fix helps locally and hurts somewhere else, while the old assumptions keep costing you money.

Optimising network, inventory and production together

Today, three teams improve three parts of the chain, each against its own target. Our model plans three things together: your network (which warehouses you run and which customers each one serves), your inventory and your production. A decision about a warehouse shows its effect on stock and factory load at once, in francs and delivery days.

When a supplier changes or a customer moves, you rerun the model instead of starting a new project. You can test a question before you commit. What if this warehouse closed, or that supplier took twice as long? You get one plan where network, inventory and production decisions support each other.

Supply chain network design for today’s demand

Supply chain network design decides how many warehouses you need, where they go and which customers each one serves. Underneath is a facility location problem: the model weighs building and running costs against transport costs and delivery times. Your demand forecast says what each region will buy. Inventory optimisation sets each site’s stock, and replenishment planning decides when to reorder. Because one model links them, your supply chain optimisation works as one plan instead of four projects.

What a network model has to include

Most network design guides price transport by distance alone. Two more things change which sites are best. First, there are hours when heavy trucks can’t drive, for example at night. So your trucks can only leave from a fixed time in the morning, however short the route looks on the map. Second, some transport costs depend on the truck’s weight and emission class as well as on the kilometres.

Take a warehouse that looks central on the map. If the first trucks can only leave at a fixed time, it may still be too far away for an early delivery. We put these driving hours and these costs into the model. Then each site’s catchment is the area your trucks can reach in time. The use cases below describe each step.

How a project runs.

Each of the three phases ends with something you can check before we go any further.

  1. Understand

    We start with your operation. What do you plan, where does it go wrong, and what would a better week look like? Then we tell you straight whether optimisation can help, and sometimes the answer is no.

    • A written assessment
    • A clear go or no-go
  2. Model

    We write your decisions, goals and rules into a mathematical model, which is just a precise description of how your operation works. Then we run it on your own data. You see side by side what each plan costs and what it delivers, and pick the one that fits your priorities.

    • A documented model
    • Results on your own data
  3. Implement

    We test with your data and go through the results with your team. Once they trust it, we connect the model to your systems, so it runs every day without anyone stepping in by hand.

    • Source code and documentation
    • Training for your team

Common questions.

Something else? Ask us directly.

There’s no fixed cycle. One trade article reports that companies now review their sites every 18 months on average. It used to be every 24 months. It’s better to check again when something big happens: a large customer moves, you switch a supplier or transport gets more expensive. Once a model exists, a rerun is quick. So you can check the network every year instead of every few.

The cost to build and run the site, the transport to and from it, and the delivery times you promise customers. Two more things change the result: the hours when your trucks are allowed to drive, and costs that rise with truck weight. Wages and land prices at the site count as well. A model weighs them together and shows what each choice of site costs.

Software helps when you have people who can keep the data current and run scenarios. Outside help pays when the question is new and your data first has to be collected and cleaned. We usually do the first study with you, then hand over the model. Your team reruns it when a large customer moves or a supplier switches.

It depends on the problem, so we agree the timeline with you up front. Every project starts with a diagnostic, a short look at how you plan today. It shows which data, how much time and what budget a model for daily use needs. Only then do you decide.

No. We connect to your ERP, your warehouse management system or your planning spreadsheet. We build the model only for the planning that gives you trouble today. Your systems keep running as before.

Almost nobody’s data is clean. The diagnostic shows what the model needs and what’s missing. Then we build the model to cope with messy data.

Off-the-shelf tools are built for many companies at once, so they don’t know your special rules. We build a model that follows exactly your rules. Then we hand it over, and your team owns it.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go