Skip to content

Scan reports

Enhanced plan

A scan report is a once-a-day email summarising a label-checking session’s scans, with a CSV attached. Set one up per session and pick who receives it.

  • Where to configure
  • Setting up a schedule
  • What the email contains
  • Sending a test
  • Things to know
  • See also

Settings → Cloud Platform → Scan Reports tab. Schedules are per session — each label-checking session has its own.

  1. Session — pick the label-checking session to report on.
  2. Send time (UTC) — the time of day the report is emailed, in UTC (default 08:00). The picker is always UTC, so allow for your local offset.
  3. Recipients — tick who should receive it. The list comes from Reports → Recipients, so add recipients there first if the list is empty.
  4. Click Enable daily report (or Update schedule if one already exists). To turn it off, click Disable.

You need at least one recipient selected before the schedule can be enabled.

  • Subject: Label-checking scan report — YYYY-MM-DD
  • Body: a short cover note naming the session and date.
  • Attachment: a CSV of that day’s scans aggregated per SKU — the SKU, barcode, product, scan mode (standard/target), and counts.

The scheduled email always covers the most recently completed day, not the day in progress. Days are bucketed by the device’s recorded scan time, so a scan made just before midnight counts on the day it happened even if it synced after midnight.

Send test now emails the report immediately to the selected recipients, using the current day’s scans (including ones still coming in). It doesn’t change the schedule or the real daily send — it’s just a preview.

  • Needs recipients. Configure them under Reports → Recipients first.
  • Needs scan data. If the session has no completed day yet, the scheduled send is skipped (no empty email) and a test reports that there’s nothing to send.
  • Revoked sessions stop automatically. If you revoke a session, its schedule stops — no orphan emails.
  • One email per day. A given day is only sent once, even if the scheduler runs more than once.