Introduction
What is Transport Network Auto HUB Split?
A configuration feature that automatically inserts hub stops into pallet network transport orders at the point of order creation.
Hub assignment is driven by a postal code zone collection defined on the transport network, mapping delivery or collection postcodes to specific hub depots.
An optional alternative hub can also be configured per postal code rule, used for cross-docking scenarios.
Why does it exist?
In central pallet networks (e.g. Palletline, Palletforce), orders typically need to route through one or more hub depots between collection and delivery.
Previously, planners had to manually add hub legs to consignments after order creation — a repetitive and error-prone process.
Auto HUB Split eliminates this manual step by resolving and inserting the correct hub automatically based on the order's postal codes.
How does it work?
A Hub postal codes zone collection is configured on the transport network, listing postal code prefixes and the hub depot codes they map to.
When an order is created, Qargo evaluates the collection or delivery postal code against this table and inserts the matched hub as a stop in the consignment structure.
If a hub depot has no Location assigned, it will not be inserted — the location field controls whether the hub is active.
Hub postcodes must be added at tenant level before it becomes available. Where these are blank the feature will fail to insert the stop.
Terminology
Term | Definition |
Hub | A central transhipment depot through which pallet freight passes between collection and delivery legs in a pallet network. |
Hub postal codes | A zone collection table on a transport network that maps postal code prefixes to hub depot codes. |
Zone collection | A configurable table of postal code rules used to match orders to specific locations or depots. |
Starts with | A partial postcode prefix used as a matching rule (e.g. "LS" matches all Leeds postcodes). Leave empty for a whole-country catch-all. |
Alternative hub | Hub depot location that is suggested when more than one column matches the postcode rules. Can also be used for cross-docking flexibility. |
Lead time | A configurable time offset (in hours or days) applied to the hub leg within the hub postal code rule. |
HUB Split | The automatic division of an order consignment into collection, trunk-in, hub, trunk-out, and delivery legs. |
Tenant activation | An active transport network integration must be enabled before the hub configuration fields appear on a transport network. |
Configure Hub Postal Codes
Hub postal code configuration is done at the transport network level. Each row in the zone collection maps a postal code prefix to the hub depot that should be inserted for orders matching that postcode.
Prerequisites
Before configuring hub postal codes:
CONFIRM that the custom fields
central_transport_network__hubandcentral_transport_network__alternative_hubshave been added under 'Additional fields'.
ENSURE the hub depot(s) have a Location set — without a location, the hub will not be inserted even if a matching rule exists.
Add Hub Postal Code Rules
NAVIGATE to CONFIGURATION → Locations → Transport networks.
SELECT the relevant transport network.
OPEN the Hub postal codes tab. This displays the zone collection table for hub matching.
CLICK to create a set of postcode rules
Rules can be set based off of postcode prefix or a range of postcodes
COMPLETE the fields for each rule (See the table below)
SAVE the configuration.
Field | Description |
Country | The country this rule applies to. |
Starts with | Postal code prefix to match against (e.g. |
Hub | The depot code of the hub to insert when this rule matches. |
Alternative hub | The system will use the parameters in the post codes and compare to the order data to determine an alternate location to be suggested. |
Lead time
| (Optional) Lead time to apply to this hub leg. |
‼️When multiple rules match an order's postal code at the same level of specificity, the first matching row in the table takes precedence. Place more specific rules above less specific ones.
Configure a Default (Catch-All) Hub
A catch-all rule can be added to handle orders where no specific postal code prefix matches. To create a default:
ADD a row with the Starts with field left empty.
SET the Hub to the depot code that should apply as a fallback.
POSITION this row below all specific rules in the table, so it is only matched when no other rule applies.
How Hub Stops Are Inserted
Once configured, the hub insertion process is fully automatic and requires no planner action.
On Order Creation
When a new transport network order is created:
Qargo evaluates the order's collection and delivery postal codes against the Hub postal codes zone collection.
The system identifies the first matching rule (prioritising more specific postcode prefixes over shorter ones).
If the matched hub depot has a Location assigned, the hub stop is automatically inserted into the consignment structure.
The resulting order structure follows a standard pallet network layout:
Collection leg → Trunk in → Hub → Trunk out → Delivery leg
If an Alternative hub is configured on the matched rule, it is also populated on the order for cross-docking reference.
‼️Hub and alternative hub fields are not updated retroactively if hub stop locations change after an order has been created. Re-creation of affected orders may be required in such cases.
When a Hub Is NOT Inserted
The hub will not be inserted if:
No matching rule is found in the Hub postal codes table (and no default rule is configured).
The matched hub depot does not have a Location assigned.
The tenant-level additional fields have not been enabled.
Alternative Hub Configuration
The Alternative hub field provides flexibility by recording a secondary hub option alongside the primary one.
Alternative hubs are evaluated using the same post code table .
The resolved alternative hub is stored on the order and is available in the cross-docking mobile workflow.
Lead Time Configuration
Lead time for the hub leg can be set directly on the hub postal code rule.
NAVIGATE to the Hub postal codes zone collection on the transport network.
SELECT the Transport network to update
CLICK into the 'Load lead time' and select from the drop down options:
Same day as collection
Collect + 1 day
Collect +2 day
SAVE the rule.
The configured lead time is applied to the hub leg when the order is created.
Troubleshooting
Symptom | Likely cause | Resolution |
Hub postal codes tab not visible on the transport network | Custom additional fields not created | Navigate to Configuration > Additional fields. Under CONSIGNMENTS select 'Add custom field'. Add the 2 options and make them ACTIVE. |
Hub stop not inserted on order creation | Hub depot has no Location assigned | Open the hub depot and assign a Location |
Hub stop not inserted on order creation | No matching rule in the zone collection | Add a postal code rule or a catch-all default row |
Wrong hub inserted | More specific rule is below a less specific one | Re-order the zone collection rows — more specific prefixes must appear higher in the table |
Alternative hub is not suggested | Alternative hub column is empty on the matched rule | Add the alternative hub depot code to the relevant row in Hub postal codes |
Hub assignment not updated after config change | Hub fields are not retroactively synced | Re-create affected orders to pick up the updated hub configuration |