What is Conditions Management?
Conditions management is the systematic administration, maintenance and automated application of all commercial terms – prices, discounts, surcharges, flat rates and contractual Service Level Agreements (SLAs) – between a company and its business partners. In the logistics and warehouse environment, it specifically covers the conditions agreed with carriers, clients (in contract logistics operations), suppliers and customers for services such as storage, handling, value-added services (VAS) and transport. A capable Warehouse Management System (WMS) captures every executed service event, evaluates it against the stored condition master data and provides the result automatically to the ERP for invoicing.
What does conditions management cover in a logistics context?
Conditions are the commercial translation of physical logistics services. While the WMS controls operational execution (goods receipt, storage, picking, shipping), conditions management defines how those services are monetised. Typical components include:
- Price conditions: base prices per storage bin, pick line, order or shipment
- Discount conditions: volume discounts, customer discounts, promotional prices with validity periods
- Surcharge conditions: dangerous goods, express, oversize or weekend surcharges
- Flat rate conditions: monthly flat rates for storage area, IT provision or minimum revenue
- Freight conditions: tariffs per carrier, zone, weight and shipment type including bunker adjustment factor (BAF)
- SLA conditions: agreed service levels with bonus/malus rules for over- or under-performance
Where is conditions management used in a WMS?
Conditions management is particularly relevant for companies with complex contract and client structures. Typical use cases include:
- Contract logistics (3PL/4PL): client-specific billing per customer, storage location and movement
- Carrier management: real-time selection of the cheapest shipping provider per shipment
- Value-added services: billing of labelling, display assembly, co-packing and returns processing
- Supplier conditions: verification of incoming invoices against agreed purchasing terms
- E-commerce shipping: dynamic selection of shipping tariff based on cart value, region and delivery time
Comparison: where is conditions management handled?
Conditions can be maintained in different systems. The following overview shows the typical division of responsibilities between ERP, TMS and WMS:
| Criterion | ERP (e.g. SAP S/4HANA) | TMS (Transport Management) | WMS (e.g. proLogistik proWMS) |
| Primary condition type | Sales and purchasing prices, discounts | Freight tariffs, carrier zones | Storage, handling and VAS conditions |
| Conditions technique | SAP condition technique (V/06, VK11) | Tariff engine, routing rules | Service-event-based rule set |
| Data source | Order header, master data | Shipment data, waybill | Warehouse movements, pick/pack events |
| Output | Invoice, posting | Freight cost calculation | Service report for invoicing |
| Real-time capability | Periodic (monthly/quarterly close) | Per shipment | Per posting in real time |
Technical requirements for a WMS conditions module
Not every WMS supports conditions management end-to-end. The following functions are essential for reliable performance-based billing:
| Function | Requirement |
| Multi-client capability | Separate condition records per customer, client or warehouse with individual validity periods |
| Service event capture | Automatic posting of all relevant events (pick, pack, storage, inventory, VAS) |
| Rule engine | Conditions with tiered prices, time windows, minimum quantities and bonus/malus logic |
| ERP integration | Bidirectional connection via OData, IDoc or REST API for invoicing and master data sync |
| Audit trail | Complete traceability of every priced posting for audits and dispute resolution |
3 steps to introduce conditions management in your WMS
- Define the condition model: Capture every billable service (receipt, storage, pick, VAS, shipping) and the corresponding price structure. Distinguish between volume-based, time-based and event-based conditions.
- Maintain master data and rule set: Store conditions with validity period, scale and contract reference in the WMS. Ensure clean versioning so that historical billings remain reproducible.
- Automate the ERP connection: Configure an interface (e.g. SAP IDoc or OData) that transfers priced service reports automatically to the ERP. This eliminates manual Excel lists and correction postings.
FAQ – Frequently asked questions on conditions management
What is the difference between conditions management and pricing?
Pricing focuses on determining sales prices for end customers. Conditions management is broader: it covers purchasing prices, discounts, surcharges, SLAs and contractually agreed logistics service prices, and applies to customers, suppliers and service providers alike.
Is the SAP conditions module sufficient or is a dedicated WMS module needed?
SAP handles commercial conditions very well via its conditions technique (V/06, VK11). However, for the operational capture of warehouse-level services – which movement was triggered when and by whom – a WMS is required that generates these events cleanly and passes them to SAP for evaluation. Both systems work complementarily.
How is conditions management used in contract logistics?
3PL providers use conditions management in the WMS to map different price models per client – for example storage flat rates, picking by line item or complexity tiers. At month-end, the WMS produces a client-specific service report that is fed automatically into invoicing.
Which interfaces are typical for conditions management between WMS and ERP?
Common interfaces are SAP IDocs (e.g. INVOIC, INVOIC02), OData services for SAP S/4HANA and REST APIs for non-SAP ERPs such as Microsoft Dynamics or Oracle. Older systems sometimes still rely on EDIFACT messages or file-based transfers (CSV, XML).
More about Terms Management & Bonus Settlement with “BONSAI”