Library · Stock / inventory · How to run this
Fullstack exception queue bay is not QA hold cut
Open one Fullstack exception queue bay. Note when the exception entered. Note when ops cleared it. Keep exceptions next to that span. The difference is FS exception-queue hours — QA hold cuts and pick-tote rails never feed this bay.
Pair: Exception-queue lag on Stock. Hold twin: FS hold-release. Tote twin: FS tote-dwell.
Exception queue stamps
Enter hour — Hour Fullstack parked the order/line on the exception queue bay.
Clear hour — Hour ops cleared / released that exception on the same bay.
Exceptions — Fullstack exception rows inside that enter → clear window.
FS exception-queue hours = clear hour − enter hour. Fat FS exception-queue hours means staff the exception bay before you pace waves — blank chips stay blank.
Refuse these shortcuts
Refuse inventing FS exception-queue hours. Refuse dumping QA hold-release day CSVs or tote-dwell exports into enter/clear boxes. Refuse treating staging-dwell or pack-to-ship spans as exception-queue hours. Refuse blending buildings when one Fullstack exception queue bay owns the stuck pile.
See also: Stock, FS hold-release, FS tote-dwell, FS staging-dwell.
Procedure
- Type enter hour, clear hour, and exceptions.
- Read FS exception-queue hours.
- Staff the exception bay when FS exception-queue hours are material.
Failure modes
- Inventing FS exception-queue hours.
- Dumping QA hold-release or tote-dwell exports into enter/clear boxes.
- Treating staging-dwell or pack-to-ship spans as exception-queue hours.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- FS exception-queue hours
- Clear hour − Enter hour on one Fullstack exception queue bay.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Fullstack hold-to-release lag?
- Exception queue bay vs QA hold cut. [Hold-to-release lag](/manuals/fullstack-hold-to-release-lag) stays on QA hold/release days. Enter / clear hours for stuck WMS exceptions belong on this exception bay.
- Is this Fullstack tote-dwell lag?
- Exception queue wait vs pick-tote dwell. [Tote-dwell lag](/manuals/fullstack-tote-dwell-lag) aligns tote-empty against tote-fill. Here you only score clear hour − enter hour on exception rows.
- What FS exception-queue hours should I invent?
- None. Pull enter hour, clear hour, and exceptions from the same Fullstack exception queue bay.