Skip to content

Main content

Incoterm Cost Component Caller Allocation Tool

Allocate supplied cost components using explicit payer flags; no Incoterms rule is selected or interpreted.

Loading tool…

Description

Allocate supplied cost components using explicit payer flags; no Incoterms rule is selected or interpreted.

A logistics record separates ordered, reserved, dispatched, received, lost, and available quantities. It can also distinguish volume, mass, packaging, and cost bases. A balance or ratio checks supplied records and assumptions without verifying physical inventory, a contract, or safe loading.

Allocate supplied cost components using explicit payer flags; no Incoterms rule is selected or interpreted.

When to use this tool

Use Incoterm Cost Component Caller Allocation when you need the particular supplied count, loading-budget, timing, or cost term in a logistics record.

How to use the tool and how it works

  1. Enter amounts, buyerPays. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read buyerTotal, sellerTotal. Use the output convention below.

Partition aligned nonnegative amounts into buyerTotal and sellerTotal using buyerPays flags.1

Input fieldMeaning and unitsAccepted input
amountsAmountsRequired. Array of finite number; maximum items 256.
buyerPaysSupplied cost-allocation flags; no Incoterms rules are looked up.Required. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
buyerTotalBuyer TotalRequired. Finite number.
sellerTotalSeller TotalRequired. Finite number.
json
{
  "input": {
    "amounts": [
      100,
      20,
      30
    ],
    "buyerPays": [
      true,
      false,
      true
    ]
  },
  "output": {
    "buyerTotal": 130,
    "sellerTotal": 20
  }
}

Limitations and assumptions

  • All amounts need one currency and cost boundary. The flags are caller allocations, not an Incoterms lookup, contract interpretation, customs decision, or determination of risk transfer.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.

Alternative or Complementary methods

Check the original stock, shipment, measurement, and contract records before acting on a balance. A full packing, routing, procurement, or load assessment may require more than the returned term.

References

  1. Calculation and input contract: supply-chain/incoterm-cost-component-caller-allocation — tool.io

Similar or alternative tools