Hub-to-hub transport —
fully orchestrated
Routing rules, customs clearance, and parcel-level tracking across your entire hub network — defined once, runs automatically. Know exactly what’s in each hub, what’s cleared to load, and where every bag is heading.
End-to-end linehaul — one platform
From inbound ASN to final-mile handoff, every step of the transport chain is tracked and orchestrated through a single system.
Downstream systems push ASN data to the linehaul platform ahead of bag arrival. Each hub sees an inbound schedule — which trucks are expected, when they should arrive, and which are running late. When a bag arrives without an ASN it can be registered as an external unit and routed onward without requiring upstream system access.
Parcels group into bags, bags onto pallets or into containers. Each level is tracked independently so downstream systems receive parcel-level events without needing to track the grouping structure themselves. Scanning any group triggers events for every item inside — one scan moves hundreds of shipments through the tracking chain simultaneously.
The hub stock list shows everything sitting in the building right now — bags, destinations, routing rules, and hold status. Mobile loading builds the shipment record in one tap. Bags without a cleared customs status are automatically excluded from the load list — no manual checks required by the operator.
Customs Broker Rules assigned to each routing rule determine which broker handles which leg. The platform auto-submits export declarations and T1 transit documents, waits for broker confirmation, and gates dispatch accordingly. 20+ brokers are supported natively; others via manual document upload. Multiple clearance points on a single truck are handled independently.
Once a vehicle departs, every parcel inside it receives a tracking event automatically. At the destination hub, an unloading scan confirms receipt. Last Mile Connect integration pushes the bag and pallet manifest to the receiving carrier — no manual manifest needed on the driver's end, and no re-scanning of individual items at destination.
From parcel to truck — tracked at every level
Downstream systems receive tracking events at the parcel level — they never need to track bags or pallets themselves. The linehaul platform manages the full grouping hierarchy and propagates all events downward automatically.
Parcels group into bags; bags onto pallets or into containers; containers onto trucks or aircraft. Each level has its own scan events, so you can track the state of any unit in the chain independently — and drill down from a truck departure all the way to individual parcel status.
When a truck departs, every bag on it receives a dispatched event. Every parcel inside those bags receives the same event, automatically. Receiving carriers need only scan the truck on arrival — all parcel statuses update in one operation, with no re-scanning of individual items required anywhere in the chain.
Events propagate downward through the hierarchy. A departure scan on the truck creates departure events on every container, pallet, bag, and parcel it carries. Downstream systems consuming parcel-level events never need to be aware of the grouping structure — they simply receive the parcel events as they occur.
Define once — runs automatically
Routing rules define the complete path each bag takes from origin hub to final-mile carrier. Schedules attach departure times and frequency so every hub always knows what's arriving and when.
Each routing rule defines the full transport path: origin hub, any intermediate transit or customs clearance hubs, destination hub, and final-mile carrier. Rules match incoming bags by destination and carrier, then resolve the correct next stop automatically. A single shipment can pass through one or more intermediate hubs — for import licences, customs clearance, or carrier handoff requirements — without manual intervention at any step.
Each routing rule can carry a recurring or one-off schedule — departure time, transit duration, and frequency. The platform builds an inbound schedule per hub automatically: what vehicles are expected, when they should arrive, and which are overdue. When a vehicle departs, it appears on the destination hub's inbound view with the expected arrival time calculated from the schedule.
If a vehicle has not arrived within its expected window, a delay flag is raised on the destination hub's inbound view. Operators can act before the next dispatch window closes — holding outgoing loads, notifying customers, or escalating to the carrier — before the issue compounds further down the chain.
Stock list, loading & dispatch — mobile-first
Everything operators need to run a hub — knowing what's in the building, loading a truck, and dispatching it — all accessible from a phone on the warehouse floor.
See exactly what's sitting in the hub right now — every bag, its destination, its matched routing rule, and its hold status. Bags without a matching rule are flagged immediately so operators can act before dispatch time, not after.
Any bag can be manually put on hold to prevent dispatch. Customs integration automatically holds bags whose import declarations haven't cleared — they cannot be marked "ready to pick up" until all parcels inside are released by the broker authority.
Optimised for phone use on the warehouse floor. All bags in "ready to pick up" status matching the outgoing route appear in a single list — one tap loads them all and creates the shipment record. Barcode scanner and camera both supported.
Simple inbound / outbound scans for any group — bags, pallets, containers. Creates an arrival or departure event even without a full routing context, displayed alongside structured shipment records in the same view. Useful for tracking third-party freight that arrives without a pre-registered ASN, or for quick interim milestones that don't trigger a full loading workflow.
Each shipment record carries a loading tab (what was added before departure) and an unloading tab (what was received at destination). Items that were not loaded or not yet processed are clearly marked. Discrepancies between loaded and unloaded quantities are immediately visible — nothing is lost between hubs, and every variance has a record.
Automated clearance — 20+ brokers, manual fallback
Customs Broker Rules assigned to each routing rule determine which broker handles which leg. The platform prepares, submits, and tracks customs documents automatically — dispatch is gated on clearance status.
When a shipment is completed, the platform automatically transmits export declaration data to the assigned broker, waits for confirmation, and generates the T1 transit document. The T1 — required for cross-border road transport — is available directly on the shipment page for operators to view and print. Shipments cannot depart until the document is received and confirmed by the broker.
Clients with multiple trade lanes assign different Broker Rules per route — one broker for UK–DE, another for UK–FR. The system selects the correct broker per shipment leg automatically. Multi-clearance-point shipments are also supported: one truck, two customs jurisdictions, with separate declarations generated and tracked independently for each border crossing.
For brokers without an API connection, or for shipments handled by external parties, managers upload the customs document directly into the platform. Once uploaded it is available on the shipment page — the same place the operator looks — keeping everything in one system regardless of how the document was obtained. No separate file-sharing or email chains needed.
Only bags whose export declarations are in "released" status can be loaded onto a vehicle. The mobile loading interface enforces this automatically — bags awaiting clearance are excluded from the load list until the broker confirms release. Non-compliant departures are structurally impossible, not just policy-dependent.
Store pickups & local deliveries — driver app included
Plan local collection and delivery routes, track progress in real time, and push manifest data to carriers automatically via Last Mile Connect — all within the same platform as the linehaul network.
Managers create local route plans specifying driver, vehicle, date, and the sequence of stops — warehouses, retail stores, client locations, or any address. Each stop is marked as a delivery, collection, or both, with expected quantities of pallets, bags, or boxes. A "warehouse" in this context is any location where goods can be stored or collected — including retail stores, client pickup points, or partner facilities.
Drivers use the phone-optimised interface to navigate their stop list, mark stops as visited or skipped, and record actual collected or delivered quantities. Dispatch sees live route progress in real time as stops are completed. Last Mile Connect integration pushes bag and pallet content data to receiving carriers automatically when a group is dispatched — no manual manifest needed on the driver's end.
Edge cases handled — without manual workarounds
Six dedicated scan operations for the exceptions that happen in every hub — customs inspections, regulatory holds, unknown units, and export milestones — each with its own record and audit trail.
Extract a single parcel from a bag for customs inspection without holding the entire bag. The bag continues to its destination; the extracted parcel gets its own handling record and can be flagged for a scheduled inspection appointment with automatic email notification to the relevant parties.
Mark any item as held with a description of its physical location in the warehouse. Prevents it from appearing in load lists until manually released. Used for regulatory holds, damaged items, or parcels awaiting missing documentation — with the hold reason and location recorded for audit purposes.
Register unknown incoming units — bags or pallets not created in a downstream system — with a house reference and basic details. Allows the warehouse to accept, route, and track third-party freight within the same platform without requiring upstream system access or creating exceptions in the main workflow.
Trigger an explicit export event for a bag or group before it departs the origin country. Used with customs integrations that require an export milestone in addition to the manifest submission — such as jurisdictions where physical departure must be separately confirmed before the import process can begin at the destination.
Record an import arrival event at the clearance-point hub. Used by integrations that require confirmation of physical arrival before the broker initiates import clearance — ensuring the platform event sequence matches the legal customs process precisely, with no timing gaps in the documentation trail.
Physical Geo ID tags attached to bags will be linked to their records in the platform. If a tagged bag is detected moving in the wrong direction — or not moving when it should be — the system alerts operators automatically, before the error compounds further along the transport chain.
Built for operators in the middle of the chain
TMS / Linehaul serves any business that runs a hub — receiving bags from upstream carriers, processing or clearing them, and handing off to the next leg.
Receive inbound bags from multiple origin carriers and route them to your final-mile network. Customs clearance runs automatically at your hub — hold management tied to import declaration status means no bag departs until all parcels inside are cleared by the authority. T1 and other transit documents are generated, stored, and surfaced to operators without chasing the broker manually.
Multi-hub networks with complex routing rules and intermediate stop hubs. Multiple customs brokers per account — different brokers for different trade lanes. Multi-clearance-point shipments: one truck, two customs jurisdictions, handled automatically with separate declarations per border. Local collection routes from retail stores and client sites managed in the same platform as the long-haul network. Last Mile Connect integration for carrier data exchange without manual manifests.
Common questions
TMS / Linehaul integrates with 20+ customs brokers globally. You configure broker assignments per trade lane — the platform automatically routes customs documents to the correct broker based on origin-destination pair and shipment type.
Yes. Routing rules are set at the trade-lane level: you choose which hub pair handles a lane, assign backup routes, and define cut-off times. Rules apply automatically at bag creation — no manual decisions per shipment.
Warehouse staff use a mobile web interface to scan parcels into bags, verify customs clearance status, and confirm loading. The app works on any device with a camera — no app installation required. Cleared vs. held parcels are visually flagged.
Missing scan alerts surface in the operator dashboard within minutes. You can see which bags were expected at a hub and which haven't been confirmed. The platform maintains full audit history so you can investigate gaps down to the individual parcel.
From routing rules to customs documents — handled automatically.
See how the linehaul platform fits your hub network and trade lanes.