Scan statistics

Enhanced plan

Every scan an operator makes on a Label Checker device is recorded. Scan statistics is the admin-side view of that activity for one session — a drill-down from days, to the runs inside a day, to the individual scan log — with a CSV or Excel export at every level.

Opening scan statistics

P&H Cloud Platform (Beta) → Label Checking → click the Scan activity icon (bar-chart) in a session row’s Actions column.

The three levels

Scan statistics is one page that drills down through three levels:

Day report — one row per day the session was used: Day · Runs · Scans · Matched · Unmatched · Open/Closed. Click a day to open it.
Day detail — that day’s totals (matched / unmatched; runs and scans each broken out standard vs. target) and a table of the runs inside the day, each with its operator. Click a run to open it.
Run detail — the run’s metric cards plus the scan log: one row per scan — Time · Outcome · SKU · Barcode · Product · Scanned. The log is paginated for long runs.

The day a scan belongs to is assigned by the device at scan time, so the grid matches exactly what the operator saw on the device. Looking for one specific item instead of browsing by day? See Item look-up.

The scanning day

A scanning day rolls over at your shop’s own local midnight — not a fixed universal time — so an evening shift’s scans land on the day your team actually worked, not the next one.

Where the timezone comes from. It is a setting you own, on the Scanning day boundary card in Settings → Cloud Platform → Label Checking. The first time you open that tab, Logistified fills it in from your Shopify store’s timezone; from then on you can change it with the searchable picker (or reset it to your Shopify value with Use Shopify’s). Every new session picks up whatever is stored. If nothing is stored yet, the card says so and scanning days roll at UTC midnight until you pick a zone.

Changing it later. Click Save and the new zone is stored and pushed onto every session that is already issued — no reissue needed. (Already saved and just want live devices to pick the stored zone up again? Use Re-apply to active sessions under the picker.) Each device adopts the change at its next day roll, so the day of the switch runs a little long or short just that once. Days already recorded keep the dates they were recorded under.

Runs, and standard vs. target

A run is a continuous stretch of scanning within a day — an operator can start a fresh run, and a run still open at the end of the day is finished automatically at day close.

Each run is in one of two modes:

Standard — straight label-checking against the expected list.
Target — counting toward a target quantity.

By default, target-mode scans also count toward the plain running total — on the device, and in the daily scan report email. Untick “Include target results in standard totals” when creating or editing a session to keep them separate instead: the device’s on-screen tally and the scan-report email then split standard and target into two totals rather than merging them.

Exporting

Every level offers a complete download — the whole day (all its runs) down to a single run — in CSV or Excel (.xlsx):

Level	Where	What you get
Day report	per-row Export menu	the whole selected day
Day detail	Download day menu (header) + per-run menu	the whole day, or one run
Run detail	Export run menu	that run

The export is always the full scan log for the chosen scope — it is not limited to the page you’re looking at. Each row carries the day, run, mode, operator, time, outcome, SKU, barcode, product, and scanned quantity.

When it says “not available yet”

Scan statistics reads the scan history back from the device platform. If the page shows “Scan statistics not available yet”, the platform side isn’t live for your shop yet — this is expected before the feature is fully rolled out, and the page degrades gracefully rather than erroring.