Skip to main content

What is an order?

Written by Rasmus Hallgren
Updated this week

Overview

An order in Gordon Cloud represents a delivery that needs to be completed. It contains all the necessary information required to plan, execute, and track a delivery from creation to completion.

Orders are the foundation of the delivery workflow. Every route, stop, and delivery activity in the platform is built around orders.

An order typically includes key details such as:

  • Recipient information (name, address, contact details)

  • Delivery details (date, time window, instructions)

  • Items or goods to be delivered

This information enables planners and dispatchers to assign orders to routes, optimise deliveries, and ensure that drivers have the correct details when performing deliveries.

How orders are used

Orders move through different stages in the delivery process:

  1. Created – The order is added manually, imported, or received via integration.

  2. Planned – The order is assigned to a route.

  3. Dispatched – The route is executed by a driver.

  4. Delivered (or updated) – The delivery is completed or updated with a final status.

Throughout this lifecycle, the order acts as the central object that connects planning, execution, and tracking.

Why orders matter

Orders ensure that:

  • Deliveries are structured and traceable

  • Drivers have clear instructions and accurate information

  • Planners can organise and optimise routes efficiently

  • Operations teams can monitor delivery progress in real time

Understanding what an order is is the first step to effectively working with deliveries in Gordon Cloud.

Did this answer your question?