An ERP system in Croatia should be chosen according to the processes it must connect, local accounting requirements, total cost and the implementer's ability to put the system into real use. A list of functions and a licence price are not enough. What matters more is how sales, purchasing, inventory, accounting and management will work in the same process.
If you have only a few employees, simple operations and reliable accounting software, you may not need an ERP system yet. ERP makes sense when you enter the same data in several systems, keep important records in spreadsheets, or cannot reliably follow what happens from quotation to payment.
ERP guide: all topics in one place
This guide gives a framework for choosing. For specific questions, see the detailed articles:
- Basics: what an ERP system is, CRM or ERP and when invoicing software is no longer enough
- Cost and timelines: how much an ERP system costs, how long implementation takes and Odoo pricing
- ERP by industry: manufacturing, retail, wholesale, construction and hospitality
- Comparisons: Odoo or Pantheon, Minimax, PANTHEON, e-racuni.hr or Odoo, Odoo or Business Central, Odoo or Orka and Odoo or IN2 Opus
- Croatian requirements: Fiscalization 2.0, eRačun in practice and Odoo accounting
- Implementation and migration: Odoo implementation, moving from Pantheon and Odoo Online, Odoo.sh or your own server
How do you choose an ERP system in Croatia?
Start with the business process, not a supplier presentation. Write down how a quotation, order, delivery, invoice and payment are created today. Then do the same for purchasing, inventory, manufacturing or projects, depending on what the company does.
For each process, answer five questions:
1. Who enters the data and who approves it?
2. Which document or event starts the next step?
3. Where is the same data re-entered today?
4. Which reports do management and accounting actually use?
5. What must remain connected to an external system?
Only then should you compare ERP solutions. You will get a clearer scope, more realistic proposals and less room for misunderstanding during implementation.
What must an ERP system cover?
An ERP system does not need to cover the entire company from day one. It must reliably cover the processes included in the first project phase and leave a clear path for later expansion.
The most common areas are:
- CRM, quotations and sales orders
- purchasing and purchase-order approvals
- inventory, serial numbers and replenishment
- invoices, collections and accounting
- manufacturing, bills of materials and work orders
- projects, timesheets and field service
- e-commerce and POS
- management reporting
Ask for a demonstration of your own process. A general demonstration may show many functions, but it does not prove that your pricing, approvals, warehouse locations or invoicing method are covered.
Croatian localisation is more than translation
A Croatian company should verify the chart of accounts, taxes, fiscal positions, invoices, e-invoices, bank data, reports and other required process elements. The existence of a localisation package does not by itself mean that every business scenario is ready for production.
Odoo lists Croatia among its available fiscal localisations in its official documentation, but also states that the localisation package must be correctly configured and adapted to company requirements. Key scenarios should therefore be tested with the responsible person and accounting before go-live. See the Odoo documentation on fiscal localisations.
Do not accept only a claim that a system is "compliant". Ask for a list of what is included, what needs additional configuration and who confirms the test results.
Cloud ERP or your own server?
Cloud ERP reduces the need for your own infrastructure, but it does not remove the need to maintain data, user rights, integrations and upgrades. Your own server provides more technical control, with greater responsibility for availability, backups and maintenance.
Odoo offers different hosting models. Odoo Online is a service managed by Odoo and does not support non-standard modules. Odoo.sh and self-hosting are more suitable when a project requires additional modules or development. The differences are described in the official Odoo hosting documentation.
For a mid-sized company, it is not enough to ask whether a solution is in the cloud. Ask where the data is kept, who makes backups, how upgrades are tested, what happens to integrations and how the system can be transferred if circumstances change.
Standard functions or custom development?
Use standard functions wherever they cover the process well. They are easier to maintain and upgrade. Custom development makes sense when a process creates a real business difference or when the standard flow cannot reasonably support it.
The problem appears at two extremes. Too much development increases cost and upgrade risk. Too little adaptation sends users back to spreadsheets, email and manual records. A good implementer must explain what should change in the system and what is more sensible to change in the process.
How do you verify an ERP system before signing a contract?
Select two or three processes that are important enough, and troublesome enough, to show the real difference between solutions. Prepare the same input data and expected result for each. The supplier then does not demonstrate a pre-prepared ideal example, but your scenario.
A useful test scenario can be a sales order with a special price list, partial delivery, return of part of the goods and payment in two instalments. For manufacturing, it can be material planning, a work order, consumption and final costing. Write the acceptance criteria in advance: which documents must be created, who approves them and which report must be correct at the end.
This does not require buying software. Preparing the scenario alone often shows that the company has not agreed its own process, which should be resolved before implementation.
How do you choose an ERP implementer?
A reliable implementer does not start by promising everything. They first need to understand the processes, data, priorities and project constraints.
Before deciding, ask for clear answers to these questions:
- Who leads the analysis and who makes decisions during the project?
- What exactly is in the first phase and what remains out of scope?
- How are migration data prepared and verified?
- Which scenarios are tested before production?
- Who trains key users?
- How are issues reported and resolved after go-live?
- How are additional changes estimated?
- How is the next system version prepared?
Ask for written scope and responsibilities on both sides. An ERP project rarely succeeds if the supplier cannot reach key users or the company has no person who can make process decisions.
If you are already considering Odoo, see what Odoo implementation in Croatia looks like and which decisions need to be made before starting.
How do you compare ERP proposals?
Do not compare only the licence or the initial project price. Compare the total scope and cost over the period in which you will use the system.
A proposal should clearly separate:
- licences and hosting
- analysis and configuration
- data migration and cleansing
- integrations and custom development
- testing and training
- support after go-live
- maintenance and upgrades
A less expensive proposal can be a good choice if the scope is smaller and clearly defined. The problem arises when two proposals look comparable but one does not include migration, testing or support. For a more detailed overview, see what affects the cost of an Odoo implementation.
When can Odoo be a good choice?
Odoo can connect CRM, sales, purchasing, inventory, accounting, manufacturing, projects and other applications on one platform. An overview of current applications is available in the official Odoo documentation.
An advantage is phased implementation. A company can start with sales and inventory, then add purchasing, accounting or manufacturing. A broader overview is available on the Odoo ERP for Croatian companies page.
Odoo is not automatically the best choice for every company. If you only need simple invoicing or a highly specialised industry program without a need to connect other processes, a smaller solution may be less expensive and simpler.
Checklist before the final decision
Before signing a contract, you should have:
1. a list of processes and priorities
2. an agreed first project phase
3. a list of data for migration
4. confirmed integrations
5. test scenarios and acceptance criteria
6. named responsible people
7. a training and support plan
8. an estimate of the total cost
If one of these elements is missing, the proposals are probably not ready for a fair comparison.
Do you need an ERP project assessment?
If you are comparing ERP systems or are unsure how much scope you need, send a description of your current process. A short conversation is usually enough to clarify whether you need a full ERP system, phased implementation or a simpler solution.
