Two companies may deliver similar services while organising approvals, documents and billing differently. Adapting ERP means determining which differences can be handled through available settings and which require a data connection or an additional feature.
Configuration uses the capabilities already available
Module selection, numbering settings, reference lists and user roles are examples of configuration areas. Their limits depend on the capabilities of each module. That is why it helps to describe a need in terms of what should happen, rather than immediately requesting a new screen.
For example, “we need a separate numbering series for a particular group of documents” is a more precise starting point than “we need our own document module”.
Integration connects information from elsewhere
If data originates in a tool that the business intends to keep, the need may be for an integration. You should identify the source, the information to be exchanged, the frequency and the person responsible for resolving errors.
A one-off transfer of historical data and a daily exchange of new events are different tasks. They have different requirements and should be assessed separately.
A custom module handles an additional part of the process
A custom module is worth considering when you need new data, decisions or actions outside the product's available scope. One example might be a specialist process for accepting completed work before billing. First, describe its outcome, participants and connections to the contract.
Consider the work that comes later
Every extension will be used, changed and checked as the system develops. It is useful to establish its owner, acceptance criteria and maintenance arrangements from the outset. This makes adaptation part of the business process, rather than a one-off change to the application's appearance.
With Vector ERP, we begin by understanding the need. We then select configuration, integration or an extension to achieve the agreed outcome.