Importers in foreign trade: the complete guide

The import manager who answers status questions during the S&OP meeting doesn’t have a small team: they have a process that depends on manual follow-up to work. Each analyst controls their shipments the way they learned. When one goes on vacation, the manager doesn’t know where things stand.

Well-controlled imports don’t depend on who knows the most; they depend on a recorded process, automatic alerts and a dashboard that shows what needs action today. Without that, the operation scales linearly: more volume, more people, more spreadsheets.

FollowNet One is e.Mix’s foreign trade software for importers: it centralizes every import shipment (ocean, air and road) with standardized events, deviation alerts and a real-time dashboard so the team handles exceptions before they turn into cost. This guide explains how to set up end-to-end import control, what separates a predictable operation from a reactive one, and how to implement it without an endless project.

• → The problem: each analyst controls their shipments their own way, with no standard, no alerts and no visibility for the manager
• → The cost and risk: invisible demurrage, recurring emergency freight and decisions based on outdated data
• → The mechanism: standardized events by trade lane + automatic alerts + a consolidated exception dashboard
• → How to start: one critical trade lane, 10 events mapped, first alerts in less than 30 days

What separates a predictable import operation from a reactive one

In reactive operations, the problem is discovered once the cost has already arrived: the demurrage invoice, the emergency freight to meet the production deadline, the S&OP meeting that turns into a session of explanations. The analyst didn’t fail; the process failed to alert them in time.

In predictable operations, the expected standard is configured in the system for each trade lane. When a shipment deviates from it (ETA slipping by more than 48 hours, free time about to expire with no pickup scheduled, DI not registered on time), the alert arrives before the impact. The analyst acts at the right moment, not afterwards.

The 5 critical control points in imports

Every import operation has events that, when not monitored, generate avoidable cost. The five most common:

1. ETA and forecast variation: an original ETA slipping by more than 48 hours with no update on the shipment signals a problem, whether with the ocean carrier, the forwarder or the documents. The alert needs to arrive before the planning meeting, not after.
2. Free time and demurrage expiration: each shipment has a different deadline by carrier and route. Without a centralized record, control depends on whoever remembered to calculate it. The result is demurrage that shows up on the invoice, not on the dashboard.
3. Inspection channel: a red channel completely changes pickup planning. Without an immediate alert, the trucking company is called for the original date and arrives while the shipment is still with Brazil’s Federal Revenue.
4. Pending documents: a B/L with errors, a mismatched invoice, an incomplete packing list: any problem document not caught before the DI (import declaration) is registered leads to a red channel, delays and storage costs.
5. Pickup and delivery confirmation: picking up the container is the event that ends the demurrage risk and starts the detention risk. Without a defined owner and deadline, the container sits idle longer than necessary.

How to set up import control by trade lane

The most common mistake when setting up import control is trying to configure everything at once. The result is a project that never ends because the operation is too big to map in one go.

The right approach is by trade lane: pick one (the one with the highest volume or the highest historical demurrage cost), map that lane’s 10 critical events, configure the traffic-light criteria and activate the alerts. With the first lane working, the second is configured faster because the logic has already been validated.

First trade lane checklist:

• Ocean carrier and transport mode defined
• Contracted free time recorded per shipment
• 10 critical events mapped with the expected deadline
• Traffic-light criteria defined: green / yellow / red
• An owner per type of exception
• Alerts configured at least 72 hours ahead for critical events

Multinational imports: the same dashboard for several countries

Operations that manage imports in more than one country face an additional challenge: each country has different regulations, local forwarders with different systems and time zones that make consolidation harder. The regional manager depends on manual reports from each local team, which arrive in different formats and with different delays.

With FollowNet One, each local operation feeds events into the platform and the regional manager sees the consolidated dashboard for every country, with the same exception criteria, the same traffic lights and the same auditable history. Management by exception works the same way for 50 shipments in Brazil and 300 shipments spread across five countries.

Proof from the field: from reactive imports to a predictable operation

Before: Productive and unproductive imports coexisted with no visible difference: the analyst couldn’t tell what was within the standard from what was generating cost.

After: A dashboard split by trade lane clearly shows where the operation is performing and where there’s a deviation, without going through shipment by shipment.

Luciano Braga, Foreign Trade Coordinator, Positivo Tecnologia
Video (in Portuguese): https://www.youtube.com/watch?v=rRclDf1iQrw&t=13s

How FollowNet One structures imports

FollowNet One was built with import logic as its foundation, not as an add-on module. Every registered shipment has a unique key, events by trade lane, alert criteria configured with the customer and an auditable history of each stage.

The analyst starts the day on the exception dashboard, not on the list of every shipment. Those within the standard stay green. Those with a yellow or red light arrive with context: what happened, what the risk is and who the owner is. The S&OP meeting becomes a decision session, not a status update.

How to set up predictable imports without an endless project

Owner: Import Manager or Coordinator, responsible for defining the exception criteria for each trade lane and making sure every active shipment has an owner and a deadline recorded.

Cadence: daily, reviewing the exception dashboard before the workday starts; weekly, reviewing KPIs by trade lane and adjusting criteria.

Traffic-light KPI: number of demurrage occurrences without a prior alert, with a target of zero. Any demurrage generated without a configured alert is a process failure, not an operational one.

First scope: the trade lane with the highest volume or the highest historical demurrage cost in the last 12 months. Configure 10 events, define the traffic lights, activate the alerts. Visible results in the first month.