Tank container logistics
Tank container logistics: what operational requirements does this place on a TMS?
At first glance, planning a tank container may seem similar to planning any other container. You need a loading location, a destination, a time, and a means of transport. In practice, however, tank container logistics is considerably more complex.
A tank container is used to transport liquids, gases, and other bulk products. These may include food products, as well as chemicals and hazardous substances. As a result, planning is about much more than simply determining where a container is available.
A TMS for tank container logistics must support more than just trip planning. The system must be able to connect the container, product, cleaning, documentation, planning, and transport status.
Quick navigation:
- What makes tank container logistics different from regular container logistics?
- 1. Cleaning must be part of the planning process
- 2. Cargo history and tank suitability must come together
- 3. ADR information must be linked to the transport order
- 4. Loading and unloading appointments must be part of the planning process
- 5. Multimodal transport requires planning per transport leg
- 6. Document management must be linked
- Conclusion
Co-founder and Director of Adaption, expert in logistics software and process digitalization
What makes tank container logistics different from regular container logistics?
In standard container transport, the main focus is usually on availability, location, dimensions, weight, planning, and the movement of the container.
With tank containers, the suitability of the specific tank also plays an important role. The planner must, for example, be able to assess:
- what the tank’s previous cargo was;
- which product will be loaded next;
- whether cleaning is required;
- whether the correct documents are available;
- whether the tank is technically suitable for the product;
- whether additional treatment is required, such as heating;
- which regulations apply to hazardous substances;
- when the tank needs to be available at a terminal.
As a result, tank container planning involves more interdependencies than simply planning a route from A to B.
A change in one part of the process can affect the rest of the planning. If cleaning takes longer than expected, for example, a loading slot may be missed. A change of product may mean that a different tank is required. A missing document may mean that a container cannot be loaded. It is precisely these dependencies that place specific requirements on the Transport Management System.
1. Cleaning management must be part of the planning process
After unloading, a tank container often cannot immediately be used for its next load. Depending on the previous and next cargo, cleaning may be required, possibly combined with treatments such as drying, steaming, or heating.
In Europe, the EFTCO Cleaning Document (ECD) is widely used for this purpose. It records the cleaning operations performed and the applicable cleaning codes. For a TMS, this means cleaning must be an integral part of operational planning. The system should, for example, be able to record:
- where and when cleaning takes place;
- which treatment is required;
- which cleaning codes and documents apply;
- from what point the tank is available again.
This means a planner does not have to manually check whether a tank is actually ready for its next assignment after unloading.
2. Cargo history and tank suitability must come together
In regular container transport, the main consideration is whether a container is available and meets the required technical specifications. With tank containers, it is also important to know what was previously carried in the tank and whether the tank is suitable for the next product. A planner must therefore be able to determine whether a specific tank can be used for a specific load.
The following data is relevant, among other things:
- tank type and capacity;
- technical specifications;
- previous cargoes;
- product or P numbers;
- product compatibility;
- inspection status;
- customer requirements and usage restrictions.
This information must be linked to the tank itself. This ensures that the operational history remains available even after a transport order has been completed.
TMS software therefore requires not only an order history, but also a clear equipment history. A tank is only truly available when it is not only free, but also suitable and ready for the next load.
3. ADR information must be linked to the transport order
Tank containers are widely used for chemical products and other hazardous liquids. As a result, ADR information often plays a more structural role in tank container transport than in regular transport planning.
When hazardous substances are transported, the relevant ADR information must be correctly linked to the product and the transport operation. Depending on the cargo, this may include:
- UN number;
- proper shipping name;
- ADR class;
- packing group;
- tunnel restrictions;
- hazard labels;
- tank instructions;
- quantity and weight;
- required transport documentation.
This information must be stored in a structured way within the TMS. It can then be used for planning, documentation, and operational checks without planners having to enter the same information repeatedly.
4. Loading and unloading appointments must be part of the planning process
In tank container transport, loading and unloading times are often closely linked to production processes, terminal capacity, and safety procedures. As a result, missing a time slot can have consequences that go beyond simply arriving later.
Chemical terminals and production sites, for example, often work with fixed loading and unloading times. Additional requirements may also apply to drivers, equipment, documentation, and registration procedures. A missed time slot can affect waiting times, subsequent transport, and multimodal connections.
The TMS must therefore link loading and unloading appointments directly to the transport planning. The planner must be able to see when a tank is expected, which preparations are still outstanding, and whether the planned arrival time is still achievable.
5. Multimodal transport requires planning per transport leg
Tank containers are specifically designed to be transported between different modes of transport without transferring the product itself. As a result, combinations of road, rail, and sea transport are relatively common within a single logistics assignment.
An assignment may, for example, consist of:
- transport from a depot;
- cleaning;
- transport to the loading location;
- pre-carriage to a terminal;
- rail or sea transport;
- onward transport to the consignee;
- return transport to a depot or the next location.
A Transport Management System must be able to plan these transport legs individually while still treating them as one integrated assignment.
If one part of the operation is delayed, it must be immediately clear which subsequent connection or appointment will be affected.
6. Document management must be linked to the tank, cargo, and transport
In tank container logistics, documentation is not only linked to the transport order, but often also to the tank itself and the specific cargo. This makes document management more complex than in transport operations where documents are primarily linked to a single trip or order.
This includes cleaning documents, ADR documentation, inspection records, transport documents, and product information.
Digital storage alone is therefore not sufficient. The TMS must make it clear which document belongs to which tank, cargo, or assignment and whether all required documentation is complete. A cleaning document, for example, should remain linked to the relevant tank and cleaning operation so that this information can be retrieved again later.
Document management therefore becomes an integral part of equipment management and transport planning.
Conclusion: tank container logistics places different demands on a TMS than regular container transport
Planning is not simply about knowing where a container is located and when it is available. The previous cargo, cleaning status, next cargo, product specifications, ADR data, and technical characteristics of the tank can all determine whether a transport operation can be carried out.
In addition, tank container transport is inherently multimodal. A single assignment may involve multiple transport legs, terminals, depots, cleaning stations, and carriers. A delay or missing activity at the beginning of the process can affect every subsequent step.
A TMS that supports these operations must therefore go beyond planning trips and storing documents. It must connect the tank container, cargo history, cleaning, product, documentation, and transport planning.
It is precisely this integration that determines whether planners are simply recording what happens digitally or actually gaining control over their tank container operations.
Sources and background
- UNECE, ADR 2025
https://unece.org/adr-2025-files - Government of the Netherlands, ADR 2025
https://www.rijksoverheid.nl/onderwerpen/gevaarlijke-stoffen/vraag-en-antwoord/wat-is-het-adr - EFTCO, EFTCO Cleaning Document (ECD)
https://www.eftco.org/ecd - EFTCO, EFTCO Cleaning Codes
https://www.eftco.org/eftco-cleaning-codes - EFTCO, Cleaning Stations
https://www.eftco.org/cleaning-stations - Stolt Tank Containers
https://www.stolttankcontainers.com/