> 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/technical-guides/oms/stale-waiting-process.md).

# Stale Waiting Process

This tutorial explains step by step how **packages stuck in the Waiting status for a long time** are moved to **Stale Waiting**, how reservations are managed, cancellations are handled, and how packages can be moved to Delivered status.

<figure><img src="/files/5MrsTI8Pv9RFvOKN06OO" alt=""><figcaption></figcaption></figure>

***

## <mark style="color:red;">**1. Moving Packages to Stale Waiting**</mark>

#### **Purpose:**

Automatically move packages that have been in **Waiting** status for a long time to **Stale Waiting**, allowing the brand to handle the subsequent process.

#### **Steps:**

**1.1 Configuration**

* The **`MARK_STALE_WAITING_PACKAGES_DAY`** variable in **Application Settings** defines the reference for moving packages to Stale Waiting.
* **Default value:** 15 days
  * Packages that have been in Waiting status for 15 days or more will be marked as Stale Waiting.
* This value can be updated according to operational needs:
  * Example: For longer operational timelines, set to 20 days.

**1.2 Runtime**

* A **nightly automated task** runs at **03:00 AM**.
* The task checks all packages in Waiting status and identifies those that have been waiting **equal to or longer than `MARK_STALE_WAITING_PACKAGES_DAY`**.
* These packages are automatically moved to **Stale Waiting** status.

**1.3 Reservation Management**

* All reservations for packages moved to Stale Waiting are **automatically cancelled**.
* This frees up inventory and leaves the package handling to the brand.

**Note:** This step does not require manual intervention; the automated task handles all cancellations.

***

## <mark style="color:red;">**2. Cancellation of Packages in Stale Waiting**</mark>

#### **Purpose:**

The brand can manage Stale Waiting packages in Omnitron through **partial or full cancellation**.

### <mark style="color:red;">**2.1 Partial Cancellation**</mark>

* Steps:
  1. The **first package** in the Stale Waiting package is fully cancelled.
  2. For products not cancelled in Omnitron, a **new package** is created at the same location.
  3. The new package is started in **Stale Waiting** status and the process continues under the brand’s control.

**Example Scenario:**

* Package contains 10 products, 4 are cancelled → Remaining 6 products are placed in a new Stale Waiting package.

### <mark style="color:red;">**2.2 Full Cancellation**</mark>

* Steps:
  1. All products in the package are **cancelled**.
  2. The package process is **fully terminated**.

**Example Scenario:**

* Package contains 5 products, all are cancelled → Package is completely closed.

**Note:** Full cancellation does not create a new package; the process stops entirely.

***

## <mark style="color:red;">**3. Moving Packages to Delivered**</mark>

#### **Purpose:**

If requested by the brand, packages in **Stale Waiting** can be moved **directly to Delivered** status without any intermediate state.

#### **Steps:**

1. Execute the **Deliver The Package** command in Omnitron.
2. The package moves directly to **Delivered** without going through any intermediate status.

**Notes:**

* This allows Stale Waiting packages to be marked as delivered quickly.
* Can be applied based on brand request.


---

# 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/technical-guides/oms/stale-waiting-process.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.