Skip to main content
All CollectionsPallet networksPalletlinePalletLine - Configuration
Pallet network routing & local zone extension
Pallet network routing & local zone extension
Duygu Demir avatar
Written by Duygu Demir
Updated over 10 months ago

The depot codes corresponding to a specific collection or delivery location are evaluated based on the postcode manager, which may include a default.

The result of the evaluation is stored on the consignment and visualised as such after export; there are also columns in the order table that visualise it:

If only the requesting depot is visible and not the collection/delivery depot, this means that the consignment has a collection/delivery depot that are both owned by the tenant. In that case we don’t store the depot codes, as they are also used to determine whether or not status updates / documents need to be synced with Contrado, which we won’t do for these consignments to prevent creating loops. This is in the assumption that these consignments also won’t be executed by leveraging the Palletline hubs, but instead the depots will execute them themselves.

Owned postal codes

Extra owned postal codes wrt the Contrado Gazetteer data can be configured in Qargo. This can be used when the depots extend their local collection/delivery area as they build up a better relationship with the clients in that zone than the main depot in that zone. The Palletline system allows passing a postal code to the API for these use cases. This instructs Contrado not to gazetteer that postal code themselves but instead to accept the value passed. We call this an “override”.

For the Palletline integration specifically, the result of this evaluation is:

  • For export:

    • if exporting a collection stage: passed for the delivery stage only

    • if exporting a delivery stage: passed for the collection stage only

    • if exporting a direct stage: never passed

  • For label generation: always passed for both collection and delivery. As at the point where the label is generated there is not yet known which stage will be exported, we always pass it for both stages.

  • This might be an issue if the delivery depot code was overridden during label generation but not during export. If the depot would execute the collection, as the delivery depot code is on the label, the label might be incorrect and would need to be reprinted in the depot. The collection depot code is not on the label, so there the issue never arises.


    When using postcode overrides, this is visualised in Contrado as follows:

Did this answer your question?