<aside> 👋

The Exceptions module gives warehouse managers and associates a single place to triage, investigate, and resolve inventory issues raised across receiving, put-away, picking, replenishments, cycle counts, work orders, and requisitions — keeping inventory accurate and audit trails complete from the first flag through final closure.

</aside>

Page Overview

• Access this page from: Main Menu > Exceptions.
• The exceptions workflow is broken into a multi-step process designed for desktop, with mobile-friendly review:
  1. Exception Queue/Dashboard: Filter, sort, and assign open exceptions across all sources.
  2. Detail View & Editing: Open an exception drawer to see source context, item, location, quantities, and notes.
  3. Resolution Selection: Pick the right resolution type (Accept, RTV, Disposal, Quarantine, or Transfer).
  4. Resolution Workflow: Step through the resolution-specific form to capture reason, method, packages, or transfer destination.
  5. Approval & Closure: Request manager approval where required, then resolve and close the exception.

Exception Steps

Detailed steps

1️⃣ Exception Queue & Dashboard

The dashboard provides a real-time table of every exception raised in the active warehouse, defaulted to the open work that needs attention.

• Default View: On load, the queue is filtered to In-Progress statuses — Open, In Progress, On Hold, and Escalated — so closed and resolved items are out of the way until you need them.
• Source Visibility: Each row shows the source that raised the exception: Receipt, Put Away, Cycle Count, Replenishment, Work Order, or Requisition. Tap the source to jump back to the originating record.
• Type & Cause: The Type chip shows the exception category (e.g. quantity mismatch, damaged, slot conflict). A Cause column captures the underlying reason once a resolver assigns it.
• Item & Location: Each exception is linked to the affected Item and Slot/Location so you can spot zone hot-spots at a glance.
• Quantity Affected: The Qty Affected column shows how many units the exception covers. This drives downstream resolution (e.g. how many units to dispose or transfer).
• Age: Exceptions are sorted by age (oldest first) by default. The age column highlights items that have been waiting too long for triage.
• Assignment: Use the inline Assigned To picker on each row to assign an exception to a user without opening the drawer.

2️⃣ Filtering, Sorting & Searching

The table supports column-level filtering so managers can slice the queue down to the work that matters in the moment.

• Type Filter: Multi-select across exception types. At least one type must remain selected — clearing it forces "all".
• Item Filter: Search and select specific items when investigating a SKU.
• Source Filter: Narrow to one or more source modules (e.g. only Receiving exceptions).
• Location Filter: Filter to specific slots or zones.
• Time Range Filter: Default range is Past 60 Days. Quick options include This Week, This Month, Past 60 Days, or a custom date range.
• Status Filter: Defaults to in-progress statuses; toggle in Resolved or Closed when reviewing historical work.
• Assigned To Filter: Multi-select users to view a specific resolver's queue.

3️⃣ Detail View & Editing

Selecting an exception opens an edit drawer with full context, history, and resolution controls.

• Source Entity Snapshot: The drawer shows the originating entity (e.g. the Receipt Line, Put-Away task, or Cycle Count audit) with a View History action that opens a change-tracking timeline.
• Static Details: Read-only fields display the exception type, item, slot/barcode, expected vs. actual quantity, affected quantity, and creation date — sourced from the raising module.
• Status Field: Required, set from a dropdown. Typical lifecycle: Open → In Progress → On Hold / Escalated → Resolved → Closed. Changing status to Resolved automatically stamps a resolvedDateTime if one isn't already set.
• Assigned-To Picker: Reassign ownership at any time. The change is saved with the exception.
• Notes Thread: A running notes thread captures every comment, approval action, and resolution step, stamped with timestamps for the audit trail.
• Documents: Attach photos, RMAs, or other supporting files via the Documents panel. Adding a document marks the form dirty so you don't lose attachments on accidental navigation.
• Inventory Adjustments Timeline: When inventory has been adjusted as part of resolution, the adjustments timeline shows each movement linked to this exception.

4️⃣ Resolution Types

Each exception is closed by selecting one of five Resolution Types. The form swaps to the matching workflow once you pick a type.

Accept Into Inventory

Used when the discrepancy is acceptable as-is and the affected stock should be brought into available inventory.

• When to use: Over-receipt that the buyer approved, items that pass inspection after a quality flag, or rebalancing that resolves on the shelf.
• Captured: Resolution notes, optional cause type. The system updates the inventory bundle and marks the exception Resolved on save.

Create RTV (Return to Vendor)

Used when defective or wrong-vendor items must be returned upstream.

• When to use: Vendor shipped wrong item, damaged on arrival, recalled stock.
• Captured: Vendor selection (RTV Vendor), packages built for return, generated shipment ID for tracking.
• Approval Required: Yes — like Disposal, RTV requires manager approval before it's finalized (see step 5).
• Outcome: A return shipment is created and linked to the exception, inventory is withdrawn from the bundle, and the exception moves to Resolved.

Disposal

Used when items must be removed from inventory entirely.

• When to use: Items beyond repair, obsolete, safety hazards, quality failures, or other irrecoverable cases.
• Captured:
  • Disposal Reason — Beyond Repair, Obsolete, Safety Hazard, Quality Failure, or Other (notes required if Other).
  • Disposal Method — Trash, Recycle, Hazmat Disposal, Electronic Waste, Donation, or Other (notes required if Other).
  • Disposal Confirmed checkbox — must be checked before save.
• Approval Required: Yes — disposal kicks off the Approval Workflow (see step 5).
• Outcome on confirm: The system withdraws the affected quantity from inventory, logs the dollar value impact (computed from item Stock Value × affected quantity when available), records who approved, and resolves the exception.

Quarantine

Used when items must be held out of pickable inventory while investigation continues.

• When to use: Suspected damage, awaiting QA decision, recall hold, or vendor investigation.
• Captured: Quarantine reason, slot the items are moved to, optional notes.
• Outcome: Inventory is moved to a quarantine slot so picking workflows skip it, and the exception is set to On Hold. It stays tracked until the quarantine is lifted (resolved into Accept, Disposal, RTV, or Transfer).

Transfer

Used when items belong at a different warehouse.

• When to use: Wrong warehouse received, inventory rebalance, customer request, manager request, or other.
• Captured (multi-step):
  1. Warehouse Details: Destination warehouse (cannot be the active warehouse), transfer reason, optional notes.
  2. Package Details: Build the packages from the affected inventory bundle and quantity.
  3. Shipping: Select service type (default FedEx Ground) and create the outbound shipment.
• Outcome: A shipment record is created and linked to the exception. On dispatch, the inventory leaves the active warehouse and the exception resolves.

5️⃣ Approval Workflow

Some resolutions — Disposal and Create RTV — require manager approval before they are finalized.

• Request Approval: The resolver fills out the resolution form and clicks Request Approval. The exception status moves to await manager review and the request timestamp is captured.
• Manager Review: Users with the Exception Manager Approval permission see Approve / Deny controls inside the resolution drawer.
• Approve: Captures the approver's full name, sets the exception back to In Progress, and unlocks the next confirmation step (e.g. inventory withdrawal for disposal).
• Deny: Records the denial along with the manager's name. The resolver can revise and resubmit, or cancel the resolution.
• Cancel Resolution: At any point before final save, the resolver can cancel. A confirmation modal asks "Are you sure you want to cancel this resolution?" before clearing the resolution-specific fields.

6️⃣ Status Lifecycle & Closure

Exceptions move through a defined status lifecycle that controls which fields can be edited.

• Open: Newly raised; everything is editable.
• In Progress: Active work; resolver can edit details and resolution.
• On Hold: Paused pending external information. Editable.
• Escalated: Bumped to a manager. Editable.
• Resolved: Resolution complete. The resolution form locks; status and notes remain editable in case re-opening is needed.
• Closed: Final state. The full record is read-only — no edits to status, notes, or resolution.
• Resolved Date: Stamped automatically the first time status moves to Resolved and preserved on subsequent edits.

:lightbulb: User Insights

• Triage from the queue: Use Type and Source filters together (e.g. Damaged + Receipt) to spot vendor-quality patterns. Use Location filter to find zones with chronic mis-slotting.
• Right-size the resolution: Accept clears small discrepancies fastest; Quarantine is the safe pause when you're unsure; Disposal and RTV both require approval and inventory write-down so use them deliberately.
• Audit trail is automatic: Every status change, assignment, note, and resolution step is timestamped on the exception. The notes thread is the source of truth — write what you did, why, and what's next.
• Closed is final: Once an exception is Closed, the record is locked. If something needs to change, re-open the source entity and raise a new exception linked to it.