--- title: "Shipments" description: "What a Shipment is (one pickup + dropoff), the pivot between an order and a tour, routing onto a tour, and its statuses." url: "https://support.pr-4.orbit.do/en/core-features/shipments" locale: "en" lastReviewed: "2026-09-13" --- # Shipments What a Shipment is (one pickup + dropoff), the pivot between an order and a tour, routing onto a tour, and its statuses. > **Note:** A `Shipment` is a single cargo move — one pickup and one dropoff for a defined load. It is the pivot that links what a customer booked to how it is actually driven. A `Shipment` is the one thing physically carried from A to B: a single pickup, a single dropoff, and the load that travels between them. It is not the customer's booking — that is the `Order` — and it is not the plan that drives a vehicle — that is the `Tour`. Because every `Shipment` references both an `Order` and the `Tour` carrying it, it is the pivot that joins Orbit's commercial side to its operational side. You bring a `Shipment` into play by **routing** it onto a `Tour`. Its pickup and dropoff then become two positions in that tour's ordered list of stops, and the carrier who does the work attaches to the `Tour` — not to the shipment itself. **Key highlights** * **One move, two ends** — a single pickup and a single dropoff for one defined load. * **The pivot** — a `Shipment` joins the commercial `Order` to the operational `Tour`. * **You route, not assign** — route a `Shipment` onto a `Tour`; the carrier attaches to that tour. * **Unrouted is normal** — a shipment waiting to be planned is a resting state, not a fault. * **Nothing is deleted** — cancelling or failing a shipment keeps the record and its history. ## Routing a Shipment onto a Tour Planning a `Shipment` means routing it onto a `Tour`. In Orbit MissionControl you either add it to an existing tour or create a new tour from it. Once routed, its pickup and dropoff take their place in the tour's stop sequence, and the carrier is assigned to the tour to carry it. A `Shipment` carried directly sits on one `Tour` at a time, and it is freely re-routable. If plans change, you can unroute it and route it onto a different tour; the tour it left is filed into the shipment's history rather than erased. A shipment carried in stages is routed one stage at a time, so its legs can sit on several tours at once: see the **Legs** article. Either way, you never assign a carrier to a shipment directly. You route the shipment, then assign the carrier to the tour. ## Shipment statuses A `Shipment`'s status is reached in two ways. The **planning** states are the ones you control directly by routing and unrouting. The **execution** states follow automatically from the tour as its driver works through the stops — you do not set them, and there is no way to push a shipment straight to `Delivered`. To understand a shipment's execution status, look at its `Tour`. | Status | What it means | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Unrouted` | Not yet on a tour — waiting to be planned. A normal resting state. | | `Partially Routed` | Carried in stages, with some stages planned onto a tour and some not yet. | | `Routed` | Planned onto a tour, but the tour has not started moving it yet. | | `En Route: On the Way to Pickup` | The tour is running and heading to collect the load. Set by the tour, not by you. | | `En Route: On the Way to Delivery` | The load has been collected and is on its way to the dropoff. | | `Waiting at Hub` | The load has been set down at an intermediate stop and is waiting for its next stage to collect it. A planned pause, not a fault. | | `Waiting for Tour Review` | The tour has finished and is awaiting the operator's review. | | `Delivered` | The move is complete. | | `Cancelled` | The move was called off; the record is kept. | | `Failed` | The move could not be completed; the record is kept as a faithful account of what happened. A shipment closes here as undeliverable when a `Load` on it is written off. | ## Unrouted, cancelled and failed are all normal An `Unrouted` shipment is not broken — it simply has not been planned onto a tour yet, and sits ready for you to route it. In Orbit MissionControl these gather in the **Unrouted** view so you can plan them together. Cancelling or failing a `Shipment` never deletes it. Both actions detach the shipment from its tour and mark it accordingly; the record and its full history remain available. A `Failed` shipment is a faithful record of a move that could not be completed, not an error to be cleared away. A shipment also closes as undeliverable when a `Load` on it is written off, because goods that are written off will never travel again. Loads on the same shipment that were delivered stay delivered, so the record shows what arrived as well as what did not. See the [Writing Off Goods That Cannot Be Delivered](https://support.pr-4.orbit.do/en/multi-leg-logistics/writing-off-goods-that-cannot-be-delivered) article. ## Example A load of chilled goods needs to travel from Rotterdam to Berlin. Orbit creates a `Shipment` with the Rotterdam pickup and the Berlin dropoff; it starts `Unrouted`. An operator routes it onto a `Tour` with a refrigerated vehicle and assigns a carrier to that tour. When the driver starts the tour, the shipment moves on its own through `En Route: On the Way to Pickup` and `En Route: On the Way to Delivery`, then to `Waiting for Tour Review` and finally `Delivered` — all driven by the tour, not by editing the shipment. ## Frequently asked questions **Q: Why is my shipment Unrouted?** Because it has not been planned onto a `Tour` yet. `Unrouted` is a normal waiting state — route the shipment onto a tour when you are ready. **Q: How do I move a shipment to Delivered?** You do not set it directly. A shipment's execution status follows its tour, so it reaches `Delivered` when the tour carrying it is driven to completion. **Q: How do I give a shipment to a carrier?** Route the shipment onto a `Tour`, then assign the carrier to that tour. There is nothing to assign a carrier to on the shipment itself. **Q: Can one shipment be on two tours at once?** Yes, when it is carried in stages: each stage is routed onto its own `Tour`, so a shipment travelling via a hub can be on two tours at the same time. A shipment carried directly is on one tour at a time and is freely re-routable, with each previous tour kept in its history. See the **Legs** article. **Q: Does cancelling or failing a shipment delete it?** No. Nothing is deleted. The shipment detaches from its tour and is marked `Cancelled` or `Failed`, but the record and its history stay available. **Q: How does a shipment relate to its order and tour?** The `Shipment` is the link between them: it belongs to one `Order` (the commercial side) and is carried by one `Tour` (the operational side). See the **Orders** and **Tours** articles.