Häufig gestellte Fragen
Is a pure inventory management system enough, or do I need a full ERP for trade?
A pure inventory management system (WaWi) primarily covers purchasing, warehousing and sales and is sufficient for many smaller merchants whose accounting and controlling run separately. A full ERP additionally integrates financial accounting, cost accounting, multiple legal entities and often CRM in one system, so stock levels, documents and reports do not have to be reconciled across interfaces. As a rough guide: with rising turnover, several warehouses or branches, international business and a growing number of suppliers and items, the benefits of an end-to-end ERP solution prevail. The transition is fluid, which is why many vendors expand their inventory management systems into modular ERPs.
How many sales channels and marketplaces should a trade ERP connect directly?
For German merchants, Amazon, eBay, OTTO and Kaufland Marketplace are now the standard expectation; in the fashion segment, platforms such as Zalando or AboutYou come on top. What matters is less the sheer number than the depth of integration: a native, bidirectional connection transfers items, stock levels, orders and shipping data automatically and reduces manual maintenance effort significantly compared with generic iPaaS bridges. If a direct connection is missing, the channel can usually be added via middleware or connectors, though this incurs additional licence and maintenance costs. During selection, you should check which channels are supported out of the box and how frequently stock levels are synchronised.
How does an ERP prevent overselling in multichannel sales?
Overselling occurs when the same stock is sold in parallel on several channels and inventory levels are not updated quickly enough. A well-integrated trade ERP maintains a central, channel-spanning inventory and pushes changes back bidirectionally to shops and marketplaces, ideally in near real time or at short intervals of a few minutes. In addition, mechanisms such as safety stocks, reservations for open orders and channel-specific stock buffers help cushion shortages during load peaks. The less frequently synchronisation runs, the higher the risk of cancellations and marketplace penalties at high volumes.
Which legal obligations must a trade ERP cover in Germany?
In the B2B area, companies have had to be able to receive and process structured e-invoices (such as XRechnung or ZUGFeRD from version 2.0.1) since 1 January 2025; staggered transitional periods apply to sending, with issuers whose prior-year turnover exceeds 800,000 euros required to send e-invoices from 2027 and all others from 2028 at the latest. Brick-and-mortar retailers with electronic tills are additionally subject to the German Cash Register Security Ordinance with a certified technical security system (TSE), the obligation to issue receipts and the reporting obligation for cash register systems via ELSTER in force since 2025 (the first deadline was 31 July 2025). Across the board, tax-relevant records must be archived in a GoBD-compliant, unalterable and audit-proof manner, with accounting documents such as invoices retained for only eight instead of ten years since 2025, while ten years continue to apply to annual financial statements and balance sheets. A modern trade ERP should cover these requirements via e-invoicing, till and archiving functions or connect them via certified interfaces.
What does introducing an ERP system in trade cost and how long does it take?
Costs depend heavily on the deployment model, user count and degree of customisation: cloud solutions are usually billed per user per month, while on-premises systems entail higher one-off investments. Typically for the industry, a substantial share of the total budget is consumed not by licences but by implementation, data migration, interfaces and training, so mid-market projects frequently land in the five- to six-figure range. Project duration in the mid-market typically ranges from a few months to around one and a half years depending on complexity, with extensive individual customisation extending the timeframe. Concrete figures can only be quoted seriously after reviewing your own processes, channels and data volumes.
Cloud or on-premises — which suits a trading company better?
In trade, fluctuating load peaks such as Black Friday or seasonal business often argue for cloud models, because computing capacity can be scaled flexibly and updates and maintenance sit with the provider. A large share of new mid-market projects now starts cloud-first, while existing productive on-premises systems often remain in parallel use for many years. In practice, hybrid architectures are common, in which customer-facing functions run in the cloud while sensitive or tightly integrated areas are operated locally and connected via integration platforms. The decision should be guided by scaling needs, data protection requirements, existing IT and the desired control over updates.