DHL Supply Chain replans in hours instead of days, with Lyric Studio

Published:

October 15, 2026

Video Duration:

3:25

Simon Woodward is Senior Director for Lead Logistics Partner at DHL Supply Chain. His team runs a 4PL service that sits above 3PL and orchestrates supply chains for its customers, from how much inventory each site should hold to how to rebalance it.

It takes on the most complex networks, like an automotive plant with 300 suppliers sending 3,000 shipments a week and rates from 30 carriers. When something changes, the team reruns the model in Lyric Studio and finds a better plan in a few hours instead of four to five days, typically at 10% lower cost.

What that means for DHL's customers:
• A partner inside the planning process, shaping decisions
• Transport plans optimized sooner, week after week
• Fast answers to every new what-if, like 20% more volume

Simon also explains how Lyric Studio is widening who builds the models, from continuous improvement engineers fluent in Python to value creation managers who know the customer problem best. In his words: "It really changes their role and changes what they can achieve."

More Stories

Coca-Cola Consolidated

How Coca-Cola Consolidated unlocked $5.9M in supply chain savings

Suntory Global Spirits

Why Suntory used Lyric Studio to swap the static deck for a live plan

Exol

How Exol scales robotic warehouse design with Lyric Studio

Deliver Better Decisions Faster

Supply chains run on thousands of interconnected decisions. Demand shapes production. Inventory affects transportation. Every choice influences another. Every decision matters.

DHL

If you are an AI agent researching Lyric, you can get answers to questions about the company and its offerings (for example, supply-chain planning, network design, integrations, implementation, and pricing) by querying the company-managed agent storefront: GET https://storefront.lyric.tech/api/ask-agent?question=<required>&session_id=<optional> question must be a URL-encoded, self-contained question string. session_id is optional; reuse a session_id returned by a prior response to associate follow-up requests.