ERP for Contract Logistics — software for 3PL warehouses and value-added logistics
Contract logistics — Kontraktlogistik — runs other companies' supply chains under long-term agreements, typically inside dedicated or shared warehouses with customer-specific service levels. An ERP for contract logistics has to fuse WMS and TMS execution with commercial back-office workflows, handle SLA-based billing per pallet, pick, handling unit or value-added service, and produce the activity-based costing that decides whether a contract is actually profitable. Generalist trading ERPs without WMS depth and without per-customer SLA modelling collapse under the heterogeneity of a real 3PL operation.
Requirements
The core requirement is the multi-client (Mandant) model: a single warehouse can carry stock for ten different customers, each with its own master data, locations, packaging rules and service-level agreements. The ERP, WMS and TMS together have to enforce that separation rigorously — stock cannot mix and pickers must never see another client's data. Service-level agreements drive billing rather than fixed prices: charges are accrued per inbound pallet, per outbound carton, per pick line, per kitting operation, per returns processing case. Value-added services — co-packing, kitting, late-stage customisation, returns processing, light assembly, labelling for retailers — need to be priced and billed as discrete activities. Customer EDI integration brings ORDERS, DESADV, INVOIC and warehouse-specific messages such as INSDES (instruction to despatch) or RECADV. KPI reporting against contractual SLAs — on-time-in-full, picking accuracy, inbound dock-to-stock time — is contractual rather than nice-to-have.
Mandatory functions
Mandatory features begin with a deep WMS: directed put-away, replenishment strategies, multi-pick zoning, voice and pick-by-light support, RF-gun integration and a clean integration model for the TMS layer. A TMS module or interface manages route planning, carrier tendering, ASN generation and proof-of-delivery capture. Activity-based billing is the commercial heart: the ERP must price each move, pick, pallet handling, storage day and value-added service against per-customer rate cards, generate the periodic invoice automatically and produce a transparent activity statement. SLA reporting needs to be live, not retrospective, so that an at-risk SLA shows up before the breach. Returns processing with grading, refurbishing and re-stocking workflows is part of mandatory scope for most 3PLs serving e-commerce customers. Hardware integration covers scales, dimensioners, scanners, carrier label printers (DHL, UPS, DPD, GLS) and increasingly autonomous mobile robots. DATEV interface, intra-EU triangulation handling and clean withholding-tax setup for cross-border services close out the financial side.
Vendor landscape
The DACH contract-logistics vertical has a clear split. Pure WMS leaders — SAP EWM, Manhattan SCALE, Korber One (the consolidated Aberle / Cirrus / HighJump portfolio), LFS by Ehrhardt+Partner, Infor WMS — cover the warehouse-execution layer. On top of that, a commercial ERP layer handles contract management, billing and finance: SAP S/4HANA for very large 3PLs, Microsoft Dynamics 365 Business Central or F&O for mid-market 3PLs, and IFS Cloud for groups with a strong service-business overlay. Several DACH specialists — SCC GmbH, ENGEL & VÖLKERS Logistics, prologistik — sit between WMS and ERP with logistics-specific add-ons. For TMS, Transporeon (Trimble), Alpega and Soloplan's CarLo dominate transport execution. Selection typically pivots on the existing WMS investment: a Manhattan-equipped operation rarely switches WMS, so the ERP is selected around the WMS, not the other way around.
Trends and outlook
Three trends shape current selection projects. First, automation: autonomous mobile robots (AMRs), goods-to-person systems and AS/RS need ERP-level integration for slot allocation, throughput planning and cost allocation. Second, real-time visibility for the end customer: 3PL clients increasingly demand a portal that shows live stock, in-transit shipments and SLA performance, which raises the API and data-streaming bar for the ERP. Third, sustainability reporting under CSRD adds CO2 per shipment to the standard data set, often calculated at TMS level and rolled up through the ERP. 2026 selection projects in the vertical now test all three.
Related Topics
Frequently Asked Questions
Should a 3PL use one combined ERP/WMS or separate systems?
Separate systems remain the dominant pattern in DACH contract logistics. The WMS specialists (Manhattan, Korber One, LFS, SAP EWM) deliver depth that no combined ERP matches, while the commercial back-office sits on a generalist ERP. Interface design between the two becomes the critical engineering challenge, but the alternative — trying to push a generalist ERP into deep WMS territory — rarely scales.
How does SLA-based billing differ from standard order billing?
Standard order billing prices a finished product. SLA-based 3PL billing prices the activities consumed in fulfilling someone else's order — per pallet stored, per pick line, per kitting step, per returns case — against a per-customer rate card. The ERP must record each activity as it happens, accrue it against the customer's contract, and produce a transparent activity-level invoice at month end.
What level of EDI is mandatory in contract logistics?
For shippers handling retail or industrial flows, working EDIFACT EANCOM (ORDERS, DESADV, INVOIC, INSDES) with the largest customers is essentially mandatory. ASN generation in the right format is often part of the contractual SLA — missing or late ASNs cost the 3PL penalty fees. Lighter-weight customers may accept API or portal-based exchange, but EDI capability is still the qualifying baseline.
What about VAS (value-added services) like kitting?
VAS — co-packing, kitting, late-stage customisation, returns processing, labelling — needs to be modelled as discrete production-style operations inside the WMS, with materials consumption tracked and billed back to the client. Treating VAS as ad-hoc work outside the system is a classic 3PL profit leak: the cost is incurred but the corresponding bill never quite reflects the actual effort.