ERP implementation & support
ERP

ERP implementation & support

From choosing the system to the first month closed inside it — and afterwards, for as long as you need us.

What it actually is

An ERP is the one place where orders, stock, production, invoices and accounts are visible together. Until it exists, each department has its own version of the truth and somebody reconciles them in a spreadsheet every month.

We implement two platforms: Odoo, for small and mid-sized companies that want a complete system at a predictable cost, and SAP, for large companies or those inside a group that mandates it. We make that choice together, at the start, and we write down the reasons.

Most of an ERP project is not software. It is the decision about what the process should look like, the migration of old data, and getting people used to a new way of working. Our budget and schedule reflect that, because otherwise the project ends with an installed system nobody uses.

Who it is for

  • Companies that have outgrown their invoicing and stock package and already keep parallel records in spreadsheets.
  • Manufacturers who cannot state the true cost of a finished product without calculating it by hand.
  • Businesses with a warehouse and an online shop that regularly find differences between displayed and actual stock.
  • Companies required to file e-Factura, e-Transport and SAF-T who currently do it with monthly manual effort.
  • Subsidiaries of international groups that must report in a format the shareholder imposes.

Who it is not for

  • Companies under 10 users with a single simple flow. A good stock package costs ten times less and does the job.
  • Organisations that cannot free an internal owner for at least half their time for the duration of the project.
  • Requests for "exactly as now, but in a different system". If the process does not change at all, the saving does not appear and the project does not pay for itself.

What we actually do

01

Platform selection

Two or three weeks comparing platforms against your real requirements rather than feature lists. You get a written recommendation with the five-year cost of each option, licences and maintenance included.

02

Process analysis and configuration

We document how you work today, decide together what stays and what changes, and configure the system to the agreed process. Code customisation happens only where configuration cannot reach, and is justified in writing.

03

Data migration

Master data, balances, stock, sales history. We clean the data before moving it — a new ERP loaded with the old system's dirty data inherits all of its problems.

04

Romanian fiscal compliance

e-Factura and e-Transport built into the flow, Romanian chart of accounts, VAT on collection where applicable, and preparation for SAF-T (D406) reporting.

05

Integration with existing systems

Web shop, till, bank, field applications, large customers' systems. Every interface is documented and monitored.

06

Role-based training and go-live

We train each role on its own process, not on the whole system. Go-live happens on a date chosen together, with us on site for the first days.

07

Post go-live support

The first two months are the hard ones. We stay with allocated time, then move — if you want — into a monthly support and development contract.

How long it takes

  1. 1

    Platform selection

    2–3 weeks

    Argued comparison and decision. Skipped if the platform is already chosen.

  2. 2

    Analysis and process design

    3–6 weeks

    We document the target process and fix the exact scope of the implementation.

  3. 3

    Configuration and development

    6–14 weeks

    We build the system to the agreed process, with a demo every two weeks.

  4. 4

    Data migration and testing

    3–5 weeks

    Repeated trial migrations and testing by real users on their own data.

  5. 5

    Training and go-live

    2–4 weeks

    Role-based training, cutover and on-site assistance.

  6. 6

    Stabilisation

    4–8 weeks

    Fixes, adjustments, and the first month-end closed in the new system.

What you supply

  • An internal project owner with authority to decide and at least 50% of their time allocated.
  • A key user from each department, for analysis and testing.
  • Exports from the current system: master data, balances, stock, history.
  • The process decisions that are yours to make — we cannot choose for you how a discount gets approved.
  • Availability for real testing before go-live, not just formal sign-off.

What it costs

We invoice by stage, at a fixed price per stage. After analysis the scope is known, and from there the price does not move unless you ask for extra work in writing.

Odoo, 5–15 users, standard modules

from€12,000

per project

8–12 weeks

Includes

  • Process analysis and configuration
  • Sales, purchasing, stock and accounting
  • Migration of master data and balances
  • e-Factura built into the flow
  • Role-based training and 30 days of post go-live assistance

Odoo, 15–50 users, with manufacturing or customisation

from€32,000

per project

4–7 months

Includes

  • Everything above, plus manufacturing or other additional modules
  • Up to three integrations with existing systems
  • Custom development where configuration cannot reach
  • History migration and repeated migration rehearsals

SAP Business One or S/4HANA

from€65,000

per project

6–12 months

Includes

  • Analysis, configuration and Romanian localisation
  • Data migration and integrations
  • Training and assisted go-live
  • Stabilisation through to the first year-end

Support and development after go-live

from€850

per user / month

Includes

  • Guaranteed incident response time
  • A monthly budget of hours for adjustments
  • Version and fiscal localisation updates

Indicative prices, excluding VAT, for our services. Odoo or SAP licences are paid separately, direct to the vendor, and their value is set out explicitly before you decide.

Configure an estimate

Frequently asked questions

What does an ERP implementation cost in Romania?+

For Odoo, from €12,000 for 5–15 users on standard modules and from €32,000 for 15–50 users with manufacturing or customisation. For SAP, from €65,000. Licences are paid separately, direct to the vendor. These prices are for our services and are confirmed after the analysis stage.

How long does an ERP implementation take?+

Eight to twelve weeks for a standard Odoo implementation on core modules, four to seven months once manufacturing or customisation is involved, and six to twelve months for SAP. Those timelines include data migration and training, not just configuration.

Odoo or SAP — which suits us?+

Odoo is the usual choice for companies up to roughly 200–250 users that want a complete system at a predictable cost. SAP earns its place in large companies, in industries with very strict traceability requirements, or where the shareholder mandates the platform. The selection stage answers exactly this question in writing, with five-year costs for each option.

What happens to the data in our current system?+

We migrate master data, balances and stock on every project; sales and document history depending on how useful it is to you and how clean it is. We run at least two rehearsal migrations before the real one, and the old system stays available for reference for an agreed period.

Do you cover e-Factura, e-Transport and SAF-T?+

Yes, and we treat them as part of the flow rather than a separate task. Invoices go to SPV automatically with a record of what was sent and what failed, e-Transport is generated at dispatch, and the data structure is prepared for SAF-T (D406) reporting.

What happens after go-live?+

We stay with you for a minimum of 30 days included in the project, which covers the first month-end close. After that most clients move to a monthly support and development contract from €850 a month — but it is not compulsory: the system is yours and anyone can maintain it.

Shall we talk about your project?

Thirty minutes, no obligation, at the end of which you know whether we can help and roughly what budget it takes.