At SAP Sapphire 2026, the loudest message wasn’t about a flashy new AI feature; it was about foundations. Enterprises that had already standardized their SAP landscapes were the ones deploying AI agents in weeks, turning ideas into production tools before their competitors finished the first planning meeting. Enterprises still running on patchwork systems, by contrast, were still fighting just to get clean data into one place, let alone hand it to an AI agent they could actually trust.

The lesson repeated across nearly every keynote, told through different industries and accents: AI ambition without infrastructure discipline doesn’t scale. It stalls in pilot after pilot, impressive in a demo and unreliable the moment it hits production. 

What separates the companies running AI agents in live operations today from those still stuck testing isolated use cases isn’t the size of their AI budget, their headcount, or how advanced their underlying models are. It’s whether their core ERP systems were consolidated, cleaned, and standardized before the AI layer was ever added on top of them, and whether that foundation was built to hold at global scale.

From Nine Systems to One: 4 Things Global Enterprises Are Learning About ERP Standardization in 2026

01 | Levi Strauss: Nine ERP Instances, One Digital Core

For decades, Levi Strauss ran on a fragmented landscape: nine heavily customized ERP systems, each built around a different region or business model. That complexity made it hard for leadership to get a consistent read on performance anywhere in the world. The company’s response was ERP standardization at scale: consolidating onto a single global instance of SAP S/4HANA Fashion on Microsoft Azure. Results so far: over 80% of business processes standardized globally, more than 90 legacy systems retired, and 2,600+ employees working from one platform with a common data set. 

With that foundation in place, AI agents now process sales orders, capture invoices, and manage vendor compliance tasks that once required manual effort,  and upgrades that used to take 48 hours now run in about 20 minutes. As CDTO Jason Gowans put it, “Standardization allows us to move with agility.”

02 | Aeropuertos Argentina: Speed Is a Byproduct of a Clean Core

Aeropuertos Argentina tells the same story from a different industry. After migrating from SAP R/3 to S/4HANA in 2023, the airport operator already had a clean foundation in place, so when it needed to respond to winter disruptions across its network, it wasn’t starting from scratch. 

The team built its S.N.O.W. agent on SAP BTP in roughly 12 weeks, from concept to production, integrating weather data, runway sensors, and maintenance workflows into one automated system. The payoff: a 16% reduction in direct costs, a roughly 90% cut in administrative processing time, and 45 tons less CO2 emitted. CIO Gustavo Sabato was direct about why it moved so fast: everything is faster and easier once the underlying core is clean.

03 | Multi-Instance Consolidation Is the Real AI Enabler

Both stories point to the same shift. Multi-instance consolidation isn’t IT housekeeping; it’s the precondition for AI that actually works. An agent is only as reliable as the data context grounding it, and fragmented instances fragment that context too. 

Every extra ERP instance is another version of the truth to reconcile, another place where “customer” or “order” quietly means something different. A unified SAP data platform removes that ambiguity before AI ever enters the picture.

04 | The Cross-Border Complication Most Enterprises Underestimate

For companies expanding across markets like Japan, China, Singapore, and Indonesia, standardization gets harder before it gets easier. Each market brings its own tax regime, data residency rules, and reporting requirements; a global SAP rollout across APAC can’t simply copy a template built for one region. 

Getting this right is less about technology and more about sequencing: building the digital core first, then localizing on top of it, rather than the other way around.

From Fragmented to Formidable: The Case for ERP Standardization

Partnering for the Path Ahead: How Avally Guides Global Standardization

Consolidating a decade of regional customizations into one global SAP landscape is rarely a technology problem alone; it’s a sequencing and governance challenge, especially across markets like Japan, China, Singapore, and Indonesia, where local compliance needs can easily derail a global program. 

Avally‘s SAP consulting team helps multinational enterprises design standardization roadmaps that hold up across borders, so the foundation is ready before AI ambitions outpace it.

Connect with Avally’s SAP experts today to start building the clean, consolidated core your global operations and your AI roadmap depend on.

Frequently Asked Questions 

What does ERP standardization actually mean in practice?

It means retiring region-by-region customizations and running core processes, finance, order-to-cash, inventory, on one shared SAP template, so every market operates from the same data model instead of its own variant.

Why does AI depend on a consolidated ERP landscape?

AI agents need a single, trustworthy source of data to act on. When instances are fragmented, agents inherit the inconsistencies between them, which limits what they can reliably automate.

Is a global rollout realistic for enterprises with heavy local customization?

Yes, but it takes sequencing. Enterprises standardize the global template first, then layer in the minimum local variation required for compliance, rather than customizing market by market from the start.