Types of ERP systems: what's out there and how to choose one for your process

An ERP system is a single accounting and planning environment where finance, warehouse, purchasing, production and HR all work with the same data rather than with copies in different programs. ERP types are distinguished by four independent attributes. These are scope (a general-purpose platform or an industry package), delivery (a cloud subscription or your own servers), scale (one legal entity or a group of companies with consolidation) and origin (whether the product is listed in the Russian software register or not). The type is chosen based on which of the company's processes don't fit standard master data. The vendor's place in a ranking says little here.

Below we look at how each of the four forks works and what it will mean a year from now. What an industry package gives you and where it starts to get in the way. Why the cloud wins for mid-sized businesses and loses where the critical infrastructure law applies. What lies behind a register listing and what it does not promise. Why a system for a holding company and a system for a business with one warehouse break in different places. And what information about your own operations you need to gather before the first vendor demo.

What is an ERP system in plain terms?

In short: a shared database and shared rules for every department, instead of a set of programs that don't know about each other.

Whether you need one comes down to a single question: how many people does it take to answer "what is our stock of this item right now?" If the answer is pieced together from an export, a chat thread and the shift supervisor's memory, the data already lives in three places and the versions don't match. A single system removes that split: there is one record, and everyone who needs it for their role sees it.

That is also where the types come from. Different businesses need different depth: a plant cares about processing stages and cost of goods, a distributor about reservations and payment terms, a group of companies about consolidation across dozens of legal entities. No single product covers all of this equally well, which is why the market split into classes. We described the moment spreadsheets stop coping in a separate article, when a business should move off Excel.

How do I know whether my company needs ERP?

You need ERP when the company's data and processes are spread across several systems, reports are assembled by hand, and production, warehouse, purchasing and finance can't be linked quickly. Check for a single environment, duplicate data entry, reporting delays and limits on growth, then carry out a process audit.

Fragmented data

Departments keep records in separate programs, spreadsheets and exports, and staff reconcile stock and transactions by hand. This is a sign that there is no single information space.

Manual reporting

Management struggles to get costs, profit, stock levels or production status quickly. The more time it takes to assemble and check a report, the more concrete the ERP question becomes.

Limits on growth

Processes are getting more complex, the number of departments is growing, and the current systems can't support production or integrations. In this case ERP is evaluated against the company's actual exceptions.

What types of ERP systems are there?

In short: four attributes that combine almost freely, so a "type" is four answers, not one.

The vendor lists that fill search results collapse these axes into a single column and present an overall ranking of the best. Such a list has little practical value: the same platform is sold both as a subscription and for your own hardware, and an industry package is almost always built on top of a general-purpose one.

The register shows the size of the choice. According to Alexey Stoyanov, director of the competence center at the T1 group, as cited by CNews on January 9, 2026, the Unified Register of Russian Software, the official list that qualifies products for import substitution requirements, contains 234 products in the ERP class. The whole market for such systems is estimated at 110 billion rubles, and 70–80% of sales go to a single vendor. In other words, hundreds of products share roughly a fifth of the market's money.

Industry-specific or general-purpose ERP: what's the difference in practice?

In short: an industry package saves months at the start and takes away freedom later.

An industry product comes with a ready-made domain model. For food production that means batches and shelf lives, for metals processing stages and quality certificates, for distribution reservations, payment terms and returns. All of this is already named in the words your process engineers use, and the first phase goes noticeably faster.

The bill for that convenience arrives in year two. The process departs from the industry template in a couple of places, changes are written on top of someone else's logic, and every vendor update has to be re-tested. The further you have moved from the template, the more each new release costs.

A general-purpose platform works the opposite way: less ready-made logic, more work describing processes, but customization doesn't fight someone else's industry model. The rule of thumb is simple. If your process looks like your industry peers', take an industry package. If it is your competitive advantage, the template will have to be broken, and breaking someone else's costs more than building your own.

Demand for these projects is holding up in industry. K2Tech surveyed 150 respondents and conducted 15 in-depth interviews in machine building. According to the results published on July 29, 2026, 37% of companies named ERP and information security as their efficiency drivers: ERP is a priority for 20%, security for 17%. Software import substitution scored 14%, and shop-floor automation 11%.

Cloud or your own server: what changes financially and legally?

In short: the cloud removes infrastructure costs, and in some industries the law makes this choice for you.

The economics are quick to calculate. A subscription eliminates buying servers, database licenses and a full-time administrator, but ties you to the provider's pricing for years ahead. Your own environment needs money up front and people on an ongoing basis, but leaves you in control of availability and of where your customers' data physically sits.

The segment where the cloud wins has shifted in recent years. The Russian cloud services market grew by 24% in 2025, against 60% a year earlier. These are figures from the SaaS Rating led by Askar Rakhimberdiev, CEO of Lognex, the company behind MoySklad (a Russian inventory management service), reviewed by ComNews on April 24, 2026. In the same piece, Pyotr Vasilenko of Graftech describes the market's main shift: cloud services are moving from the enterprise segment into mid-sized and small businesses.

Large industrial companies often have no choice. Presidential Decree No. 166 of March 30, 2022 prohibited government bodies and contracting entities from running foreign software on the significant critical information infrastructure (CII) facilities they own from January 1, 2025. And under Government Order No. 360-r, in late February 2026 ERP systems were included in a unified list of 397 standard industry critical infrastructure facilities: telecoms, energy, petrochemicals, mining, metals and a number of other industries. For the system owner this adds categorization, certified security tools and continuous monitoring.

The practical conclusion for these industries: the choice between a subscription and your own environment is made together with an information security specialist, not on financial calculations alone. What can and cannot be handed to an external service under Federal Law 152-FZ, Russia's personal data protection law, is covered in our article on neural networks without data leaks.

What does a listing in the Russian software register give you?

In short: eligibility where import substitution is mandatory; a listing says nothing about whether the product suits your load.

The register answers the question of eligibility. Without a listing, a product can't be deployed where import substitution requirements apply: public procurement, state-owned companies, significant critical information infrastructure facilities. For a private company outside that perimeter, a listing is optional, though it is seen as insurance against the vendor leaving the market.

What the register doesn't promise is that the system will handle your transaction volume. This is clear from how slowly foreign products are being replaced where there is no formal ban. They remain at 25% of oil and gas companies, 24% in metals and 19% in machine building (T1 estimate, January 2026). Companies stay on what they have already invested in until replacement becomes mandatory or clearly profitable.

The market as a whole has hit the same logic. ANO NCC ISU, an industry competence center for enterprise management systems, estimates the Russian resource management systems market at 110 billion rubles as of early 2026; domestic products hold 75% of it, and that growth came from implementations launched in 2022–2024. The center's CEO, Kirill Semion, forecasts for 2026 that the market's nominal size will hold steady while the actual number of projects launched shrinks.

Is ERP for a holding company the same as ERP for a mid-sized business?

In short: no, and they break in different places.

A mid-sized company runs into functionality limits: missing batch tracking, cost calculation, sensible purchase planning. A holding company runs into architecture limits. ANO NCC ISU named the barriers on May 20, 2026 based on a survey of 11 corporations with combined revenue of 28.5 trillion rubles for 2024. About Russian systems, it says: "the architecture cannot handle the load of the largest holding companies, and complex transactional scenarios are not fully covered." It all comes down to the monolith: the system can't be scaled to a holding company's volume. Next to it on the list of barriers are limited functionality, insufficient module depth and high project costs.

The same source puts a national price on the issue: spending on ERP replacement in 2022–2025 is estimated at 90–130 billion rubles. Kirill Semion summed up the situation more briefly: "What took Oracle or SAP decades, we are trying to run through in five years."

What follows for the selection process is this. Read vendor case studies by load and group structure, not by industry: how many legal entities are in the system, how many concurrent users, how consolidation is assembled, what happens at month-end close. A company with one warehouse doesn't need these questions, and has no reason to pay for a holding company's safety margin. How to connect several systems when a single environment can't be built right away is covered in our article on systems integration.

How does the ERP type affect total cost of ownership?

In short: each fork is cheaper on one side at the start and more expensive on the other, and the question is when the bill arrives.

One cost item doesn't appear in any row of the table and is still larger than many of them: your employees' time. Describing processes, cleaning up master data and accepting project phases are done by people who are closing the month and shipping orders at the same time. How phases and costs break down in automation projects is shown in our piece on AI adoption in business.

Where do you start choosing an ERP type?

In short: with six answers about yourself, not with vendor demos.

Without these answers, every presentation looks equally convincing:

1. A described process with its exceptions. The way work actually happens, not a "how it should be" diagram: what happens with a return, a stock mix-up, an urgent shipment or an advance payment.
2. A list of exceptions in your master data. Items and counterparties that are not handled under the general rules. These are what decide whether an industry template will be enough.
3. Access to your own data. Exports of stock, orders, contracts and settlements in machine-readable form. If one person pulls this data out by hand, migration will become a separate project.
4. A list of integrations. Accounting system, bank, marketplaces, warehouse equipment, document management. Each connection means separate money and separate risk.
5. Access rights. Who sees cost of goods, who sees purchase prices, who sees employees' personal data. This is decided before design, because access rights affect the data structure.
6. An owner after launch and a support budget. A person inside the company with the authority to decide how the process works, and money to develop the system over a three-year horizon.

The first three items are about the business, not IT. They are also the ones most often skipped: comparing commercial proposals is more interesting than describing your own way of working. Which figures a finished system should give management every day is shown in our breakdown of management reporting.

When does an off-the-shelf solution fall short?

In short: when there is more customization than out-of-the-box logic, and this is visible already at the stage of choosing a type.

An off-the-shelf product sells you someone else's way of working. As long as your procedures, master data and access rights match the standard ones, it's a good deal: you pay for proven logic and don't pay for developing it. The mismatches start with exceptions: every company has its own discount approval process, its own reservation rules, its own incentive calculation and its own roles in document workflows. Configuration covers the first few mismatches; after that, changes are layered onto someone else's architecture, and the bill for every update grows.

A hybrid most often turns out to be the working answer. Statutory accounting lives on the platform, while the area that gives you an advantage is built separately and connected through data exchange. In our wholesale case that is exactly what we did: the accounting system was left untouched, and order processing with stock-based reservation moved into a separate environment with two-way data exchange. Orders began to be processed in minutes instead of hours, and accounting didn't have to move anywhere. We worked through this choice in detail in the article custom system or off-the-shelf product.

We work under contract, keep data in Russia and support the system after handover: we build ERP and CRM systems, integrations and AI agents around a company's specific process. Choosing an ERP type is a conversation about your specifics, not about vendor rankings: what exceptions sit in your master data, what the load is at month-end close, what the regulator requires of you. If that conversation is relevant for you now, tell us about your task, and we'll go through your processes and work out the options together.

Sources

• CNews, January 9, 2026. "Instead of SAP: who is moving to Russian ERP and how" — 234 ERP-class products in the Unified Register, shares of foreign systems by industry, estimates by Alexey Stoyanov (T1)
• CNews, July 29, 2026. K2Tech study of machine building — 150 respondents and 15 in-depth interviews, 37% on ERP and information security, breakdown of priorities
• CNews, May 20, 2026. Barriers to ERP import substitution according to ANO NCC ISU — survey of 11 corporations, the monolith and holding company load, spending of 90–130 billion rubles, quote from Kirill Semion
• CNews, April 9, 2026. ANO NCC ISU forecast for the ERP market — 110 billion rubles, 75% held by domestic products, 70–80% of the market held by one vendor, forecast for 2026
• ComNews, April 24, 2026. SaaS Rating — cloud market growth of 24% in 2025 against 60% in 2024, demand shifting to mid-sized and small businesses
• Presidential Decree of the Russian Federation No. 166 of March 30, 2022 — ban on foreign software at significant CII facilities from January 1, 2025
• CNews, March 30, 2026. ERP recognized as CII facilities — Government Order No. 360-r, list of 397 standard facilities, obligations of system owners