Customization is always optional, whereas the software must always be configured before use (e.g., setting up cost/profit center structures, organizational trees, purchase approval rules, etc.). The software is designed to handle various configurations and behaves predictably in any allowed configuration. The effect of configuration changes on system behavior and performance is predictable and is the responsibility of the ERP vendor. The effect of customization is less predictable. It is the customer's responsibility, and increases testing requirements. Configuration changes survive upgrades to new software versions. Some customizations (e.g., code that uses pre–defined "hooks" that are called before/after displaying data screens) survive upgrades, though they require retesting. Other customizations (e.g., those involving changes to fundamental data structures) are overwritten during upgrades and must be re-implemented.
Customization is always optional whereas the software must always be configured before use (eg setting up cost/profit center structures organizational trees purchase approval rules etc) The software is designed to handle various configurations and behaves predictably in any allowed configuration The effect of configuration changes on system behavior and performance is predictable and is the responsibility of the ERP vendor The effect of customization is less predictable It is the customer's responsibility and increases testing requirements Configuration changes survive upgrades to new software versions Some customizations (eg code that uses pre–defined "hooks" that are called before/after displaying data screens) survive upgrades though they require retesting Other customizations (eg those involving changes to fundamental data structures) are overwritten during upgrades and must be re-implemented