ERP system — what it is, when a small business needs one and what it really costs

An ERP system is usually bought like a program: you compare modules, prices and screenshots. Yet ERP is first and foremost an organisational decision. The decision that sales, the warehouse, purchasing and finance stop keeping their own lists and start writing to a single database, which from then on is the source of truth. The order, the stock level and the invoice become one record seen from three sides, not three copies that somebody reconciles every week.

If that decision makes sense for your company, the software will be found. If it doesn't, the best system in the world won't fix anything.

We write this from a specific position: we don't sell ERP and we don't implement it. We integrate with it — the online shops, forms and applications our clients already have. So we see ERP from a side that isn't in the vendors' brochures: from the side of the data that has to go into it and come out of it. Below: what an ERP system is, when a small business needs one and when it doesn't, and what the things you won't find in the price list cost.

What is an ERP system

An ERP system (enterprise resource planning) is software in which sales, stock, purchasing, production and finance work from one shared database. When a salesperson takes an order, the warehouse immediately sees the goods reserved, and accounting sees the invoice to come. Nobody copies anything, because everyone is looking at the same record.

That is the core of the answer to "what is ERP", and to the ERP meaning people search for. The rest is the list of modules that typical ERP software is made of:

• sales — quotes, orders, price lists, discounts, invoices;
• stock and logistics — stock levels, goods in, goods out, stocktaking, several warehouses;
• purchasing — orders to suppliers, receiving goods, purchase invoices;
• finance and accounting — receivables and payables, payments, the ledger, tax returns;
• production — bills of materials, work orders, material consumption (only for companies that manufacture);
• HR and payroll — in many systems a separate module.

Not every company needs all of them. A wholesaler can live without production, and a service company without a warehouse. That is why ERP solutions are usually sold by module, and you pay for the ones you use. "ERP program", "ERP software" and "ERP system" mean the same thing in practice — the difference is one of scale, not of idea: a small program for a wholesaler and a system for a group of companies rest on the same principle of one database.

ERP software vs accounting software, MRP and CRM

What is an ERP system, then, as a class of software? Calling something "an ERP system" means exactly that: software that connects several areas of the company in one database. Accounting software isn't in that class, because it deals with one area — recording what has already happened, meaning invoices, costs and taxes. ERP starts earlier: with the order, the reservation of goods and the purchasing plan, and accounting receives finished documents from it.

MRP (material requirements planning) means working out what materials are needed: how much raw material to buy, and when, to produce the goods that have been ordered. Historically, ERP grew out of systems like this, and today MRP is usually one of the production modules in a larger system.

A CRM handles the relationship with the customer before and after they buy: enquiries, conversations, quotes, reminders. An ERP handles what happens once the order is placed. We go into the difference in more detail in our article on ERP vs CRM and how to choose a CRM for a small business.

How many companies use ERP — Poland vs the EU

According to GUS (Statistics Poland, Główny Urząd Statystyczny), "Use of information and communication technologies in enterprises and households in 2025" (Wykorzystanie technologii informacyjno-komunikacyjnych w przedsiębiorstwach i gospodarstwach domowych w 2025 r.), table 12, in 2025 40.5% of Polish enterprises with at least ten people used ERP software. For comparison, the EU average is 46.45% (Eurostat). The average hides the most important thing, which only the breakdown by company size shows:

Polish medium-sized companies are exactly at the EU level, large ones clearly above it. The whole gap sits in small companies: 32.9% against 41.08%. The GUS tables show that close to 60,000 small enterprises work without an ERP. Companies with fewer than ten people aren't covered by the survey at all.

The same tables show a second thing: ERP is above all a tool for companies that sell from stock or manufacture. In wholesale trade 56.0% of enterprises use it, in manufacturing 42.8% and in construction 28.9% — counting companies of all sizes together.

What follows from this? Not that a small company "should catch up". Two thirds of Polish small firms work without an ERP, and some of them rightly so. What follows is a question worth answering honestly: have we reached the point where separate lists cost more than one system would? That is what the next part is about.

Does a small business need an ERP?

A small business needs an ERP when the same information — about an order, goods or a payment — has to be up to date in several places at once, and today somebody keeps it that way by hand. Headcount matters less here than people think. What counts is how many times a day you copy data from one program into another.

These are the signals that show it:

You hold stock, and the numbers don't match. A customer orders goods you no longer have, because sales in the shop, on the phone and through a sales rep don't see the same stock levels. Every quarterly stocktake uncovers differences nobody can explain.

You manufacture. Even simple production needs to know how much material was used, how much is on its way and what has to be bought before the next job. A spreadsheet copes with a few products; with several dozen it starts to lie.

You sell through several channels. An online shop, a marketplace, wholesale, a physical outlet. Each channel has its own orders, but the goods are the same. Without a shared database, somebody copies orders from one system to another or reconciles stock at the end of the day.

Somebody retypes data by hand. The order from an email into the sales program, the invoice from the sales program into accounting, stock levels from a spreadsheet into the shop. Every retyping costs time and is a chance for a mistake, and when that person is on holiday, the process stops.

When accounting software is enough. If you run a service business, hold no stock, and your sales come to a dozen or a few dozen invoices a month, an ERP would be an expensive superstructure over a problem you don't have. Good invoicing and accounting software that handles KSeF (Krajowy System e-Faktur, the National e-Invoicing System) is enough — purchase invoices then arrive in a structured form, and part of the work disappears by itself. How to make use of that is covered in our article on business process automation. For customer conversations add a CRM, and for the rest, individual tools.

Between accounting software and a full ERP there is an intermediate step that is easy to forget: trading and inventory software. It handles sales, stock and invoices, while the bookkeeping is done by an external accountant in their own program, which the documents reach by export. For many small shops and wholesalers, that is enough for years. It is worth moving to a full system only once production, several warehouses or several sales channels are in play, all needing to see the same stock at the same moment.

If you recognise one signal, it is usually enough to sort out that one area. If you recognise two or three — and they concern goods that pass through sales, the warehouse and accounting — this is exactly the moment the GUS figures point to, when ERP for small business stops being overkill.

One all-in-one system or connected modules?

Anyone looking for an ERP faces a choice that vendors rarely spell out. You can buy one system with modules — sales, stock, accounting and HR from one vendor, on one database. Or you can put together a set of separate programs — accounting, a CRM, an inventory program, an online shop — each the best at its own job, joined by integrations.

On the market, three groups of products are easy to tell apart. We don't rank them, because the choice is decided by your process, not by the brand:

• trading and inventory software for small businesses — sales, stock and invoices, for example Subiekt, Wapro Mag or Comarch ERP Optima: often with an accounting module, installed locally or available in the cloud;
• modular ERP systems for medium-sized and larger companies — for example Comarch ERP XL, Symfonia ERP or SAP Business One: more modules, production, many warehouses and branches, usually implemented by a vendor's partner;
• cloud ERP — systems in the browser, on a subscription, without a server of your own; many vendors in the other two groups now also offer a version like this.

One system gives the most where the areas are tightly interwoven: an order reserves goods, a dispatch from the warehouse creates an invoice, the invoice goes straight into receivables. Nothing needs synchronising, because there is nothing to synchronise — the data sits in one place. The price is a compromise: the CRM module in an ERP is rarely as convenient as a separate CRM, and an online shop from an ERP vendor is rarely as flexible as a dedicated e-commerce platform.

Connected modules give freedom: each department works in a tool suited to it, and replacing one doesn't mean replacing everything. The price is integrations. Every connection has to be built, tested and maintained, and when one program changes the way it exchanges data, the connection has to be fixed. We know this side of the bill from our own work: in our online shop calculator, ERP integration is flagged as "often the biggest hidden cost — budget separately".

A simple rule follows. The more data passes between areas every day, the more one database pays off. A wholesaler where every order touches stock, a reservation and an invoice will benefit from one system. A company where sales and accounting meet once a month over an invoice will manage with two programs and one connection. In practice, many small companies choose the middle way: trading and inventory software as the core, with the online shop and the CRM connected to it by integration. In what order to build such connections, and how to decide which system owns which data, is a question we work through with every client who connects a shop to an ERP.

What an ERP system costs — the things that aren't in the price list

"How much does an ERP system cost?" has two answers. The first is in the vendor's price list. The second — usually bigger — is in the items the price list doesn't contain. The total cost has five parts.

1. Licence or subscription. This is the only item some vendors publish. An example from the Comarch ERP Optima price list, in the subscription variant for companies, as of 22 September 2026: the Logistyka (Logistics) Basic module costs PLN 75 net a month per seat, Finanse (Finance) Basic PLN 50 and CRM PLN 50. Just two modules, Logistics and Finance, on three seats come to PLN 375 net a month, or PLN 4,500 net a year. We quote only prices we could read in a published price list. Prices of other programs for small companies, such as Subiekt or Symfonia, appear in calculators on the vendors' sites or in an offer from a reseller rather than as price-list text, so we don't quote them; for modular systems, ask the vendor or its partner for a quote covering the modules and users you need.

2. Implementation. Configuring the system to your processes: warehouses, document types, price lists, permissions, print templates. In small trading and inventory software this is sometimes a few days' work; in a modular ERP, it is a project run by the vendor's partner. Vendors don't publish these rates in their price lists.

3. Data migration. Product and customer records, opening stock, open receivables and payables. The data has to be extracted from old programs and spreadsheets, cleaned and loaded. The formats involved — CSV, XML or an API — and the order of work are something to settle with whoever does the migration before the first file is exported.

4. Training. The time of people learning the new program, who in the first weeks work more slowly than in the old one. It is a cost that doesn't appear on an invoice, but it is in every implementation.

5. Integrations. This is the item we know best, because it is our work. In our [online store cost calculator](pages:69b1d28de5961b9519f27fbc), integrating an online shop with an ERP — for example with Subiekt or WF-Mag — costs PLN 12,000. Maintaining it, in our [website maintenance cost calculator](pages:69bfe4f90d5d51379c34259c), is PLN 120 net a month. Why that much? We wrote it into the calculator configuration: synchronisation needs two-way data mapping — orders go to the ERP, stock levels come back to the shop — and each ERP vendor uses a different API or file protocol, so a connection like this is rarely reusable from one project to the next. Maintenance is a separate item because the connection has to be watched whenever one side changes the way it exchanges data.

Put those numbers side by side. A one-off integration costs more than two years of the subscription for two modules on three seats from the example above (PLN 12,000 against PLN 4,500 a year). That doesn't mean the integration is a waste or that the ERP is cheap. It means that an ERP budget worked out from the price list alone is understated whenever the ERP has to talk to an online shop, a marketplace or an application.

ERP implementation — where it goes wrong

Plenty of failure statistics circulate about ERP implementations. We don't quote any, because none of them can be reliably checked. What our integration work does show is where an ERP implementation starts to fall apart. It is almost always the same three places.

Messy master data. An ERP is only as good as the data that goes into it. The same product recorded three times under different names, a customer with two VAT numbers, units of measure sometimes in pieces and sometimes in packs, stock levels nobody has confirmed with a stocktake. A new system doesn't tidy this up by itself — it moves the mess to the place where it becomes official. In an integration we see it immediately: the shop and the ERP have to agree on one identifier for each product, and if the product records contain duplicates, the connection either stops or sends out wrong stock levels. Cleaning the data has to be planned before the implementation, not after.

Blurred ownership of the process. Every process in an ERP — taking an order, dispatching goods, closing the month — needs one person who decides how it should run and is responsible for making sure its data is right. When there is no such person, decisions are made by the implementation consultant, or by nobody. The system then reflects somebody's idea of the company, not the company. The simplest test: for each module, ask who in your company will say "yes, this is how it should work" and who will notice when it stops working. If the answer is "the team" or "everyone", it means nobody.

Tailoring everything from day one. It is tempting to rework the system straight away so that it behaves exactly like the current way of working, exceptions and habits included. That is usually a mistake. The standard process in a mature ERP has been tested in many companies and often turns out better than a local workaround that survived only because nobody questioned it. A more sensible order: first run the standard, work with it for a few weeks, and only then change what really gets in the way. Every change made in advance is a cost at implementation and at every update after it.

Integrations belong in that plan from the start, not at the bottom of the list. If the ERP is to take orders from an online shop, the format of those orders and the product identifiers have to be agreed together with the product records — otherwise the connection is built on data that will change in a month.

Cloud ERP or on your own server

An ERP can run on a server in the company or as a service in the browser. The choice comes down to three things.

Access. A cloud ERP works wherever there is an internet connection: from the office, the warehouse, home, or a sales rep on the road. A system on your own server needs remote access, which somebody has to set up and secure.

Updates. In the cloud, the provider updates the system — new tax-form templates or KSeF changes reach you without any work on your side. On your own server, updates are installed by someone in-house or by a service company, and every customisation of the system makes the next one harder.

Backups. In the cloud, the provider makes the backups, and you check in the contract how often and for how long they are kept. On your own server, backups are your responsibility — and your risk, if nobody checks that the data can actually be restored from them.

There is a fourth matter too: leaving the provider. With a cloud ERP, the data sits with them. Since 12 September 2025 the EU Data Act (Regulation 2023/2854) has applied, and it covers software delivered as a service too. The contract with the provider must set a notice period for starting a switch of no more than two months, a transition period of up to 30 days, and an exhaustive specification of the data that can be exported (Article 25(2)). From 12 January 2027, the provider may not charge for the switch itself (Article 29). With an ERP this matters, because it holds the whole history of sales, purchasing, receivables and payables. Before you sign, check in what format you will get the data and whether that includes documents, not just master records. This is a description of the rules, not legal advice — go through the scope of the export in the specific contract with a lawyer.

Where to start

Not with choosing a program. Start with a sheet of paper on which you write down two things.

Processes. How an order runs in your company from being taken to being paid: who takes it, where they record it, who dispatches the goods, who issues the invoice, who chases the payment. At each step, mark where data is retyped by hand.

Data. What master records you have — products, customers, price lists, stock — in which programs and spreadsheets they live, and which version is the true one when they differ.

That sheet often answers the question of whether you need an ERP by itself. If the manual retyping happens in one place, one connection is enough. If it happens in five, it is worth talking to ERP vendors and handing them the sheet as a starting point. If your process is unusual enough that no off-the-shelf system will handle it, work out whether a tool of your own would pay off — we cover that in our article on off-the-shelf versus custom software, and the cheaper middle way in our article on low code and no code.

If you already have an ERP, or are choosing one right now, and need it to talk to an online shop, a form or an application — that is our part of the job. See how we approach it: custom software development and ERP integrations. For the wider picture, which business software solves which problem, see our guide to business software.

Where these figures come from

• Share of companies using ERP in Poland — GUS, "Use of information and communication technologies in enterprises and households in 2025", table 12; enterprises with at least 10 people.
• Share of companies using ERP in the EU — Eurostat, Statistics Explained, "E-business integration", 2025 data, extracted in May 2026.
• Comarch ERP Optima prices — the price list on comarch.pl, subscription variant for companies, read on 22 September 2026, net prices.
• Integrating an online shop with an ERP and maintaining it — our online store and maintenance cost calculators, as of 22 September 2026.
• Rules — Regulation (EU) 2023/2854 (Data Act), Articles 25 and 29.