Can ERP Customization Become an AI Advantage?
ERP (enterprise resource planning) customization is often treated as a liability, but when those custom processes reflect a company’s genuine competitive strengths, they could give AI (artificial intelligence) something valuable to work with. In his recent article for CIO, contributor Ghassan Kabbara explores that idea through a fictional comparison of two retailers that choose the same cloud ERP and implementation partner but take very different approaches to customization. One retailer heavily customizes its ERP around its merchandising, pricing and replenishment processes. The other sticks with the standard configuration. The customized implementation costs more and takes longer, but it preserves processes the company believes genuinely differentiate it. The interesting part comes later, when both companies begin using the ERP vendor’s AI capabilities. The standard implementation works smoothly, but its AI delivers essentially the same capabilities available to other customers. The customized ERP, however, gives AI access to the company’s distinctive workflows and business rules. In Kabbara’s story, that foundation allows the AI to produce more useful, differentiated results.
The article isn’t necessarily arguing that companies should customize everything. Instead, it raises a more useful question: Which processes are actually worth preserving? Customization can create technical debt, higher implementation costs and greater maintenance requirements. But eliminating every customization simply for the sake of standardization could also mean giving up processes that provide real business value. The bigger takeaway is that ERP customization isn’t automatically good or bad. The real question is whether the customization captures something genuinely valuable—and whether that foundation can eventually help technologies like AI make the business even more effective.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.


