The 10 Most Common Problems with Old ERP Systems, from 500+ Conversations

An old ERP system rarely feels broken overnight. It creeps in: a spreadsheet here, a manual reconciliation there, a workaround that becomes a permanent fixture. Eventually someone on the team puts the question everyone’s been thinking on the table: "Why are we still doing it this way?"

Across 500+ conversations with retailers in the DACH region, the same patterns show up year after year. Whether it’s e-commerce, multichannel retail, or a producing midmarket business, the problems that trigger an ERP switch boil down to ten themes.

This article is for you if you own an ERP decision or are preparing for a switch. You get the ten most common triggers in order, with what they mean day-to-day and a clear direction for a solution. At the end, we show the pattern behind all ten.

Data source: 500+ qualified first-time conversations with retailers in the DACH region from 2024 to 2026, categorized by the main problem each named. The order in the article follows how often the topic came up as the central pain point.

What connects the ten topics: as soon as retailers name them clearly, the switch isn’t far off. These problems are triggers, not just symptoms. Saying them out loud means you’re ready to change something.

1. Manual processes eat the time you need for growth 

By far the most common topic. In 8 of 10 cases, manual work is on the table as the main issue.

The symptoms repeat. Orders get typed into the ERP by hand from the shop or marketplace. Delivery notes land on paper in the warehouse. Payments get ticked off in online banking and assigned one at a time. Excel sheets grow unchecked because the ERP can’t answer the question.

What this means in your business: Manual work is expensive, error-prone, and makes growth impossible. Every new sales channel, every new marketplace, every new hire enlarges the manual block instead of dissolving it. At some point, the payroll line is the only lever you have left.

What helps: A modern ERP takes the recurring entries off your plate. Order import, document creation, shipping labels, payment reconciliation, and warehouse bookings run without a human in between. What matters isn’t "as much automation as possible" but automated flows that fit your process.

2. Inventory and warehouse without real-time data costs margin 

The second classic (7 of 10 retailers). Poor inventory management shows up in almost every other conversation. The ERP doesn’t know what’s in the warehouse. Or it knows it too late.

The consequences run through the whole business. Oversells in shop and marketplace. Search time in the warehouse because locations aren’t recorded. Inventory counts that take days. Reorder recommendations based on gut feel instead of consumption data.

What this means in your business: Inaccurate inventory is doubly expensive. You tie up capital that doesn’t know it’s sitting with you, and you lose sales at the same time because you artificially list items short. At higher revenues, the gap between system and reality gets exponentially more expensive.

What helps: Warehouse locations, a scanner process, and an ERP that books every intake and outflow in real time. Inventory in the shop, on Amazon, in accounting, and in the warehouse has to come from the same source. Once that’s in place, inventory counts, reorder recommendations, and shipping can be automated cleanly.

3. Missing reporting makes decisions a coin flip 

A topic that comes up in every second conversation. It matches the first point: if you work manually, you don’t have data. If you don’t have data, you’re flying blind.

Three patterns repeat: standard reports that don’t reflect the business. Dashboards that don’t exist. Analyses that cost several days of Excel work before the numbers add up.

What this means in your business: Without clean reporting, you make decisions on feelings. Which channel performs? Which SKU brings margin, which only brings revenue? Where is the next hire worth it? These questions need numbers, not guesses.

What helps: An ERP that keeps all business data in one place. Orders, inventory, purchasing, accounting, and marketing channels run into the same data model, so reports get pulled instead of built by hand.

4. Broken links between ERP, shop, and accounting cost more than any license 

A pattern that comes up in every second conversation: islands instead of one system. Shop, accounting, warehouse, and CRM don’t talk to each other. Employees are the human bridge. Data gets copied back and forth. Errors happen right there.

What this means in your business: Every interface you have to maintain yourself is a weak point. It breaks on updates, it produces duplicate data, it forces teams into workarounds. What first looks like flexibility becomes technical debt over time.

What helps: An ERP with maintained, documented integrations to the systems you use. At Xentral, that’s over 200 connections out of the box, from Shopify, Shopware, and Amazon to DATEV and Lexware to DHL, DPD, and Mollie. Custom-built connectors stay the exception, not the rule.

5. Weak shop and marketplace connections block growth 

Almost 4 of 10 retailers talk about issues at the interface to their online business. This is the more specific sibling of point 4. Anyone selling multichannel knows the pattern.

Orders from Amazon, Shopify, or TikTok Shop don’t land in the ERP automatically. Inventory syncs at the pace of minutes rather than seconds. Marketplace fees, promotions, and discounts arrive in accounting wrong or not at all.

What this means in your business: Orders that trickle into your ERP one at a time are lost hours. Inventory that lags means oversells, and that puts your marketplace accounts at risk. On Amazon, it costs you Prime status.

What helps: Marketplace integration as a required feature of your ERP, not an add-on. Real-time inventory, automatic order import, clean mapping of fees and promotions into accounting.

6. Complex processes and poor usability slow the team down 

One in five retailers says it directly: the current system is too complicated. New hires need weeks before they’re productive. Existing employees build Excel sheets to bypass ERP tasks. Functions exist, but nobody can find them. Other functions get used even though they were built for something else.

What this means in your business: Software the team can’t operate isn’t software; it’s a mortgage. It makes onboarding expensive, errors more likely, and frustration a permanent mood.

What helps: Take usability seriously before you sign the contract. Test trial phases with real employees. Browser-based instead of installed client. Clear workflows instead of a configuration jungle.

7. Missing scalability blocks the next growth step 

A rarer but especially urgent topic. Anyone who wants to grow and notices the system can’t keep up usually has a clear budget too.

Typical triggers: a tenfold order volume the architecture can’t support. A planned international expansion with Pan-EU shipping that can’t be mapped in the current system. A new marketplace that would take another six months of project work.

What this means in your business: An ERP that just barely supports your current size becomes a brake tomorrow. Scaling rarely fails at sales; it fails at the processes that have to run in the background.

What helps: A cloud-based ERP that grows with you. Multi-tenant capability, multi-currency, multi-warehouse, and marketplace standards from day one, so the next channel is a configuration, not a project.

8. Legacy systems without maintenance are a risk, not a savings play 

A recurring pattern at 1 in 7 retailers: the current ERP isn’t being developed further, or it hangs on a single external developer. The list of named systems is long. All share one trait: technical debt that compounds with every year.

Some vendors discontinue the product. Others don’t respond to support requests for months. Updates arrive, break your customizations, and cost days every time. The one programmer who knows the system is the biggest weak point and the only pillar at the same time.

What this means in your business: An old ERP isn’t cheap just because no license fee is flowing. You pay in workarounds, external developer days, missing updates, and creeping compliance risks around e-invoicing, GoBD, and GDPR. Eventually, the migration is unavoidable. Until then, it just gets more expensive.

What helps: Plan the switch as an investment, not a rescue operation. Migrate during growth, while energy, budget, and team are available, rather than under time pressure when the old system finally fails.

9. A brittle Order-to-Cash process ties up cash 

A topic that often only comes up when asked. When it does, it sits deep. Quote, order, delivery note, invoice, payment reconciliation, and dunning aren’t continuous.

Concretely: bank statements get checked off with pen and paper. Dunning runs by hand at several hundred invoices per month. Quote and order aren’t linked, partial invoices turn into chaos. The DATEV export is a CSV-tinkering project at month end.

What this means in your business: Every hour you leave between delivery and paid invoice is tied-up capital. As revenue grows, that hits cash flow directly.

What helps: Think of Order-to-Cash as one process, not three. Quote becomes order, order becomes delivery note, delivery note becomes invoice, invoice becomes payment with automatic assignment. Dunning runs rule-based. DATEV export happens without CSV work.

10. Performance issues and instability burn hours per week 

Comes up less often than the others. When it does, patience is gone. An ERP that lags costs hours per week without anyone counting.

Clicks that hang for ten seconds. Reports that take half an hour to load. System outages that last days without the vendor responding. Self-hosted servers that buckle under peak loads.

What this means in your business: One ERP-second, times every click by every employee, times every workday, adds up to a four-digit hourly total at year end. Plus the frustration you don’t see in any spreadsheet but feel at every resignation.

What helps: Cloud architecture that handles peak loads. No self-hosting obligation. Clear SLAs on availability and response time.

The pattern behind the 10 problems 

The ten points aren’t separate. They’re the same problem in different clothes.

• Points 1, 4, 5, 9 are different faces of the same theme: data doesn’t flow automatically to where it’s needed.

• Points 2 and 3 are the visibility problem: you don’t know what’s in the warehouse or what’s happening in the business.

• Points 6, 8, 10 describe the mortgage a legacy system builds up over time.

• Point 7 is what follows from all that: you can’t move forward even though you could.

The topics with the highest willingness to switch are rarely the loudest complaints. They’re the ones where the business otherwise can’t move forward. Reporting, scaling, internationalization, and performance: anyone tackling these switches not because the old system is annoying, but because the next growth chapter depends on it.

How to find the ERP that fits your business 

Three questions help find the right order of operations:

1. Which pain eats the most of your time? Make it concrete. Hours per week. Number of errors per month. Amounts that don’t get collected.

2. Where is your growth blocked? A marketplace that isn’t connected. Internationalization that can’t be mapped in the current system. Picking that can’t handle the order count.

3. What risk does your legacy system carry? Single point of failure, no support, no e-invoicing, no GoBD-compliant export.

If you answer any of these with "I don’t know," that’s already a signal. Then an honest assessment is worth doing before you go into ERP selection. If you want a structured comparison, our overview on ERP systems comparison lays out the key criteria.