Warehouse metrics
Open exceptions, timestampedfrom the moment they opened.
Compliance exceptions is the count of live rule breaches open right now — dangerous goods stored somewhere segregation doesn't allow, a rack over its rated weight, a blocked fire-safety clearance, a local policy broken — set against when each one arose, not when someone happened to notice it. WareBee checks your configured rules against the stock and layout you actually have, continuously, so the count reflects today rather than the last time someone walked the floor with a checklist.
See the dangerous goods compliance challenge
What it is
How many rules are broken right now, and since when.
On WareBee's digital twin, compliance exceptions is a count: how many of the rules you've configured — dangerous-goods segregation, racking weight limits, fire-safety clearances, or a local policy specific to your site — are broken right now, each one timestamped from the moment it opened rather than the moment someone found it. WareBee checks your rule set against the stock and layout you actually have on an ongoing basis, so the figure reflects today's exceptions, not whatever was true on the day of the last walk-round.
The count moves with how a warehouse actually runs under pressure, not with how carefully the rules were written. A putaway made against whatever space is free that shift, rather than the location the rule actually allows, opens an exception the moment the pallet lands. A rule set that lives with a single owner — safety, facilities, compliance — and gets checked on its own schedule can miss a location breaking two separate policies at once, because nobody cross-references the two. And an exception that only gets found by someone walking the floor and noticing it sits open, unmeasured, for however long that walk takes to happen.
An open exception count carries no reference point by itself — a number that would be alarming on a tightly packed single-level site can be unremarkable on a larger, more complex footprint carrying proportionally more locations to get right. WareBee checks order profile, SKU count and footprint before it reads your count at all, then compares it only against operations managing a genuinely similar scale of complexity, so what counts as high or low is decided by sites actually built like yours.
What moves this number
How an exception opens, and why it stays open.
Each one is measured on your digital twin from data you already generate, so an open exception traces back to a moment and a cause, not a guess about what the floor's been doing.
A putaway made against space, not the rule
A pallet lands wherever there's room that shift, not necessarily in the location the policy actually allows.
Under pressure to clear a dock, a putaway decision gets made against the space available rather than the rule that governs it — a hazardous case one bay over from where segregation allows, a heavier pallet waved onto a rack already near its limit. Nothing catches it at the moment it happens, so the exception sits open until something goes looking.
Rule sets checked separately, on separate schedules
Dangerous goods, racking weight and fire safety are watched by different people, on different timetables, if at all.
Each rule set tends to live with whoever owns it — safety, facilities, compliance — checked on its own schedule and rarely cross-referenced against the others. WareBee checks every rule set together against the same layout and the same stock, so a location breaking two rules at once shows up as one finding instead of waiting for two separate reviews.
Rules verified at audit, not between audits
Compliance gets checked on the day someone walks the floor — and reads as clean on exactly that day.
An audit is a snapshot: it records what was true on the day someone walked the floor with a checklist, not what's true an hour later once a pallet moves. WareBee checks the same rules continuously against the digital twin, so the exception count you can point to is today's, not the date stamped on the last visit.
Exceptions found by chance, not by system
A breach surfaces because someone happened to notice it, not because anything was watching for it.
Walking every aisle looking for what's out of place doesn't scale past a handful of locations, so most exceptions have always been found by chance, by an inspector, or by an incident. WareBee flags the drift the moment it happens, against the rules you've configured, so the count reflects what the system caught rather than what luck happened to surface.
Routed to whoever's accountable, the moment it opens.
An exception count on its own doesn't say who should act on it or how urgent it is. WareBee reads yours against a peer set matched on order profile, SKU count and footprint, then routes each open exception straight to whoever's accountable for that zone — shift lead, EHS or compliance owner — with the exact location and the rule it broke already attached.
Your team decides what to do about each one — WareBee isn't a compliance officer or a dangerous-goods safety adviser, and it doesn't replace either. What it gives that team is a continuously current list of open exceptions and a record of when the rule you set was checked and what it found, so their time goes on the judgement calls rather than on finding the problem in the first place.
- Open exception count read against a peer set matched on order profile, SKU count and footprint
- Every exception routed to the accountable owner with the location and rule attached
- A continuous record of what was checked and when — not a substitute for a compliance officer
Questions
Compliance exceptions, read the right way.
What exactly counts as a compliance exception?
It's a live count: how many of the rules you've configured — dangerous-goods segregation, racking weight limits, fire-safety clearances, or a local policy specific to your site — are broken right now. Each one is timestamped from the moment it opened, not the moment someone happened to notice it, so the figure reflects today's stock and layout rather than the state of things on the day of the last walk-round.
Does a zero exception count mean the warehouse is compliant?
No — be cautious of any reading that implies otherwise. WareBee is not a certification body and doesn't provide legal advice, and a low or even zero exception count only means no open breach was found against the rules you've configured and checked — it doesn't replace a compliance officer, a dangerous-goods safety adviser, or a formal inspection. What it gives the people who hold that responsibility is a continuously current view of where the exceptions are, so their time goes on judgement calls rather than on finding the problem first.
Why do exceptions open even when nobody's ignoring the rules?
Usually because the warehouse kept moving after the rule was set, not because anyone ignored it. A pallet lands wherever there's space during a busy shift rather than in the location the policy actually allows; a heavier load gets waved onto a rack already close to its limit because nobody was watching the running total. Each drift is small and ordinary on its own, and stays invisible until something checks for it — which is exactly what the continuous read is built to do.
Shouldn't a healthy exception count just be zero?
Because a fixed number — including zero — doesn't account for how much a site is actually managing. A large, complex footprint carries proportionally more locations to get right than a compact one, so the same open count means something different on each. WareBee checks order profile, SKU count and footprint first, then reads your count against operations managing a genuinely similar scale, so what counts as high, low or ordinary is decided by sites actually built like yours.
What data does a compliance exception count draw on?
WareBee starts from data you already generate — your warehouse layout, item and location data, and stock movements from your WMS or ERP, whether as a live feed, a scheduled export or a plain CSV upload. You add the rules that apply to your site on top of that; there's no separate compliance database to build and no bespoke integration required before the first exception count can run.
How do exceptions reach the people responsible for fixing them?
Each one routes straight to whoever's accountable for that zone — shift lead, EHS or compliance owner — with the exact location and the rule it broke already attached, rather than sitting in a report someone has to read and triage later. Because the check runs continuously, a record of when the rule was checked and what it found already exists, so whoever picks up the exception isn't starting from scratch.