Seattle freight accessorial charges to watch

Executive Summary

Seattle freight bills carry accessorial charges that reflect the port, the terrain, and current input costs, not a generic national rate card. A carrier serving the Port of Seattle and Port of Tacoma corridor prices dwell time, chassis availability, and appointment windows differently than a carrier running flat inland lanes, because container drayage and last-mile delivery through Sodo, Georgetown, and the I-5/I-90 interchange are genuinely harder to schedule than a straight highway run.

National freight cost data confirms the direction carriers are pricing into these charges. 1% year over year, both read September 6, 2026. 759 over the same period. Rising input costs give carriers cover to widen accessorial charges, and a congested, hilly, port-adjacent lane is exactly where a widened charge is hardest for an AP reviewer sitting in another region to catch.

What changes this is treating the accessorial line as a contract question, not a freight-bill question. The invoice-to-contract match has to test each Seattle-specific accessorial against what the carrier agreement actually allows for that terminal and that appointment window, not against a generic accessorial table built for a different geography.

1. What is different about freight billing in Seattle?

Seattle freight billing differs from a generic national lane on three points: port drayage accessorials tied to the Port of Seattle and Port of Tacoma, congestion and grade surcharges tied to the I-5 and I-90 corridors through downtown, and a fuel surcharge table sitting on top of West Coast diesel pricing that runs above the national average. None of these three conditions apply to a flat inland lane, which is why a national accessorial template misprices a Seattle invoice on.

A freight contract negotiated at a national level typically lists accessorial categories, detention, layover, redelivery, without specifying how a given metro's terrain or port operations should change the trigger point for each one. Seattle's terminals run appointment systems that carriers cannot always control, so detention time starts accruing for reasons outside the shipper's own dock performance.

The I-5 corridor through downtown Seattle and the I-90 floating bridge approach both carry congestion patterns that a carrier can use to justify a metro delivery surcharge, separate from any fuel line. That surcharge is a contract term, not a market fact, and it should be written down as a rate and a trigger condition, not left to the carrier's judgment on the day.

Drayage from the Port of Seattle or Port of Tacoma to an inland facility adds chassis and yard fees that do not appear on a truckload lane quote at all. A shipper who audits Seattle freight invoices against a truckload rate card, without a separate drayage schedule, will not catch these charges even when they are billed correctly, because the reference document does not cover them.

2. How does the fuel surcharge table apply to Seattle lanes?

The fuel surcharge itself uses the same national index most carrier contracts reference, but Washington fuel taxes and West Coast diesel pricing change what that index produces at the pump, which changes where the contract's surcharge breakpoint sits relative to the invoice. Gasoline PPI (BLS series WPU0571, read September 6, 2026) rose 37.1% year over year to 302.759 in July 2026, a swing large enough that a stale breakpoint understates or overstates the surcharge a Seattle-based carrier is.

Most carrier agreements tie the fuel surcharge to a published index and a breakpoint schedule: below a certain price per gallon, no surcharge; above it, a percentage that steps up with price. The mechanism is the same nationwide. What differs in Seattle is the baseline diesel price the carrier is actually paying, which sits on the West Coast fuel market rather than the national blend.

A 37.1% year-over-year move in gasoline PPI, as recorded by BLS as of September 6, 2026, signals the direction of pressure on that baseline. It does not tell a reviewer what a specific carrier should be charging on a specific Seattle lane. That number has to come from the carrier's own surcharge table, checked against the contract's stated index and breakpoint, not assumed from a national trend.

The audit question is whether the surcharge percentage actually billed matches the step the contract specifies for the index level in effect on the invoice date. A surcharge that was set correctly when fuel was cheaper and never re-tested against the current breakpoint schedule is a common way this line drifts, regardless of city.

3. Which accessorial charges should a Seattle shipper check line by line?

Five accessorial lines carry the most Seattle-specific risk: port drayage and chassis fees, detention tied to terminal appointment systems, a metro delivery or congestion surcharge, a grade or terrain surcharge for hill routes, and redelivery charges tied to dock receiving hours. Each of these has a plausible operational reason to exist and a specific contract term that should define its rate and trigger; where that term is missing or unrated, the charge has no basis regardless of how ordinary it.

Each of the five lines above answers a different operational reality of moving freight through this specific metro, and each should map to a specific clause in the carrier agreement rather than a general accessorial category. A contract that lists "detention" without a Seattle-specific trigger condition leaves the carrier free to apply a national default that may not fit a port-adjacent delivery.

The practical audit step is to pull the carrier's accessorial schedule for this lane specifically, not the master schedule for the account, and confirm each of these five categories is rated and triggered in writing. Where it is not, the charge is either negotiable retroactively or should be flagged as out of contract going forward.

• Port drayage and chassis fees: Charges tied to Port of Seattle or Port of Tacoma pickup, including chassis rental and per-diem, should match the drayage schedule in the contract, not the truckload rate card.
• Detention and appointment delay: Detention time that starts because of a terminal appointment system, rather than the shipper's own dock, should be checked against the contract's detention trigger, not accepted as billed.
• Metro delivery or congestion surcharge: A separate line for downtown or corridor delivery should have a rate and trigger written into the contract; if it does not, the charge has no contractual basis at all.
• Grade or terrain surcharge: Some carriers add a surcharge for hill routes or restricted-access delivery points common in Seattle's industrial areas; this should be a named, rated term, not a discretionary add.
• Redelivery and reconsignment: A failed delivery attempt tied to a Seattle dock's own receiving hours should be checked against whether the contract assigns that cost to the carrier or the shipper.

4. Why does port congestion change what belongs on the invoice?

Port congestion changes the invoice because delay costs that originate at the terminal, not at the shipper's dock, get passed downstream as detention, chassis, or storage charges that a shipper did not create and may not be contractually responsible for. Whether that cost sits with the carrier or the shipper depends entirely on what the contract's detention and demurrage clauses say about causation, not on how the charge is labeled on the invoice.

A container sitting at the Port of Seattle or Port of Tacoma past its free time accrues per diem and demurrage charges from the terminal and steamship line, separate from anything the trucking carrier controls. Some of that cost legitimately flows to the shipper if the contract assigns it there. Some of it should stay with the carrier if the delay was the carrier's scheduling failure.

The invoice rarely states which cause applies. It states a charge and a date. Matching that charge against the contract's causation language, and against the terminal's own appointment or gate record where available, is the only way to tell which side of that line a given fee falls on.

This is a reason to request supporting documentation, gate records, appointment confirmations, on any port-related accessorial above a threshold worth the reviewer's time, rather than accepting the carrier's own characterization of the delay.

5. How do I-5 and I-90 corridor constraints show up as billing terms?

I-5 and I-90 corridor constraints show up as billing terms in two places: a metro delivery surcharge applied to any destination inside a defined downtown or congested zone, and a longer transit-time allowance built into the base rate that can mask a scheduling failure as normal transit. Both should be named and rated in the contract; when a surcharge zone is not mapped to specific ZIP codes or delivery points, the carrier has discretion the shipper cannot audit against.

A congestion surcharge that applies to "metro Seattle deliveries" without a defined boundary gives the carrier room to apply it more broadly than the shipper intended when the contract was signed. The fix is a named zone, ideally by ZIP code or delivery point, attached to the surcharge clause.

Separately, a carrier's stated transit time for a Seattle lane should reflect the corridor's real constraints, not an optimistic straight-line estimate. A contract that promises next-day delivery on a route that regularly requires a two-day transit due to corridor congestion sets up disputes over late fees or expedite charges that have nothing to do with actual carrier performance.

Both issues are contract drafting problems more than invoice errors, and both are cheaper to fix before the next renewal than to dispute after each late invoice.

6. What should a Seattle shipper ask for before the next carrier renewal?

Before renewing a Seattle carrier contract, a shipper should request a lane-specific accessorial schedule covering drayage, detention, and any metro or terrain surcharge, a written definition of the congestion zone by ZIP code, and the specific fuel index and breakpoint table the carrier will apply, dated to the renewal. Asking for these in writing closes the gap between a national master agreement and what actually gets billed on this one lane.

A master service agreement written for a national account often defers lane-level detail to a supplemental schedule that gets updated less carefully than the main contract. Seattle is exactly the kind of lane where that supplemental detail carries real financial weight, given port operations and corridor congestion.

Requesting the lane-specific schedule in writing, rather than relying on the carrier's account manager's verbal description of "how Seattle usually works," gives the shipper a document to audit against for the life of the contract. It also creates a record for negotiating the next renewal, since a shipper can point to what was actually billed against what was actually agreed.

This is a smaller version of the same discipline that applies across every service category with geography-driven or terminal-driven variability: write the variable into the contract before the invoice arrives, not after.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and duplicate freight billing and the multi-carrier consolidation problem.

7. Frequently Asked Questions (People Also Ask)

Does the Seattle fuel surcharge use a different index than the rest of the country?

No. Most carrier contracts reference the same national fuel index regardless of lane. What differs is the actual diesel price a Seattle-based carrier pays, which sits on the West Coast market. The contract's breakpoint schedule should be checked against that carrier's stated index, not assumed from a national average.

Why do Port of Seattle and Port of Tacoma charges show up separately from the trucking invoice?

Drayage from either port to an inland facility involves chassis rental, per diem, and terminal appointment costs that a truckload rate card does not cover. These need their own schedule in the contract; without one, a shipper auditing against the truckload rate alone will miss them even when correctly billed.

Is a metro delivery surcharge legitimate on a Seattle invoice?

It can be, if the contract defines the surcharge zone by ZIP code or delivery point and states a rate. If the zone is undefined, the carrier has discretion to apply it more broadly than intended, which is a contract gap rather than a billing error.

How do I know if detention time was really the shipper's fault?

Check the contract's detention trigger against the terminal or dock's own appointment and gate records. Detention that started because of a port appointment system, not the shipper's dock performance, may not be contractually the shipper's responsibility.

Should I expect Seattle freight costs to keep rising?

BLS PPI data read September 6, 2026 shows truck transportation of freight (WPU3012) up 10.9% year over year and long-distance truckload trucking (PCU484121484121) up 8.1% year over year as of July 2026. That is a national cost direction, not a Seattle-specific forecast, but it is the basis carriers use to justify surcharge increases on any lane, including this one.

What is the difference between a grade surcharge and a congestion surcharge?

A grade surcharge is tied to terrain, hill routes or restricted-access delivery points common in Seattle's industrial areas. A congestion surcharge is tied to traffic and scheduling difficulty in a defined metro zone. Both should be separately named and rated in the contract rather than combined into one undefined accessorial.

Can a carrier charge redelivery fees for a failed Seattle delivery?

Only if the contract assigns that cost to the shipper for the specific cause of the failed attempt. If the failure traces to the dock's own receiving hours or a documentation issue, the contract's causation language determines which side bears the cost.

What documentation should I request for a disputed port accessorial?

Ask for the terminal's gate record, the appointment confirmation, and the carrier's own dispatch log for the date in question. These establish whether the delay originated at the terminal or with the carrier's own scheduling, which determines who should bear the cost under the contract.