When to implement ERP in your company? Seven signals and conditions for a good decision

In many businesses, the moment for ERP shows in a single file: an order spreadsheet that only one person understands and that has to be reconciled by hand with the warehouse and accounts. An ERP system can bring together the data and rules for sales, warehouse, finance, HR or production. Installing it does not remove chaos, though. If processes, data owners and exceptions are not described, the new system will carry the old problems over into a more expensive tool.

What an ERP system is in practice

ERP (Enterprise Resource Planning) is a class of systems supporting the planning and management of enterprise resources. Individual modules can use common data, thanks to which a change made in one process is available in other authorized areas.

The actual scope depends on the product, licence, configuration and integrations. A “real-time” report is only up to date when the source data is complete and fed in at the right frequency.

Seven signs it is time to analyse an ERP implementation

1. The same data is transferred between tools

Manually moving customers, orders, documents or states increases the number of points where an error can occur. First, you need to establish a parent source for each type of data.

2. Users work with different versions of information

If departments have different price lists, statuses or definitions, the problem also lies in the organisation. Implementation requires agreeing common dictionaries, rules and data owners.

3. Reports are mainly created by manually combining files

ERP or a separate analytics layer reduces manual steps. A correct report, however, requires metric definitions, quality checks and information on when the data was last updated. We describe this in our post on report automation.

4. The increase in the number of transactions causes more and more exceptions

A process that worked with a few orders can become hard to control at a larger scale. What matters is the number and complexity of operations, not the number of employees as such.

5. It is difficult to determine liability and the stage of the case

If the handling of an order, complaint or purchase depends on employees' private messages and memories, the workflow system can organise statuses, tasks and change history.

6. Legal or industry integrations are handled separately

KSeF (the National e-Invoicing System), banking, EDI (electronic exchange of documents with trading partners), an online shop and a production system may all need to exchange data. We write about preparing for KSeF separately in the post KSeF 2026. Each integration has to be assessed separately: scope, authorisation, error handling, monitoring and responsibility after an interface changes.

7. The company cannot safely delegate operations

Authorizations, approvals and limits can be saved in the system. But first you need to decide who approves exceptions and how the organisation handles the decision-maker's unavailability.

When an ERP implementation is premature

ERP may not be the right first step when:

• business model and processes change so frequently that a stable scope cannot be defined;
• the company does not have a project owner on its side;
• the problem can be solved by tidying up one tool or simple integration;
• benefits do not justify the cost of migration, training and maintenance;
• does not have time for data cleansing and user participation in testing.

There is no minimum number of employees at which ERP becomes necessary. A small business may have complex production or trading, while a larger organisation may run a simple, repeatable process across a few well-chosen services.

How an ERP implementation is prepared

1. Goals and metrics. Define the problem, the expected result and how it will be measured.
2. Process map. Describe the typical flow as well as the exceptions, roles and decisions.
3. Data range. Identify the sources, owners, quality, history and migration rules.
4. Requirements. Separate essential requirements from optional and future ones.
5. Solution Analysis. Check the standard features, the extensions you need, integrations and licence limitations.
6. Test plan. Prepare scenarios for users, integrations, reports, permissions and errors.
7. Startup. Choose a phased or simultaneous switchover, a fallback plan and decision criteria.
8. Stabilization. Agree how tickets, fixes, measurement of results and further development will be handled.

The implementation time cannot be reliably promised before the analysis. It depends on the modules, the number of processes, data quality, integrations, the availability of the client's team, the scope of modifications and the go-live approach.

How to assess the enova365 system

enova365 is a Polish, modular ERP system developed by Sonet. The manufacturer describes areas including finance and accounting, human resources and payroll, trade, CRM, production, processes and Business Intelligence. Module list shows that individual functions are separate elements of the offer.

The vendor states that KSeF integration is included in the licence and that more than 22,000 businesses use the system. This is the vendor's information as at the date of our review. Before deciding, confirm the current licence terms, version, the scope of the specific module and the technical requirements.

The Business Intelligence module provides reports, metrics and visualisations, but the availability of some features depends on the licence and permissions. Analyses require data modelling and configuration.

We are an Authorized enova365 Partner and implement this system, from the pre-implementation analysis to support after go-live. The detailed division of roles is set out in the project proposal.

ERP implementation costs that are easy to forget

In addition to the licence and configuration, you must take into account:

• pre-implementation analysis;
• data preparation and cleaning;
• integrations and modifications;
• employee participation in workshops and tests;
• training and manuals;
• test environments and infrastructure;
• post-boot support;
• updates, development and maintenance of extensions.

The cheapest initial offer can turn out more expensive over the whole life cycle of the system. Compare offers on the same scope and assumptions.

Questions to ask before deciding on ERP

1. What specific problem is the system designed to solve?
2. Who owns the project and individual processes?
3. Which features are standard and which require addition or modification?
4. What data will be migrated and who will approve its accuracy?
5. How will integrations, permissions and error scenarios be tested?
6. What will happen to extensions after a system update?
7. What does data export and implementation partner change look like?
8. What maintenance costs will occur after the first year?

From process analysis to an ERP decision

The signs described here indicate that it is time to analyse your processes and data. The purchase decision is made only on the basis of that analysis, comparing ERP with a simpler integration, an industry application or tidying up your current tools. We describe the scope of the pre-implementation analysis on the page enova365 implementation.

Sources

• Soneta, enova365: vendor's home page, https://www.enova.pl/ (accessed 02/10/2026)
• Soneta, enova365: system modules, https://enova.pl/moduly-systemu/ (accessed 02/10/2026)
• Soneta, Mocne strony enova365 (enova365 strengths) (number of companies using the system), https://enova.pl/mocne-strony-enova365/ (accessed 10/10/2026)

As of 2 October 2026.