Logistics & supply chain

Transportation

Transport systems are the dispatch desk working with the driver's phone. Get assignment, loading, delivery, and proof-of-delivery flowing and freight settlement stops being a monthly argument.

Cluster Logistics
Focus Dispatch · waybills
Delivery Gate by gate, acceptable and operable

How we see this industry

Dispatch and in-transit

A transport system is not a wall of trucks in a control room. What actually runs is the desk and the driver’s phone: where to load, which vehicle, which route, who signs, when the POD returns, how freight is settled. Any of those four steps as photos in a chat group becomes a month-end fight. We fix the shipment model first: shipper, consignee, cargo, lane, trip, charge lines. Dispatch considers body type, payload, driver credentials, and in-transit conflicts; loading has a list and exceptions (over, short, damage); how precise location is to the customer is agreed in the design, not argued after go-live as “do we need to the door.”

POD and sign-off

E-sign, paper POD photo, exception refusal—state writes back to the shipment. Finance will not pay without a POD; a POD in a driver’s pocket for a week stalls receivables. Freight often has a contract rate, extras, tolls, waiting, and detention; rules are configurable and exceptions approved. Reconciling is shipment detail, not “about how many trucks this month.”

Own fleet and subcontract

Many companies subcontract when own trucks are short. If subcontract dispatch, settlement, insurance, and credential expiry live in another spreadsheet, the desk cannot see real capacity. We treat subcontract as a capacity resource on the same shipment, settle at contract rate, and block dispatch when credentials expire. Claims (damage, delay) hang on the shipment and the liable party instead of a new email thread.

Accessorials

Detention, deadhead, second delivery, wait overtime—if those fees have no rules, driver and shipper each remember a different month. Lane optimization can wait; load lists, exception photos, and e-POD must be actions a driver will actually do. Hazmat, reefer, and oversize mixed into a general pool must be blocked at dispatch by credential checks. Insurance claims should carry cargo and sign-off evidence off the shipment so a second pile of paperwork is not started.

Offline driver app

The driver app must be few steps and able to cache offline, so load and sign still complete on poor fuel or signal. Go-live pilots a fixed lane or one fleet, connecting shipper orders and payables. Training is dispatch and lead drivers. A transport system that works can dispatch, get a sign-off back, match charges, and show a customer where the freight is.

Typical scenarios

Assignment and dispatch

Assign by vehicle type, payload, route, and driver availability, with reassignments recorded.

In-transit and tracking

Position comes from GPS or the driver app, with alerts for unexpected stops and route deviation.

Delivery and proof

Drivers capture proof of delivery with photos, electronic receipts return immediately, and paper ones are scanned and filed.

Common blockers and how we handle them

Blocker

Customers call to ask where the goods are and dispatch rings drivers one by one

How we handle it

Tracking and milestone status live in the system, and customers can self-serve with a waybill number.

Blocker

Freight rates differ per customer and settlement is checked by hand

How we handle it

Rate rules are configured per customer and lane, waybills price automatically, and exceptions are held for review.

Blocker

Proof of delivery never comes back and payment stalls

How we handle it

Receipt status feeds performance review, with automatic reminders to drivers and carriers when overdue.

Common system modules

Waybills and orders

Customer orders, waybill creation, splits and merges.

Vehicles and drivers

Vehicle records, document expiry, driver rosters.

Dispatch

Assignment suggestions, load factor, reassignment.

In-transit tracking

Tracking, milestone status, exception alerts.

Delivery and receipts

Electronic sign-off, receipt filing, overdue reminders.

Rating and settlement

Customer rate rules, carrier settlement, statements.

Delivery gates

  1. Scope

    Spread out today’s dispatch, load, sign-off, and POD. Write own fleet vs subcontract, charge lines, and what this phase must enter the system.

  2. Architecture

    Fix the shipment model, location granularity, and freight rules. Confirm how the driver app, shipper orders, and payables connect.

  3. Build & integrate

    Connect dispatch, in-transit, and e-sign on a real lane. POD write-back and exception-fee approval are acceptance items written first.

  4. Launch & operate

    Run one fleet or one fixed lane first; train dispatch and lead drivers. Settlement matches shipment detail; iterate next on subcontract credentials.

Related capabilities

Related industries

Industries we ship in

Walk us through your process before anything gets built

Tell us how the work happens today, where it breaks, and when you need it live. We will come back with a scope you can check and a phasing plan.

Contact Us

Email
service@wehoope.com
Phone
+86 139-2520-6166
Address
W903, Shenzhen-Hong Kong Industry-Education-Research Base, 201 Gaoxin South 7th Road, Nanshan District, Shenzhen