Supply Chain Sandbox: Run What-Ifs Without Touching Production

What a supply chain sandbox is

A sandbox is the workspace, not the analysis. It is the place where you can change inputs, run scenarios, compare options side by side, and discard whatever does not work, all without consequence to your real operation. The work stays in the sandbox until the operator decides what to act on.

The pattern comes from software engineering, where teams have used staging environments for decades. Supply chain teams adopted it later because the data plumbing was harder. There is no equivalent of git clone for an ERP. But the need is the same. You want to try things. You do not want trying things to break production.

Why operators need a sandbox

The work of supply chain operations is mostly steady-state with occasional high-stakes decisions. The high-stakes decisions are where careers are made and lost, and where the cost of being wrong is highest. Before changing a supplier allocation, rerouting a lane, or rebalancing inventory across distribution centers, the operator needs to know: what is the likely cost? What is the likely service impact? What is the worst case if I am wrong about the inputs?

Without a sandbox, the analysis happens in spreadsheets, in consulting engagements, or by making the change and watching what happens. Spreadsheets handle simple cases but break when the question crosses tiers or involves uncertain inputs. Consulting takes weeks. Making the change and watching has the obvious downside of finding out the answer by paying for it. A sandbox compresses the decision cycle to hours.

Sandbox vs simulation vs digital twin

These three words get used interchangeably in vendor marketing. They should not be. They describe different layers of the same stack.

Digital twin (the persistent model)

The digital twin is the always-on, updating picture of your supply network. Suppliers, lanes, inventory, demand, costs, and the connections between them. The twin is the source of truth that every scenario reads from. See the digital twin pillar for what a twin actually is and the four levels of capability.

Simulation (the act of running a what-if)

A simulation is a single run against the model: given these inputs and these rules, project forward and report the result. See the simulation pillar for the techniques and when to use which.

Sandbox (the environment where simulations run)

The sandbox is the workspace that holds your scenarios, lets you compare them, manages access, and keeps the analysis separated from production. The twin is the data; the simulation is the engine; the sandbox is the room.

How the Hylios sandbox works

The Hylios sandbox is built into the twin, not bolted on as a separate tool. When an operator wants to test a scenario, they describe the change (a tariff rate, a sourcing shift, a lane reroute) or pick from a starter library, and the platform runs it against the calibrated twin. Results come back as ranges with the trade-offs across cost, service, risk, and time made explicit. Hylios calls balls and strikes on each option; the operator decides what to do.

A few specifics about how it works in practice:

• No production touch. Scenarios run against the calibrated twin, not against your ERP or WMS. Nothing in the sandbox can write back to your real systems.
• 12-month default horizon. Every scenario runs for 12 months by default, long enough to see seasonality and downstream consequences. The operator can shorten or extend the horizon when the question calls for it.
• Lightweight or heavyweight. A quick tariff what-if runs in seconds. A multi-tier network redesign runs on the same twin without a new build. The platform scales the model to the question rather than forcing the operator to scale the question to the model.
• Granular by default. The twin runs at SKU and unit-level economics across every stage of the supply chain in any country. Scenario results inherit that granularity, so the operator can drill into a specific SKU or lane without re-modeling.
• Plain-language results. Output is the trade-off picture, not a wall of statistics. Confidence ranges, a sensitivity table showing which inputs drove the answer, and a citation trail back to the public events that informed the model.

The full Hylios methodology (how the twin gets built, calibrated, and scenarized) is documented at /methodology.

Use case: tariff sensitivity

A retailer's import director wakes up to news that Section 301 is expanding to a new HTS category. Without a sandbox: convene a working group, pull HTS-level import data, model the cost impact in spreadsheets, escalate to procurement to look for alternatives. Two weeks gone before anyone can answer "what is the margin impact?". With Hylios: open a sandbox scenario, parametrize with the category and rate, run. Output in under an hour: which SKUs are most exposed, what the landed-cost delta looks like, which alternative sources are pre-vetted, what the working capital impact is over the 12-month horizon.

Use case: supplier shock

A semiconductor supplier announces a six-week capacity reduction after a fire at one of their plants. The downstream exposure is not obvious. The customer buys from this supplier directly for some SKUs but indirectly (via a contract manufacturer) for others. Without a sandbox: operations manually traces the bill-of-materials impact, takes days, and inevitably misses some exposures. With Hylios: the supplier shock scenario propagates through the network automatically, identifies affected SKUs direct and indirect, shows service-level risk by week, and suggests alternative sources with capacity availability.

Use case: lane rerouting

A six-week port slowdown on the West Coast looks increasingly likely. The freight director wants to know: should we pre-emptively shift 40 percent of West Coast volume to East Coast ports? The math involves capacity at alternative ports, cost differential by lane, transit-time delta to inland DCs, and the operational reality that not all volume is easy to shift. Without a sandbox: weeks of analyst work plus a carrier negotiation. With Hylios: model the rerouted network as a scenario, simulate transit times under the proposed allocation, compare total landed cost and service-level outcomes against status quo across several recovery shapes.

How to roll out a sandbox

Step 1: Decide which decisions a sandbox would help

Start with the questions that take the longest today and the ones where the cost of being wrong is highest. Tariff response and disruption response usually top both lists. Use those as the first scenarios.

Step 2: Pick a platform that matches your team

Heavy snapshot-and-fork sandboxes work for organizations with dedicated modeling teams. Decision-first platforms like Hylios work for ops teams that want to ask the question and get the answer without a six-month rollout. Pick based on how your team actually works, not on feature count.

Step 3: Author the starter scenario library

A sandbox without scenarios is just a calibrated model. The library is what makes it usable for non-specialists. Authoring 10 to 20 scenarios covering tariff, disruption, demand shock, supplier shock, and lane reroute unlocks ops adoption. Scenarios should be parametrized so users adapt them without editing the model directly.

Step 4: Tie it to the news

The sandbox is most valuable when it is tied to current events. When an article flags an emerging tariff threat, a port slowdown, or a supplier disclosure, the relevant sandbox scenario should be pre-populated automatically. That tightens the gap from news to decision from weeks to hours. The Hylios stack does this natively: daily intelligence briefs link to the matching sandbox scenarios.

Frequently asked questions