The main challenge with ERP is that, no matter how good it is, it cannot address 100% of your organization's needs.

There will always be company-specific needs such as reporting or KPIs.

There are also likely to be several integrations that you might require, such as integrating your inventory forecasting or demand planning system or e-commerce.

These integrations and reporting requirements will drive changes to your core ERP functionality, such as exposing additional data fields through interfaces or on the screens.

While customizations provide great flexibility to tailor the experience to your needs, over-customizing could fire back due to increased technical debt and maintenance.

Also, the team that may have written the customization may move out, and the code may not be as documented as the OEM code.

If the customization is done by the vendor, they might not even share the source code with you, creating vendor lock, a much tighter lock than with the product or with the OEM.

In fact, a study by Panorama Consulting showed that 90% of ERP systems have at least minor customizations, while 36% have customizations that involve modifying over 50% of the code.

How to make a decision whether it is wise to customize an ERP or not?

Let's hear from experts Martin Davis (CIO/CDO), Ashish Parulekar, Aaron Spool, Mike Schlagenhaufer, Chris Gherardini, and Sam Gupta as they share their expertise on customization of ERPs vs maintenance nightmares.

Watch the live stream on:
���� [ Ссылка ]
👀 [ Ссылка ]

Now, please share your experiences with the customization of ERPs in the comment below. 👇

#ERP #CFO #CIO #CEO #WBSRocks

свернуть