Container transporter and CFS software holds the container as the unit of work: the delivery order it moves against, the trailer and driver assigned, the timings at each gate, the free time granted and the detention accruing, ground rent and storage, the delivery to the consignee, and the empty return that closes the cycle. With Pentoggle, an operator can describe how containers actually move through the business and generate the starting application around it.
This business is defined by clocks it does not control. The shipping line grants free days on the container. The port or CFS charges for cargo occupying space. Both start running on events that happen before a trailer is even assigned, and both continue running through delays caused by documentation, customs, the consignee's warehouse or a shortage of trailers.
Many container transport firms already run Tally for accounting and a GPS provider for trailer tracking. Those stay where they are. What is often still managed outside them is the container itself: which delivery order it belongs to, how many free days remain, where it currently is, and whether the empty has gone back.
Key takeaways
- Two separate clocks usually run on the same shipment, owned by different parties on different tariffs, and the operator is exposed to both.
- Free time is the most valuable thing in the operation and is consumed by delays that are frequently documented nowhere.
- The empty return is roughly half the movement and generates no revenue of its own, so it is the leg that gets deprioritised and the one that produces the charge.
- Responsibility for detention and ground rent depends on the contract and on the cause of the delay, which makes the timestamp record commercially valuable rather than merely tidy.
- A useful number is turnaround time per container, from gate-out to empty return.
How a container transporter makes money
The revenue is usually simple. A rate per container movement, varying by size, weight, distance and whether it is import or export, agreed with a forwarder, a CHA or the cargo owner directly. Some operators work on dedicated contracts with steady volume. Most take work as it comes from a set of regular forwarders.
The cost is a trailer, a driver, diesel, tolls and the time both are occupied. Because the rate is per movement and the cost is per day, the entire economics turn on how many movements a trailer completes in a month. A trailer waiting eleven hours at a CFS gate earns nothing for those hours and still costs its EMI, its driver and its insurance.
Then there is the category that does not appear in either column until it goes wrong. Detention charged by the shipping line when the container is held beyond free days. Ground rent or storage charged by the port or CFS while cargo occupies space. Neither is your revenue. Both can become your cost, depending on the contract and on who caused the delay.
The spreadsheet is often not the problem
A movement register works for an operator running fifteen trailers.
The trouble starts at identifiable points.
When the free-day clock is in somebody's head
Free days were granted on the delivery order. How many remain today, across thirty open containers, is a calculation nobody is doing continuously, so it is discovered at the point the charge appears.
When timings are approximate
Detention and ground rent are computed from timestamps. Reconstructing gate-in and gate-out from memory a week later produces a position you cannot argue from, so the charge is simply paid.
When the empty is out of sight
The loaded delivery is the visible job. The empty return is an errand, and containers sit at consignee premises for days because nobody's list shows them.
When trailer utilisation is unknown
The fleet ran thirty movements this month. Whether that is good depends on how many it could have run, and that number does not exist anywhere.
What container transport software holds
Delivery order and container details
DO reference and validity, container numbers, size and type, seal, weight, and the shipment it belongs to.
Free time and expiry
Free days granted, the date the clock started, days remaining, and an alert before expiry rather than after.
Trailer and driver assignment
Which trailer, which driver, and when it was despatched against which container.
Gate and milestone timings
Gate-in and gate-out at port, CFS and consignee, recorded with timestamps at the point they happen.
Detention and ground rent
Charges accruing under the applicable tariffs, against whom, with the elapsed time and the cause recorded.
Delivery and unloading
Arrival at consignee, waiting time, unloading start and finish, and any documentation collected.
Empty return
Where the empty has to go, by when, current status and confirmation of return.
Billing and recovery
Movement charges billed to the customer, plus any detention or ground rent recovered rather than absorbed.
Two clocks, two owners, one exposure
The commercial structure worth understanding is that there are usually two separate charges accruing against time, and they belong to different parties.
The container belongs to the shipping line. The line grants a period of free time and charges detention beyond it, under its own tariff. The clock is about how long you keep their box.
The cargo occupies space at a port or CFS. That operator charges ground rent or storage, under its own tariff. The clock is about how long the cargo sits.
The two run on different schedules, are charged at different rates, and are billed by different parties. A delay of five days can generate both. An operator who tracks only one is exposed to the other.
Responsibility depends on the contract and on the cause. A delay caused by the consignee's warehouse being full is usually not the transporter's charge. A delay caused by the transporter's own trailer shortage usually is. Between those sit the ambiguous cases, which are the majority: documentation that arrived late, a customs process that took longer than expected, a strike, a public holiday nobody accounted for.
This is why the timestamp record is a commercial asset rather than an administrative one. When the charge arrives and the question is who bears it, the operator with hour-by-hour records of where the container was and what it was waiting for is in a materially different negotiating position from one working off recollection. The record does not decide the outcome. It determines whether there is a conversation at all.
Tariffs, free-time periods and charging rules are set by individual lines, ports and CFS operators and are revised. Build the application to hold what your own delivery orders and contracts specify rather than assuming a standard.
The empty return is half the job
Every import container movement is two legs. The loaded leg from port or CFS to the consignee, which is the job the customer is paying for. And the empty leg from the consignee back to the nominated depot, which is not.
Because the second leg has no revenue attached, it receives less attention, and this is where the operation loses money in three separate ways at once.
The trailer is occupied. A trailer on an empty return is a trailer not available for the next loaded movement, which is a direct utilisation cost.
The detention clock is still running. Free time is on the container, not on the cargo, and it ends when the empty is returned. A container unloaded on Tuesday and returned on Friday spent three days accruing against the line's clock for no operational reason.
And the return has its own constraints. The depot nominated by the line may not be the nearest one. It may have gate timings. It may refuse a container over a condition issue, which sends the trailer somewhere else entirely.
Treating the empty return as a tracked leg with its own status, deadline and owner, rather than as the tail end of a completed job, is one of the few changes in this business that improves utilisation and reduces charges simultaneously. The list that matters is short and nobody currently has it: containers unloaded but not yet returned, with days elapsed and free time remaining.
Workflows this business depends on
- Trip Sheet and Settlement Software, for the trailer movement and its expenses.
- Fleet Management Software, for trailer utilisation and availability.
- Shipment Tracking Software, for the status a forwarder or cargo owner wants without calling.
- Logistics Invoice and Billing Software, for movement billing and recovery of charges.
- Vehicle Document and Compliance Software, for trailer documents and port entry requirements.
- Freight Forwarder and CHA Software, which is frequently the customer placing the work.
Why container transporters choose Pentoggle
The container is the record
Delivery order, timings, charges and empty return all held against the container rather than spread across a movement register.
Free time tracked as a countdown
Days remaining across every open container, visible before expiry rather than discovered on an invoice.
Timestamps captured at the gate
Gate-in and gate-out recorded on a phone when they happen, which is what makes a detention conversation possible.
The empty return is a tracked leg
Unloaded but not returned, with days elapsed, as a live list rather than an afterthought.
Sits around your accounting
Tally and comparable systems continue handling accounting, invoicing and GST. Pentoggle adds the operational workflow around containers, trailers, timings and charges.
A useful number for container transport
Turnaround time per container, from gate-out to empty return.
This single figure absorbs almost everything that determines whether the operation is profitable. Trailer availability, gate waiting, consignee unloading delay, empty return lag and documentation friction all extend it, and all of them cost either utilisation or detention.
Measure it in hours rather than days, because the delays worth attacking are frequently a matter of hours and disappear entirely at daily resolution.
Break it into segments once you have the total. Gate-out to consignee arrival is a routing and traffic question. Arrival to unloading complete is a consignee question and often a contractual one. Unloading to empty return is entirely yours. Most operators assume their problem is the middle segment and find, when they measure, that the last one is longer.
Ready to build software for your container operation?
The line is charging you for a box.
The port is charging you for the cargo.
Neither clock stops because nobody was watching it.
Describe how your containers, trailers and timings actually work to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.