Notes
Reconciling port authority throughput releases with your own stack counts

If you've ever pulled a count of container stacks off a satellite pass and then watched the port authority post a TEU number that doesn't line up, you already know the two series aren't measuring the same thing. One is a snapshot of boxes sitting on the apron at a given hour. The other is a monthly tally of moves, lifts, and transfers that gets assembled, checked, and revised before anyone outside the terminal sees it. Reconciling them means understanding the lag and the translation between the two, so your early read holds up when the official number finally lands.
Why a stack count and a TEU release won't match line for line
A stack count from a daily pass tells you how much box inventory is sitting at the yard on the day of the image. It doesn't tell you how many of those boxes moved on or off a vessel, how many were repositioned empties, or how many sat there for three weeks waiting on a trucking slot. The monthly throughput release, by contrast, is a flow number: total TEU handled, usually broken into loaded and empty, import and export, sometimes by terminal. It's reported on a lag, often three to five weeks after month-end, and it can get revised in the following release once the port authority reconciles its own operational logs.
So you're comparing a point-in-time inventory read to a monthly flow figure that's still being audited when you first see it. That mismatch is structural, not a flaw in either series. The fix is to stop expecting the two to match on any single day and instead track whether the direction and magnitude of change agree over a stretch of weeks.
A second wrinkle: anchorage queues and vessel calls sit between the two numbers. A yard can be stacking up because throughput is rising, or because vessels are queued at anchorage and not berthing on schedule, which backs up the stack without changing underlying cargo flow much at all. Reading stack counts alongside vessel call frequency and queue length at the same port tells you which story you're in before you extrapolate to a TEU estimate.
A reconciliation routine that holds up over a quarter
Build the comparison at the level the port authority reports, not finer. If the release is monthly TEU for the whole port, don't try to reconcile a single terminal's daily stack count against it; aggregate your daily reads to a weekly or monthly average first, across however many terminals the port's own figure covers.
The throughput number the port authority releases this month actually reports on the prior month, so line up this month's average stack count and vessel call volume against next month's release, the one that will cover the current month. This sounds obvious written down and is the single most common mistake when people first start laying the two series side by side in a spreadsheet.
Track the spread, not just the level. Once you have a few months of paired observations, you can watch whether your satellite-implied read is consistently running ahead of, behind, or in line with the official number's direction of travel. A persistent offset is fine and often useful. It just means your early read needs a fixed adjustment before anyone treats it as equivalent to a hard TEU figure. What matters for a trading or allocation decision is whether the stack count moved before the official release confirms it.
When the official release finally drops, go back and check whether your stack-count trend called the direction right over the prior one to three weeks. That's the real test, and it's the one that tells you whether the daily feed is earning its keep as an early read rather than just a parallel series that happens to exist.
This is exactly the gap Trade Flow Index is built to sit inside: a daily stack, vessel-call, and anchorage-queue read at named ports, delivered as a time series you can line up against the monthly release once it posts. If you're tired of waiting on the official number to find out what already happened at the berth, take a look at what the feed covers.