If you use the same rate cards on locations that have the same postal code prefix, or are in the same range, you can use the postcode zone groups.
Qargo supports robust postcode zone configuration to ensure accurate mapping and compatibility with pricing tables.
Navigate to Locations
Click on Postcode zone groups
Click on New postcode zone group on the left side
Complete the 'General Info' to add a list of post code zones or post code ranges. This includes:
Name of the postcode zone group
active toggle - defaults to Active when creating new groups
a description - use this for any specific details that should be visible to users selecting this group for rates.
There are 2 tables where post code zones can be configured.
Postal Code prefixes. These fields will use just the beginning letters or numbers of the recognised post code syntax of the corresponding country. For example, UK postcodes all begin with a letter, which can be one or 2 characters, this is the prefix. If setting ranges for countries that do not use this type of format, this table can be left blank, and these would be set in the ranges table.
Postal Code ranges. Ranges can be a combination of both alpha and numerical data. The critical thing when setting a range, is to ensure the beginning and end points capture the entire range.
Including Letters in Postcode Zones
Postcode zone groups in Qargo also support alphanumeric formats, like the Dutch "1000 AA" style. To define these zones, set a range with flexible criteria that includes both numeric and letter-based codes. For example:
To include "1000 AA": Set the range from
Start = 1000toEnd = 1001. Incrementing the numeric portion of theEndrange ensures inclusivity for alphanumeric zones.Use the same exclusive-end rule used for numeric ranges to maintain accuracy when mapping these alphanumeric postcodes.
!!️ Qargo uses an inclusive start and an exclusive end rule to define ranges. This means that the range will include the lower bound (start value) while excluding the upper bound (end value). Always set the end value to one unit greater than the highest postcode you want to cover.
To include only postcode 1000: Start = 1000, End = 1001. To include postcode 1000 through 1300: Start = 1000, End = 1301. For example, postcode 1300 will be included while 1301 will be excluded. Incorrectly configuring range values can lead to pricing errors, so it's crucial to use the inclusive start and exclusive end rule to ensure that prices are applied as expected.
This flexibility also applies to alphanumeric postcodes, ensuring compatibility. For example, "1000 AA" could be configured by setting a range from Start = 1000 to End = 1001, accurately mapping such alphanumeric codes.
Using Postcode zone overrides for route charge calculations.
Why use a postcode zone override?
Postcode zone overrides allow users to use a different post code instead of the specific one assigned to the location.
Useful in cases where a location is associated with multiple addresses, for example the Port of Antwerp.
Key postal codes associated with the port and surrounding areas:
2000: Antwerp city center (where the Port Authority's old address was located).
2030: Directly associated with industrial and port terrains, including many terminal addresses and the current Port Authority address.
2040: Associated with the districts of Berendrecht-Zandvliet-Lillo, which are located in the far north of the port area.
2100: Home to the European Logistical Support Office (ELSO) facility located within the broader Antwerp area.
In this example each of these postcodes can be mapped to one specific postcode that can then be used for generating a route based cost calculation.
Create a postcode zone override
Navigate to LOCATIONS > Postcode zone groups
Click '+ New postcode zone group'
Give the new zone a name that clearly identifies what it is used for.
Add a description to help users understand what this zone is used for
Create the zone mapping: (see article link below for more details)
Postcode Prefix - use the beginning of the postcode only.
Postcode range - use a start and end range of postcodes, allocating the range to a single postcode.
‼️ All postcodes that fall within the range will be mapped to the specified zone
Enter the country code - all mapping must be within the same country
Enter the postcode prefix or range in the 'starts with' / 'start' & 'end' column
Enter the OVERRIDE postcode to use in the 'Zone code' column
This will be the postcode used in place of the original.
Add all overrides to the same table.
📚 Only 1 postcode zone group can be entered in the organisation settings.
Click Save
The next time a location is used that contains a postcode included in the override table, the postcode specified in the Zone Group will be used instead of the actual postcode in the location.
Practical Examples of Postcode Ranges
Four-Digit Postcode Examples:
To include only a specific postcode, such as
1000:Start = 1000,End = 1001.To include multiple postcodes, such as
1000through1300:Start = 1000,End = 1301.
To include an alphanumeric postcode such as "1000 AA", you can define the range with
Start = 1000andEnd = 1001. This approach ensures the numeric part matches while accommodating alphanumeric elements.
Five-Digit Postcode Examples (International Uses):
To cover postcodes up to and including
99999, set the range as:Start = lowest desired value,End = 100000.
The principles of inclusive start and exclusive end apply universally across geographic regions and postcode formats. You can also combine prefixes and ranges to account for the complete scope of the zones covered, ensuring compatibility with diverse logistic configurations.
When dealing with country-specific formats such as the Dutch alphanumeric "1000 AA," configurations can easily account for such variations without deviating from the principles of inclusivity and exclusivity.
To complete the table, enter the Country using the appropriate 2letter code. Ensure that postcodes are entered without typographical errors, such as confusing the letter 'O' with the number '0,' to prevent mapping inaccuracies.
Enter the prefix and / or ranges.
Enter the Zone Code associated the post code. This can be a Name, ID Number or Alphanumeric combination. Multiple prefixes / ranges can be assigned to the same zone code as necessary.
Once added, you can add the Zone Group to the rate cards.
If switching to a different postcode zone group results in unpopulated columns, ensure to copy the zone entries before making the change and re-paste them afterward to maintain accurate mappings.
If you notice missing rates for specific orders, ensure the delivery postcode is included in the rate card setup and update the zoning configurations for the corresponding regions. Missing zones can be added manually, and charges can then be manually recalculated to resolve this issue.
If added to your rate card, there will be a link add at the bottom of your postcode zone group so that you can easily navigate to that rate card.
Troubleshooting Incorrect Zone Mapping
First, verify that the affected rate card includes all relevant postcode groups and tiers for the specific scenario, and ensure no prefixes or ranges are misconfigured.
Occasionally, mapped zones may not correspond to user expectations. This is typically due to conditions in the rate card:
Verify Vehicle Type and Zone Conditions: Certain vehicle types may influence zone allocation. For example, if a job price is mapped to Zone B instead of the expected Zone A, check the vehicle type and applicable conditions in the rate card that might redirect the zone pricing.
Check Related Calculation Conditions: Confirm that all pricing logic in your configuration supports your expected outcome. Making these validations will solve unexpected results and align pricing with intended zone mappings.3. Missed Upper Boundary: If the highest boundary is not included as expected, verify that the
endvalue is set one unit higher than the desired value.Cross-Region Configurations: When spanning multiple countries, ensure that configured ranges align correctly with each country's postcode format and structure.
Handling Gazetteer Updates from External Networks
Qargo also integrates with external networks like TPN and Hazchem for managing postcode areas. Here’s what you need to know:
Network-Versus-Qargo Responsibilities: Qargo does not internally manage the assignment of postcodes for TPN and Hazchem. Instead, changes in depot assignments or postcode areas are governed by these networks’ own gazetteers.
API Updates: Updated assignments are automatically transmitted to Qargo via API payloads during import/export operations.
Custom Overrides: If you use owned postal codes, you can configure or update these in Qargo to enforce specific depot assignments for exports. By managing these updates effectively, you can synchronize Qargo settings with external changes without requiring additional manual interventions.
