Operational control
What do import exceptions really cost, and how do you measure it?
Import exceptions such as ETA changes, missing files, broker questions and unexpected invoices cost the most when nobody owns the next decision. Measure them as a loss chain: the signal, the action that was missed, the charge or delay that followed and the margin impact, rather than as a generic efficiency estimate.
By Ayhan Karaca, Co-Founder · Updated: September 29, 2026
How should you measure the cost of an import exception?
The financial case should connect a real signal to a real outcome: a changed ETA was not acknowledged, pickup planning started late, storage or expedite spend appeared, and margin changed. Official data establishes the surrounding exposure—FMC reports $15.4 billion collected in D&D by nine carriers over five years, while CBP reports 105,103 merchandise entries on a typical FY2024 day—but each company's preventable share must be measured from its own records.
| Signal | Coordination gap | Possible measure |
|---|---|---|
| ETA changed | No pickup owner | Late-plan hours and resulting charge |
| Document missing | Request buried in email | Time to complete and rework |
| Customs question | Evidence split across parties | Response time and dwell |
| Invoice arrived | No shipment or event link | Unmatched value and close delay |
| Customer commitment at risk | Commercial team sees it late | Expedite, concession, or lost-order evidence |
Which costs hide beyond the fees?
Storage, exam handling, demurrage, detention, and expedite invoices are visible losses. Less visible consequences include delayed inventory availability, a purchasing decision made with stale cost, customer service reacting too late, and skilled staff spending hours reconstructing status. Treat these as hypotheses until company evidence confirms them.
What should every exception record contain?
A useful exception record states what changed, its source and time, the business consequence, the accountable owner, the next deadline, the requested evidence, and the resolution. Priority should follow consequence and time sensitivity rather than whoever sends the most email.
- Define material events and escalation thresholds.
- Assign one accountable owner for the next decision.
- Keep partner requests and evidence with the exception.
- Close with outcome and actual cost where available.
- Review recurring patterns without exposing sensitive shipment data publicly.
How Tyllus helps
Tyllus connects orders, shipments, ETA context, documents, partner follow-up, customs questions, exceptions, and costs in a shared operational view. Teams see what changed, what is waiting, who owns the next move, and which evidence supports the outcome. Tyllus supports better decisions; it does not control partners or authorities, promise delivery dates, or guarantee savings or revenue.
Make the next decision visible.
See how Tyllus can connect shipment exceptions with owners, partner follow-up, evidence, and financial context.