THE RESULT
What the data shows
The largest computed metric is 384 for (50.0, inf]; the smallest is 12 for (0.0, 1.0]. Metric: median_units (Units per invoice).
Distinct codes measure variety, not package count; bulk buyers can dominate units.

| item band | orders | median units | median value gbp |
|---|---|---|---|
| (0.0, 1.0] | 1,641 | 12 | 45 |
| (1.0, 5.0] | 2,867 | 56 | 122.4 |
| (10.0, 25.0] | 6,660 | 172 | 309.4 |
| (25.0, 50.0] | 3,711 | 255 | 453.1 |
| (5.0, 10.0] | 2,979 | 98 | 189.2 |
| (50.0, inf] | 2,102 | 384 | 836.4 |
THE METHOD
From source to answer
Aggregate invoice lines before calculating order-size bands.
The Python source exposes this study’s transformations. The complete project download includes shared preparation and evaluation routines.
THE NEXT DECISION
What follows from the finding
Compare handling effort across order types once packing-time and fulfillment-cost records are available.
Where the conclusion stops
Historical invoice lines; credits are not reliably matched to original sales. Gross purchases are not profit. Unidentified customers cannot support customer-level conclusions. Exact repeated lines remain unless the study explicitly compares removal.
Related studies may reuse observations or holdouts. These are historical analyses; associations and backtests do not demonstrate commercial impact. Further model tuning needs new, untouched evaluation data.