logistics.incoterm-responsibility

export function incotermResponsibility(rule: string, edition: number): IncotermResponsibility

export type Party = "seller" | "buyer";

/** One rule's split of costs and risk between seller and buyer. */
export interface IncotermResponsibility {
  readonly rule: string;
  readonly edition: number;
  /** "Free Carrier" */
  readonly name: string;
  /** false for the four sea and inland waterway rules: FAS, FOB, CFR, CIF */
  readonly anyMode: boolean;
  /** where the seller delivers, which is where risk passes to the buyer */
  readonly delivery: string;
  /** true only for the D rules; under C rules the seller pays the carriage but risk passes at shipment */
  readonly riskPassesAtDestination: boolean;
  /** loading onto the collecting vehicle at the seller's premises */
  readonly loadingAtOrigin: Party;
  /** export formalities, licences and export duties */
  readonly exportClearance: Party;
  /** who contracts and pays for the main international carriage */
  readonly mainCarriage: Party;
  /** who must insure the goods; null when neither party is obliged to */
  readonly insuranceBy: Party | null;
  /** the minimum cover the rule requires, when there is an obligation */
  readonly insuranceCover: string | null;
  readonly unloadingAtDestination: Party;
  /** import formalities */
  readonly importClearance: Party;
  /** import duty, import VAT and other import taxes */
  readonly importDuties: Party;
}

import { incotermResponsibility } from "#fune/logistics.incoterm-responsibility@^1";

import { INCOTERMS } from "./logistics_incoterm_responsibility_data.ts";  ← this capability’s own data, compiled from data/incoterms.json into the same file by fune build
import { type IncotermResponsibility, type Party } from "./logistics_incoterm_responsibility_types.ts";

/**
 * Where the seller delivers (and risk passes) under an Incoterms rule, and
 * which party pays for each stage, from the ICC rules for the edition named.
 */
export function incotermResponsibility(rule: string, edition: number): IncotermResponsibility {
  if (!Number.isInteger(edition)) throw new TypeError(`edition must be a year, received ${edition}`);
  if (!INCOTERMS.some((r) => r.edition === edition)) {
    const editions = [...new Set(INCOTERMS.map((r) => r.edition))].join(", ");
    throw new RangeError(`no data for Incoterms ${edition}: this version covers ${editions}`);
  }
  const row = INCOTERMS.find((r) => r.edition === edition && r.rule === rule);
  if (row === undefined) {
    const rules = INCOTERMS.filter((r) => r.edition === edition).map((r) => r.rule).join(", ");
    throw new RangeError(`unknown Incoterms ${edition} rule "${rule}": expected one of ${rules}`);
  }
  return {
    rule: row.rule,
    edition: row.edition,
    name: row.name,
    anyMode: row.anyMode,
    delivery: row.delivery,
    riskPassesAtDestination: row.riskPassesAtDestination,
    loadingAtOrigin: row.loadingAtOrigin as Party,
    exportClearance: row.exportClearance as Party,
    mainCarriage: row.mainCarriage as Party,
    insuranceBy: row.insuranceBy as Party | null,
    insuranceCover: row.insuranceCover,
    unloadingAtDestination: row.unloadingAtDestination as Party,
    importClearance: row.importClearance as Party,
    importDuties: row.importDuties as Party,
  };
}

Install

fune build

With that line in your source, in a TypeScript project (language typescript in fune.project), fune build resolves it and nothing else, pins them in fune.lock, downloads only the TypeScript package of each, and builds the code above into your project’s .fune/build, one readable file per capability with a header linking back here. Or pin a range in fune.project and build in one step:

fune add logistics.incoterm-responsibility

The manifest, vectors and README with only the TypeScript implementation. Install it without the registry with fune add ./logistics.incoterm-responsibility-1.0.1-typescript.fune, or fetch it from a terminal with fune pull logistics.incoterm-responsibility@1.0.1:typescript.

The whole function, every language, is one file too: logistics.incoterm-responsibility-1.0.1.fune, 28,648 bytes, sha256 7c969bfc65419b68fd7060978248e8b5e566a203722cc52d1ed598d7ca14c5a8. It installs into a project of any language.

// fune: before logistics.incoterm-responsibility

// fune: after logistics.incoterm-responsibility

// fune: step logistics.incoterm-responsibility after <n|label>

More from the author

Loading at the seller's premises is the buyer's under EXW and the seller's under every other rule.

## What people get wrong

- **C rules move cost, not risk.** Under CPT, CIP, CFR and CIF the seller pays for the main carriage, but the goods travel at the buyer's risk from the moment they are handed to the first carrier or loaded on board. That is why the result has `riskPassesAtDestination` separately from `mainCarriage`. - **Insurance "none" means no obligation**, not "uninsured". Under the other nine rules neither party must insure; whoever bears the risk usually does. - **CIP and CIF differ in 2020.** CIP requires all-risks cover (Institute Cargo Clauses (A)); CIF still requires only the minimum, Clauses (C). - **DPU replaced DAT** in 2020 and is the only rule where the seller unloads. `DAT` with edition 2020 is an error, as is an edition with no data. - **Sea rules are for sea.** FAS, FOB, CFR and CIF are meant for goods loaded on a vessel, not for containers handed over at a terminal, where FCA, CPT and CIP fit better (ICC's own guidance).

Terminal handling and other charges at either end depend on the contract of carriage as well as the rule; under the C rules, unloading charges the seller paid under its contract of carriage are not recoverable from the buyer. This capability reports the rule's default split, not a contract's.

## Editions are data

A contract names its edition ("FOB Incoterms 2020"), and older editions stay in use for years, so the edition is an argument and not a date. Incoterms 2010 or a future edition would be new rows, not new code. The rule code must be the capitals as ICC writes it.

## Sources

- International Chamber of Commerce, Incoterms 2020 (ICC publication 723E); overview and 2020 changes, https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/ - UK Department for Business and Trade, "Choosing the right incoterms for your goods", https://www.great.gov.uk/advice/prepare-for-export-procedures-and-logistics/international-trade-contracts-and-incoterms/

## Notices

Incoterms® is a registered trademark of the International Chamber of Commerce. This capability is not endorsed by the ICC.

1.0.1 adds its attribution notices (NOTICE). The code and the tests are unchanged.

Files