Exception to resolution
Assign a floor problem to its owner and follow the corrective work through resolution.
6 stages · 1 approval
Roles and responsibilities
-
Step 1Raise
Receipt NumberReceipt TypeScheduled Arrival AtActual Arrival AtProduction
-
Step 2Route
Adjustment NumberLocationItemLot Number
-
Step 3Triage
Exception NumberException TypeSeverityLocationDamage
-
Step 4Fix
Adjustment NumberLocationItemLot Number
-
Step 5Resolve
Task NumberOrderFrom License PlateCarton
-
Step 6Learn
Exception NumberException TypeSeverityLocationDamage
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Raise
Warehouse Operator, Packer or Receiving Lead records the problem from the task or receipt in progress. Type, location, license plate, exact item, affected quantity, severity and useful photos establish what was found. The report does not itself change an order quantity or authorize a stock adjustment.
Route
Shift Supervisor monitors the routed queue while configured rules assign the issue by type. A short pick releases the unusable claim before seeking replacement stock; damage holds affected goods; wrong-item and not-found reports can request moves or protected counts. Overages go to dock review, blocked bins to building review and equipment failures to floor supervision.
Approval required
Triage
Shift Supervisor owns floor issues, Inventory Controller owns stock discrepancies, Receiving Lead owns dock discrepancies and Warehouse Manager owns building restrictions or escalated decisions. The applicable owner reviews the evidence and takes the issue into triage. Critical severity escalates to Warehouse Manager under the routing policy.
Fix
Inventory Controller coordinates stock corrections, or Shift Supervisor coordinates operational task recovery. The fix uses a released move, protected count, authorized adjustment or recorded disposition. A held task resumes only when its restriction is resolved by the permitted role. Above-threshold adjustments still require Warehouse Manager approval, regardless of how urgently the exception was raised.
Resolve
Shift Supervisor, Inventory Controller, Receiving Lead or Warehouse Manager closes the issue they own with the resolution and linked evidence. Recount, move, adjustment, return disposition, quality escalation or no-action findings remain distinguishable. Related task and order outcomes reflect the actual work; closing an exception cannot silently reduce requested demand or erase a receipt discrepancy.
Learn
Inventory Controller reviews recurring stock issues and their count results. Exception history can inform future count selection or a proposed reslotting move. Pick Accuracy and the task records help investigate repeated problems, while Warehouse Manager reviews changes that require operating authority.
Approvals and exception handling
1 approval required in this process
-
Triage
Shift Supervisor or Inventory Controller or Receiving Lead or Warehouse Manager signs · fix waits
Exceptions, LicensePlates, Inventory - A replacement pick must not retain both the unusable allocation and a new claim for the same shortfall.
- Damage and quality restrictions prevent further allocationMoving a plate alone cannot clear its hold.
- A count locks the affected location; stale locks or inventory versions require renewed reconciliation before posting.
- Every adjustment retains its source and approvalException ownership grants no additional adjustment authority.
- Stock found in another bin should be investigated as a movement problem before an unexplained write-off is proposed.
- Local quantity eventsOutward integration deliveries have separate identities, so retrying notification does not repeat a correction.
When the process needs attention
-
shortage
Route
A short pick releases the unusable claim before seeking replacement stock; damage holds affected goods; wrong-item and not-found reports can request moves or protected counts.
-
exception
Fix
Above-threshold adjustments still require Warehouse Manager approval, regardless of how urgently the exception was raised.
-
late
Resolve
Related task and order outcomes reflect the actual work; closing an exception cannot silently reduce requested demand or erase a receipt discrepancy.
-
exception
Learn
Exception history can inform future count selection or a proposed reslotting move.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Raise | ExceptionsPickTasksPackTasksReceiptsInventory | Observed issue and affected work linked |
| 2 Route | ExceptionsPickTasksInventoryReservationsCycleCountsMoveTasksAdjustments | Controlled follow-up work proposed |
| 3 Triage | ExceptionsLicensePlatesInventory | Applicable owner reviews evidence and restrictions |
| 4 Fix | CountResultsLocationLocksMoveTasksAdjustmentsInventoryStockEventsStockMovements | Authorized correction or task recovery recorded |
| 5 Resolve | ExceptionsPickTasksPackTasksOrderLinesReceiptLines | Resolution and related task outcomes retained |
| 6 Learn | ExceptionsCycleCountsCountResultsMoveTasks | Repeated issues inform count or slotting review |
Process reports
All reportsPick Accuracy
Unique valid PickConfirmations outcomes and net confirmed quantities by operator, Zone and Wave, with linked downstream Exceptions and retry/reversal exclusions. Show the actual count/quantity denominator and customer-impact evidence rather than an unexplained combined score.
Expiring Lots
Exact Inventory identities grouped by expiry date and remaining life at planned/actual shipping date, with lot/serial, plate, physical quantity, reservation stage and hold status. Show applicable Items.MinShelfLifeDays and order lot conditions; 30/60/90-day buckets are reporting ranges, not release authority.
Cycle Count Accuracy
First-count results within both effective quantity and percent tolerance divided by eligible first-count positions, with discovered stock, serialized discrepancies, stale snapshots and no-data cases flagged separately. Show recount rate and signed/absolute variance by like item/BaseUOM; do not sum incompatible units as one quantity.
Run by an agent
Agent support
Human decisions remain with the authorized people. An assistant cannot release a wave, close a receipt or manifest, approve a stock correction, invent delegation or turn an uncertain carrier response into a confirmed shipment. It can prepare evidence and proposals. Every permitted write must retain its identity, scope and source context.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› exception to resolution · raise on Exceptions, PickTasks, PackTasks, Receipts, Inventory
✓ Warehouse Operator, Packer or Receiving Lead records the problem from the task or receipt in progress.
› exception to resolution · route on Exceptions, PickTasks, InventoryReservations, CycleCounts, MoveTasks, Adjustments
✓ Shift Supervisor monitors the routed queue while configured rules assign the issue by type.
› exception to resolution · triage on Exceptions, LicensePlates, Inventory
⏸ approval · waiting for the shift supervisor or inventory controller or receiving lead or warehouse manager
# 3 more stages after approval: fix, resolve, learn
Other processes
4 moreDock to stock
Reconcile each delivery and move confirmed stock from the receiving dock into storage.
6 stages · 1 approval
Order to ship
Take an accepted order through reservation, wave release, picking and packing to carrier handover.
6 stages · 2 approvals
End of day manifest close
Match the staged load to carrier documents, close the manifest and confirm handover.
6 stages · 1 approval
Cycle count to adjustment
Turn a protected physical count into an evidenced, authorized stock correction.
6 stages · 2 approvals