Types of ERP systems: what they are and how to pick one that fits your process

An ERP system is a single environment for accounting and planning, where finance, warehousing, procurement, production and HR work with the same data rather than with copies scattered across different programs. ERP types differ along four independent attributes. These are coverage (a general-purpose platform or an industry build), delivery (a cloud subscription or your own servers), scale (one legal entity or a group of companies with consolidated reporting) and origin (listed in Russia's domestic software registry or not). You choose the type based on which of your company's processes do not fit into the standard reference data. A vendor's position in a ranking says very little here.

Below is how each of the four forks works and how it will make itself felt a year later. What an industry build 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 registry entry and what it does not promise. Why a holding company's environment and a system for a company with one warehouse break in different places. And what facts about your own operations you need to gather before the first vendor demo.

What is an ERP system in plain terms?

Short answer: a shared database and shared rules for every department, instead of a set of programs that know nothing about each other.

One question shows whether you need such an environment: how many people are involved in answering "what is our current stock on this item right now". If the answer is assembled from a data export, a chat thread and the shift supervisor's memory, the data already lives in three places and the three disagree. A single environment removes that fork: there is one record, and everyone whose role requires it can see it.

The types grow out of this too. Different businesses need different depth: a plant cares about production stages and costing, 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 when spreadsheets stop coping separately — when a business should move off Excel.

What types of ERP systems are there?

Short answer: 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 one column and produce a general ranking of the best. There is little practical use in such a list: the same platform is sold both as a subscription and for your own hardware, and an industry build is almost always assembled on top of a general-purpose one.

The size of the choice is visible in the registry. The Unified Register of Domestic Software holds 234 products of the ERP class, according to figures from Alexey Stoyanov, director of the competence center at the T1 group, cited by CNews on January 9, 2026. The whole market for such systems is valued at 110 billion rubles, and a single vendor takes 70–80% of sales. In other words, hundreds of products split roughly a fifth of the market's money among themselves.

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

Short answer: an industry build saves months at the start and takes away freedom later.

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

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

A general-purpose platform works the other way around: less ready-made logic, more work describing processes, but customization is not fighting someone else's industry model. The guideline is simple. If the process looks like everyone else's in your industry, take the industry build. If the process is your advantage in the market, the template will have to be broken, and breaking someone else's is more expensive than building your own.

Demand for such projects holds up in industry. K2Tech surveyed 150 respondents and ran 15 in-depth interviews in mechanical engineering. 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%, shop-floor automation 11%.

Cloud or your own server: what changes in money and in law?

Short answer: the cloud removes infrastructure spending, and in a number of industries the law closes this fork for you.

The economics are quick to calculate. A subscription removes buying servers, database licenses and an in-house administrator, but ties you to the provider's pricing for years ahead. Your own environment demands money up front and people permanently, but leaves you in control of availability and of where client data physically sits.

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

Large industrial companies often have no choice. Presidential Decree No. 166 of March 30, 2022 barred government bodies and customers from running foreign software on the significant critical information infrastructure facilities they own from January 1, 2025. And Government Order No. 360-r, in late February 2026, added ERP systems to a single list of 397 standard industry-level critical infrastructure facilities: telecom, energy, petrochemicals, mining, metallurgy and several other sectors. For the system's owner, that adds categorization, certified security tools and continuous monitoring.

The practical conclusion for these industries: the "subscription or your own environment" fork is decided together with an information security specialist, not by a financial calculation 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 the article on using neural networks without leaking data.

What does a listing in the domestic software registry give you?

Short answer: admission where import substitution is mandatory; the entry says nothing about whether the product suits your workload.

The registry answers the question of admission. Without an entry, a product cannot be supplied where import substitution requirements apply: public procurement, state-owned companies, significant critical information infrastructure facilities. For a private company outside that perimeter the entry is optional, though people treat it as insurance against a vendor leaving the market.

What the registry does not promise is that the system will handle your transaction volume. That is clear from how slowly foreign products are leaving where there is no formal ban. They remain in place at 25% of oil and gas companies, 24% in metallurgy and 19% in mechanical engineering (T1 estimate, January 2026). Companies stay on what they have already invested in until replacement becomes mandatory or obviously worthwhile.

The market as a whole has run into the same logic. The NCK ISU non-profit values Russia's resource management systems market at 110 billion rubles as of early 2026; domestic products hold 75% of it, and that growth came from implementations started in 2022–2024. The center's CEO Kirill Semion forecasts for 2026 that the market's nominal size will hold while the real number of projects being launched declines.

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

Short answer: no, and they break in different places.

A mid-sized company runs into functionality: it lacks batch tracking, costing, coherent procurement planning. A holding company runs into architecture. NCK ISU named the barriers on May 20, 2026 based on a survey of 11 corporations with combined 2024 revenue of 28.5 trillion rubles. On Russian systems it puts it this way: "the architecture does not withstand the load of the largest holding companies, complex transactional scenarios are not covered in full." It all comes down to the monolith: scaling the system up to a holding company's volume does not work. Alongside in the list of barriers are limited functionality, insufficient module depth and the high cost of projects.

The same report names the price tag for the country: spending on ERP replacement over 2022–2025 is estimated at 90–130 billion rubles. Kirill Semion put the situation more briefly: "What took Oracle or SAP decades, we are trying to sprint through in five years."

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

How does the ERP type affect total cost of ownership?

Short answer: every fork is cheaper on one side at the start and more expensive on the other — the question is when the bill arrives.

One cost item fits none of the table's rows and is larger than many of them — your employees' time. Describing processes, cleaning up reference data and signing off on phases is done by people who are simultaneously closing the month and shipping orders. How phases and costs break down in automation projects is shown in the piece on adopting AI in business.

Where do you start when choosing an ERP type?

Short answer: with six answers about yourself, not with vendor demos.

Without these answers, every presentation looks equally convincing:

1. A documented process including exceptions. How work actually happens, not a "how it should be" diagram: what happens on a return, a mis-shipment, a rush delivery, a prepayment.
2. A list of exceptions in the reference data. Items and counterparties that are not accounted for under the general rules. They are exactly what decides 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 extracts this data by hand, migration will become a project of its own.
4. A list of integrations. Accounting system, bank, marketplaces, warehouse equipment, document workflow. Each connection is separate money and a separate risk.
5. Access rights. Who sees cost price, who sees purchase prices, who sees employees' personal data. This is decided before design, because rights affect the data structure.
6. An owner after go-live 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 points are about the business, not about IT. They are also the ones most often skipped: comparing commercial proposals is more interesting than describing how you actually work. Which numbers a finished environment should deliver to a manager every day is covered in the breakdown of management reporting.

When does an off-the-shelf solution fail to cover the task?

Short answer: when there is more customization than out-of-the-box logic — and that is visible while you are still choosing the type.

An off-the-shelf product sells you someone else's model of how work is done. While your regulations, reference data and access rights match the standard ones, the deal is a good one: you pay for proven logic and do not pay to develop it. The divergences start with exceptions — every company has its own discount approval flow, its own reservation rules, its own bonus calculation and its own roles in document workflow. Configuration covers the first few divergences; after that the changes sit on someone else's architecture, and the bill for each update grows.

A hybrid most often turns out to be the workable answer. Regulatory accounting lives on the platform, while the area that gives you your advantage is built separately and connected by data exchange. In our wholesale case we did exactly that: the accounting system stayed untouched, and order processing with stock reservations moved to a separate environment with two-way exchange. An order started taking minutes to process instead of hours, and accounting did not have to move anywhere. We covered the fork between an off-the-shelf product and a system built around your own process separately — custom system or off-the-shelf.

We work under contract, keep data in Russia and support the system after handover: we build ERP and CRM environments, 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 the exceptions in your reference data are, what the load is at month-end close, what the regulator requires of you. If that conversation is relevant right now — tell us about the task, and we will walk the processes and cost the options side by side.

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 from Alexey Stoyanov (T1)
• CNews, July 29, 2026. K2Tech study on mechanical engineering — 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 NCK 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. NCK ISU forecast for the ERP market — 110 billion rubles, 75% held by domestic products, 70–80% of the market with a single vendor, forecast for 2026
• ComNews, April 24, 2026. SaaS Rating study — cloud market growth of 24% in 2025 against 60% in 2024, demand shifting to mid-sized and small business
• Presidential Decree No. 166 of March 30, 2022 — ban on foreign software at significant critical infrastructure facilities from January 1, 2025
• CNews, March 30, 2026. ERP recognized as critical infrastructure facilities — Government Order No. 360-r, list of 397 standard facilities, obligations of system owners