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

# Order lifecycle

> How orders progress from submission to delivery.

Every order follows a defined status lifecycle from submission through production to delivery.

## Status flow

```
PENDING_APPROVAL → APPROVED → PROCESSING → MANUFACTURING → EMBROIDERY → QUALITY_CHECK → PACKED → DISPATCHED → DELIVERED
```

Orders that do not require approval skip Pending Approval and start at **Submitted**. **Rejected** and **Cancelled** are terminal states.

## Status definitions

| Status               | Description                                             |
| -------------------- | ------------------------------------------------------- |
| **Pending Approval** | Awaiting approval (required by the employee's rule set) |
| **Submitted**        | Placed and entered into the production queue            |
| **Approved**         | Approved and ready for production                       |
| **Processing**       | Being prepared for manufacturing                        |
| **Manufacturing**    | Garments are being manufactured                         |
| **Embroidery**       | Custom embroidery or branding is being applied          |
| **Quality Check**    | Finished garments are being inspected                   |
| **Packed**           | Packed and ready for dispatch                           |
| **Dispatched**       | Shipped to the store                                    |
| **Delivered**        | Received at the store (terminal)                        |
| **Rejected**         | Rejected by an approver (terminal)                      |
| **Cancelled**        | Cancelled (terminal)                                    |

Orders never move backwards. Only Administrators advance order status.

## How status advances

* **Single order.** Find the order and click **Advance Status**.
* **Batch advance.** Find the store order batch and click **Advance** at group level; every eligible order in the batch moves to its next stage.
* **No automatic advancement.** Every transition requires manual action.

## Store order batches

Orders submitted together are grouped under a **store order batch** (`SO-#####`) for their store. Each submission gets one batch, and every order in it links to that batch.

A batch's displayed status uses a worst-first rule: the member order with the earliest lifecycle stage determines the batch status. If a batch holds orders at Packed, Manufacturing, and Approved, the batch shows **Manufacturing**.

## Rejected and cancelled orders

Rejected orders keep their rejection reason in the status timeline. They remain in the system as records; place a corrected order through the [ordering workflow](/orders/placing-orders) if needed.


## Related topics

- [Managing orders](/administrator/managing-orders.md)
- [Viewing store orders](/store-manager/viewing-orders.md)
- [Viewing orders (HR)](/hr/viewing-orders.md)
- [Common concepts](/getting-started/common-concepts.md)
- [Introduction](/getting-started/introduction.md)