> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/seller-center/managing-package-rejection-reasons-mpos-and-sellers.md).
# Managing Package Rejection Reasons MPOs & Sellers
This guide explains, step by step, how to manage order rejection/cancellation reasons in the MPO panel, and how sellers use those reasons when rejecting a package from the Seller Panel.
### Managing Rejection Reasons (MPO Panel)
1. In the MPO panel, go to **Settings > Order Rejection Deductions**.
2. Open the Order Rejection Reasons list. This shows every defined order rejection/cancellation reason, along with its current Active/Passive status.
3. For any reason you want sellers to see when rejecting a package, set that row's **Is Seller Reason** toggle to **Active**.
4. For reasons that should not appear to sellers, leave the Is Seller Reason toggle set to **Passive**. The reason's overall Status field can remain Active — that field only controls whether the reason is active in the system at all, not whether it's shown to sellers.
5. Changes apply immediately; no separate save step is required. Refresh the list to confirm the updated state.
{% hint style="info" %}
Status and Is Seller Reason are two separate fields: one controls whether the reason is active in the system, the other controls whether it's shown to sellers.
{% endhint %}
### Rejecting a Package (Seller Panel)
1. In Seller Center, go to **Orders > Packages**.
2. Locate the package to be rejected and click the **Reject** action button on that package's row.
3. The rejection reason list that appears now shows only the reasons an MPO has marked as Is Seller Reason.
4. Select the reason that fits the situation and confirm the rejection.
---
# 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://docs.akinon.com/tutorials/seller-center/managing-package-rejection-reasons-mpos-and-sellers.md?ask=&goal=
```
`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.