> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spherecast.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Exceptions

> The Cockpit's action list of operational supply-chain issues — stockouts, overstock, delays, and more — with one-click fixes.

## What this page is for

Below the KPI cards, the main area of the Cockpit is a tab called **Exceptions**, with a count badge showing how many are open. An *exception* is one actionable operational supply-chain issue tied to a specific product or record — something that needs a planner's attention now.

This is your daily to-do list. Each row names the problem in plain language and, where possible, offers a one-click action to fix it. When everything is healthy, you will see **"No exceptions at this time."**

> This screen is about *operational* problems (stockouts, delays, excess). It is different from the [Data alerts](/guide/home/data-alerts) screen, which flags *data-quality and setup* problems. Keep the two separate in your mind.

## What you see

| Column      | What it shows                                                                    |
| ----------- | -------------------------------------------------------------------------------- |
| **SKU**     | The Stock Keeping Unit — the unique product code.                                |
| **Record**  | The affected item: a warehouse, product, or order.                               |
| **Type**    | A colored badge naming the kind of issue (see below).                            |
| **Message** | A plain-language explanation of what is wrong.                                   |
| **Actions** | The button that resolves it (Expedite, Defer, or Consolidate), when one applies. |

## Exception types

| Type (badge color)                | What it means                                                                                    |
| --------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Stockout** (red)                | A product is out of stock.                                                                       |
| **RM/WIP stockout** (red)         | A raw material (RM) or work-in-progress (WIP) component is out of stock, threatening production. |
| **Stockout risk** (orange)        | A product is projected to run out soon.                                                          |
| **RM/WIP stockout risk** (orange) | A component is projected to run short.                                                           |
| **Overstock** (purple)            | More stock than needed.                                                                          |
| **Expiration risk** (orange)      | Stock at risk of expiring unsold. *(Your company may rename "Expiration.")*                      |
| **Order delay** (blue)            | An order — for example a purchase order — is at risk of arriving late.                           |
| **Demand exception** (purple)     | An unusual demand pattern that needs review.                                                     |
| **Consolidation** (green)         | Purchase orders that could be merged to save cost.                                               |
| **Sales deviation** (yellow)      | Last month's sales differ sharply from the recent average.                                       |

A sales deviation message reads like a headline, for example *"Spike: Sold 1,200 units last month, +45% vs 3-month avg of 830"* or a *"Drop: ..."* version when sales fell.

## How the actions work

The **Actions** column matches the button to the problem:

* **Stockout-family rows** (stockout and stockout-risk types) show an **Expedite** button — pull an incoming order in earlier so stock arrives sooner.
* **Overstock rows** show a **Defer** button — push an order later so you stop adding to the excess.
* **Consolidation rows** show a **Consolidate** button — merge purchase orders together.

Each action opens in a new tab so you keep your place in the list. You can **Dismiss** an action, which greys out the row, and later **Restore** it if you change your mind. If a row has already been acted on, its button is disabled — for example *"Already expedited — no further expedite possible for this product."*

**Clicking a row** jumps you straight to the right place to work:

* Order delay → the affected [purchase order](/guide/supply-planning/purchase-orders).
* Demand or sales issues → the [demand plan](/demand), pre-filtered to that product.
* Consolidation → the purchase-order consolidation screen.
* Everything else → the product's supply view.

## Finding what matters: filters and sort

* **Search** by SKU or title.
* Filter by a single **alert-type** chip to show just one kind of exception.
* Narrow further by **Assignee**, **Warehouse**, **Supplier**, **Group**, and **Category**.
* Use the **Include bundles** toggle to show or hide bundled products.

Sorting puts the most urgent, actionable work first: **expedite-actionable** rows lead, then **defer** rows, then the rest.

## Step by step: clear a stockout risk

1. On the Cockpit, open the **Exceptions** tab.
2. Click the **Stockout risk** chip to show only those rows.
3. Read the **Message** to confirm the product and how soon it runs out.
4. Click **Expedite** in the Actions column. The order opens in a new tab, pulled in earlier.
5. Back on the list, if the item is handled, **Dismiss** the row to grey it out.

## Example

You open Exceptions to a badge reading **23**. Sorted by default, the top rows are red **Stockout** and orange **Stockout risk** items with **Expedite** buttons. You expedite two, then reach a yellow **Sales deviation**: *"Spike: Sold 1,200 units last month, +45% vs 3-month avg of 830."* You click the row, land in the demand plan for that product, and adjust the forecast so the spike is not treated as normal.

> **Tip:** See [Expedite / Defer & supply planning](/guide/supply-planning/overview) for how pulling orders in and pushing them out reshapes your plan.

> **Note:** Dismissing an action only greys the row for you — it does not cancel the underlying order. Use **Restore** to bring a dismissed action back.
