Transport order: what it is, what it contains and how to manage it

In brief

In day-to-day practice, many companies call the form used to organise a trip a transport order: customer, collection location, destination, date, goods, references, agreed price and operating instructions. It is a very useful item, but one misunderstanding should be avoided: the operational order does not automatically coincide with the transport contract governed by law.

For an SME, the most robust approach is to treat the order as the single operational source for the individual assignment and link it, where it exists, to the contract or commercial agreement governing the relationship with the customer. This way, the planner knows what has to be carried out, while administration and management can reconstruct the economic and contractual agreement on which the service is based.

An operational order and a contract are not the same thing

The transport contract is the legal relationship under which the carrier undertakes to move goods from one place to another in exchange for payment. The order is often the document through which that relationship is made concrete in a specific activity: “collect tomorrow at 08:00 in Bergamo, deliver to Verona, 12 pallets, customer reference X”.

In ongoing relationships, there may be a framework contract and dozens or hundreds of implementing orders. In other cases, an accepted quotation, email, order and agreed terms may together document the relationship. This is why it is not prudent to decide that “the order is enough” or, conversely, that “the order has no value whatsoever”: the content, form and context of the relationship have to be considered.

Operationally, it is advisable to distinguish at least three levels:

1. commercial agreement/contract, which governs financial terms and responsibilities;
2. transport order, which describes the individual service;
3. execution and evidence documents, such as DDT, CMR, POD and other relevant documents.

What Legislative Decree 286/2005 says

The central Italian reference for third-party road haulage contracts is Legislative Decree no. 286 of 21 November 2005. Article 6 generally requires a written form and a date certain to promote fairness and transparency in relations between the parties. The provision also identifies the essential elements of contracts entered into in writing.

The elements that the rules require or consider in the contract include the identification of the carrier and contracting party, any loader, the carrier’s registration number with the Albo, the type and quantity of goods, the places of taking over and redelivery, and the financial elements provided for by the current text. The legislation has been amended several times: before using a standard contract template, it is therefore advisable to check the updated text and have it validated by a professional.

For an SME, the practical point is not to turn every dispatcher into a lawyer. It is to create a flow in which essential information does not remain scattered between a phone call and a chat. A well-structured order does not replace the contract, but it reduces operational ambiguities and makes it easier to demonstrate what was requested and what changed.

Which data it is useful to collect

An order form should contain at least:

• a unique order number or reference;
• the customer/contracting party and operational contact;
• any loader different from the contracting party;
• collection location, date and time window;
• delivery location, date and time window;
• description of the goods;
• quantity, weight, packages or pallets where relevant;
• any characteristics affecting the vehicle required;
• price or reference to the rate list/contract, if company organisation provides for it;
• notes and instructions received from the customer;
• associated documents;
• assigned driver and vehicle;
• activity status;
• history of relevant changes.

For dangerous goods, waste, food, exceptional transport or other special categories, additional information and documents may be needed. The standard order should therefore not be used as a universal compliance checklist.

How to manage changes and versions

The real problem starts when the order changes. If the customer moves collection from 08:00 to 11:00 or changes the delivery address, the new data must immediately become the current operational version. Continuing to leave an old email, an Excel sheet and a WhatsApp message in circulation creates three different “truths”.

A good internal rule is: one form alone represents the current status of the order, while important changes remain recorded in the history. There is no need to keep every minor correction, but it must be possible to understand who changed a material piece of information and when.

Practical example

A customer sends an email request for 18 pallets from Brescia to Bologna. The dispatcher records the order and assigns a vehicle and driver. In the afternoon, the customer communicates that delivery will no longer be in the city of Bologna but at a warehouse at Interporto.

If the change remains only in the dispatcher’s chat, the driver may leave with the wrong address. If instead the amendment updates the operational order, the new destination becomes the reference for everyone. The history keeps a record of the change and the company can reconstruct what happened in the event of a dispute.

Operational checklist

• Does each order have a unique identifier?
• Are the customer, collection and delivery always completed?
• Are weight and quantity recorded when they affect the vehicle and documentation?
• Are special instructions visible to those who have to carry them out?
• Are important changes recorded and communicated to the driver?
• Can the relevant contract/rate list be retrieved?
• Are DDT, CMR or other documents associated with the same order when present?

Frequent mistakes

Using WhatsApp as the order archive. Chat is excellent for communicating, but weak as the single source of operational information.

Confusing the order and the contract. A complete order helps execution, but does not by itself guarantee that all legal requirements of the written contract have been met.

Overwriting a change without a record. If a destination or time changes, knowing when and why may be important.

Entering only what the dispatcher needs. The order should also be readable by administration and the driver, with access consistent with each role.