In short
ERP stands for Enterprise Resource Planning and refers to centralized business software that maps a company's key business processes in one coherent system. This typically includes merchandise management and warehousing, purchasing, sales, financial accounting, production and often human resources.
The aim of an ERP system is to connect these areas on a common database, so that information is recorded only once and used consistently throughout the company.
ERP meaning: what is enterprise resource planning?
In plain terms, enterprise resource planning means planning and controlling all of a company's resources – goods, money, staff, machines and time – in one system instead of in many separate tools. The ERP is the operational backbone: it knows what is in stock, what has been ordered, what has been invoiced and what is still open. Other systems such as the online shop, the CRM or a customer portal draw on this data or report back to it.
The term grew out of manufacturing. Its predecessors were MRP (material requirements planning) and MRP II (manufacturing resource planning), which calculated material needs and production capacity. Around 1990 the analyst firm Gartner coined the term ERP for systems that extended this approach to finance, sales, purchasing and HR. Today the term covers everything from industry-specific packages for a few dozen users to global suites for corporate groups. People sometimes search for an "enterprise resource planner"; the established term is ERP system or ERP software.
Why companies use an ERP
Without a central system, companies often maintain the same data several times in separate stand-alone solutions: stock in one spreadsheet, invoices in another program, customer master data somewhere else. This leads to duplicate work, inconsistencies and errors. An ERP creates a single source of truth: an order, a stock level or a customer record exists exactly once and is up to date for every department that needs it. That makes processes faster, more traceable and easier to plan.
A second reason is control. Because purchasing, sales and accounting work on the same data, management can see margins, open items and stock turnover without first merging exports. Many legal obligations, such as orderly bookkeeping and retention of business documents, are also easier to meet when every transaction runs through one system.
Core modules of an ERP system
An ERP system is usually built from modules that a company licenses and activates as needed. The names differ between vendors, but the building blocks are similar:
- Finance and accounting: general ledger, accounts payable and receivable, cost accounting, payment runs and financial reporting.
- Merchandise management and warehousing: stock levels per warehouse and storage location, goods receipt and issue, stocktaking, batch and serial numbers.
- Purchasing: suppliers, purchase orders, order proposals based on stock and demand, supplier prices and conditions.
- Sales and order management: quotations, orders, delivery notes, invoices, credit notes and customer-specific prices and discounts.
- Production: bills of materials, work plans, production orders and capacity planning – the original MRP core.
- Human resources: staff master data, working time and, depending on the system, payroll.
- Reporting: evaluations across all modules, from daily sales figures to margin analysis.
Some systems also include CRM functions, service management or document management. Whether these are good enough or whether a specialized tool is the better choice depends on how central the respective process is for the business.
How an ERP system works
At the heart of every ERP are two kinds of data. Master data describes things that change rarely: articles, customers, suppliers, prices, bank details. Transaction data records what happens: a quotation becomes an order, the order triggers a picking list, the delivery note leads to an invoice, the invoice to an open item and finally to a payment. Each step builds on the previous one and references it.
Because all modules write to the same database, one business event updates every affected area at the same time. When a customer order is shipped, the stock falls, the revenue appears in sales reporting and the receivable appears in accounting – without anyone typing the data in again. This document chain is what distinguishes an ERP from a collection of individual tools.
Types of ERP systems and deployment models
ERP systems can be distinguished by their scope and by how they are operated.
- Standard ERP vs. industry solution: general-purpose systems cover the typical processes of many industries and are adapted by configuration. Industry solutions bring specific processes out of the box, for example for bicycle retail, food production or wholesale.
- On-premise: the company runs the ERP on its own servers or in a data center it controls. This offers maximum control but requires its own operations, updates and security.
- Cloud/SaaS: the vendor operates the system and provides it as a subscription. Updates arrive regularly, but individual adaptations are more limited.
- Hybrid and two-tier ERP: larger groups often combine a central ERP at headquarters with leaner systems in subsidiaries, or keep parts on premise and parts in the cloud.
Whether to adapt a standard product or build parts yourself is the classic make-or-buy question; the trade-offs are described under off-the-shelf software and custom software.
Widespread ERP systems
Different systems are common in mid-sized and enterprise businesses, including SAP (for example SAP Business One or S/4HANA), Microsoft Dynamics 365, Sage, abas, Proalpha, Odoo and Oracle NetSuite, alongside numerous industry-specific and sometimes in-house solutions. The systems differ greatly in scope, flexibility and the quality of their interfaces. The interfaces in particular are often the decisive factor when the ERP has to work with other systems.
ERP vs. CRM, PIM and WMS
ERP is often confused with neighbouring systems. Each has its own focus, and in larger setups they work together:
| System | Main question | Typical data |
|---|---|---|
| ERP (enterprise resource planning) | What do we buy, stock, sell and invoice? | Articles, stock, prices, orders, invoices, accounting |
| CRM (customer relationship management) | How do we win and look after customers? | Contacts, leads, opportunities, activities, campaigns |
| PIM (product information management) | How do we describe our products in every channel? | Descriptions, attributes, images, translations |
| WMS (warehouse management system) | Where exactly is each item and how is it picked? | Storage bins, picking routes, scanner movements |
As a rule of thumb: the ERP is responsible for commercial truth (what something costs and how much of it is available), the PIM for product content, the CRM for the customer relationship before and after the sale. For product data in particular, a PIM in front of the shop often pays off; see our e-commerce PIM.
ERP and e-commerce
For retailers and manufacturers who sell online, the connection between ERP and web shop is particularly important. Stock levels, prices, orders, customer and invoice data must flow reliably between both systems. If this connection is weak or only runs via nightly imports, the result is outdated stock, overselling and manual rework. A clean, preferably event-based ERP integration ensures that stock changes reach the shop immediately and incoming orders land in the ERP without anyone typing them in.
| Data object | Usual direction | Note |
|---|---|---|
| Articles and variants | ERP → shop (often via PIM) | Commercial data from the ERP, marketing content from the PIM |
| Prices and discounts | ERP → shop | In B2B including customer-specific and tiered prices |
| Stock levels | ERP → shop | As close to real time as possible to avoid overselling |
| Orders | Shop → ERP | Including payment and shipping method |
| Order status, tracking, invoices | ERP → shop | So customers see the status in their account |
| New customers | Shop → ERP | Existing B2B customers are often created in the ERP first |
In B2B, the ERP usually holds even more of the logic: customer-specific price lists, credit limits, payment terms and framework agreements. A B2B shop that ignores this information shows wrong prices or accepts orders that accounting later has to stop. That is why B2B projects start with the question of which ERP rules the shop has to respect; more on this on our Shopware B2B page.
The question of the leading source
With every ERP integration it has to be clarified early which system is the leading source for which data object. "Both" is not a viable answer, because otherwise contradictory states arise depending on the order of the write operations. It is common and proven practice for stock and prices to come from the ERP, while customer and order data are created in the shop and flow from there into the ERP. This clear division prevents conflicts and keeps the data consistent.
Architecture of an ERP connection
Robust integrations do not couple ERP and shop directly at database level but via a dedicated integration layer with a clear adapter for each system. This layer translates between the data models and decouples the systems, so that an ERP update, for example, does not immediately put the shop at risk. Lightweight message brokers or the webhook mechanisms of modern platforms such as Shopware 6 are often used, together with documented REST APIs on the ERP side. The result is a maintainable connection that stays stable as volumes grow. In practice we have connected shops to very different systems, for example DiVA and DiVA BC at Bike Discount, the CDH merchandise management system at Suthor and ERP plus PIM at Mellerud.
How to choose an ERP system
An ERP selection binds a company for many years, so the decision deserves a structured process. These criteria have proven useful:
- Process fit: write down your core processes first and check how many of them the system covers in the standard. Every adaptation increases costs and update effort.
- Interfaces: check whether the system offers documented APIs for the shop, PIM, CRM, shipping and banking. Missing or proprietary interfaces are the most common reason for expensive special solutions.
- Total cost of ownership: compare not only license prices but also implementation, operation, updates, internal effort and a later exit. The method is described under total cost of ownership (TCO).
- Scalability: more users, more locations, more countries and currencies – check what changes technically and commercially.
- Partner ecosystem: most ERP systems are implemented by partners. Their experience in your industry often matters as much as the software itself.
- Deployment: decide early between on-premise, cloud and hybrid, including the question of where the data is stored.
A written requirements specification makes vendor offers comparable and prevents the selection from being decided by the best demo rather than the best fit.
Introducing an ERP: phases and pitfalls
ERP projects typically run through analysis, selection, configuration, data migration, testing, training and go-live. The technical work is rarely the biggest risk. Projects more often stall because processes were not clarified before configuration, because master data is migrated without cleaning it up, or because key users have too little time alongside their daily work. Old customizations that nobody can explain anymore are a further source of technical debt; a new ERP is a good opportunity to drop them instead of rebuilding them.
For online retailers, the shop connection belongs in the project plan from the start. If the ERP changes but the integration is only adapted at the end, the shop goes live with gaps – or the ERP launch has to wait for the shop.
ERP as the foundation of digitalisation
A well-integrated ERP is often the foundation of further digitalisation projects. Customer portals, automated quotation generation or document management rely on ERP data and only deliver their benefits when this data is clean and up to date. If you want to digitalise processes, check early how accessible and reliable the data in your own ERP is – it is often the lever on which many follow-up projects depend.
Frequently asked questions about ERP
What does ERP stand for?
ERP stands for enterprise resource planning. It describes software that plans and controls a company's resources – goods, money, staff and capacity – in one integrated system.
What is an ERP system used for?
To run the operational core of a business: purchasing, warehousing, sales, invoicing, accounting and, in manufacturing, production. Its main benefit is that every department works on the same, current data.
Is an ERP the same as accounting software?
No. Accounting is one module of an ERP. Accounting software alone does not know stock levels, purchase orders or production orders; an ERP links these processes with the financial side.
When does a business need an ERP?
Typical signals are data maintained several times in different tools, stock figures nobody trusts, manual transfers between shop and accounting, and growth that the existing tools can no longer handle. The right time is before these workarounds become the actual process.
Can an online shop be connected to an ERP?
Yes. Modern shop systems such as Shopware 6 offer APIs and webhooks for this, and most ERP systems provide interfaces or connectors. What matters is a clear definition of which system leads for which data and a robust integration layer in between. See our ERP integration service for how we approach such projects.