New study: The Agentic AI gap
Read nowStable ERP core
for standard processes
Purpose-built applications
for specialized needs
Connected capabilities
that can evolve and scale with the business
Enterprise transformation needs both global consistency and local flexibility.
Large businesses bring years of growth and local decisions into an S/4HANA transformation. They may be working across different processes and data structures to serve customers with very different requirements.
S/4HANA can provide a common foundation for core processes. But some business needs are specialized: they can be country-specific or subject to frequent changes. They don’t always fit naturally into a global ERP template.
The challenge is deciding how to meet those needs without compromising the transformation.
Architecture choices have a bigger impact at enterprise scale.
It can seem straightforward to customize the ERP whenever the business needs something more. But as custom functionality accumulates, the core becomes more complex to maintain.
Even a relatively focused change triggers complex regression testing. Teams need to wait for a larger release cycle or take on the testing effort to make sure other processes still work.
Meanwhile, business needs keep evolving. New markets. New regulations. New operational requirements. These don’t wait for the next ERP release.
The choice shouldn’t be between a rigid ERP and a customized one. It’s about putting each capability in the right place.
A digital core is more than an ERP.
Our solution
Keep S/4HANA focused on standard financial and supply-chain processes. Where a business requirement needs more flexibility, build a purpose-specific application alongside the ERP and connect it through a clean integration.
This gives you a way to:
- Keep S/4HANA focused on core processes.
- Adapt applications as business needs change.
- Release updates independently of the ERP.
- Use your existing platforms and tools.
- Add new capabilities as your business grows.
Success story: a business need better served outside the ERP
Brenntag’s returnable-packaging processes varied across countries. Some teams used local SAP developments, while others relied on spreadsheets. The business needed a better way to track packaging movements, including what a container had held, without making packaging management another major customization inside S/4HANA.
Brenntag and Cloudflight built PacMan, a dedicated packaging-tracking application that integrates with S/4HANA. The initial deployment in Ireland established the integration foundation. From there, the application could evolve to support more complex flows and additional capabilities.
PacMan is one example of the broader approach: meet a specific business need with a connected application, while keeping the ERP focused on what it does best.
Getting the architecture right starts with understanding the business.
Deciding what belongs in S/4HANA and what doesn’t is more than just a technical exercise. It takes a partner who can understand the business problem, work within your technology environment to help shape a solution that fits.
Cloudflight brings software-development and supply-chain experience to that conversation. We work collaboratively and challenge assumptions when needed. We build solutions designed to fit your landscape, not make you fit ours.



