Skip to main content
All CollectionsFAQ
Insights - Users calculations
Insights - Users calculations

How the data is calculated on Insights page Users

Updated over a week ago

The Insights > Users tab offers analytics for shipped orders, items, orders per hour, items per hour, and picking accuracy. The filters control which orders are included in the calculation. Users can also view their own shipping insights from within their profiles.

User attribution

Performance values are credited to the user who changes the order's status to “shipped”. Orders which transition to the "shipped" status without a user's touch are excluded.

Orders per hour

The average time it takes to process an order from the "opened" status to the "shipped" status, projected over an hour.

Example:

  • If a single order takes 30 minutes to go from "opened" to "shipped", your average orders / hr calculation would be "2".

  • If a single order takes 1 minute to go from "opened" to "shipped", your average orders / hr calculation would be "60".

Items per hour

The average number of order items picked within the time taken to process an order from the "opened" status to the "shipped" status, projected over an hour.

Example

  • If a single order for 1 item takes 30 minutes to go from "opened" to "shipped", your average items / hr calculation would be "2".

  • If a single order takes 1 minute to go from "opened" to "shipped", your average items / hr calculation would be "60".

Hourly, daily, weekly, monthly filters

Setting hourly, daily, weekly or monthly filters does not change the calculation, but rather how the data points are presented — whether they are aggregated by day, week, month, etc.

Accuracy

Picking errors can be measured by the "accuracy" level. Scans for invalid or incorrect barcodes are used to calculate the accuracy of picking.

Example:

  • If 1/100 scans are incorrect, accuracy will be shown as 99%.

Orders API

Raw "scans" and "misscans" are available through the API and contain item and timestamp data for specific metrics you may need. Have your developers reach out for API support.

Did this answer your question?