Canary7 Analytics

Allocation by Warehousefully / partial / unallocated

Fully Allocated

Partial

Unallocated

Fully Allocated % by Warehouse

Order Intake

Order Detail

Shipment # ↕	Warehouse ↕	Status ↕	Allocation ↕	Sale Value ↕	Planned Dispatch ↕

Order Intake

Fulfillable Revenue % by WarehouseThe share of the revenue in open orders that can be shipped right now. Orders worth €0 (claims and marketing giveaways) are left out, so a warehouse with only those shows n/a.

Fulfillable Order Volume % by Warehouse

Picking Accuracy %How often pickers find the item where the system says it is. Higher is better; a low week usually means stock was missing when they went to pick, not the picker's fault. Weekly All-time Show values

weekly picking accuracy · higher is better

Picking accuracy per warehouse · by week

Warehouse ↕	Week ↕	Picking Scans ↕	Short-Picks ↕	Accuracy % ↕

Allocation Performance by Warehouse open shipment headers · soft allocation status breakdown

Warehouse	Total Orders	Fully Alloc	Partial	Unallocated	Fulfillable Order Volume %	Total Revenue	Fulfillable Revenue	Fulfillable Revenue %	Status

SKU Allocation Performance by Market order-line SKU level · live from shipment-detail (open orders)

Warehouse ↕	Child SKU ↕	Description ↕	Orders ↕	Total Units ↕	Allocated Units ↕	Pooled Units ↕	Alloc Rate % ↕	Lines Alloc % ↕

Accuracy % by Warehouseaccurate lines / total counted

Unit Variance by Warehouse

Accuracy % Trend Show values

Avg Days: Plan Created → Completed

CC Warehouse Summaryall plans incl. spot checks · line accuracy = accurate/measured lines · unit accuracy = (system − shortfall − overage)/system units

Warehouse ↕	Total Plans ↕	Plans w/ Counting ↕	Total Lines ↕	Accurate Lines ↕	Variance Lines ↕	Line Accuracy % ↕	Unit Accuracy % ↕	Shortfall Units ↕	Overage Units ↕	Unit Variance ↕	Cost Variance ↕

CC Plan Detailmulti-location counts only · single-location user-initiated counts summarised above

Plan Created ↕	Plan No ↕	Warehouse ↕	Status ↕	Operator ↕	Total Locations ↕	Count Lines ↕	Accurate Lines ↕	Variance Lines ↕	Line Acc % ↕	Unit Variance ↕	Unit Acc % ↕	Shortfall Units ↕	Overage Units ↕	Date Captured ↕	Date Completed ↕	Days to Complete ↕

User-Initiated Counts: Short-Pick Frequency (inferred) single-location recounts raised when an item isn't found at the pick face · frequency signal only, no quantities recorded · inferred from operational practice, not a WMS reason field Show values

Triggered checks per ISO week

Short-Pick Checks by Warehouseuser-initiated counts · current filters

Short-Pick Checks by Operatorwho raised them (users.name) · top 12

Most-Affected Locationsbins ranked by how many user-initiated counts they triggered, chronically unreliable pick faces · filter with the warehouse chips above

#	Location ↕	Warehouse ↕	Triggered Checks ↕	First ↕	Latest ↕	Operators ↕

Most Discrepant Itemssorted by absolute count variance · current snapshot

#	Item Code ↕	Warehouse ↕	Plan No ↕	Counted ↕	Expected ↕	Diff ↕	Abs Diff ↕	% of Total Variance ↕

Jobs by Type

Closed Jobs TrendNumber of warehouse jobs finished over time. Dates before we began collecting data (June 2026) are left out.

User Performance Summary

User × Type User only

Job Breakdown: Type × Warehouse × Assignee

Type ↕	Warehouse ↕	Assignee ↕	Total ↕	Open ↕	Closed ↕	Instructions ↕	Created At ↕

Assignee

👤

Select a user to view their performance

Long-Running OrdersOrders exceeding 1 hour of span, likely paused/interrupted, not continuous work. For review.

Reference ↕	Worker ↕	Warehouse ↕	Screen ↕	Scans ↕	Work Span ↕	First Scan ↕	Last Scan ↕

Work Time by User

Worker ↕	Orders Worked ↕	Total Scans ↕	Median Work Time ↕	Avg Work Time ↕

Per-Screen BreakdownPicking vs Packing (and other screens) per user · spans over 1h excluded from medians

Worker ↕	Screen ↕	Orders ↕	Scans ↕	Median ↕	Avg ↕

Stock Over TimeOne dot per day. The chart fills in as more daily snapshots are collected.

On-Hand Allocated Suspended Value € ⚠️

Show values

SKU Drill-Downbacktrack one SKU across snapshots + current breakdown

🔎

Pick a SKU to see its stock history and current breakdown

Inventory Detail

Item Code ↕	Description ↕	WH ↕	Batch ↕	Expiry ↕	On-Hand ↕	Allocated ↕	Suspended ↕	In-Transit ↕	Value € ⚠️ ↕

Low-Stock / At-Risk SKUson-hand at or below threshold · most critical first

On-Hand ≤ Hide zero on-hand Hide negative on-hand

Item Code ↕	Description ↕	WH ↕	On-Hand ↕	Allocated ↕	Suspended ↕

Orders Created vs Closed (daily) How many orders came in versus how many were shipped, each day. "Created" counts orders by the day they entered the system; "Closed" counts orders by the day they were dispatched (marked Closed). When the green line sits below the blue, the backlog is growing. Show values

Created Closed (dispatched)

Loads Closed per day Vehicle loads dispatched each day. One closed load carries many orders. Counted as the number of distinct loads among the orders dispatched that day, so it splits per warehouse (see the table below); the daily line is the total across sites. This runs a little under the raw load-closure log, which also counts empty or edited loads. distinct loads among dispatched orders · per-warehouse split in the table below Show values

Throughput by Warehouse Orders created and dispatched over the selected date range, per warehouse. "In progress" is a snapshot of orders started but not yet shipped right now — a current state, not a per-day figure, so it isn't split across the range.

Orders by Stage (per Warehouse)live open orders by leading status

Jobs (per Warehouse)live job states

Job Volume Trendclosed jobs per day (job_perf_daily), per warehouse

Order Volume Trendopen orders per day (alloc_daily), per warehouse

Shipping Volume per Warehouseopen-order demand by SKU · follows the global warehouse chips

#	SKU	Description	Total Units	Orders	Lines

Pending Put-Away → Allocation OpportunityIncoming stock waiting to be shelved, and how many open orders it could help fill once it is. An estimate, not a promise.

Warehouse ↕	Receipt # ↕	Container ↕	PO ↕	Item ↕	Description ↕	Qty Pending ↕	Target Loc ↕	Potential Alloc ↕

Orders That Would Become FulfillableOpen orders that can be shipped in full from stock on hand now, plus the extra ones that become shippable once today's incoming stock is shelved. Each order lists the containers its stock would come from. An estimate, not a promise. Include on-hold orders in simulation Count all stock incl. QC/suspended

Warehouse ↕	Order # ↕	Age (days) ↕	Fulfillable when ↕	Lines ↕	Containers (receipt #s) ↕	Sale Value ↕

Greedy Container Priority (revenue-first)The best order to shelve the containers already at the dock, so the most valuable orders get completed first. Each row shows the extra orders and revenue that container would free up. Kept separate per warehouse.

Warehouse ↕	Rank ↕	Container (receipt) ↕	Units ↕	Orders unlocked ↕	Revenue unlocked ↕	Cumulative orders ↕	Cumulative revenue ↕

Inbound ContainersThe best order to ship the containers still on their way, so the most valuable orders can be completed soonest. A container isn't counted for stock you'll already have once today's dock work is shelved. Shows containers already logged in the system.

Warehouse ↕	Rank ↕	Container ↕	ETA ↕	Supplier ↕	Units ↕	Orders unlocked ↕	Revenue unlocked ↕	Cumulative orders ↕	Cumulative revenue ↕

Partial Progress (still short after put-away)Orders that get closer once incoming stock is shelved but still can't ship in full — what it helps with, and what's still missing.

Warehouse ↕	Order # ↕	Age (days) ↕	Put-away helps ↕	Still short ↕

Decide to Fulfil (Electronics / Misc)Orders whose only missing items are Electronics or Misc. You can source those separately and still ship the order. A decision aid, not a promise.

Warehouse ↕	Order # ↕	Age (days) ↕	Missing Electronics/Misc items ↕	Sale Value ↕

On-Hold OrdersOrders currently on hold, shown per warehouse and always visible. "Would ship if released" means every item on the order is available now.

Warehouse ↕	Order # ↕	Hold Comment ↕	Reason Code ↕	Sale Value ↕	Would flip if released ↕

⚙️ Supabase not configured. Paste your anon public key into SUPABASE_ANON_KEY near the top of this file's script, and run enable_dashboard_read.sql in Supabase, to enable historical trends.

⚙️ Jobs 📦 Allocation & Fulfilment 🔄 Cycle Count 📈 SKU

Date Range

User Job Type

Jobs Completed per Daysum across selected user / type

Median Completion Time Trend

Average Completion Time Trend

Daily Detailjob_perf_daily

Date ↕	Worker ↕	Job Type ↕	WH ↕	Jobs Done ↕	Median ↕	Avg ↕	Stale ↕