Consolidated release status across 4 carrier portals and 3 terminals into one priority queue. Demurrage charges dropped 40% in the first 60 days.
Engagement map
From operating problem to measured outcome
5 weeks delivery · 6 tools in the implementation stack
Challenge
Pacific Coast Logistics handled 600 import containers per month across LA/Long Beach and Oakland.
What we built
We built an automation layer that pulls carrier release status, customs clearance, terminal availability, and free-time data into a single container queue.
Result
Demurrage charges dropped 40% in the first two months.
Recorded outcomes
Delivery timeline: 5 weeks. Metrics are shown in the same context as the published engagement.
Pacific Coast Logistics handled 600 import containers per month across LA/Long Beach and Oakland. Their ops team of 6 spent mornings manually checking carrier portals, terminal sites, and customs status to build a daily priority list. By 10 AM, the list was already stale. Free time expired overnight or over weekends with nobody catching it. They were leaking $45,000-$60,000 per month in avoidable demurrage and detention charges.
We built an automation layer that pulls carrier release status, customs clearance, terminal availability, and free-time data into a single container queue. Each container is ranked by hours of free time remaining, client priority, and estimated cost exposure. Ops gets proactive alerts when containers approach free-time expiry without a booked appointment or assigned drayman. Client-facing notifications go out automatically when action is needed from their side, missing approvals, pending payments, or document gaps.
Demurrage charges dropped 40% in the first two months. The ops team shifted from 70% reactive firefighting to spending most of their time on proactive container management. Gate-out cycle time after release improved because the team stopped missing available containers buried in email. Three client billing disputes in the first quarter compared to an average of twelve previously.
The implementation path shown here follows the actual engagement summary.
Implementation sequence
Container discharge detected via carrier API
Availability and release status pulled from carrier portal and terminal system.
Customs release
freight release, and hold status consolidated into a single container record. Status: actionable or blocked with specific blockers listed.
Free-time countdown calculated
Container ranked in the priority queue by hours remaining, cost exposure, and client tier.
If actionable and no drayage assigned
alert to dispatch with recommended drayman based on port/lane performance.
If blocked
targeted notification to the responsible party, finance for freight release, broker for customs hold, client for missing approval.
Client receives structured email
container status, what's at risk, what action is needed, and deadline.
Container gates out
Move-off time recorded. Daily dashboard updates with performance metrics and next-day risk list.
Results like these start with a free call.
If the same approach fits your situation, I'll tell you how. If it doesn't, I'll tell you that too.
Book a Free Call