Workarounds Can Be a Red Flag in Cross-Border Operations

In his recent article about desire paths, Chris Caplice, Ph.D., of DAT Freight & Analytics and the Massachusetts Institute of Technology Center for Transportation and Logistics makes an important point:

When teams keep finding ways around governance processes, the answer is not always tighter enforcement. Sometimes the shortcut itself is a signal that the system’s design no longer matches how decisions should be made in live operations.

In cross-border supply chains, that signal matters even more.

In a domestic setting, a workaround might cause delays, confusion or rework. In cross-border execution, the same workaround can point to a bigger issue: While a rule might exist (in a policy manual, standard operating procedure, broker instruction or someone’s institutional knowledge), it might not be embedded into operational decisions.

That difference matters because cross-border failures rarely stay contained. A tariff classification change, incomplete customs documentation, outdated ERP master data, or a mismatch between landed-cost logic and shipment requirements do not remain one team’s problem for long.

Such issues move across procurement, broker coordination, customs filing, shipment release, inventory timing, returns handling, merchant expectations and customer service. By the time the issue becomes visible, teams are no longer deciding whether to move something forward. They are trying to unwind a decision that is already in motion.

The Missing Decision Layer

That is why recurring workarounds in cross-border operations should not be dismissed as simple noncompliance. In many cases, they point to a missing layer of system control.

Consider a common example: A procurement or operations team must respond quickly to a tariff shift or a sourcing change. But ERP master data has not caught up, and customs requirements are missing from the order or shipment workflow. The shipping team already knows the order will stall at clearance unless someone manually changes a field, sends an offline note, or routes the case through an informal exception path.

On the surface, this looks like process drift. In reality, it reflects a systemic gap: compliance is still treated as something to check later, rather than as a condition of whether execution should move forward at all.

The same pattern shows up across cross-border commerce and supply chain environments. Merchant systems may accept orders before execution readiness is truly aligned. Shipment workflows may trigger before routing, customs and documentation conditions are fully validated. Procurement teams may commit to suppliers or inventory flows before the latest tariff, import control or cost logic has been reflected in operational workflows.

In each case, the workaround is not the root problem. The real problem is that the system lacks a built-in decision layer that can determine what may proceed, what must pause, what requires escalation, what needs rerouting, and what basis for that decision should be captured.

That is the real control point.

The failure is not simply that people bypass the process. The failure is that the governing decision was never encoded where it mattered — before execution was allowed to move ahead. When that happens, policy, feasibility and accountability are all pushed downstream, and teams are left to repair the consequences manually.

The Transition to Executable Governance

That is why compliance in mature cross-border systems should be treated as operating infrastructure rather than as administrative review.

A resilient operating model does not depend only on retrospective audits or ad-hoc overrides. It builds governance into the path itself. It checks whether key conditions are satisfied before a commitment becomes operational or a shipment is released.

And it preserves enough decision history that when delays, disputes or exceptions arise, teams do not have to reconstruct the logic from scattered emails, spreadsheet edits and downstream symptoms.

Desire paths show where operational reality has outrun system design. In cross-border operations, they also show where governance has not yet become executable.

The organizations that respond well will do more than reduce compliance friction. They will build procurement, trade and fulfillment systems in which policy requirements, operational feasibility and execution discipline are aligned from the start — instead of being reconciled manually after commitments are already in motion.

(Photo credit: Getty Images/Itto Ilmatar)