Shipment Exceptions: Silence Costs You the Client

Anyone running deep-sea ocean freight into Santos, Paranagua or Navegantes knows rollovers, blank sailings, vessel delays and customs-channel holds show up every week. ANTAQ, Brazil’s waterway transport agency, publishes service regularity data for long-haul routes, and the numbers line up with what operators already see on the ground: a meaningful share of scheduled port calls gets changed. For the operations desk, these exceptions are Tuesday. The problem starts when the importer calls to ask why nobody told them.

Most forwarder switches we have seen started with a troubled shipment and an importer who found out late. The rate may be competitive, transit time may be average, but when cargo is delayed and the importer discovers it on their own, trust breaks at a point no discount can repair.

The exception is part of operations; silence is the operator’s choice

Rollovers, blank sailings, berthing delays, red-channel customs holds and cargo retention by a regulatory body (ANVISA, MAPA or Inmetro in Brazil) are recurring events in international trade. An importer with two or three years of experience knows these events by name and expects them to happen. They expect their freight forwarder to tell them first, before they have to check the carrier’s website, the terminal tracker or the DUIMP status on Brazil’s Portal Unico themselves.

The difference between a forwarder that keeps the client and one that loses them often comes down to one gap: how long it takes for the exception to travel from the operator’s screen to the importer’s inbox. If the operator spots a rollover on the carrier portal Monday morning and notifies the importer Monday afternoon, the importer has already checked the tracking, already seen the container disappear from the scheduled vessel and already decided the forwarder was not paying attention.

In practice, exception communication at most Brazilian forwarders happens by email, with no template and no deadline. The operator notifies when they can, and the message might be a single line saying “the vessel was delayed” or three paragraphs of justification. Neither version helps the importer do what they actually need to do: notify their own customer, reschedule production or renegotiate a delivery date.

The importer builds their entire chain on the date you gave

When the operator confirms the booking and reports an ETA of the 15th at Santos, the importer plans everything from that date. The customs broker starts preparing the clearance instruction, finance provisions the exchange rate, the warehouse reserves space and the sales team promises delivery to the end customer. Every link in that chain works off the date the forwarder provided. When something changes and the update lags by two days, each link discovers the delay on its own, usually after the original deadline has already passed.

The cost of late communication goes beyond the exception itself, which might be detention, a rebooking fee or a storage charge. The bigger cost is the cascade inside the importer’s operation. A retail importer who scheduled receiving for a shelf-replenishment window loses that window when the ETA shifts without notice. An industrial importer who bought raw materials for a production line scheduled the following week either stops the line or buys domestically at a higher price.

A forwarder that measures service quality by transit time and freight rate per container is measuring the part the importer already compared before signing. The part the importer evaluates after signing is whether the forwarder can anticipate problems and communicate them clearly. In FIATA’s research on shipper expectations, information predictability consistently ranks among the top three factors in the decision to keep or switch a logistics provider.

Four pieces of information every exception update needs

An effective exception update fits in one paragraph, as long as it covers four things: what happened, why, what the new timeline is and what the operator is already doing about it.

Start with the fact, without euphemism. “Container MSKU1234567 was rolled from MSC Oriane, voyage 426E, originally scheduled to load in Ningbo on 28 Sep” is a fact. “There was a change to the booking” is vague enough to force the importer to call back and ask what happened.

Then the cause, as far as the operator can tell. If the carrier rolled the container due to overbooking, say so. If it was a blank sailing, say so. If the operator does not know yet because the overseas agent has not responded, say that too, and state when they expect an answer. The importer can tell the difference between “I don’t know yet, I’m checking” and “I don’t know and I didn’t ask.”

Third, the revised timeline, even if it is rough. “The next vessel with available space on the same route departs Ningbo on 5 Oct, ETA Santos 12 Nov” gives the importer what they need to replan. If no vessel is confirmed yet, provide a window: “we are negotiating space on the next two available sailings and will confirm by tomorrow at 2 pm.”

Last, the operator’s action: what has been done and what comes next. “We have already requested rebooking on MSC Arina, voyage 428E, and are awaiting confirmation from our Ningbo agent” closes the loop. The importer knows the issue is being handled and has a date to follow up.

Writing a message with these four pieces takes about the same time as writing a vague one, because the operator already has the information when they discover the exception. What eats time is the back-and-forth afterward, when the importer gets a generic notice and has to call to find out what actually happened.

Each type of exception calls for different timing

How urgently you communicate depends on how much the exception changes the importer’s plan.

A rollover demands the most speed. When a container drops off the scheduled vessel, the importer needs to know the same day. Transit time changes, the ETA changes, and the entire chain of deadlines has to be rebuilt. If the operator waits for the carrier to confirm the next vessel before saying anything, the importer has already lost two or three business days they could have used to adjust.

A blank sailing is similar but usually comes with more lead time, since carriers tend to announce schedule cancellations one to three weeks in advance. An operator who monitors carrier advisories can alert the importer before the shipment is at risk, not after.

Vessel delays at the destination port are different. The information comes from the carrier or the terminal and shifts as the vessel approaches. Notifying the importer of every ETA fluctuation creates noise. The better approach is to communicate when the variance exceeds a threshold agreed with the importer. Some importers want to know when the delay exceeds two days; others, five. That threshold should be set at the start of the relationship.

A red-channel customs hold on the DUIMP (Brazil’s single import declaration) is something the importer cannot control but needs to know about, because a physical inspection extends the clearance timeline by days or weeks. The customs broker gets the notification, but the freight forwarder has to make sure the information reaches the importer with a diagnosis: what is being required, the estimated timeline and whether the importer needs to provide any documents.

Cargo retention by a regulatory agency (ANVISA, MAPA, Inmetro) follows the same logic. The importer needs to know what the agency is requesting and what remains outstanding, because supplementary documentation often depends on the exporter overseas, and every day of waiting is a day of bonded storage that will be charged.

A well-communicated exception retains more than a cheap rate

An importer who receives an exception update with fact, cause, timeline and action stays in control of their own planning, even when the news is bad. An importer in control keeps working with the same forwarder. The relationship breaks when the importer discovers the problem on their own, calls the operator and hears “I was just about to tell you.”

In shipment visibility, we covered the cost of the importer not having access to shipment milestones. Exception communication is a different problem: the importer may have tracking access, may see that the ETA changed, but still needs the operator to explain what it means for their specific process and what is being done. Tracking shows the raw fact. The operator turns that fact into a diagnosis and a next step.

Forwarders that document exceptions and the updates they sent build a record they can point to when the importer questions, months later, why a particular shipment was delayed. A communication logged in the system with date, time and content is proof the importer was informed. Without that record, the dispute becomes one person’s word against another’s, and the relationship erodes over something the operator communicated verbally but never wrote down.

Every status question an importer sends to the operator has a cost, as we covered in a previous post. During an exception, the cost is higher, because the question becomes “what happened, why wasn’t I told, and what are you going to do?” That conversation takes 15 to 30 minutes per occurrence, versus two or three minutes for a proactive update that covers the basics.

How Tier2 Portal takes the status question off the operator’s desk

The operational milestones the operator records in Tier2 Cargo appear automatically for the business partner in Tier2 Portal. When the ETA changes, the partner sees the update without calling. When the shipment reaches a milestone (cargo arrival at the bonded terminal, DUIMP registration), the information is available in the portal, on the forwarder’s own domain and under the forwarder’s brand.

For exceptions that need explanation, like a rollover or a customs hold, the operator still needs to communicate the diagnosis and the next step. The Portal handles the status and document layer, freeing the operator to focus on the communication that actually needs a person: the exception, the context and the action.

Learn about Tier2 Portal or get in touch.

The next step is to agree on a threshold with the importer

Before waiting for the next exception to test a better communication approach, the operator can do one thing today: ask the importer what level of schedule variance they want to know about. Two days, five days, any change at all. That single number defines when to communicate and removes the operator’s judgment call of “is it worth flagging?” The answer is always the same: the importer would rather know too early than find out too late.