Overview
When creating orders in Gordon Cloud—whether manually, via CSV import, or through integrations—each order is built from a set of defined fields.
These fields control how the order is validated, planned, and executed. Some are required, meaning the order cannot be created without them, while others are optional but enable more advanced workflows.
This article provides an overview of the most important fields, how they are used, and what is required to successfully create an order.
Why correct field mapping matters
Correctly populating order fields ensures that:
Orders are successfully created without errors
Routes can be optimised correctly
Drivers receive accurate delivery instructions
Notifications are triggered properly
Integrations remain synchronised and reliable
Incorrect or missing required fields will result in failed imports or incomplete orders.
Required & recommended fields
Below is a list of recommended fields to use when creating the order. We have included the field name, short description, example value, and an indication whether it's a required (✅) or recommended (👍) field.
Definition | Example | Required |
external_ref |
| ✅ |
customer-name Name of the customer |
| ✅ |
address Customer address |
| ✅ |
zip Customer postal code |
| ✅ |
city Customer postal city |
| ✅ |
mobile Customer phone number |
| 👍 |
Customer email address | 👍 | |
deliverydate Order delivery date |
| ✅ |
time-window Time window the customer has requested |
| ✅ |
deliverygroup Name of the Delivery Group the order belongs to |
| ✅ |
notes Notes to the driver |
| 👍 |
inventory[0].name Item name |
| ✅ |
inventory[0].quantity Item quantity |
| ✅ |
inventory[0].weight Item weight (in kg) |
| 👍 |
inventory[0].type Item temperature zone |
| 👍 |
Optional fields
Below is a list of optional fields to use when creating the order. We have included the field name, short description, and an example value.
Available field | Example |
external_id External ID from your internal system |
|
address2 |
|
country_code Country code (ISO) |
|
entrycode Entry code to the customer's building |
|
latitude Latitude coordinates of the address |
|
longitude Longitude coordinates of the address |
|
description Description of the order |
|
delivery-requirements.delivery-in-person |
|
delivery-requirements.id-check If you want the end customer to show their ID upon delivery, set this field to |
|
baseServiceTime Will add extra service time (minutes) to the order if it requires extra time for the driver. |
|
inventory.[0].width Width of the inventory (cm) |
|
inventory.[0].height Height of the inventory (cm) |
|
inventory.[0].length Length of the inventory (cm) |
|
inventory.[0].serviceType Specify if it's a delivery or pickup item. |
|
inventory.[0].articles.[0].name Name of articles tied the item. |
|
inventory.[0].articles.[0].quantity Number of articles with the name tied to the item. |
|
Summary
An order in Gordon Cloud is defined by structured fields that control every part of the delivery process.
At a minimum, you must provide external_ref, delivery date and time, address information, and item information. Adding more detailed fields improves planning accuracy, delivery quality, and automation capabilities.
For full technical details and formatting requirements, see the CSV specification and integration documentation.