---
title: "Pallet network routing & local zone extension"
description: ""
url: https://help.qargo.com/us/articles/143822-pallet-network-routing-local-zone-extension
locale: us
updated: 2024-10-24
---

# Pallet network routing & local zone extension

The terminal codes for a specific pickup or delivery location are evaluated based on the ZIP code manager, which may include a default.\
\
The result of the evaluation is stored on the shipment and is visualized as such after export. Columns in the order table also visualize it:\
​

![](https://help.qargo.com/media/fed5ab800eb1-image.png)

:::callout{tone="note"}
If only the requesting terminal is visible and not the pickup/delivery terminal, the shipment has a pickup terminal and a delivery terminal that are both owned by the tenant. In that case, the terminal codes aren't stored. These codes are also used to determine whether status updates/documents need to be synced with Contrado, which doesn't happen for these shipments to prevent loops. This assumes that these shipments also won't be executed through the Palletline hubs; instead, the terminals execute them themselves.
:::

## Owned postal codes {#h_e85251f70f}

Extra owned ZIP codes in addition to the Contrado Gazetteer data can be configured in Qargo. This is useful when terminals extend their local pickup/delivery area because they have a better relationship with the clients in that zone than the main terminal in that zone. The Palletline system allows passing a ZIP code to the API for these use cases. This instructs Contrado not to look up that ZIP code in its own gazetteer, but to accept the value passed instead. This is called an “override”.\
For the Palletline integration specifically, the result of this evaluation is:

-   For export:

    -   if exporting a pickup stage: passed for the delivery stage only
    -   if exporting a delivery stage: passed for the pickup stage only
    -   if exporting a direct stage: never passed\
        ​
-   For label generation: always passed for both pickup and delivery. When the label is generated, it isn't yet known which stage will be exported, so it's always passed for both stages.\
    ​
-   This might be an issue if the delivery terminal code was overridden during label generation but not during export. If the terminal executes the pickup, the label might be incorrect because the delivery terminal code is on the label, and the label would need to be reprinted at the terminal. The pickup terminal code isn't on the label, so the issue never arises there.\
    \
    \
    When ZIP code overrides are used, this is visualized in Contrado as follows:\
    ​

    ![](https://help.qargo.com/media/cf3208932188-image.png)


## Related articles

- [Multiple terminals](https://help.qargo.com/us/articles/143914-multiple-terminals.md)
- [Set up local zones for transport networks](https://help.qargo.com/us/articles/147313-set-up-local-zones-for-transport-networks.md)
- [PN - PalletLine order import/export](https://help.qargo.com/us/articles/143830-pn-palletline-order-import-export.md)
- [Pallet network routing & Gazetteer](https://help.qargo.com/us/articles/143815-pallet-network-routing-gazetteer.md)
- [PN - Palletways: Multi-terminal support](https://help.qargo.com/us/articles/608889-pn-palletways-multi-terminal-support.md)
