Hub-to-hub network management

Routing, customs and tracking. Configured once, running automatically.

For operators who run hubs: accept inbound from upstream carriers, clear or process it, hand it to the next leg. Every step from inbound ASN to final-mile handoff is orchestrated in one system, and dispatch cannot happen before clearance, structurally rather than by policy.

Request a Demo →
15 Customs brokers integrated
100% Automatic event propagation
6 Specialised scan types for edge cases
How it works

From origin warehouse to destination hub, one orchestration

The platform covers the full transport chain through a single system. Rules decide the next stop; scans move the status.

Inbound and ASN

Each hub sees what is coming before it arrives

ASN data is pushed ahead of the physical bags, so every hub sees its inbound schedule and delays in real time. Bags without an ASN are registered as external units under a house reference and routed without access to upstream systems.

  • Customs statuses via broker integration or manually
  • Lifecycle statuses: receipt, transit, hub delivery, handoff
  • Exception scenarios: hold, customs seizure, return to sender
Hierarchy and propagation

Scan the group, update every item inside

The grouping hierarchy is set per client: parcels into bags, bags onto pallets or into containers, containers onto trucks. Scanning any group generates events for everything inside it, and receiving carriers scan the vehicle on arrival with no re-scanning of individual bags.

Hub operations

Stock list, holds and mobile loading

The hub stock list shows what is in the building, where it is heading, and which bags are on hold or awaiting clearance. Held bags never appear in the loading list. Loading is done by scanning units, with barcode scanners or a standard smartphone camera.

  • Manual holds, or automatic holds driven by clearance status
  • Loading and unloading records across every stage and hub
  • Role-based access configured per operator
Routing rules

Define the path once; the rule decides per bag

Each rule defines origin hub, transit and customs hubs, destination hub and last-mile carrier, and carries its own departure time and frequency. Incoming bags match by destination and carrier, so the next stop is never a manual decision.

Customs clearance

Fifteen brokers, and no departure before confirmation

Broker rules are assigned per route; the platform tracks export, import and transit declarations where the broker supports it. Dispatch is blocked until confirmation arrives, enforced at the UI level.

  • Multi-broker, multi-lane: the right broker selected by route automatically
  • Multi-clearance-point: one truck, separate declarations per border crossing
  • Declarations uploaded automatically via broker API, or manually for brokers without one
Final-mile handoff

Departure scan out, manifest pushed, unloading scan in

When a vehicle departs, every parcel inside receives a tracking event. Through Last Mile Connect the bag and pallet manifest reaches the receiving carrier, and the unloading scan at destination confirms receipt. Local routes and the driver interface run collections and deliveries in the same platform.

Capabilities

Built for the complicated middle of the chain

Intermediate hubs, several customs jurisdictions on one truck, and the edge cases that otherwise become manual workarounds.

Network

The rules and schedules the network runs on.

  • Routing rules and schedules

    Full transport path per rule, with departure time and frequency.

  • Flexible hierarchy

    Any grouping levels the client needs, each tracked independently.

  • Live / Test switching

    Try settings and processes against production data without touching live shipments.

  • Inbound visibility

    ASN-driven schedules and delays per hub in real time.

Customs

Compliance the interface enforces.

  • 15 broker integrations

    Automatic declaration submission and status tracking where the broker supports it.

  • T1 generation

    Transit documents generated in the flow, per lane.

  • Dispatch gating

    Non-compliant departures are structurally impossible, not merely against policy.

  • Manual fallback

    Document upload for brokers without an API or clearance handled by third parties.

Edge cases

Six specialised scan types.

  • Parcel extraction

    Pull one parcel for inspection without holding the whole bag.

  • Regulatory hold

    Hold with a recorded physical location, released manually.

  • Unknown unit registration

    Bags without an ASN registered under a house reference for onward routing.

  • Export and import milestones

    Explicit events for jurisdictions that require separate confirmation.

  • Geo ID tag alerts

    Physical tags on bags; an alert when one moves the wrong way or stops too long.

Why it pays

Fewer decisions per shipment, and none of them manual

Once routing rules and broker integrations are configured, the network runs itself; the operator watches exceptions, not the flow.

Configured once, runs automatically

  • No manual routing decision per shipment
  • Schedules carried by the rules, not by a whiteboard
  • Bags without ASN still routed, under a house reference

Compliance by construction

  • Dispatch gated on clearance at the UI layer
  • The right broker chosen per lane, several jurisdictions per truck
  • Every declaration and hold on the record

Visibility at scale

  • One departure scan updates hundreds of parcel statuses
  • Real-time stock and inbound per hub
  • Driver progress live for dispatch, from any phone
In the V-TER ecosystem

V-TER Linehaul runs on its own. It runs better connected.

Every V-TER platform shares one data layer and one API, so connecting two of them is configuration, not an integration project. Here is what each one does for V-TER Linehaul.

Carrier connectivity API

Last Mile Connect

On departure, the bag and pallet manifest is pushed to the receiving carrier through Last Mile Connect; local collection and delivery routes push their manifests the same way.

Visit Last Mile Connect (dedicated site) Shipping orchestration

V-TER Ship

Parcels orchestrated in V-TER Ship arrive with their routing already decided; V-TER Linehaul carries them hub to hub, and the departure scan updates every parcel's tracking.

Explore V-TER Ship Reverse logistics

V-TER Returns

Closed pallets from V-TER Returns hubs travel back to the retailer on V-TER Linehaul, with the POD notification closing the return.

Explore V-TER Returns Customs compliance AI

HSCodifi

Where a lane crosses a border, HSCodifi supplies the classification behind the declarations that gate dispatch.

Visit HSCodifi (dedicated site)
Who it is for

Operators in the middle of the chain

Anyone who receives from one carrier, does something to the freight, and hands it to the next.

Postal operators and last-mile hubs

Manual hub processes replaced by an automated platform with full tracking.

3PL operators and logistics networks

One system for the transport chain, instead of fragmented tools and manual coordination.

Cross-border operators

Automatic customs clearance across multiple trade lanes through one platform.

FAQ

Common questions

Configuring routing rules, broker integrations and hub setup for your transport network. The Live / Test switch lets the configuration run against production data before it touches a live shipment.

Yes. Declarations for brokers without an API, or handled by third parties, are uploaded manually, and the clearance status they set is what the loading list obeys. The gate is the same whichever way the confirmation arrives.

Through Last Mile Connect. At departure, the bag and pallet manifest is pushed to the receiving carrier automatically, so there are no manual manifests and no re-scanning of individual bags at destination.

No. Loading, scanning and driver routes run in the mobile interface from a standard smartphone browser, with the camera as the scanner where no dedicated device is available.

Ready to let the network run itself?

From routing rules to customs documents, handled automatically.

Bring one lane and one broker. We will configure the rule, run it in Test against your real bags, and show the first gated departure.

Request a Demo →