I Told Everyone 'Container Arrives Week 48.' Three Teams Made Three Different Plans.

October 2024. I was coordinating a shipment of custom packaging machines from a manufacturer in Ho Chi Minh City to our warehouse in Los Angeles. The order had been in production for 14 weeks. Our holiday retail clients were already sending me emails with subject lines in all caps. Everyone needed these machines yesterday.

I got the vessel confirmation from our freight forwarder in Singapore. The container was booked on the Maersk Sebarok, departing Cat Lai Terminal Week 44, transshipping through Singapore, ETA Los Angeles Week 48. I forwarded the email to the warehouse team and our logistics coordinator with a single line at the top: "Container arrives Week 48 — plan accordingly."

I thought I'd been clear. I had not been clear.

Three teams, three calendars

Here's what I didn't know at the time. Our manufacturing partner in Vietnam tracked production weeks using a simple system: Week 1 starts January 1st, seven-day blocks after that. The Singapore freight forwarder used ISO 8601 week numbers — the international standard where Week 1 is the week containing the first Thursday of the year. And our warehouse in Los Angeles used US calendar weeks, where Week 1 contains January 1st and weeks start on Sunday.

In 2024, those three systems produced three different date ranges for "Week 48":

Vietnam factory (simple week numbering):
  Week 48 = November 25 – December 1
  (counted from Jan 1, seven-day blocks)

Singapore forwarder (ISO 8601):
  Week 48 = November 25 – December 1
  (coincidentally matched Vietnam this time)

Los Angeles warehouse (US system, Sunday start):
  Week 48 = November 24 – November 30

Look at the US dates. The warehouse team's "Week 48" ended on November 30th — a Saturday. The container actually arrived at the Port of LA on December 2nd — a Monday. To the Singapore forwarder, December 2nd was Week 49. To the warehouse team who'd been told "Week 48," the arrival looked six days early because... well, to them Week 49 hadn't started yet. But the container was already there.

Wait — let me re-read that. It's confusing. Which is exactly the problem.

Here's what actually happened on the ground: The container arrived December 2nd. The warehouse had scheduled a receiving crew for "Week 48" based on their US calendar — meaning they expected it by November 30th at the latest. When December 2nd came, the crew had already come and gone. Nobody was scheduled to receive cargo that Monday because, in their system, they'd moved on to Week 49 tasks. The container sat.

It sat for six days. Six days of detention charges at $185 per day. Six days of our retail clients asking where their machines were. Six days of me staring at tracking updates that said "Available for pickup" while nobody picked anything up.

The phone call I'll never forget

I called the warehouse supervisor on December 3rd. "Hey Mike, any update on the container? Tracking says it's been ready since yesterday."

Long pause. "What container?"

"The one from Vietnam. The packaging machines. ETA Week 48."

Another pause. "Week 48 was last week. We staffed up Wednesday through Friday. Nobody showed up with a container. We figured it got delayed and you'd update us."

This is the moment when I realized the problem. I had said "Week 48" to three different groups of people, and each group had silently translated those words into different calendar dates. Nobody asked for clarification because — and this is the part that still gets me — everyone thought they knew what it meant.

I had to call a trucking company for an emergency pickup, pay for six days of port storage I hadn't budgeted for, and explain to my boss why a $1,100 line item had appeared out of nowhere. The explanation — "I used a week number without specifying which week numbering system" — sounded like I was making excuses. It was the truth.

"I had said 'Week 48' to three different groups. Each group silently translated those words into different calendar dates. Nobody asked for clarification — because everyone thought they knew what it meant."

What I do differently now

After that mess, I changed three things about how I communicate shipment dates. These are small changes that take maybe 30 extra seconds per email. They've saved me from repeating this mistake at least twice that I know of.

1. Never use a week number without the date range. Every shipment update I send now looks like this: "ETA Week 48 (November 25 – December 1, ISO)." Three extra words. The date range is the anchor. The week number is just shorthand for people who already know their system matches mine.

2. Ask every new partner: "What week numbering system do you use?" I now include this question in my onboarding calls with new suppliers, forwarders, and warehouses. Half of them look at me like I'm speaking a different language — which, honestly, is kind of the point. If they don't know what I'm asking, they're probably assuming their system is the only system.

3. Verify the calendar, don't trust the week number. I keep WeekNumber.cc bookmarked. Before I send any date-related email, I punch in the key dates and check the ISO week number, the US week number, and the simple week count. If there's a discrepancy — which happens more often than you'd think — I flag it before anyone else has a chance to misinterpret it. ISO 8601 defines these rules precisely, and a quick check is all it takes to avoid a six-day mistake.

Why this happens more than people admit

Here's something interesting I learned after this disaster. The ISO 8601 standard was published in 1988. That's almost 40 years ago. And yet, the United States still uses a completely different week numbering convention in most business contexts. The US government's fiscal calendar? Different again. The broadcast industry? They have their own broadcast calendar where weeks always start on Monday and months have either four or five weeks. There's a manufacturing standard. A retail 4-4-5 calendar.

I didn't know any of this before my container sat at the port for six days. Now I can't unsee it. Week numbers are everywhere in logistics — on bills of lading, shipping manifests, warehouse booking systems, delivery schedules — and almost nobody specifies which system they're using. They just write "Week 48" and assume everyone else's Week 48 is their Week 48.

It almost never is.

The $1,110 lesson

The detention and storage charges came to $1,110. Not enough to lose my job over, but enough to get a very uncomfortable look from my boss. The bigger cost was the six days of lost production time while our retail clients waited for machines that were sitting two miles from our warehouse.

I've told this story to every new person on our logistics team. Some of them nod politely. A few have come back to me months later and said, "Hey, that week number thing you warned us about? It just happened."

It always happens. The only question is whether you catch it before or after the container arrives.