Skip to content

Main content

Product Return Inspection Lag

Calculate signed calendar-day lag between supplied product return receipt and inspection dates.

Loading tool…

Description

Measure a supplied return-inspection date's signed gap from receipt.

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 return-inspection date's signed gap from receipt.

When to use this tool

Use Product Return Inspection Lag when you already have returnReceivedDate, inspectionDate and need to measure a supplied return-inspection date's signed gap from receipt.

How to use the tool and how it works

  1. Enter returnReceivedDate, inspectionDate. 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 signedCalendarDays. Use the output convention below.

Parse real UTC dates; return inspectionDate-returnReceivedDate in days.1

Input fieldMeaning and unitsAccepted input
returnReceivedDateReturn Received DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
inspectionDateInspection DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
signedCalendarDaysSigned Calendar DaysRequired. Safe integer.
json
{
  "input": {
    "returnReceivedDate": "2026-10-28",
    "inspectionDate": "2026-11-01"
  },
  "output": {
    "signedCalendarDays": 4
  }
}

Limitations and assumptions

  • Negative gaps are retained. No actual receipt, inspection, refund deadline, entitlement or completed return 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.

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/product-return-inspection-lag — tool.io

Similar or alternative tools