Exceptions visible while the fruit could still be protected
One record from stuffing plan to gate-out. Plan, movement, sensor reading and damage sit on the same container rather than in four inboxes.
About the customer
Client A, the same produce-shipping operator, reconciling refrigerated and dry containers across its line
The customer's fleet carries its own produce in refrigerated containers and also lifts third-party cargo. Terminals send EDI; the office still reconciled BAPLIE files against a spreadsheet; temperature excursions and damage lived in separate threads from the movement that caused them. On a perishable trade, a box that cannot be placed in the chain is a claim waiting to start.
Customer identity withheld at the operator's request. The operating profile is factual.
The problem
Stowage, movement, reefer readings and damage reports did not share a system of record. Load, discharge, restow and shift were often backfilled at the end of the voyage. CODECO, COARRI and BAPLIE messages arrived in one inbox; the bay plan lived in another. A temperature excursion could be noticed hours later, unlinked to slot or move. Reconstructing a short or off-temperature box took longer than the claim window comfortably allowed.
What was deployed
- Bay plan management with weight distribution, hazmat segregation and reefer slot control
- Real time movement logging, with no end of voyage backfill
- Terminal EDI matching on CODECO, COARRI and BAPLIE with immediate exception flags
- Reefer temperature and humidity against stow position, with excursion alerts
- Damage and survey records tied to the causing movement, with photographs
Customer impact
Published percentage claims are omitted where the customer has not released them. Impact is stated in operational terms.
Every box has a chain
Plan, movement, sensor and damage sit on one container record instead of four inboxes.
Exceptions in time
EDI mismatches and reefer excursions flag during the call or the passage, not after discharge.
Claims with a file
A short or damaged box comes with stow position, movement log and photographs already attached.
Same line as the schedule
Container state and the rotation board describe the same voyage, not two offices' versions of it.
Start with a complimentary assessment
A working session against your fleet, flag mix and manning model. We map where you are today, where the record breaks, and what an honest roadmap looks like. No charge, and no obligation to go further.
What you leave with
- A map of where crew, wage and report data currently breaks
- Which module earns its place first, and why
- A staged roadmap with a proof of concept scoped to one area
- An indicative cost envelope before you commit anything
The product behind this study
Container software: bay planning with weight, hazmat and reefer slot control, BAPLIE and terminal EDI matching, excursion alerts, and damage tied to the move.