Shipment vs order vs trip vs stop

Transport software talks about orders, shipments, trips and stops as if everyone agrees on the meaning. They don’t. Most operational confusion in a TMS comes from one of these four being misused. Getting them straight is the foundation of clean data and honest reporting.

The four objects

Order

The commercial contract with a customer. One order is what the customer asked for and what you will invoice.

• One customer, one agreed price.
• Contains one or more stops (pickups and deliveries).
• Owns the revenue side of the data.

Stop

A single physical action at a single address: a pickup or a delivery.

• Belongs to one order.
• Has a time window, an address, a contact.
• Carries cargo (items, weight, volume).

Shipment

The physical movement of cargo from a pickup to a delivery. It’s the execution view of what’s promised in the order.

• One order can have multiple shipments (e.g. split delivery).
• One shipment connects at least one pickup and one delivery.
• Owns the carrier and execution data (assigned vehicle/carrier, POD).

Trip

A route a vehicle drives, made up of one or more stops, often across multiple shipments.

• One vehicle, one driver, one day (typically).
• Carries stops from one or many shipments.
• Owns the operational cost side (fuel, hours, tolls, kilometres).

How they relate

Customer
  ↓
Order
  ├── Stop A (pickup)
  ├── Stop B (delivery)
  └── Shipment X (links A → B)
                ↓
              Trip 42 (vehicle, driver)
                ├── Stop A
                ├── Stop B
                └── Stop from another order

One trip can carry stops from multiple orders. One order can be split across multiple trips. The shipment is the bridge between commercial and operational.

Why mixing them up breaks reporting

• Margin per “order” but not per shipment — split deliveries become invisible.
• Cost per “trip” but no link to revenue — operations can’t see what made money.
• CO₂ allocated to the order, not the shipment — incorrect when one order has multiple shipments on different vehicles.
• POD against the trip, not the shipment — proving delivery to this customer’s cargo becomes impossible.

A clean TMS keeps the four objects separate and links them explicitly.

How Routix models it

• Orders hold customer, stops, cargo and revenue.
• Stops belong to an order; cargo belongs to a stop.
• Shipments link an order’s pickup(s) and delivery(ies), and carry the carrier assignment.
• Trips (in Dispatch) carry stops from one or more shipments and represent the vehicle’s day.
• Cost and revenue are tracked per shipment (commercial) and per trip (operational), and reconciled.

Once you internalise these four, every screen in the app makes more sense.

Related concepts

• What is a TMS?
• What is dispatch management?
• LTL vs FTL

See this in Routix

To see this data model in a real product, start on www.routix.com  and then compare Orders, Stops, Shipments and Dispatch. Those four Routix surfaces make the commercial and operational objects explicit instead of mixing them together.