How Nina Prevents Demurrage Charges: A Container Free-Time Case Study

US demurrage costs are not a rounding error. They are a structural margin problem.

The Federal Maritime Commission reported that US ocean carriers collected $15.4 billion in demurrage and detention fees between 2020 and 2025. US demurrage rates run approximately four times the global average. For any distributor or retailer moving containers through American ports, that gap shows up on invoices quarter after quarter, often before anyone on the team knew a charge was coming.

One Nauta customer identified $300,000 per year in potential demurrage exposure before deploying Nina. That number did not come from negligence. It came from the same problem most operations teams face: container free-time deadlines buried in Bills of Lading, tracked manually, across dozens of active shipments at any given time.

This is the fourth case study in Nauta’s agent series. The first two covered Alec and invoice matching and shipment delay detection. The third covered Nina and order visibility. This one focuses on how Nina handles container free-time tracking and demurrage prevention specifically.

The Problem With Manual Free-Time Tracking

Every container arriving at a US port has a free-time window, typically three to five days, before demurrage charges begin accruing. Miss that window and fees can reach $150 to $450 per container per day, depending on the port and carrier.

The challenge is not that teams are unaware of free-time. The challenge is that tracking it manually across 30, 50, or 100 active containers is operationally expensive and error-prone. Free-time deadlines live inside Bills of Lading. Those documents arrive by email, get forwarded to logistics coordinators, sometimes get logged into a spreadsheet, and sometimes don’t. A container sitting two days past free-time is not a failure of intent. It is a failure of visibility.

When the customer in this case study audited their demurrage invoices going back 18 months, the pattern was consistent: charges were not concentrated in a few large incidents. They were spread across dozens of containers, each one a small miss that added up to $300,000 annually. No single event looked catastrophic. The aggregate was.

How Nina Reads Free-Time Deadlines

Nina is Nauta’s Shipment Watch Agent. Within the broader Nauta agent architecture, which also includes Alec, the Document Control Agent, and Marcus, the Inventory Watch Agent, Nina tracks what is happening to your containers from purchase order through final delivery.

For demurrage prevention, Nina’s workflow starts at the Bill of Lading.

When a Bill of Lading arrives, by email, through a carrier portal, or from a connected TMS, Nina reads it, extracts the container number, port of discharge, carrier free-time terms, and estimated arrival date. That data flows into Nauta’s unified data layer, where it sits alongside your ERP records, your WMS, and your procurement data.

Nina then calculates the free-time expiration date for each container and monitors it daily.

The T-5, T-3, T-1 Alert Sequence

Nina does not wait for a problem to surface. She runs a daily check across every active container and flags those approaching their free-time deadline. The alert sequence works on a countdown.

T-5 days: Nina surfaces the container in your exception queue with the free-time deadline, current port status, and estimated demurrage exposure if pickup does not happen in time.

T-3 days: Nina escalates the alert and drafts a pickup coordination request or free-time extension request to the relevant carrier, ready for your team to review and send.

T-1 day: Nina sends a final alert and marks the container as critical. The draft communication is pre-populated with container details, the specific deadline, and the cost at risk.

Your team does not need to pull a report, check a spreadsheet, or remember which containers are close to expiring. Nina brings the exceptions to them, ranked by potential cost.

Ranking Containers by Financial Exposure

Not all at-risk containers carry the same urgency. A container at the Port of Los Angeles with a $300/day demurrage rate and two days of free-time remaining is a different problem than one at a smaller inland port with a $75/day rate and four days remaining.

Nina ranks the exception queue by potential exposure, not just by proximity to deadline. Your logistics team sees the highest-cost risk at the top of the list every morning, without any manual sorting.

For the customer in this case study, that ranking alone changed how the team allocated attention. Before Nina, they worked from a shared spreadsheet sorted by arrival date. After deployment, they worked from Nina’s exception queue sorted by dollar exposure. In the first week, Nina surfaced three containers the team had not flagged as urgent, all three within 48 hours of their free-time expiration.

The Cash-to-Cash Impact

Demurrage charges are not just an operational nuisance. They compress margin and extend your cash-to-cash cycle.

When a container sits past free-time, your inventory is effectively frozen. You are paying daily fees on goods you cannot sell, cannot receive into your WMS, and cannot deploy against open orders. For a distributor managing tight inventory turns, a week of unexpected demurrage on a high-value container can turn a profitable shipment into a net-negative event.

The customer in this case study did not eliminate demurrage entirely after deploying Nina. Some delays are outside any team's control, like port congestion, customs holds, and carrier equipment failures. What changed was the category of charges that were preventable. In the 12 months following deployment, charges attributed to missed free-time deadlines dropped by more than 80 percent. The remaining charges were tied to delays that were genuinely unavoidable.

That outcome maps directly to one of Nauta’s core value pillars: margin protection through autonomous action on data your team already has but cannot process fast enough manually.

Nina Within the Nauta Agent Architecture

Nina does not operate in isolation. She reads from the same unified data layer as Alec and Marcus.

When Nina flags a container at demurrage risk, that signal is visible across Nauta. If the delayed container carries inventory that Marcus has already flagged as critical to an open purchase order, the exception surfaces with additional context: not just the demurrage cost, but the downstream inventory risk if the container does not clear on time.

That cross-domain visibility is what separates Nauta’s architecture from point solutions that handle only one part of the problem. A standalone demurrage alert tool tells you a container is late. Nauta tells you the container is late, what it will cost per day, which open orders depend on it, and what your team needs to do next.

If your team is managing container free-time manually today, the math is straightforward. At four times the global average, US demurrage rates are not going to normalize. The exposure only grows as shipment volumes increase. Nina handles the monitoring, the alerts, and the draft communications. Your team handles the decisions.

To see how Nina fits into your operations, book a demo at getnauta.com.