Definition
Little's Law relates long-run averages within the same system boundary: average work in progress equals throughput rate multiplied by average time in the system. For a stable return-inspection process, it connects the number of units awaiting or undergoing inspection with completed units per day and average receipt-to-inspection-completion time.
Why It Matters
- A merchant may track return counts and completion times in separate systems, making the operational picture difficult to reconcile.
- Return intelligence needs a defined boundary: carrier transit, warehouse inspection, and refund settlement are different processes.
- A Commerce Intelligence OS can organize these measurements so teams investigate the stage actually responsible for a backlog.
How It Works
- Choose entry and exit events and a consistent item unit. For inspection, use warehouse receipt and completed inspection; count rework consistently.
- Measure time-weighted average work in progress, throughput, and flow time over an appropriate period. Check whether arrivals and departures support a reasonably stable interpretation.
- Compare the measured averages using common time units. Investigate boundary mismatches, missing receipts, and unresolved items when they disagree.
- Inspect queue age and stages before assigning a recovery action. An average does not reveal the oldest cases, and a growing backlog needs a separate arrival-versus-capacity analysis.
Ecommerce Example
Context: Illustrative example: an inspection process averages 120 return units in progress and completes 40 units per day under stable conditions.
Recommended move: The implied average flow time is 120 divided by 40, or three days. Compare that with receipt-to-completion records using the same boundary.
Why it matters: This does not promise every item a three-day turnaround or establish how quickly a temporary backlog can be cleared. The numbers are hypothetical.
iKawn Framework
Bound
The iKawn framework distinguishes receipt, inspection, disposition, and refund events.
Measure
Keep queue inventory, throughput, and elapsed time at a consistent unit.
Reconcile
Investigate disagreement before publishing a process-performance claim.
Prioritize
Combine average flow measures with case age to guide operational review.
Concise Summary
Little's Law is a consistency relationship between process averages. Use aligned boundaries and stable-flow evidence, then inspect individual delays separately.