Orders raised against a reference type and number
Including bill of lading
Powered by STOS, the Smart Terminal Operating System
Every order carries its own timeline
A customer instruction becomes an order, the order carries its shipments, each shipment gets a vehicle and is recorded through gate in and gate out at both the pickup and the destination. When a customer calls to ask where their container is, the answer comes off the record rather than out of somebody's memory.
How the module runs
● 7 stages
Order
01Shipment
02Vehicle assigned
03Gate out
04In transit
05Gate in
06Delivered
07The module at work
Screens captured from the running application. Customer, staff and supplier names have been replaced before capture.
Why it exists
Transport status usually lives in a phone call
Most terminal transport desks track movements in a spreadsheet and confirm them by phone. It holds together until a customer asks what time the container left, or until an order sits at the destination for two days before anyone notices. Logistics records the movement as it happens, against the order, so status is a property of the record rather than something somebody remembers.
What Logistics covers
Multiple shipments or containers under one order
Vehicle and transporter assignment per shipment
Gate in and gate out recorded at both pickup and destination
A per-shipment timeline from origin to destination
Pickup pending and destination pending queues
So nothing waits unnoticed
Reporting built for customers
Operations and management separately
Orders
One order, many shipments
An order is the customer instruction. The shipments under it are the containers that actually move.
Logistics Dashboard
Every order with its number, reference type, reference number, customer, status and creation date, counted as draft, active, in-transit, overdue and delivered. Columns can be dragged to group the list by any field.
Add New Order
An order raised against a reference type and reference number, so it ties back to the bill of lading or terminal record it came from.
Order Workspace
One order with its information panel and its shipments, each counted by status: vehicle not assigned, scheduled, in-transit, completed and over due.
Movement
Recorded at the gate, not afterwards
Gate movement is where a shipment stops being a plan and becomes a fact.
Gate Movement
Vehicle assignment and gate actions against a selected order and shipment. Nothing unlocks until both are chosen, so a movement cannot be recorded against the wrong container.
Vehicle assignment
The vehicle and transporter attached to the shipment, changeable when plans change, with the change recorded.
Pickup and destination queues
Pickup pending and destination pending counted separately on the dashboard, because a container waiting to be collected and one waiting to be delivered are different problems.
Tracking
The timeline a customer actually asks for
Six timestamps per shipment answer almost every question a customer has.
Order Tracking
A timeline per shipment from origin to destination: gate in and gate out at pickup, in transit, gate in and gate out at destination, and close, each with its own timestamp.
Shipment status
Not started, in progress and completed counted across the shipments on the order, so a part-delivered order is visible as part delivered.
Order history
Every status change retained against the order, which is what makes a disputed delivery time answerable.
Insights and setup
Three audiences, three reports
A customer, an operations manager and an executive want different things from the same data, so the module reports to each of them separately.
Logistics Insights
Three report views: customer, for shipment tracking and delivery status; executive, for SLA performance and fleet summary; and operations manager, for gate turnaround and live manifest.
Report filters
Reports generated by date range, order number, reference or bill of lading number, customer, status and container or shipment number.
Vehicles
Vehicle number, vehicle type and the transporter it belongs to, which is what vehicle assignment draws from.
Roles
Who sees what
Access is granted per module and per role, so two people signed into the same platform see different work.
| Role | What the role works with |
|---|---|
| Transport desk | Raising orders, assigning vehicles, scheduling shipments |
| Gate clerk | Gate in and gate out at pickup and destination |
| Customer service | Order status and tracking, answering where a container is |
| Operations manager | Gate turnaround, live manifest, pickup and destination queues |
| Executive | SLA performance and fleet summary across the period |
| Administrator | Vehicles, transporters, reference types and role access |
How it fits
The order ties back to the terminal record
An order is raised against a reference type and reference number, which is usually the bill of lading the terminal already holds. That is what keeps Logistics joined to the rest of the platform rather than running as a separate transport system with its own version of the truth.
- Single sign-on with STOS core and every other module
- Orders raised against the bill of lading or terminal reference
- One customer master shared with CRM and with Accounts
- Transport charges billed through the same run as terminal handling
FAQ
Questions buyers actually ask
Yes. An order is the customer instruction and the shipments under it are the containers. Each shipment gets its own vehicle, its own gate timestamps and its own position on the timeline.
Gate in and gate out at the pickup, in transit, gate in and gate out at the destination, and close. Six timestamps, each recorded as it happens, with the origin and destination named.
Through its reference type and reference number. In most cases that is the bill of lading, which is the same reference the terminal holds the container against.
The gate movement screen requires both an order and a shipment to be selected before any vehicle assignment or gate action unlocks.
The dashboard counts overdue orders alongside draft, active, in-transit and delivered, and pickup pending and destination pending are counted separately so the two kinds of waiting are not mixed together.
Yes. Logistics Insights has three views: customer for tracking and delivery status, operations manager for gate turnaround and live manifest, and executive for SLA performance and fleet summary.
Yes, like every add-on module. It is usually added by operators who run their own transport rather than subcontracting all of it.
See Logistics on your own terminal data
Bring your own customers, tariffs and volumes and we will walk the module end to end on a live system.