Skip to content

Main content

Delivery Promise Delay Value

Compare an actual delivery timestamp with an explicit promised timestamp using a strict late boundary.

Loading tool…

Description

Measure a supplied delivery delay relative to a promised timestamp.

Consumer records distinguish events, choices, prices, quantities and supplied survey scales. A unit-price comparison requires comparable goods and quantity units, while a reversed score retains the original scale bounds. An observed time gap or selected option does not establish motivation, causation, consent or the fairness of a commercial practice.

Measure a supplied delivery delay relative to a promised timestamp.

When to use this tool

Use Delivery Promise Delay Value when you already have promisedTimestampSeconds, deliveredTimestampSeconds and need to measure a supplied delivery delay relative to a promised timestamp.

How to use the tool and how it works

  1. Enter promisedTimestampSeconds, deliveredTimestampSeconds. 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 delaySeconds, late. Inspect late before interpreting the associated values.

Return delivered-promised seconds and late=delivered>promised.1

Input fieldMeaning and unitsAccepted input
promisedTimestampSecondsPromised Timestamp SecondsRequired. Finite number.
deliveredTimestampSecondsDelivered Timestamp SecondsRequired. Finite number.
Output fieldInterpretationReturned shape
delaySecondsDelay SecondsRequired. Finite number.
lateTrue strictly after the promised timestamp; equality is not late.Required. Boolean.
json
{
  "input": {
    "promisedTimestampSeconds": 1000,
    "deliveredTimestampSeconds": 1120
  },
  "output": {
    "delaySeconds": 120,
    "late": true
  }
}

Limitations and assumptions

  • Equality is not late and early deliveries give negative delays. Matching clocks are assumed; no transaction, legal promise or service quality is verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • 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. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the original transaction, interface, survey and event records for a behavioral conclusion. Use the complete study design and applicable commercial terms when interpreting comparisons; local flags and ratios do not estimate demand or verify an actual customer experience.

References

  1. Calculation and input contract: consumer-behavior/delivery-promise-delay-value — tool.io

Similar or alternative tools