ERP for e-commerce and D2C brands — what online retailers really need.

Online retail looks simple from the outside: an order comes in, goods go out. In reality, this is one of the most process-dense business models an ERP has to serve – with order flows from multiple channels, fast warehouse and shipping operations, payment reconciliation, returns management and marketing systems. This profile shows why classic ERP systems frequently fail these requirements and which systems really carry in the e-commerce mid-market.

1. What sets e-commerce/D2C ERP apart from classic trade ERP

Classic trade ERP is built for B2B order flows, wholesale structures, field sales and moderate inventory turnover. E-commerce and D2C bring four structural differences:

• High order volumes with small baskets. Instead of 200 orders with 50 line items, 5,000 orders with 1–3 line items. ERP performance and pick-pack efficiency become critical.
• Speed as a competitive advantage. Same-day shipping or "ordered by 2pm, delivered tomorrow" is the minimum standard. The ERP has to orchestrate order-warehouse-shipping in seconds, not hours.
• Variety of sales channels. Own shop, marketplaces, social commerce, B2B portal, possibly stationary retail – consolidating all of this onto one inventory and one data foundation is demanding.
• High return rates and service requirements. 20–40 % returns are common in B2C. The ERP has to handle returns cleanly, restock goods, reverse payments, link customer service inquiries to sales.

An ERP that does not cover these four areas in standard quickly produces manual processes, duplicate maintenance and delays in e-commerce. As soon as scaling beyond 1,000 orders per day kicks in, that becomes an operational brake.

2. Load-bearing functions for online retail and D2C

The following functional areas regularly decide between success and failure in e-commerce/D2C selection projects.

Shop and marketplace integrations

An e-commerce-capable ERP brings standard connectors for major shop systems (Shopify, Shopware, WooCommerce, Magento, JTL) and marketplaces (Amazon, eBay, Otto, Zalando, Idealo). Custom builds per channel are a warning sign – they don't scale.

Inventory across channels

An item sold on Amazon must immediately reduce inventory on the own shop and eBay. Without central inventory with real-time synchronisation, oversells emerge – one of the most common reputation killers in e-commerce.

Shipping and logistics processing

Connection to shipping providers (DHL, UPS, DPD, GLS, Hermes), label printing, tracking, warehouse management with picking strategies (pick-by-light, wave-picking), connection to fulfilment service providers (3PL). Returns management belongs here too.

Payment processing and reconciliation

In e-commerce, payments run through payment service providers (Stripe, PayPal, Adyen, Klarna). The ERP has to automatically match incoming payments to orders, post fees correctly, handle chargebacks and reversal processes.

Accounting integration (DATEV)

Order → invoice → payment → shipping → possibly return → reversal invoice – many documents are created in B2C. A native DATEV interface that maps these flows is not optional in DACH e-commerce.

Marketing and customer data

Connection to newsletter tools, CRM, marketing automation. Ideally the ERP feeds order data to marketing systems and receives campaign/conversion data back. That turns shipping history into a steering tool.

3. Which ERP systems are particularly relevant in e-commerce

In SME and lower mid-market e-commerce, Xentral is a dominant candidate because the system was architecturally aimed at exactly this business model – shops, marketplaces, shipping and DATEV as standard scope. Odoo is an alternative when the business model is more strongly integrated with CRM, marketing and service. In growing mid-market and international scenarios, NetSuite moves into focus. Classic mid-market ERPs like Business Central or Weclapp often require additional integration work in e-commerce setups.

4. Typical mistakes in ERP selection for e-commerce

• ERP is selected before the shop. In reality the shop often sets the pace (platform, performance, customer experience). The ERP follows – not the other way round.
• Number of channels underestimated. "We only sell through our shop" is rarely true – marketplaces, social commerce, B2B come quickly. Scalable multichannel logic belongs in the requirements.
• Returns management forgotten. 20–40 % return rate means: per 100 orders, 30 come back. Anyone without a returns standard in the ERP builds Excel lists for returns.
• DATEV as downstream topic. In B2C, masses of documents are created. A native DATEV interface is mandatory, not an add-on.
• Performance requirement overlooked. 500 orders/day are different from 5,000. The ERP has to scale – performance tests belong in the selection phase.

5. Frequent questions on ERP for e-commerce and D2C

Do I need an e-commerce-specialised ERP or is a standard ERP enough?

Above 100 orders per day and several sales channels, an e-commerce-specialised or at least e-commerce-proven ERP almost always pays off. For small, single-channel setups a standard ERP with a shop connector can suffice.

How many orders per day can the typical candidates handle?

Xentral and comparable systems are established in the 1,000–10,000 orders/day range in DACH mid-market. Above that, architecture (caching, job queues, database scaling) becomes decisive. Performance and scaling tests should be part of the selection here.

How tightly should the shop be integrated with the ERP?

Tightly enough that order, inventory, status and return are synchronous – without manual intervention. Loose integrations via CSV exports are no longer viable in scaling phases.

What does an ERP setup cost for a growing online retailer?

For 20–80 users with shop, marketplace, shipping and DATEV integration: typically mid five- to low six-figure range in year one. Scales with the business model.

When is the switch to a larger ERP (NetSuite, D365 F&O, S/4HANA) worthwhile?

For multi-entity setup, international expansion, consolidation needs or volumes the current system cannot architecturally handle anymore. The switch is plannable but not a trivial project – put it on the roadmap early.

---

Note: This profile does not replace an individual project assessment. The patterns and recommendations are experience values from selection projects in the German-speaking mid-market.

Author: Joerg H. Paul Schaefer · As of: May 2026 · erp-check.info is a vendor-neutral information platform.