← Back to Supply Chain Review Ocean Freight

Carriers announce $2,000–$3,000 per-FEU Peak Season Surcharges on transpacific

Source: FashionNetwork / FreightWaves · 2026-07-04 · 7 min read
中文

Supply Chain Action Points

Read this first — the conclusion, and the moves to make:

  1. By 30 June, get the applicable-timestamp rule in writing for every open transpacific booking, covering booking, gate-in, on-board and bill of lading dates, and align documents to the earliest one the carrier will accept on 100% of July volume.
  2. Split every quote into base, increase and surcharge as three separate lines, and refuse any quote whose surcharge line carries no expiry date; have that standard in force by 10 July.
  3. Model the 25-FEU book at $2,500 a month for three months and for twelve months before signing anything; if the twelve-month case exceeds the freight budget by more than 5%, cut volume or secure the expiry clause.
  4. For contracts renewing after July, cap the increase at the low end of the announced band, $2,000 per FEU, and write the surcharge expiry as a date rather than a season.
  5. From the last week of July, ask forwarders what share of bookings actually billed at $3,000; below half, treat the band as soft and negotiate free time and equipment guarantees instead of a rate discount.
Skip to the detailed analysis ↓
Summary

Several ocean carriers plan General Rate Increases and Peak Season Surcharges of $2,000–$3,000 per 40-foot container on transpacific lanes effective around mid-July, on top of already elevated spot rates. The move aims to capture peak-season demand even as front-loading eases.

The Analysis

The announcement reads: general rate increases and peak season surcharges of $2,000 to $3,000 per FEU on the transpacific, effective around mid-July, on top of spot rates that are already elevated. Four items, and only one of them is a number. The others are a band, a date with a hedge inside it, and a reference to a level nobody has printed.

$3,000 is 50% above $2,000. Start there, because a carrier that publishes a range has not published a price. It has published a negotiating position with a floor it will defend and a ceiling it hopes you accept, and the gap between the two is the entire commercial conversation you are about to have.

The useful work is not arguing over whether mid-July is early or late. It is taking the band apart: which line of your invoice it lands on, which timestamp decides whether it reaches your box, and how long it is allowed to stay there.

The midpoint is where the trouble starts. Budget at $2,500 per FEU and you have budgeted at a price nobody pays. A shipper with a negotiated agreement reaches the floor; a shipper without one gets the ceiling. The midpoint is the average of two populations, and you are inside one of them, not inside the average.

Take the two instruments apart, because they are not the same money. A general rate increase resets the base. It is permanent in the only sense that matters: every renewal, every index-linked clause and every future comparison starts from the new figure. A peak season surcharge is supposed to be temporary, and it becomes temporary only if something in the document says when it stops. One line compounds for years, the other should vanish in a quarter, and on your invoice they arrive in the same column. Whoever issues the bill has no incentive to remind you which is which.

The dollar amount is fixed, so the percentage is not. On a port-to-port base the same $2,500 is a larger share of your total than on an all-in base that already carries inland haulage and destination charges. This is why peer benchmarking on this announcement goes wrong so reliably: two importers compare the surcharge, agree it is $2,500, and conclude they are in the same position, while one is absorbing a materially larger share of its own landed cost. Establish what your base is and what sits inside it before you argue about the number.

Now the word that costs the most: around. Mid-July is not a date until somebody tells you which timestamp governs. There are at least four in a normal file, being booking confirmation, gate-in, on-board date, and the date on the bill of lading. They are rarely the same day, and in a week with a sailing delay they are not even the same week. Cargo gated in on 14 July that sails on 18 July is decided by a document field, not by a market view. The practical consequence of an effective date announced as a spread of days is that the surcharge lands on whoever is holding the booking when the carrier system reads the field, and the field is chosen by the party with the weaker incentive to be generous.

Direction changes the exposure. Under FOB terms the buyer owns the freight, so the surcharge is a cash event: it leaves the account in the month the invoice lands. Under CIF or DDP the seller carries it, which sounds like protection and usually is not, because the seller re-prices the next purchase order with a cushion. That cushion is a second surcharge with no line on the invoice, priced by someone who is now assuming the worst about a band that runs to $3,000. An importer on DDP terms can pay more, later, with less visibility than the FOB buyer who at least saw a number.

The detail worth the most attention is the one sentence about front-loading easing. Carriers are pushing this into a softening volume base. That does not make the announcement fake. It makes it a test. The published band is a price-discovery instrument: put $3,000 on the table and count how many bookings accept it. The tell is not the level, it is the implementation rate, meaning the share of bookings actually billed at the top of the band. When that share is low, carriers protect the published number and give the discount somewhere else, as extra free time at destination, an equipment guarantee, or a waiver on the second sailing. None of those move an index. So the index holds while the paid rate softens, and a procurement team benchmarking against the published number buys certainty at the exact moment certainty is getting cheaper.

Timing runs on three clocks and most budgets model one. The booking is made three to five weeks before sailing. The sailing is when the cost is incurred. The invoice arrives two to four weeks after that, and the landed cost falls in the month of arrival, which is when the variance appears against a budget set months earlier. Your decision window closes at booking, so the number you need is not the July number. It is the number you can still influence in late June.

Run it on a small book. Assume 25 FEU a month on the transpacific, and assume the surcharge bills at the $2,500 midpoint for the sake of argument; both figures are my assumptions, not numbers from the announcement. That is $62,500 a month. Held for a full year it is $750,000. Held for the peak only, which I will assume is three months, it is $187,500. The gap between those two answers, $562,500, is the value of one clause: the expiry date. You will spend more time arguing about the difference between $2,000 and $3,000 than about whether the thing expires, and the expiry is worth more money.

Which is the counterfactual worth stating plainly. Had the carriers announced a single all-in number, you would have one decision and no lever. The band is the lever, and it exists because they are not certain either. Had you signed an all-in rate with a cap on increases this spring, July would not be your event at all; it would be somebody else's invoice. And if you do nothing, you do not pay the announced price. You pay the announced price, plus your supplier cushion on the next order, plus the premium on bookings you place late because nobody built the cutoff calendar.

Lock when the all-in quote you are handed exceeds your own contract base by more than the announced surcharge. That is the line. Past it you are not paying a surcharge; you are paying a surcharge and a base increase wearing the same label, and only one of them was announced. The carriers have told us the range they want. They have not told us the range they will get, and that part is still being decided one booking at a time.

↑ Back to the key points

— By Vivian Zhao