> For the complete documentation index, see [llms.txt](https://howto.sellercraft.co/how-to-sellercraft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://howto.sellercraft.co/how-to-sellercraft/oms/sellerwizard/ops-report/simple-ops-report/oversold-skus.md).

# Oversold SKUs

Overselling can lead to dissatisfied customers, negative reviews, and lost sales. By tracking oversold SKUs and quickly resolving overselling issues, sellers can maintain customer satisfaction and prevent financial losses.

{% hint style="info" %}
By analyzing the data in this table, sellers can identify trends and patterns related to overselling. For example, they may discover that overselling occurs more frequently for certain SKUs or during specific periods of time. This information can help sellers improve their inventory management and prevent overselling in the future.
{% endhint %}

<figure><img src="/files/ZDM1rSvxDbkW1uXHue9M" alt=""><figcaption><p>Oversold SKUs</p></figcaption></figure>

{% hint style="info" %}
The table can be exported through the designated button located on the upper right-hand corner of the table.
{% endhint %}

## Column Definition

<table><thead><tr><th width="161">Column</th><th>Description</th></tr></thead><tbody><tr><td>Order Number</td><td>The unique identification number of the order that caused the overselling issue.</td></tr><tr><td>Shop</td><td>The online marketplace or e-commerce platform where the overselling issue occurred.</td></tr><tr><td>SKU Affected</td><td>The SKU that was oversold.</td></tr><tr><td>Units Affected</td><td>The number of units of the SKU that were oversold.</td></tr><tr><td>Customer Contact</td><td>The contact information of the customer who ordered the oversold SKU.</td></tr><tr><td>Status</td><td>The current status of the order</td></tr><tr><td>Order Value at Risk</td><td>The total value of the oversold units, which indicates the financial impact of the overselling issue.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://howto.sellercraft.co/how-to-sellercraft/oms/sellerwizard/ops-report/simple-ops-report/oversold-skus.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.