qompassNow TMS
A complete transportation lifecycle — not a collection of modules.
Built for complex Hub-and-Spoke, PTL, FTL and multi-leg networks — where a shipment moves through multiple hubs, vehicles, teams and legs before reaching its destination.
Demand → Decision → Consolidation → Movement → Hub Processing → Execution → Delivery.
Order entry to draft billing
Step through the full transportation flow.
Every stage below is a real, configurable layer of qompassNow — not a marketing diagram. Click through to see what happens at each step.
Stage 1 of 6
Purchase Order / ASN
Demand enters through PO, ASN or direct booking.
- Direct WMS integration
- API / EDI
- Excel upload
- UI / portal
- Mobile
Decide before you dispatch
Decide how the shipment should move before anyone plans a trip.
The booking only specifies origin and destination — the Network Determination Engine works out the best-fit operational path through hubs, considering consolidation, capacity, schedule and constraints together.
Consolidate
Compatible bookings by leg / destination
Capacity
Weight, volume, vehicle fit
Schedule
Cut-off, departure, transit feasibility
Constraints
Service, vendor, location, rules
Configurable, not fixed
Every customer can run a different booking process.
qompassNow uses configurable Booking Workflow Profiles instead of one rigid process.
Standard
Approval
Multi-Invoice
LSP Mode
Rules engine
Operational policy, enforced automatically.
Rules apply during booking, confirmation, network selection, diary, trip planning, execution and hub processing — and return a clear outcome.
Pass
Continue processing.
Warning
Allow processing, notify the user.
Hold
Require operational intervention.
Reject
Prevent further processing.
Consignments
033 active
Plan to controlled execution
Every operational milestone, tied back to the shipment.
Pickup, linehaul, hub transfer, last-mile and delivery — with e-POD, geofencing, GPS, alerts and full end-to-end traceability.
- Pickup
- Linehaul
- Delivery + e-POD
- GPS & alerts
- Exception management
- Traceability
Close the loop
Know the freight cost of the actual movement — not just the planned cost.
Rate
Actual
Reconcile
Bill
Under the hood
Six functional layers, one operational platform.
From master data to control tower — everything QompassNow does maps back to a clear functional layer.
Why it doesn't become one giant module
Each part of the platform owns a different business question.
Booking
What does the customer want transported?
Rules
Is the demand operationally and commercially valid?
Network
How should it travel?
Confirmation
What transportation commitment are we making?
Diary
What transportation demand needs to move together?
Trip
What physical transport resource will move that demand?
Hub
What is physically present, and what happens next?
Execution
What is actually happening in the physical operation?
POD
Was the transportation obligation completed?
What changes
What changes when the whole lifecycle is connected?
Service
Better delivery commitment control.
Network
Lower avoidable freight and leakage.
Destinations
Higher utilization and better allocation.
Demand
Faster exception response.
Capacity
Objective vendor performance.
Outcome
Repeatable processes across every location.
The platform turns transportation from a series of handoffs into a measurable operating system.