Most process documentation describes the happy path. This is the other half — a working reference for what actually goes wrong on a fulfillment floor, who owns it, how the line keeps moving anyway, and how it gets closed out.
Why this exists
The happy path through a fulfillment center is short and gets all the attention: receive, stow, pick, pack, ship. The exceptions are where the actual operating discipline lives — a mismatched carton count, a phantom-inventory bin, a mis-sort, a wave that spikes past capacity near cutoff. Every one of those has to be handled without stopping the line, and the pattern for handling it repeats more than it first appears to.
I built this as a drill reference: something to walk a new supervisor through, or to check your own design against when standing up a new node. It covers the four pillars of forward and reverse flow — Inbound, Storage, Outbound, Returns — broken into 24 sub-processes, each with its happy path and four categories of exception.
How to read it
Every sub-process follows the same structure: pillar → sub-process → happy flow → exception, and every exception is filed into one of four buckets:
- Material — the thing itself is wrong: damage, wrong item, a packaging failure.
- Data — record and reality have diverged: a quantity mismatch, an unknown SKU, a sync lag.
- Execution — people or SOP failed: a mis-stow, a mis-pick, a skipped check.
- Flow — volume outran capacity: bunching, overflow, a cutoff risk, an asset down.
Each exception card carries a root cause, an owner, the operator buffer — the specific move that keeps the line running instead of stopping it — and the resolution path. Toggle Drill mode to blur the answers and test yourself before revealing them; useful for onboarding, less useful if you're just trying to look something up. The scope is deliberately narrow: standard, non-large-format parcels only — cold-chain/fresh and oversized/bulky flows run different playbooks (see cold-chain monitoring for that adjacent case).