Skip to main content

Set up local zones for Transport Networks

This article shows how to setup allocated Local Zones for Transport Networks. Zones set here are an override to the official Gazetteer zones.

Duygu Demir avatar
Written by Duygu Demir
Updated over 3 weeks ago

Below covers how you can configure your local zones for the Network, or also how you can add zones that are officially not allocated to yourself, but you do actually serve. Accurate postcode zone configuration is essential for ensuring resources like depots, trucks, or placeholder resources are allocated efficiently. Misconfigurations could lead to unintended assignments or operational inefficiencies.

The postal codes and depots that you assign in this table, will basically override the official "gazetteer" This overriding process helps in automating resource assignments and ensures depot stops are correctly added to orders, preventing misrouting or bypassing critical steps.

Efficient transport operations depend significantly on well-configured postcode zones. Misconfigurations can affect order routing, resource allocation, and depot processing, potentially causing delays or inefficiencies.

Navigate to Locations -> Transport networks Tab to add your local zones to the system.

  1. Select transport network where you would like to make adjustment/ setup of local zones and navigate to Owned postal codes


In the table, you will have options to insert the country code, the postcode and your depot code.

Use the table on the left for full postcodes and "starts with" postcodes,
Use the table on the right for inserting postcode ranges.


Default depot code will make sure the consignments to get assigned to the correct depot once the postcode can not be found in the below tables.


Save your changes after adding all the date


Note: If there is no depot setup for the collection and delivery points that are in your consignment, the default zone will be applied automatically. Additionally, placeholder resources like 'Dummy OA' may also be assigned automatically in such scenarios, which could result in unintended routing. Periodically review configurations to address such issues.


Did this answer your question?