Tuesday, 06:55. Site A’s desk shows the unit Available. Site B’s sheet still says Gate In pending. Central ops opens a third workbook the night shift built “just for Houston.” The line is already on the phone. Three files, three clocks, one container number—and no shared answer that survives the next gate move.

That is the multi-site problem at US empty depots. Not “do we have a dashboard for each yard.” A system-of-record problem: when the second physical yard arrives, copy-paste tariffs and side Excel islands usually arrive with it. By peak week, “where’s my box?” is a scavenger hunt across logins.

This piece is for operators evaluating multi-depot container management software—one truth across empty yards (~200–5,000 TEU each), not a freight TMS control tower and not a marine TOS. For count-vs-bay trust inside a single yard, see container yard inventory management. For shift KPIs on one timeline, see depot operations analytics software. Here the focus stays on one shared truth across sites.

When a second yard becomes a second system of record

Opening a second empty yard should add capacity. Too often it adds a second religion.

Common fracture lines:

Site A runs gate and EIR in one tool; Site B still stamps paper and keys Gate In later
Client tariffs live in a central spreadsheet that someone “synced” last Thursday
Holds and grade rules differ by site because nobody owns the master
Central ops sees two Available counts that cannot be reconciled to the same unit timeline
Billing disputes cite Site A’s clock while the truck left Site B

A second yard is fine. A second system of record is the tax. Multi-depot container management software earns its keep when Gate In, yard state, hold, M&R, and billing events for every site write to one model—so “Houston says Available” and “Dallas says Available” mean the same commercial thing.

If each site needs its own Excel island to answer the line, you do not have multi-depot software. You have multi-depot theatre.

Cross-yard inventory answers lines actually ask

Lines do not ask for a TEU heatmap. They ask concrete questions:

Which site has the unit (or an equivalent empty that meets grade and programme)?
Is it Available, on hold, in open M&R, or already reserved?
Can we stage it without a surprise dig-out that blows the appointment?
If we move the pick to another yard, does the tariff and release rule still hold?

Cross-yard answers fail when each site’s “inventory” is a local count that never shared event IDs with the other yard. Inventory spoke owns count-vs-bay honesty inside one facility; this multi-depot spoke owns answering across facilities without opening two systems. Link, do not rewrite: container yard inventory management. Availability definition stays with container availability management—here you only need Available to mean the same thing in every yard the line can see.

Practical rule: a cross-yard search that cannot drill to the same unit timeline the gate used is not a search. It is a rumour.

Shared tariffs and client masters without copy-paste

Multi-site pain often shows up first in commercial masters, not in the stack.

What breaks under two yards:

Client rate cards edited at Site A and emailed as PDF to Site B
Storage / handling triggers that start on different clocks per site
Client portal users who see one yard’s activity and guess at the other
Dispute packs that mix Site A evidence with Site B invoice lines

Shared client and tariff masters are not “nice HQ hygiene.” They are how you stop inventing a second commercial language per fence line. Empty-depot billing owns dispute workflow detail; multi-depot owns one client master and one tariff spine across yards—so a Gate Out at either site can cite the same commercial clock. Product spine context: empty container depot software.

If central ops still pastes tariff rows into Site B’s sheet after every rate change, the second yard has already become a second commercial system.

Soft check: pick one client and one unit that moved between sites last month. If tariffs, hold state, and Gate In/Out evidence live in three places, you do not have multi-depot truth yet—you have multi-depot archaeology. See one shared model on containerhub.ai.

Role-safe access: site desk vs central ops

One login is not the same as one god-mode user.

Site desk needs:

Gate, EIR, yard moves, and local holds for their yard
Clear visibility into units they may stage for a cross-yard ask—without rewriting another site’s stack plan

Central ops needs:

Cross-yard search, programme views, and exception queues
Role-safe ability to place or clear holds that affect release—without every clerk editing every site

Role-safe access fails when “multi-depot” means everyone sees everything editable, or when central ops can only view via nightly CSV. The design target is least privilege with shared truth: same events, different write scopes.

If Site B’s desk must borrow Site A’s password to answer a line, access is not role-safe. It is tribal knowledge.

What “one truth” requires from gate → yard → billing events

One truth is not a slogan on a slide. It is a chain of events that survive site boundaries.

Minimum spine across yards:

Gate In / Gate Out stamped on the unit at the site that ran the truck—same event definition everywhere
Yard / bay state that updates from those moves, not from a nightly recount that ignores the other site
Hold / grade / open M&R that block Available the same way in every yard the client can book
Billing triggers tied to the same Gate In/Out and storage clocks the commercial master uses
Portal / desk answers that cite those events—so “where’s my box?” and “why is the invoice line that date?” share one timeline

Break any link and multi-depot software collapses into multi-file reconciliation. Gate product context when the booth is the weak link: gate management software for depots. Analytics owns shift KPIs derived from this spine; multi-depot owns whether the spine is shared across sites at all.

Reject as “multi-depot container management software”: a freight TMS empty-TEU map; a marine TOS control tower pitched at inland empty yards; two single-site depot apps with a shared logo; five site Excel books plus a Power BI tile that cannot drill to a unit event.

Buyer checklist: multi-site readiness without a second spreadsheet island

Before you buy another login, walk this list with ops and finance in the same room:

Check	Pass looks like
One unit ID across sites	Same container number drills to one timeline whether Gate In was Site A or Site B
Shared client / tariff master	Rate change once; both yards invoice from it
Cross-yard “where’s my box?”	Desk answers without opening a second system or night-shift sheet
Consistent Available rules	Hold, grade, open M&R, reservation mean the same at every yard
Role-safe site vs central	Site desk writes locally; central ops sees exceptions without god-mode chaos
Billing evidence follows the truck	Dispute pack cites Gate In/Out from the site that ran the move
No second Excel island required	Peak week does not invent a “Houston-only” workbook to survive

Nice-to-haves that still serve truth: programme filters across yards; alerts when sites disagree on Available for the same client ask; portal views scoped by client, not by which fence the clerk likes.

ContainerHub’s framing for empty-depot operators with two or more yards is the same spine scaled across sites: gate, EIR/inspections, M&R, yard state, billing, and portal on one model—so multi-depot visibility is a consequence of shared events, not a second spreadsheet religion.

Soft CTA: multi-yard depot OS on containerhub.ai

If a second yard forced a second system of record—and the line still waits while three files argue—the fix is not another weekly sync ritual. It is multi-depot container management software that keeps client masters, cross-yard unit answers, role-safe access, and gate→yard→billing events on one truth.

ContainerHub is a depot / yard OS for physical empty-container operations (~200–5,000 TEU)—gate, digital EIR, inspections, M&R, yard, billing, client portal, and Jarvis on one model—not freight TMS, not WMS SKU software, not a marine TOS pitch. Soft next step only: review the product, book a demo, or compare pricing. No directory “claim your depot” ask.

Walk one client and one cross-yard unit in a demo. Ask whether tariffs, hold state, and Gate In/Out evidence stay on the same timeline when the truck ran Site B. If those answers are clear, the second yard stops inventing a second Excel island.

Visit ContainerHub · Pricing · Demo

Multi-Depot Container Management Software: One Truth Across Yards