Smart operations
and growth with Odoo

We work that out together, before we promise anything. We start with a conversation and a short diagnosis: we look at how you run sales, purchasing, the warehouse, production, accounting and any other area that matters to you, where data is duplicated and where your current system holds you back.

A deeper analysis follows, in which we propose ways to optimise your processes and check how many of them Odoo covers. The result is a clear inventory: what Odoo covers as standard, what our Hermes modules solve and what requires custom development. The decision is then yours, made on the basis of facts. If Odoo is not the right solution for you, you find that out in good time.

Wondering whether it is time to change systems? Read Is it already time to replace your ERP.

For a comparable scope of business, implementing Odoo is considerably shorter than implementing large international ERP systems such as SAP and Microsoft Dynamics 365 Business Central. The reason is that a large part of the functionality already works as standard, and we build the system module by module rather than as one big project that only comes alive at the end.

From our projects:

• a smaller company with standard processes: 2-3 months
• a mid-sized company with several departments and a few integrations: 4-6 months
• manufacturing or complex logistics with custom development: 6-12 months

You get the exact framework in the quotation once the analysis is done. Three factors influence the duration most: the quality and volume of the data to be migrated, the number of specifics Odoo does not cover as standard, and the availability of your key users. On the last one, you have the greatest influence.

You can see how the implementation went for others among our case studies.

Yes, but not fully with the standard localisation. Odoo covers the basics as standard, and everything else a Slovenian company needs to operate compliantly is added by our Hermes localisation, proven at 70+ Slovenian companies.

Standard Odoo covers:

• the chart of accounts
• tax settings
• VAT reports (partly)

The Hermes localisation additionally includes:

• fiscal verification of invoices with FURS
• issuing e-invoices in the eSlog standard
• advance invoices
• statistical reports for the Bank of Slovenia (SFR and KRD)
• preparation and export of reports for AJPES
• export of the Intrastat report

When legislation changes we update the localisation, and every client under maintenance receives the update, so you do not have to track the changes yourself.

Separately from that, we offer payroll and HR records under Slovenian legislation, a solution that has been on the market for more than 30 years.

The work runs as a project, with one point of contact on our side and one on yours, so you always know who to ask. We run the project in six phases:

1. Analysis. In workshops by area we document your processes and requirements.
2. Defining the scope. We write the requirements into a document that you approve. It is the reference for all further work.
3. Setup. We set the system up in a test environment and configure it to the approved scope.
4. Validation. Your key users, together with our consultants, regularly review the implemented processes.
5. Training. We train users on your data and your cases, not on generic demo examples.
6. Go-live and support. We are intensively present at go-live, after which you move into regular support.

Every phase follows the approved documentation, so at any moment you know what has been agreed and where you are in the project. You can read more about the individual services on the Odoo services page.

Implementing an ERP system is a joint project, and the extent of your involvement changes from phase to phase. You need two roles:

• A project manager on your side. Connects the teams, keeps deadlines and decisions moving.
• Key users by area (sales, purchasing, warehouse, production, accounting). As a rule 4-8 hours a week, depending on the project phase.

Analysis, training and acceptance testing take the most of your time. In between, some time has to go into validating the implemented processes together with our consultants. That step, more than any other, reduces the number of surprises at go-live.

You prepare best by putting your data in order and naming your people. Those two decide the speed of the implementation more than anything else.

• Clean up your master data. Customers and suppliers, items, bills of materials, price lists. Removing duplicate and inactive records is cheaper before the migration than after it.
• Prepare opening balances. Stock, open items, fixed assets.
• Document the specifics. Exceptions, manual workarounds and the Excel files circulating outside the system are often the most important content of the analysis.
• Name the people responsible for each area and reserve time for them.
• Gather the access credentials and documentation of your existing systems, along with the requirements of any integrations (online store, bank, production equipment, specialist tools).
• Set a target go-live date against your business calendar.

You do not need to have everything in order before the first meeting. We guide you through this list; what matters is that we know where you stand.

Changes are normal in an ERP implementation and we have an established procedure for them. They do not stop the project and they do not lead to an unexpected invoice.

1. We record it as a change request with a permanent reference, so it is traceable what was requested and when.
2. We assess the impact on scope, schedule and price, and on everything connected: configuration, test scenarios, training.
3. You decide. You approve the change, reject it or move it to a later phase.
4. We build it in across all documentation and issue a new version with an entry in the change log.

That way you know at any moment what the agreed scope is, what has changed and why.