Skip to content

Main content

Order Fill Line Versus Unit Gap Tool

Calculate order fill line versus unit gap from explicit caller-supplied inputs.

Loading tool…

Description

Return lineFill as the share of fully delivered lines and unitFill as total delivered divided by total ordered, then gap=lineFill-unitFill.

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.

Return lineFill as the share of fully delivered lines and unitFill as total delivered divided by total ordered, then gap=lineFill-unitFill.

When to use this tool

Use Order Fill Line Versus Unit Gap 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 orderedUnits, deliveredUnits. 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 lineFill, unitFill, gap. Use the output convention below.

Return lineFill as the share of fully delivered lines and unitFill as total delivered divided by total ordered, then gap=lineFill-unitFill. Require aligned nonempty positive orders and deliveries within each order.1

Input fieldMeaning and unitsAccepted input
orderedUnitsOrdered UnitsRequired. Array of safe integer; maximum items 256.
deliveredUnitsDelivered UnitsRequired. Array of safe integer; maximum items 256.
Output fieldInterpretationReturned shape
lineFillFraction of fully completed lines.Required. Finite number.
unitFillDelivered units divided by ordered units across all lines.Required. Finite number.
gapGapRequired. Finite number.
json
{
  "input": {
    "orderedUnits": [
      10,
      90
    ],
    "deliveredUnits": [
      10,
      45
    ]
  },
  "output": {
    "lineFill": 0.5,
    "unitFill": 0.55,
    "gap": -0.050000000000000044
  }
}

Limitations and assumptions

  • The line metric weights each row equally while the unit metric weights quantities. Duplicated lines, compatible unit definitions, service targets, and actual fulfillment are not verified.
  • 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/order-fill-line-versus-unit-gap — tool.io

Similar or alternative tools