Every shipper knows the three-letter codes. Almost none of them use them correctly.

Incoterms — defined by the International Chamber of Commerce and refreshed in the 2020 edition — are not mere shipping labels. They are legal instruments that determine precisely where risk transfers, who pays for what leg of the journey, and who carries the insurance. Yet in my years as a consultant, I have sat across the table from logistics managers, procurement leads, and supply chain directors who routinely default to “FOB” or “DDP” out of habit, with no awareness that their choice is quietly generating gaps, disputes, and unplanned costs across their intercompany flows.

SAP Transportation Management takes this seriously. In advanced multistage scenarios, the system actually enforces Incoterm logic — splitting freight unit stages, assigning carrier responsibility, and flagging statistical legs — based on the code you enter. When that code is wrong, the system faithfully executes the wrong process, at scale, across every document.

Bridging the gap between the ICC's commercial intent and SAP's technical implementation is one of the most underestimated challenges in any TM rollout. This blog is an attempt to close it.

Source link