ERP for Mail-Order and Direct-to-Consumer Brands

Mail-order and direct-to-consumer (D2C) businesses live and die by their order-to-shipment cycle. An ERP built for trade or manufacturing will buckle at the first peak season — the workflows it lacks (cartonisation, multi-carrier routing, returns triage, real-time stock locks across channels) are not nice-to-haves but daily operational reality. This guide covers the specific ERP capabilities that mail-order and D2C operations need, the German carrier landscape and the vendors that actually fit.

Pick-and-pack workflows

The picking model is the single most consequential choice in a mail-order warehouse. Single-order picking (one picker walks one order at a time) suits low volumes and high item counts per order — furniture, configured kits. Batch picking (one picker collects items for many orders simultaneously, sorted at a pack station) suits high volumes and low items per order — fashion, cosmetics, supplements. Zone picking (the warehouse is split into zones, each picker covers one zone, orders are consolidated at the pack station) suits very high volumes with a dense SKU range — the standard for large D2C shippers.

The ERP must support whichever model the operation actually uses, with mobile picking devices (handheld scanners or smartphone clients), pick-by-light or pick-by-voice where applicable, and pack-station verification (weigh-check or scan-verify) to keep pick errors below 0.2 %. ERPs sold as ‘trade’ products without warehouse modules typically force a separate WMS on top, which works but adds an integration layer.

Returns management

The German fashion mail-order segment runs at 30–60 % return rates; supplements and cosmetics at 5–15 %; B2B mail-order at 2–8 %. An ERP that treats returns as exceptions rather than as a parallel inbound flow will collapse the cost structure. The minimum returns capability covers: pre-announced returns with QR codes on the original packing slip, inbound triage with grading (new, used, defective), refurbishment routing, automated refunds with payment-provider integration, and shelf-life-aware restocking for FMCG.

Best-practice operations measure the return cost per order alongside the picking cost and treat both as KPIs. The ERP's reporting must support this; spreadsheet-based return tracking is the surest sign of an undersized system.

Carrier integration (DHL, DPD, GLS, UPS, Hermes)

The DACH carrier mix is concentrated but the operational details differ. DHL dominates B2C parcels for small businesses with broad coverage and easy on-boarding; the API supports rate shopping, return labels and recipient-managed delivery options. DPD and GLS are strong in B2B and in larger shippers thanks to better volume pricing and time-window options. UPS covers premium and international flows. Hermes sits at the price-sensitive end of B2C.

The ERP must integrate with all carriers a shipper uses, ideally through a shipping platform (Shipcloud, Sendcloud, ShipStation, DHL Versenden) that normalises the carrier APIs and supports rate shopping at pack-time. A direct carrier-by-carrier integration is feasible for small operations but quickly becomes a maintenance burden as carriers update their APIs.

Warehouse layout and inventory accuracy

Mail-order ERPs need to track stock at bin level, not at warehouse level. Even small operations (under 5,000 SKUs) benefit from chaotic storage with system-directed put-away; large operations cannot run any other way. Inventory accuracy must be maintained through cycle counting (rolling counts of 5–10 % of bins per week) rather than annual physical inventories — the latter is GoBD-compliant for tax purposes but operationally useless.

The ERP must also handle multi-warehouse and multi-channel stock allocation. If the same SKU is sold through the brand's own shop, Amazon, eBay and a marketplace, the available-to-sell quantity must be computed in real time across channels with configurable safety stock per channel.

Mail-order ERP vendors in the DACH mid-market

The mid-market is well-served by specialist vendors. JTL-Wawi covers small to mid-sized B2C mail-order with strong shop-integration to JTL-Shop, Shopware, WooCommerce and the marketplaces. Xentral sits one tier up, with deeper financials and stronger D2C process support. Pickware is the natural fit for Shopware-centric brands. plentyOne covers marketplace-heavy operations including Amazon FBA orchestration. Billbee serves the smaller end with quick on-boarding. Generic Mid-Market ERPs (myfactory, weclapp, Sage 100) can cover D2C with module add-ons but typically do not match the depth of the specialists.

The selection question is rarely about features alone; it is about whether the specialist's product roadmap and pricing model fit the operation's growth trajectory. Many brands outgrow JTL or Billbee at 20–50k orders per month and have to migrate; planning for that migration at the start saves it twice over.

Häufig gestellte Fragen

Which ERP is best for mail order?

There is no universal 'best' system, because the right solution depends heavily on daily parcel volume. For small retailers handling up to around 100 parcels a day, lean tools such as Billbee are sufficient, while in the mid-market widely used systems such as JTL-Wawi, Pickware or PlentyONE (formerly plentymarkets) with packing stations and mobile picking dominate. From around 1,000 parcels a day, dedicated WMS and enterprise solutions such as Descartes pixi WMS, Actindo or Oracle NetSuite come into consideration. Alongside volume, the decisive factors are the marketplace connections you need, the range of carriers and the returns intensity of your product assortment.

What distinguishes a WMS from a mail-order ERP?

A warehouse management system (WMS) specializes purely in warehouse and picking control, i.e. putaway, pick routes, inventory management and packing processes. A mail-order ERP additionally covers the commercial functions, such as order management, accounting, marketplace integration and returns management. At smaller and medium volumes, the warehouse functions integrated in the ERP are usually sufficient, so no separate WMS is needed. As throughput and warehouse complexity grow, the WMS is often operated as a specialized component alongside the ERP and connected to it via interfaces.

How much does a mail-order ERP cost?

The range is wide and depends primarily on functional scope and volume. Simple plug-and-play solutions for small retailers start in the low double-digit range per month, for example Billbee with a base fee from around 9 euros plus a usage-based component. Mid-market setups with packing stations, mobile picking and several carrier connections typically range from a few hundred to over a thousand euros per month plus one-off setup costs. Enterprise projects with a dedicated WMS, voice picking and custom integrations quickly reach five- to six-figure implementation sums plus ongoing licenses, which is why a precise scaling and cost calculation before the selection is advisable.

Which carrier integrations should a mail-order ERP support?

For shipping in the DACH region, DHL Paket is the de facto standard that every mail-order ERP should connect natively via an interface for labels, tracking and returns. For international and express shipping, DPD and UPS are also important, while GLS and Hermes play a role especially for B2B and price-sensitive shipments. If the ERP does not directly support all the carriers you need, multi-carrier shipping platforms such as Sendcloud, shipcloud or Shippo help by bundling several carriers and needing to be connected to the ERP only once. Make sure the integration can also cover automated returns labels and international customs documents.

How important is good returns management in a mail-order ERP?

Returns are a significant cost factor in German online retail: according to the EHI Retail Institute, the average returns rate most recently stood at around 17 percent across all product ranges. It is considerably higher in the fashion segment, where retailers often record item-based rates of around 30 to 50 percent and, on a parcel basis, sometimes considerably more. A capable mail-order ERP should therefore provide a returns portal, automated refund workflows and clean restocking of returned inventory. This shortens processing times, prevents stock discrepancies and limits the capital-tying effects of high return rates.

Which legal obligations must an ERP cover in mail order?

Mail-order retailers must archive their invoices in a GoBD-compliant, unalterable form; since the beginning of 2025, a retention period shortened to eight years has applied to accounting records such as invoices, and in the B2B sector businesses have had to be able to receive and store structured e-invoices under EN 16931 in an audit-proof manner since January 1, 2025. Added to this is the German Packaging Act: anyone shipping goods to end consumers in Germany must register in the LUCID packaging register, license their shipping and filler packaging and report the volumes — otherwise fines of up to 100,000 euros for missing registration and up to 200,000 euros per case for missing system participation, as well as distribution bans, loom. A suitable ERP should support these processes through audit-proof document archiving, correct tax and VAT ID handling and reports on packaging volumes. Since the rules change regularly, additional coordination with your tax advisor and a licensing service provider is recommended.