Drafting Legally Robust Logistics Contracts

Separating transport, warehousing and contract logistics

Under section 407 of the German Commercial Code, a carrier undertakes to transport the goods to the place of destination and deliver them to the consignee. The CMR may apply mandatorily to international carriage by road. A warehousing contract, by contrast, concerns the storage and safekeeping of goods and is governed by sections 467 et seq. HGB. Contract logistics projects add services such as inbound inspection, order picking, packaging, assembly, stock management, returns processing and customs support.

Putting all these activities into one document does not create a single legal contract type. When a loss occurs, the decisive questions are where in the process it arose and which duty was breached. The contract should therefore break the process into modules and define takeover, custody, handover points and delivery. Interfaces between transport and storage, inventory discrepancies, handling damage and cases where the place of loss can no longer be established require particular attention.

The agreement also needs a workable rule for unlocalised or combined losses. It must respect mandatory liability regimes while preventing gaps in complex operations. Where the German Freight Forwarders' Standard Terms or other industry terms are incorporated, their relationship with the negotiated agreement and the customer's own terms should be addressed expressly.

Service levels as an operational control system

Service levels should make performance measurable. Typical metrics include cut-off times, throughput, on-time delivery, inventory accuracy, picking errors, damage rates, response times and system availability. A target value alone is insufficient. The agreement should identify the controlling data source, the measurement method, permitted exceptions and the reporting cycle.

Consequences should be proportionate. Service credits may be useful for isolated and manageable deviations. Repeated or serious failures require a binding remediation plan, escalation rights and potentially a special termination right. The contract should also state whether a service credit merely compensates for the particular service failure or excludes further damages.

Customer dependencies belong in the same framework. Incomplete forecasts, late master data or customer-side system failures may affect performance just as much as an operational error by the provider. A robust SLA therefore links metrics to responsibilities and a documented root-cause process.

Liability, claims and security rights

German transport law contains specific rules and limits for cargo loss, damage and delay. Under section 425 HGB, the carrier is generally liable for loss or damage while the goods are in its custody and for delay in delivery. These rules do not always fit additional services, pure financial loss, data loss, production stoppage or recall costs. The agreement should therefore distinguish mandatory transport liability from an additional liability framework for other duties.

A blanket exclusion of all consequential loss is often too imprecise. A more reliable approach coordinates the type of loss, the degree of fault and the applicable cap. The contract should also establish a claims process covering notice, preservation of evidence, deadlines, joint inspection, disposal of damaged goods and communication with insurers.

Carriers, freight forwarders and warehouse keepers benefit from statutory liens. For warehouse keepers, this follows in particular from section 475b HGB. For the customer, withholding operationally critical goods can create a major business risk. The agreement should therefore address scope, disputed claims, release against substitute security and access to goods owned by the customer or third parties.

Subcontracting, IT, insurance and exit

The use of carriers, warehouse operators and other subcontractors is standard practice, but it should not blur accountability. The agreement needs to state which services may be subcontracted, whether consent is required and which minimum standards must be imposed throughout the chain. The customer should retain one responsible contractual counterparty for the overall service.

Modern logistics is also an IT project. Interfaces, scanning, inventory data, access rights, information security and contingency processes require the same precision as the physical service. The contract should define manual fallback procedures and data reconciliation following system outages. Data protection and cybersecurity become particularly relevant where personal shipping data, telematics or cloud platforms are involved.

Insurance must match the contractual risk. Cargo, warehouse, general liability, cyber and professional indemnity policies cover different exposures and contain different exclusions. Limits and deductibles should therefore be tested against the agreed liability framework.

The contract also requires a workable exit. Release of goods and data, inventory verification, transition to a replacement provider, continuation of critical services and handling of open claims should be planned in advance. Only an agreement that also controls the end of the relationship can protect continuity during a provider change.