Why linehaul breaks without a system
Batch management is manual
Parcels pile up at sorting hubs with no systematic way to group them by destination. Operators rely on memory, paper lists, or spreadsheets to decide what goes where. When a truck departs, there’s no clean handoff — just hope that someone counted right.
Routes exist in people’s heads
Recurring linehaul runs follow the same lanes every day, but the knowledge lives with dispatchers, not in the system. When someone is absent, the operation stumbles. New hubs or route changes require retraining instead of reconfiguration.
Multi-hop routing is guesswork
A parcel going from Bucharest to Debrecen might need to transit through Cluj and Oradea. Without a hub network model, intermediate routing depends on operator knowledge. Parcels get stuck at transit hubs because nobody planned the next leg.
Partner handoffs are fragmented
Cross-border courier networks hand parcels to local partners at destination. Each partner needs manifests in different formats — some want API pre-alerts, others want spreadsheets, others want email. Managing this per-country is a full-time job.
From sorting hub to partner doorstep
Parcels sorted into static batch lanes by destination hub, automatically via conveyor or by manual scan.
Scan-based truck loading with destination validation — wrong-hub parcels flagged before departure.
Batch closes automatically on departure scan, manifest generated. Next batch created when first parcel is scanned — no manual setup.
Run tracked through status progression with ETAs based on route templates.
Batch unpacked at destination hub, parcels released for next-leg sorting or last-mile delivery.
Partner courier receives automated pre-alert via API, spreadsheet, or manifest email — per-country format.
Runs are created automatically from route schedules. Ad-hoc runs available for unplanned loads.
Batch Management
Linehaul lanes are defined once and reused indefinitely. Each static batch connects an origin hub to a destination hub, with an assigned sorting gate, partner carrier, and manifest recipients.
When a batch departs, the next one is created automatically when the first parcel is scanned into that lane — no manual batch creation, no empty batches. Parcels arriving at the sorting gate are added to the current batch, either through conveyor integration (automatic) or barcode scanning (manual). Action barcodes at each gate let operators switch between batch-loading modes instantly.
Batches validate every parcel on entry: destination hub must match, franchisor must match, shipment type (outbound vs. returns) must match. Mismatches are rejected before they reach the truck. Every scan is logged with typed event codes — successful loads, already-in-batch rejections, wrong-hub flags, duplicates. The audit trail covers both MySQL and ClickHouse for real-time operations and historical analysis.
Nested containers are supported — pallets and bags are modeled as sub-batches containing parcels, and truck batches can contain sub-batches, with no depth limit.
Operational safety nets are built in. If a batch stays open longer than a configurable threshold, the hub receives an email alert — catching loads that should have departed but haven’t.
Route Scheduling
Linehaul routes are templates: an ordered sequence of hub stops with scheduled days, departure times, assigned vehicles, and pricing. A route like “Bucharest → Cluj → Oradea, weekdays at 22:00” is defined once.
The system creates runs automatically from route schedules — every 60 seconds, it checks which routes need a run today and creates them with the assigned vehicle and pricing. Dispatchers see today’s runs pre-populated; ad-hoc runs can be added for unplanned loads or copied from previous days.
Each run tracks its lifecycle: loading → active → on route → arrived. Multiple batches ride on a single run, linked through a junction table. Load metrics — pallets, weight — are recorded during the loading process and available in run reports.
Network Routing
CourierManager models your hub network as a graph and uses Dijkstra’s shortest-path algorithm to compute optimal multi-hop routes. A parcel going from Hub A to Hub D through intermediaries B and C gets a computed path — not a manual routing decision.
The hub network graph is separate from linehaul routes, allowing abstract distance-based routing that adapts as hubs are added or removed. A second pathfinding mode uses actual route definitions and real street distances for operational accuracy.
Reachability is computed transitively: if Route 1 serves Bucharest → Cluj, and Route 2 serves Cluj → Oradea → Debrecen, then Route 1’s served hubs include Oradea and Debrecen through Cluj as a transit point. During loading, parcels destined for indirectly-served hubs are accepted with appropriate routing — parcels for hubs not reachable from the route are flagged.
Cross-Border Handoffs
When a batch destined for a partner courier closes, CourierManager generates the appropriate pre-alert — automatically, in the format that partner expects. Each integration is country-specific:
API-based pre-alerts for partners with real-time integration. Spreadsheet manifests (including Google Sheets generation) for partners who work from documents. Excel manifests attached to email for partners who need offline access. Customs manifests for cross-border batches requiring declaration documents.
The static batch configuration stores the partner carrier, manifest email addresses, and whether to use simplified or full manifest format. When the batch departs, everything fires automatically — the operator’s only action is the departure scan.
Partner carriers are classified as linehaul or delivery carriers. A batch can have both a linehaul franchisor (who transports it) and a delivery franchisor (who handles last-mile after arrival), enabling the full flow: sort → batch → transport → partner hub → partner delivers.
Arrival can trigger automatic status updates. When a batch is marked delivered at its destination, all child parcels can be auto-delivered — reducing manual status management for partner handoff scenarios where arrival at the destination hub equals final delivery.
for multi-hop routing
with partner integrations
from route templates
proven at scale
How CourierManager compares
| Capability | CourierManager | Typical last-mile software |
|---|---|---|
| Static batch lanes with auto-renewal | ✓ | ✗ |
| Conveyor gate integration for batch assignment | ✓ | ✗ |
| Scan-based loading with destination validation | ✓ | ✗ |
| Wrong-hub detection with automatic exceptions | ✓ | ✗ |
| Scan audit trail with duplicate detection | ✓ | Partial |
| Route templates with automated run creation | ✓ | ✗ |
| Multi-hop Dijkstra pathfinding | ✓ | ✗ |
| Transitive hub reachability | ✓ | ✗ |
| Nested containers (batch within batch) | ✓ | ✗ |
| Partner pre-alerts (API, spreadsheet, email) | ✓ | Manual |
| Customs manifest generation | ✓ | ✗ |
| Linehaul pricing per hub pair | ✓ | ✗ |
| Run load tracking (pallets, weight) | ✓ | ✗ |
Frequently asked questions
What is linehaul management?
Linehaul is the movement of parcels between hubs in a courier network — the “middle mile” between pickup and last-mile delivery. It involves batching parcels by destination, loading trucks, transporting between sorting facilities, and unpacking at the destination for onward delivery. For networks with more than one hub, linehaul coordination directly affects transit times, costs, and operational reliability.
How does multi-hop routing work?
CourierManager models your hub network as a graph with distances between connected hubs. When a parcel needs to travel from origin to destination through intermediate hubs, Dijkstra’s shortest-path algorithm computes the optimal route. At each intermediate hub, the parcel is sorted into the next outbound batch automatically — either via conveyor gate assignment or manual scan. The system also computes which hubs are reachable from each route, including through transit points, so loading validation catches routing errors before departure.
How are partner courier handoffs handled?
Each static batch lane can be assigned to a partner carrier. When the batch closes at departure, CourierManager generates the pre-alert in whatever format that partner expects — API calls, Google Sheets manifests, Excel email attachments, or customs documents. The format is configured once per partner; after that, the departure scan triggers everything automatically. This supports cross-border networks where each destination country has a different local partner with different integration requirements.
Linehaul is where courier networks either scale or break. Single-hub operations can get by without linehaul management. Multi-hub networks cannot. If your parcels move between two or more facilities before reaching the last mile, you need systematic batch management, route scheduling, and partner handoffs — not spreadsheets and phone calls.