Why this matters. The EHI Retail Institute Technology Trends in Retail 2025 report shows that 52 percent of DACH retailers invest in ERP and 42 percent in cloud infrastructure (n=119). Selecting by feature list misses the lever: whether returns, pricing and POS data land in one clean chain — or block one another.
When this view fits — and when it doesn't
When it fits:
-
you sell across channels and inventory, prices or master data drift apart;
-
returns are posted manually and visibly erode margin;
-
pricing-condition logic has hit the wall of your current system.
When it doesn't:
-
pure compliance updates without process change;
-
small single-site setups without multichannel ambition;
-
a vendor is already politically pre-selected.
Three retail types, three ERP profiles
Brick-and-mortar retail. Stationary retail carries one requirement no other type does: fiscal POS compliance (in Germany, TSE and KassenSichV). The till must connect cleanly to the ERP, branches must stay centrally controllable, and omnichannel inventory must not block itself. Starting from a pure wholesale ERP means rebuilding the POS interface as a follow-on project — usually more expensive than expected.
Wholesale and B2B. Wholesalers live by their pricing-condition engine. Volume scales, customer-group discounts, promotion stacking, contracts over term — these are not features, they are the business model. POS topics are irrelevant. A retail-style demo inspects the wrong logic.
E-commerce and multichannel. Here the return is the real margin killer, not the purchase price. Item master data with GTIN, variants and PIM integration are the precondition for omnichannel to work. The open question: integrated commerce suite, or core financial ERP plus best-of-breed POS and WMS. Both paths carry different failure modes — nobody admits this openly.
A typical mistake
A wholesaler in Lower Saxony, around 320 staff, selected its new ERP from retail-style demos. Interfaces convinced, licence cost fit. Four months after go-live, B2B condition logic — scales across contract terms, bonus accruals, customer-group stacking — could not be mapped in five of thirteen cases. Workarounds ran twelve months.
Across more than 1,200 supported selection projects we see the pattern: wholesalers fail on condition logic, not warehouse process — retailers fail on the till-to-ERP data chain, not the POS tool itself. Documenting both before any demo avoids the most expensive corrections later.
What to do next
If you want to test whether a vendor can really carry your retail context:
-
Clarify which retail type you structurally are — even if you serve all three channels.
-
Document your three hardest pricing cases and two returns scenarios with effect on inventory, receivables and VAT, before any demo.
-
Decide early: integrated suite, or core ERP plus best-of-breed — before shortlist or specification.
We assess whether your ERP can carry the retail data chain — and translate the result into a robust basis for vendor selection.
FAQ
Brick-and-mortar retail needs fiscal POS integration (in Germany, TSE and KassenSichV) and centrally controllable branches with consistent omnichannel inventory. Wholesale needs a deep pricing-condition engine — volume scales, customer groups, promotion stacking, contracts over term. The Federal Statistical Office (Destatis) separates both segments structurally; ERP selection follows the same dividing line.
A reliable returns logic joins automated inventory write-back, GDPR-compliant customer data and clean refund posting into a single workflow. In multichannel retail the return — not the purchase price — is the real margin killer. Manual posting does not scale.
Best-of-breed POS on a financial core ERP wins when POS requirements are deep and branch-specific — fashion, food, multi-format networks. An integrated suite wins when requirements are broad but shallow and a single data model beats the integration cost. Both paths carry weak spots — what matters is making that discussion explicit before vendor selection.
