The Hospital Workflow: Exception Handling No Other WMS Offers

The Challenge

The company was experiencing a roughly 5% order error rate. Not because of careless warehouse staff, but because the products themselves resist accurate counting. The question wasn’t how to train people better — it was how to build a system that could handle the inevitable exceptions without grinding the entire warehouse to a halt.

The operational complexity went deeper. The warehouse needed structured workflows for what happens when an item isn’t where the system says it should be. When a picker arrives at a bin location and the product is missing, damaged, or the wrong quantity, what happens next? In most warehouses, the picker makes a judgment call. They might skip the item, substitute something, or put the entire order aside and move on. Every one of those decisions introduces a new error.

The Hospital Workflow

The answer was the Hospital Workflow — a structured exception handling system that SkuNexus built specifically for this operation. The name comes from the medical triage concept: when something goes wrong during a pick, it gets routed to a “hospital” station where a manager resolves it with full context, while the rest of the warehouse keeps moving.

The Hospital Lifecycle

When a picker encounters a problem — item not found, wrong quantity, damaged product — they flag it on their mobile device and continue the rest of their wave. They don’t stop. They don’t make a decision about what to do. They flag and move on.

Completed totes go to the packing station as normal. Incomplete totes — the ones with flagged items — go to the hospital station. A manager loads the hospital queue and sees each exception with full context: the order number, the expected product and location, what the picker reported, and the customer’s order details.

The manager investigates. Was the item in the wrong location? They adjust the inventory and correct the bin assignment. Is the item damaged? They write it off and adjust stock. Is the item genuinely out of stock? They return it to the order decision engine, which re-routes the fulfillment — to a different warehouse location, to a dropship vendor, or to a backorder queue.

Once resolved, the item either goes back into fulfillment or the order is modified accordingly. The customer service team is notified if the order changes. If the modification affects a Shopify order, the system handles the cascade — line item changes, refund calculations, and customer communication triggers.

Tiered Replenishment

The hospital workflow exposed a related need: preventing exceptions before they happen. The warehouse now runs a three-tier replenishment system. Tier 1 (urgent) triggers when an order is waiting and the pick location is empty — pull from overstock immediately. Tier 2 triggers when stock drops below minimum — replenish before the next wave. Tier 3 fills pick locations back to maximum during downtime. The result: fewer hospital events because pick locations stay stocked.

Tote-Based Wave Picking

The warehouse uses tote-based wave picking where each tote on a cart maps to one or more orders. Pickers follow system-directed routes, scanning at every step. At the end of a wave, the cart goes to the pack station and each tote contains a verified, complete order — or a flagged exception routed to hospital.

The Results

The hospital workflow is now a standard SkuNexus capability, available to every client. But it was born here, in a warehouse where the products themselves create counting challenges that can’t be solved by better training or more careful picking.

The error rate that prompted the project has decreased as the system catches and routes exceptions before they reach the customer. The warehouse no longer stops when something is wrong. Pickers pick. Managers manage exceptions. Customer service gets notified when orders change. And the decision engine handles the re-routing when an item genuinely can’t be fulfilled from the original source.

For any operation dealing with high SKU counts, counting-sensitive products, or fulfillment complexity that generates inevitable exceptions, the hospital workflow is the feature that no other WMS offers. It wasn’t built in a product lab. It was built in a warehouse, with a client who needed it, to solve a problem that exists in every warehouse but nobody else has addressed.