SLAs with partners in foreign trade: the complete guide

The foreign trade manager who walks into the S&OP meeting with the main forwarder’s data always up to date doesn’t have better partners: they have a process that doesn’t depend on anyone’s goodwill. While the team around them sends emails asking for status, they open the dashboard, filter by partner and answer in 30 seconds.

SLAs with partners in foreign trade aren’t a cultural issue. They’re a structural one: who defines what must be delivered, in what format and by when, and who monitors it when it doesn’t arrive.

FollowNet One is e.Mix’s foreign trade software: it centralizes events, documents and alerts from every partner in the operation (freight forwarders, customs brokers, trucking companies) so the team handles deviations before they turn into cost. This guide explains what a partner SLA is in foreign trade, why most operations can’t enforce it, and how to set up a model that works without depending on phone calls, emails or good memory.

• → The problem: each partner reports in its own way, on its own time, with data only it understands
• → The cost and risk: late decisions, status rework, invisible demurrage and S&OP without reliable data
• → The mechanism: standardized events + an SLA per stage + an automatic alert when the partner doesn’t deliver
• → How to start: pick one main partner, map 5 critical events and configure the first alerts in less than 30 days

What a partner SLA is in foreign trade

A partner SLA (Service Level Agreement) is the formal agreement on what each provider must deliver, by when and in what format. In foreign trade, that means: when the freight forwarder must confirm the booking, how long the customs broker has to open the file after receiving the documents, and how far in advance the trucking company must confirm the pickup.

Most operations have these agreements: verbally, in generic contracts or in the memory of whoever has been there longest. The problem isn’t the absence of an SLA. It’s the absence of monitoring: nobody knows, in real time, how many active shipments are within the deadline and how many have already expired with no action.

Why most operations can’t enforce partner SLAs

It isn’t a lack of will. It’s the absence of an information structure.

To enforce an SLA, you need to know: when did the deadline start counting? Has the partner delivered? If not, how long has it been late? Who is responsible for following up? Without those answers available in real time, enforcement depends on memory, email or phone calls, which are exactly the mechanisms that fail when volume grows.

Three structural reasons why the SLA doesn’t work in most operations:

1. The event isn’t recorded in the system. The forwarder confirmed the booking by email. The customs broker opened the file in their own system. The status exists, but it isn’t on the importer’s platform. Without the event centralized, there’s no way to calculate whether the SLA was met.
2. The SLA has no objective definition. “Opened on D+1” is different from “opened on D+1 after confirmed receipt of the original documents”. Without an explicit criterion, any deadline is negotiable when it’s time to follow up.
3. Nobody owns the follow-up. When the SLA expires, who contacts the partner? If the answer is “the whole team” or “whoever notices first”, the SLA isn’t a commitment; it’s an intention.

The 3 pillars of a partner SLA that works in foreign trade

1. Standardized events per stage

Each stage of the import process has an event that marks its completion: booking confirmed, documents received, DI registered, channel assigned, customs release, pickup scheduled. The SLA can only be measured when these events arrive in a standardized way (same naming, same field, same timing) from every partner.

Different partners reporting different events on the same shipment is the root cause of the problem. Standardization doesn’t require the partner to change its system; it requires the event to be recorded on the importer’s platform at the right time.

2. An SLA per stage with deviation alerts

Each event has an expected deadline. The alert fires when the deadline is about to expire with no event recorded, not after it has expired. The difference between alerting 24 hours in advance and alerting after the deadline is the difference between preventing the delay and recording the damage.

Effective alerts in foreign trade are configured by type of partner and criticality of the stage: the customs broker opening the file has a shorter SLA than freight confirmation, because the impact of a DI delay is greater than a booking adjustment.

3. An owner and an auditable history per partner

Each stage has a defined owner. When the alert fires, whoever contacts the partner knows it’s their responsibility, not “the team’s”. And every interaction is recorded: when the partner was contacted, what they answered, how long it took to resolve.

That history is what turns SLA enforcement from personal friction into data-driven management. Instead of “you’re always late”, the conversation becomes: “in the last 30 days, 23% of the files were opened late; we need to understand the root cause”.

Proof from the field: from countless emails to a single dashboard

Before: Communication scattered across email, Excel and each partner’s systems. Manual input opened up countless chances for error, and when something got lost, the history disappeared with it.

After: Everything in one tool. Communication configurable per shipment or compiled per partner. What used to take the team hours is now done by the system.

Daniel Cunskis, Gateway Manager, DSV Air & Sea Brazil
Video (in Portuguese): https://www.youtube.com/watch?v=DhM9_AtSfRc&t=168s

How partner SLAs work inside FollowNet One

FollowNet One centralizes every partner’s events on a single platform. Each partner (freight forwarder, customs broker, trucking company) feeds events into the system, and FollowNet One automatically calculates whether the SLA was met for each stage of each shipment.

The operational result: the analyst doesn’t need to call the forwarder to find out whether the booking was confirmed. The dashboard shows, by traffic light, which shipments are within the SLA, which need attention and which have already expired and need action. The manager walks into the meeting knowing exactly which partners are performing below expectations, with data, not perception.

Template: SLA matrix by partner and stage

This template is the starting point: each operation adjusts the deadlines based on the partner’s real history and the criticality of the stage.

How to set up partner SLAs without an endless project

Owner: Foreign Trade Manager or Coordinator, responsible for defining the SLA criteria for each partner and making sure every event is recorded on the platform with the right timing.

Cadence: daily, reviewing the SLA dashboard before the workday starts; weekly, reviewing each partner’s performance history and adjusting criteria when needed.

Traffic-light KPI: percentage of stages delivered within the SLA per partner, with a target above 90% in the first quarter after configuration.

First scope: the freight forwarder with the highest volume of active shipments or the most recent complaints. Map 5 critical events, define the deadlines and configure the alerts. Visible results in the first two weeks.