Essentos
Use case | Container depot operations

Container depot software with real-time inventory by slot

How Essentos rebuilt container depot management with slot-level inventory, physical stacking rules, purpose-coded zones and event-by-event evidence to cut rehandles and accelerate gate-out at a depot in Spain.

The challenge: a container depot growing faster than its yard control

In a container depot, the bottleneck is rarely surface area. It is loss of yard coherence: units stacked without criteria, the same box moved three or four times before it leaves, minutes burned looking for a serial and constant radio chatter to confirm what is in the yard, where it sits and whether it is ready to release.

Essentos deployed a container depot management layer built on C-CORE: slot-level inventory tied to physical position, written operating rules (stacking, weight, compatibility), zones coded by purpose (release, customer pool, inspection, repair, reefer when applicable) and event-level evidence for every move. The yard became more ordered and noticeably faster: fewer rehandles, fewer judgement calls in the cab and predictable gate-out even on peak days.

Container depot operating panel
Slot inventory · Purpose-coded zones · Rehandle control · Release
Depot
Inventory Real slot position per container and status
one shared reference for yard, gate and admin
Zones Release · Customer · Inspection · Repair · Buffer
every zone carries a defined operating purpose
Fast release · truck
Customer · flow-based
Inspection · exception
Buffer · peak absorption
Rules Stacking, weight and compatibility rules per slot
safety and consistency without improvisation
Pace Fewer searches, fewer rehandles per shift
a depot yard that holds up under release pressure
Fast release85 %
Inspection / exception60 %
Peak buffer45 %
Observed operating impact on container depot operations
20% Release preparation
Less time per release after the outbound slot is anticipated and queued by the system, not searched on the radio.
40% Non-value rehandles
Fewer unproductive moves once stacking follows zone purpose and expected outbound flow.
15% Inventory accuracy
Each container reconciled to slot and operating status in real time, audited by event evidence.

Note: Figures observed in comparable Essentos depot deployments. Actual gains depend on volume, layout and operating discipline.

Day-to-day container depot operations

The depot handles empty container flows with truck entries and exits across the full shift. Beyond pure storage, services add operating complexity: inspections, damage exceptions and container preparation before release.

Volume and operating dynamics
  • Between 60 and 120 truck moves per day, with defined peak windows
  • Typical yard inventory of 1,800 to 3,200 containers depending on the season
  • Part of the flow needs prior action: inspection, verification, status change or preparation before release
Roles involved in the depot
  • 1 gate clerk validating inbound and outbound traffic and resolving exceptions
  • 1 administration role managing documents, statuses and confirmations
  • 1 yard supervisor prioritizing slot decisions and moves
  • 3 to 7 reach-stacker operators executing moves, releases and rehandles

On peak days the cost always shows up in the same place: rehandles without value and shift time burned looking for the right box.

Scope of the container depot deployment

The objective was direct: make the depot run on rules and slot data, not on memory and radio chatter. Essentos delivered a container depot management layer organized around four mechanics, each anchored in C-CORE evidence.

1) Real-time inventory by slot with operating status

Each container is tied to a real slot and an operating status the team understands and trusts. The depot stops running on two competing realities (what the system says versus what people remember) and starts from a single source of truth.

2) Purpose-coded zones for container depot flow

Each yard area was coded by operating intent rather than by habit:

  • Fast-release areas for high-rotation gate-out
  • Customer pools by account and contract
  • Inspection and exception zones
  • Repair areas with workflow status
  • Buffers to absorb peak load without breaking yard order
3) Stacking, weight and compatibility rules

Height, weight and compatibility rules are applied at slot decision time to protect safety and yard consistency. In a container depot, a badly stacked block is not only slower to release: it also creates real operating risk.

4) Event-by-event evidence of every move

Every relevant move leaves a usable trail: what moved, when, who executed it and to which slot. That single change ended most of the cross-checking, repeated radio confirmations and after-the-fact debates.

Real operating change in container depot management

  • Search time dropped because slot position stopped being approximate
  • Rehandles dropped because stacking now follows expected outbound flow and zone purpose
  • The supervisor moved from firefighting to prioritizing with a real, live view of the yard
  • Administration cut confirmations because operating status and slot were directly queryable
  • Truck release became predictable: less "wait while we find it" and fewer last-minute rehandles

Operating indicators tracked for depot inventory accuracy

Indicators were tracked over several months, focused on container depot yard productivity and release quality:

  • Rehandles and non-value moves per day, per crew
  • Average time to locate and prepare a release
  • Inventory discrepancies: believed position versus actual slot
  • Zone occupancy and pressure on critical pools
  • Releases with exceptions versus clean releases

Does your container depot lose coherence when volume rises?

If your depot loses time to searches, rehandles and manual coordination, Essentos can help you rebuild the yard around slot-level inventory, physical rules and purpose-coded zones. The same model is in production at container depots in Spain and runs on the same C-CORE layer used across Essentos terminals in Europe and the United States.

Related modules

Solution

TOS