320 pick tasks, 270 of them open, with the delay in minutes printed on the row. 120 bins mapped by zone with a waste score on each. 88 tasks in the path-delay queue carrying 450 minutes between them — and every alert says which aisle, which SKU, and why.
PK-10482 is 6.4 minutes late because an A-class controller sits in the H reserve and the path zigzags. The alert says that instead of drawing a red line.
warehouse.cedxsystems.com — live build
Runs on demo data. Northline DC East is the software's demo distribution centre, day shift.
Task, SKU, item, quantity, bin, wave, status and delay in minutes. PK-10206 leads the board at 9.2 minutes in progress; the exception chip counts the 54 that need a touch. Waves W-441 and W-442 carry the congestion.
Delay minutes on every open row
Wave, bin and quantity per task
39 lines/hr against a picker standard of 45
warehouse — screen-3
120 bins, each with a velocity and a waste score
Golden 19, Forward 38, Reserve 30, Cold 15, Dock 2, Pack 16 — the zone chips count the floor. R-02-04 holds an A-velocity controller at 17% utilisation with a waste score of 100, which is exactly the golden-underfill alert on the overview.
Zone chips with bin counts
Velocity A–C next to utilisation %
92 bins flagged with waste ≥ 40
warehouse — screen-2
180 putaways, with strategy and age
Directed, Bulk, Velocity match and Closest empty — the strategy is on the row, next to the dock lane it came from and its age in minutes. PA-2078 has been waiting 175 minutes in Exception; 39 putaways are stale at an hour or more.
Strategy on every row — four kinds in view
Age in minutes, sorted worst-first
139 open — the dock backlog, counted
warehouse — screen-4
Product tour
Four screens, captured from the running build.
Not a mockup and not a concept deck. This is what opens at /app/warehouse.
warehouse.cedxsystems.com
01 — Overview
The floor brief, aisle by aisle
Open picks 270, lines/hr 39 against 45, path delay 88 tasks at 450 minutes, 92 high-waste bins, putaways 139, accuracy 99.2% — and a floor-health ring at 67 because of them. Alerts name the aisle: three concurrent pickers on W-441 add 4.2 median minutes in aisle B.
Floor health 67, broken into four inputs
Highest open delay: PK-10206 at 9.2 minutes
Golden underfill flagged while A-movers sit in reserve
02 — Picks
The queue, with the delay on the row
320 tasks with the two filters that matter — 54 exceptions needing a touch, 88 rows delayed two minutes or more. Statuses run Open, Assigned, In progress, Done, Exception, Held.
88 tasks delayed ≥ 2 minutes
Wave on every row — W-441 through W-442 in view
CSV export of the filtered queue
03 — Locations
The map the delay comes from
120 bins with zone, primary SKU, velocity, utilisation, quantity and waste. A cold-zone A-mover 70 units from golden is a 5.1-minute pick delay — the location table is where that alert is born.
Velocity A, B or C per bin
Waste score ≥ 40 on 92 of 120 bins
Zone counts on the chips: Golden 19 to Pack 16
04 — Putaways
The inbound half, aged in minutes
180 putaways with quantity, source dock, target bin, strategy, status and age. The closest-empty strategy dropped an IR sensor into the wrong velocity bin — the exception aged 120 minutes before anyone touched it.
39 putaways aged an hour or more
Dock lanes named in the From column
Directed, Bulk, Velocity match, Closest empty
Who runs it
Three roles keep the floor moving.
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Picker
Works the queue top-down: 270 open tasks, 39 lines an hour against a standard of 45, and the delay column decides what is next.
open picks · 270
Pack bench
Done picks land at the 16 pack bins. The 54 exceptions get touched here before the wave closes, not after the truck leaves.
exceptions · 54
Shipping and receiving desk
Owns the dock both ways: 139 open putaways inbound, 39 of them aged an hour or more, with the dock lane named on every row.
putaway backlog · 139
The shape of it
What the demo DC actually looks like.
Every figure below is legible in the captures above. Nothing here is a projection of your floor — it is the state of the demo data.
320pick tasks270 open · 54 exceptions
99.2%pick accuracythe 54 exceptions behind it
450mtotal path delay88 tasks · median 2.3m
120mapped bins27% avg util · 92 high waste
Highest open delay, in minutesin-flight tasks — from the overview table
PK-10206 — R3 mount, in progress9.2m
PK-10048 — USB-C industrial 5m, exception8.1m
PK-10297 — wall mount large, exception7.8m
PK-10225 — industrial module, in progress6.9m
PK-10108 — edge controller 4400, in progress6.6m
Picks done50 done of 320 tasks
Done · 50
Still on the floor · 270 — including 54 exceptions
Floor health67 on path — the overview ring
67
On path — floor health 67
Median delay 2.3m · 450m across the queue
How it runs
A pick's life, in the order it actually happens.
01
Wave
Tasks group into waves — W-441 and W-442 in view — with bins and quantities attached.
02
Pick
The floor works at 39 lines an hour against a 45 standard, and delay accumulates per task in minutes.
03
Exception
54 exceptions need a touch; congestion on aisle B adds 4.2 median minutes when three pickers collide on one wave.
04
Slot
Slotting waste scores the bins — A-movers sitting in reserve while golden bins run under 20% utilisation is the re-slot list.
One record
The bin is the same record the rest of the estate reads.
An A-velocity SKU keeps its code from order book to bin to truck. CTL-4400 is a BOM line, a held work order, a pick task and a lane on the same demo estate.
Finding this out on the third call is worse for you than reading it here, and worse for us.
Warehouse is not generally available. What opens today is the live build on demo data — Northline DC East is the software's demo distribution centre, not a customer.
We have no named customers to show you, so this page shows none.
The 45 lines/hr picker standard is demo configuration. Your standard is yours; the screen shows where it is set because the demo data says so, not because we are quoting a benchmark.
The waste score flags bins; it does not re-slot them. Golden underfill is a list for a person, and this page does not claim otherwise.
The 99.2% accuracy figure is the demo floor's, 54 exceptions and all. It is not an industry average and not a promise.
No audit or compliance certification has been issued. What we can evidence about hosting, encryption and access is on the security page.
Yes. Every screenshot is a capture of the running build, and you can open the same build at /app/warehouse. It runs on demo data — Northline DC East.
What is path delay, exactly?
The minutes a pick task loses to where its bin sits. 88 tasks in the demo carry 450 minutes of it; the alerts name the cause — an A-class SKU staged in reserve, three pickers converging on one aisle — so the fix is a slotting decision, not a mystery.
What does the waste score measure?
Bins scoring 40 or more are flagged: A-velocity items sitting in cold bins, golden bins running under 20% utilisation. 92 of the 120 demo bins qualify, which is why the overview leads with it.
Is 99.2% accuracy good?
It is the demo floor's number, with the 54 exceptions counted next to it. We print the exceptions beside the rate because one without the other is marketing.
Does the putaway screen choose the strategy?
The row shows the strategy — Directed, Bulk, Velocity match, Closest empty — and its outcome, including the 120-minute exception when closest-empty landed an A-mover in the wrong velocity bin. What it does not do on this page is promise the strategy is right.
Is Warehouse audited or certified?
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is on the security page.
The floor is running. Go and look at its queue.
Live build, demo data, no card. Then check how many minutes your busiest aisle is quietly carrying.