Frequently asked questions about ERP systems

Inventory management mainly covers orders, warehouse and shipping. An ERP goes further and also integrates areas such as accounting, CRM, purchasing, production and reporting. In practice the lines are blurred – many cloud systems start as inventory tools and grow into an ERP.

Cloud ERP runs at the provider, is quick to start, updates automatically and is billed monthly – ideal for most SMEs. On-premise runs on your own infrastructure with maximum control, but causes maintenance and update effort. For the Mittelstand, cloud is the more economical choice in the vast majority of cases.

A cloud ERP is used as Software-as-a-Service (SaaS) via the browser; you install nothing yourself. It is usually billed as a monthly subscription – per user, by order/revenue volume, or as an edition, depending on the provider. A price comparison shows which model fits your business.

An ERP pays off as soon as several people access shared data and processes (orders, warehouse, invoices) no longer run cleanly in Excel – often from around 3–5 employees. There is barely an upper limit; what matters is process complexity, not headcount alone.

Typical warning signs: duplicate data entry, Excel chaos, incorrect stock, slow order processing and no reliable reports. When growth stalls on manual processes, it's time for an ERP. Our ERP finder gives you first guidance in five questions.

The standard includes order processing, warehouse/stock, purchasing, shipping, accounting as well as CRM and reporting. Depending on the industry, production (bills of materials, manufacturing), project billing or POS are added. Good systems can be extended modularly, so you only pay for what you use.

CRM manages customer relationships (contacts, sales, communication), inventory management the goods and order flows. An ERP is the overarching framework that integrates both plus accounting, purchasing and reporting. Many ERPs already include CRM and inventory features.

For most trade and service companies, a flexible standard ERP covers the requirements. Industry solutions pay off if you have very specific processes (e.g. batch/serial manufacturing, pharma, food). In the selection consulting we check whether standard is enough or a specialization makes sense.

Multi-entity capable means you can manage several legally separate units (companies, brands, countries) in one system – with separate ledgers but a shared base. This matters for corporate groups, holdings and international structures. Not every ERP handles this equally well.

Accounting software covers finance – documents, accounts, tax, DATEV. An ERP additionally steers the operational processes beforehand: orders, warehouse, purchasing, shipping. The ERP creates the documents, accounting processes them; often the finance module is integrated into the ERP or connected via an interface.

An ERP is a long-term investment and often stays in use for 7–10 years or more. That is exactly why a thorough, vendor-independent selection pays off – a wrong choice costs far more over its lifetime than the consulting.

The range is wide: lean systems start at around €50–100/month, broader SME ERPs run from a few hundred to a few thousand euros depending on users and modules, enterprise systems are priced individually. In the comparison you see the entry prices side by side.

Three models are common: per user/month (e.g. weclapp, Business Central), by order/revenue volume (e.g. Xentral, Billbee) and resource-/edition-based. Which is cheaper depends heavily on team size and transaction volume – the ranking often flips because of it.

TCO includes not only subscription fees but also setup, implementation partner, add-on modules, interfaces, training and internal effort. Over the lifetime, rollout and operation often exceed the pure license cost. That's why every profile shows a dedicated TCO section.

Typical surprises: paid add-on modules, transaction-based fees, custom interfaces, data migration, training effort and more expensive tiers due to revenue/user growth. An honest TCO calculation before signing prevents nasty surprises.

Implementation is usually billed per project and depends on process complexity, data migration and interfaces. For SMEs the range spans from a few thousand to mid five-figure amounts, much higher for enterprise. Our rollout & implementation works in clear, predictable sprints.

As a rule of thumb, implementation costs are often one to three times the annual license cost – the more complex the processes, the higher. That's why a clean detailed concept before the start is money well saved.

Open source (e.g. Odoo Community) saves license costs but shifts the effort to hosting, setup, maintenance and development. For companies with IT competence this can be cheap; without internal resources, hidden costs pile up quickly. We calculate the real TCO, not just the license price.

Set the total costs against the savings: less manual work, fewer errors, faster processing, better stock and valid reports. Many SMEs amortize a fitting ERP within 1–3 years – provided it truly fits the processes.

In user-based systems each additional full user costs extra (often two- to low three-figure per month); add-on modules are usually charged separately. In volume-based systems users are often included, instead you pay by order volume. The specific rates are in each profile.

Depending on country and region there are digitalization subsidies for software and consulting (e.g. Digitalbonus programs in DE/AT). Whether and how much applies to your project changes constantly – we point out possible avenues in the initial call, but do not replace subsidy consulting.

Watch out for minimum terms, automatic renewal, price-adjustment clauses, automatic tier upgrades on growth and costs for add-on modules/transactions. Have offers reviewed neutrally before signing – small clauses have a big effect over the years.

Beyond the subscription, plan a realistic rollout budget plus a buffer for interfaces, migration and training – and your team's internal time. In the selection consulting we provide a solid rough calculation (TCO) so you can plan cleanly internally.

For SMEs a rollout usually takes 6–16 weeks, depending on process complexity, data migration and number of interfaces. Enterprise projects run over several months. A clear detailed concept and clean master data noticeably shorten the duration.

Typical: kickoff and detailed concept, configuration, master-data migration, interfaces, test and acceptance, training, go-live and hypercare. We work in clear sprints with milestones – details on the process are on rollout & implementation.

Most important are clean master data (articles, customers, suppliers, stock), clearly named owners and a rough process understanding. The better the preparation, the smoother and cheaper the rollout.

An ERP rollout is a team sport: expect noticeable internal effort for decisions, data preparation, testing and training – especially for the core users. We handle the implementation, but process knowledge and sign-offs come from your side.

The most common reasons: unclear requirements, poor data quality, missing internal resources, too much customization and low user acceptance. A clean selection and rollout process with a realistic scope and good training prevents exactly that.

In a big bang everything goes live on one date – fast, but riskier. In a phased rollout you start module or department by department – safer, but longer. For most SMEs a pragmatic middle path with a clear core go-live is ideal; we recommend case by case.

The detailed concept records, before configuration, how your processes are mapped in the new system – document flows, rights, workflows, reporting and interfaces. It is the project's map and prevents expensive misunderstandings. We create it right at the project start.

Training is ideally role-based (everyone learns what they really need), hands-on with real processes and with documentation that stays. Good training is the biggest lever for user acceptance – and thus for project success.

Go-live is the productive start of the new system. Hypercare is the close support in the first days and weeks afterwards, when questions and fine-tuning are resolved quickly. This phase strongly determines the perceived project success.

A time-limited parallel operation is possible as a safeguard, but costs double effort and risks data discrepancies. Usually a clean cut-over date with good testing beforehand is the better choice. We plan the transition so the risk stays minimal.

The team should include a decision-capable project owner, key users from the affected departments (e.g. sales, warehouse, accounting) and IT if needed. Clear roles and decision paths matter more than team size.

Before migration, clean up duplicates, outdated articles/customers and inconsistent formats – garbage in, garbage out. Best practice is to migrate only active, checked data and archive the rest. We support with preparation and import.

Changes are normal; what matters is an orderly change management that makes the impact on time and budget transparent. A clearly bounded core scope keeps the project stable nonetheless. That's how you avoid runaway costs.

Simple setups can be done with internal competence; as soon as migration, several interfaces and complex processes are involved, an experienced partner saves time, money and nerves. We deliver the rollout turnkey or accompany your team.

Yes – most cloud ERPs offer native connections to Shopify, Shopware, WooCommerce and more. Via the interface, orders, articles, stock and tracking flow automatically. We set up the connection as part of integration & automation.

Marketplaces are usually connected natively or via middleware, so orders are processed centrally in the ERP and stock is kept in sync. Especially in multichannel this is the biggest efficiency lever. Which marketplaces a system covers natively is in the profile.

An API is the programmable interface through which other systems exchange data with the ERP. An open, well-documented REST API is important as soon as you need custom connections or automation. Without an API you are limited to the provider's standard integrations.

Middleware (iPaaS) mediates between systems that have no native interface to each other – it translates and steers data flows. It pays off with many channels, special logic or when a direct connection is missing. Whether it's needed or native interfaces suffice, we clarify per project.

Depending on the system and interface, synchronization is near real time (via webhook) or in short intervals. For stock and order status, timely synchronization matters to avoid overselling. The exact behavior depends on the connection.

Payment providers are usually connected via shop or ERP interfaces, so payments are automatically assigned to orders and passed to accounting. This significantly reduces manual reconciliation. Which payment integrations an ERP brings is shown in the profile.

Via shipping interfaces you generate labels directly from the ERP and return tracking numbers automatically to shop and customer. Often several carriers run through shipping software like Sendcloud or shipcloud. This saves enormous time in shipping.

Yes – multichannel is a core strength of modern cloud ERPs: several shops and marketplaces run centrally through one system, with shared stock and unified order processing. That's exactly what e-commerce ERPs are built for.

Good connections buffer outages, automatically retry failed transfers and report errors transparently. Monitoring and a clear support path matter so nothing goes unnoticed. We take this into account when setting up the integration.

Many ERPs offer rule-based automation (e.g. order workflows, automatic status changes, notifications), partly via a no-code editor. This saves routine work and reduces errors. We identify and set up sensible automations together.

Yes – ERP, CRM and accounting are connected via interfaces, though ERPs often bring CRM and finance features directly. The goal is a seamless data flow without duplicate entry. Which variant is leaner depends on your tools.

Native interfaces are quick to deploy, cheap and low-maintenance – the first choice if they cover your requirements. Custom connections (via API/middleware) are more flexible but more effort. We choose pragmatically: as much standard as possible, as much customization as necessary.