Container availability date disputes: when import free time should start

Discharge is not availability

A container that has been lifted off the vessel is not necessarily a container you can pick up. It may still be in a stack the terminal has not released, under a freight hold for unpaid ocean freight, under a customs or USDA hold, or in a yard block the terminal is not working. Free time that starts at discharge can burn days during which no trucker could have taken the box out of the gate.

Part 541 makes that gap visible. Under 46 CFR § 541.6(b)(6), every import demurrage or detention invoice must state the container availability date, separately from the free time start and end dates in (b)(4) and (b)(5). If the availability date is missing, § 541.5 eliminates the obligation to pay. If it is present but later than the free time start date, the invoice itself shows that free time ran while the cargo was unavailable.

What the incentive principle says about availability

The FMC's 2020 interpretive rule at 46 CFR § 545.5 explains how the Commission applies 46 U.S.C. § 41102(c), the requirement that carriers, MTOs and intermediaries maintain just and reasonable practices, to D&D. The core test in § 545.5(c)(1) is whether demurrage and detention are serving their primary purpose as financial incentives to promote freight fluidity.

On cargo availability specifically, § 545.5(c)(2)(i) says the Commission may consider the extent to which demurrage practices and regulations relate demurrage or free time to cargo availability for retrieval. Paragraph (c)(2)(iii) adds that the Commission may consider the type, recipients, format, distribution, timing and effect of notice that cargo is available. The rule does not declare charges on unavailable cargo automatically unlawful, but the logic is direct: a charge cannot motivate you to collect a box you are not allowed to collect.

That is why the availability date sits at the center of import disputes. The question is never just "how many days were billed". It is "how many of those days could this container actually have moved".

Reconstructing the true availability date

Availability is not a single field you can trust from one source. It is a combination of conditions, and each leaves a trace in carrier or terminal data. We rebuild it from four layers.

First, the carrier's EDI 315 status messages or API milestones: vessel arrival, discharge, and any release events. Second, the terminal operating system as exposed through the terminal's website or a data aggregator: whether the container shows as available, which holds are flagged, and its yard status. Third, hold history: freight holds, customs holds (often visible as CBP status), USDA or other agency holds, and terminal holds such as unpaid fees. Fourth, the arrival or availability notice the billing party actually sent, with its timestamp.

The true availability date is the first date on which the box was discharged, released by the carrier, clear of every hold, and pickable at the terminal. If those layers disagree with the date printed on the invoice, the invoice date is the one that needs explaining.

• EDI 315 or API: discharge and release events
• Terminal availability status and yard location, captured with timestamps
• Hold history, separated into carrier, customs, agency and terminal holds
• Arrival and availability notices, with send times

Holds: whose hold matters

Not every hold supports the same argument. A freight hold placed by the carrier because its own release process lagged is a billing party problem, and it bears directly on the § 541.6(e)(2) certification that the billing party's performance did not cause or contribute to the charges.

Government holds are treated differently. Section 545.5(c)(2)(iv) says the Commission may consider the extent to which demurrage and detention serve their intended purposes during government inspections, and may also consider extenuating circumstances. That is a case by case question, not an automatic waiver. A customs exam that took two days is a weaker argument than one where the box sat cleared but unreleased, or where the exam location itself delayed return. Classify the hold before you build the dispute around it.

Worked example: three lost days on six containers

Harbor Lane Outdoor, a patio furniture importer, receives a demurrage invoice for six 40-foot containers from a single vessel call. The invoice shows discharge on June 2, free time of 4 days starting June 2 and ending June 5, a container availability date of June 2, and demurrage charged June 6 through June 11: 6 days at $250 per day per container. Total: 6 containers x 6 days x $250 = $9,000.

The reconstructed record tells a different story. EDI 315 shows discharge on June 2, but the terminal's availability status for all six boxes stayed "not available" until June 5, when a carrier freight hold was released. The carrier's release message is timestamped June 5, and Harbor Lane's freight payment confirmation is dated May 29. So the printed availability date is wrong, and three days of free time (June 2 through June 4) ran while the cargo was held by the carrier.

If free time had started June 5, 4 days of free time would have run through June 8, and demurrage would begin June 9. Harbor Lane picked up the last container June 11, so the supportable charge is June 9 through June 11: 3 days. The disputed amount is 6 containers x 3 days x $250 = $4,500, half the invoice. The packet cites § 545.5(c)(2)(i), the § 541.6(e)(2) certification, the freight payment receipt and the timestamped hold history.

Writing the availability dispute

An availability dispute is strongest when it reads like a reconciliation, not a complaint. Lead with the date printed on the invoice, then the date your evidence supports, then the days and dollars that fall between them. Billing desks process these requests in volume, and a packet that shows its arithmetic on the first page gets read.

Structure it in four parts. First, the invoice identifiers: bill of lading, container numbers, invoice number and issuance date, so the request is matched to the right charge. Second, the timeline per container: discharge, each hold placed and released, the first date the box showed as available, the pickup appointment and the outgate. Third, the recalculation: free time restarted at true availability, the resulting demurrage days, and the amount you accept versus the amount you dispute. Fourth, the basis: § 545.5(c)(2)(i), and where the billing party caused the delay, the § 541.6(e)(2) certification.

Accepting the undisputed portion matters. Paying the supportable days, or offering to, shows the request is about accuracy, and it keeps the dispute narrow. It also keeps the § 541.8(b) clock focused: the billing party must attempt to resolve the request within 30 calendar days of receipt, and a narrow request is easier to resolve inside that window.

Capturing availability before you need it

Most of this evidence is perishable. Terminal availability pages show current status, not history, and hold flags disappear once cleared. If nobody captured the screen on June 3, the proof that the box was unavailable is hard to rebuild in July.

Milestone & Gate Tracking records carrier and terminal events as they arrive, timestamps each terminal status capture, and stores the hold history per container. When the invoice lands, it compares the printed availability date to the reconstructed one and flags any day of free time that ran before true availability. Our port guides at /resources/ports list what each major gateway publishes about availability and holds.

If your team works from a visibility platform such as project44, FourKites, Terminal49 or Vizion, those milestone feeds can be connected so the record exists before the invoice does. See /product/integrations for how each connection works.