# Priority Orders

### Overview

Priority Orders give merchants the flexibility to fast-track urgent shipments without disrupting the overall fulfillment flow. Orders can be flagged manually or automatically through predefined rules, pushing them to the top of the queue across Bulk Order Processing, Route Optimization, or Single Order Processing. This ensures time-sensitive requests are handled immediately while keeping fulfillment adaptable to client and shopper needs.

### How It Works

Priority Orders can be flagged either by merchants or by warehouse management, giving both sides control over urgent requests. They can also be triggered automatically through existing order automation rules, ensuring priority handling without manual intervention.

Once flagged, these orders are immediately pushed to the top of the queue. In [**Single Order Processing**](/workflows/order-fulfillment/single-order-processing.md), the system serves the urgent order next before resuming the normal sequence. In [**Bulk**](/workflows/order-fulfillment/bulk-order-processing.md) **or** [**Route Order Processing**](/workflows/order-fulfillment/route-picking.md), flagged orders are prioritized during batch creation so they are processed ahead of standard orders.

Priority Orders are also surfaced at the top of the Fulfillment Dashboard, giving managers immediate visibility and control over time-sensitive shipments. By embedding priority handling directly into each fulfillment method, the WMS ensures urgent shipments are completed without disruption, keeping fulfillment flexible and responsive to client needs.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCeonLiMPEjSEFhi8zpC0%2Fuploads%2FxxQFO18IoHUHXYn9nvLi%2FPriority.mp4?alt=media&token=e8148fc1-2dfa-4643-8f9d-21d87e35ab30>" %}
Toggling an order as Priority for expedited handling.
{% endembed %}

### Why It Matters

* Keeps urgent shipments moving by embedding priority handling directly into existing workflows.
* Provides flexibility for both merchants and warehouse management to fast-track requests.
* Supports client commitments by handling ad-hoc demands and exceptions quickly.

### Best Practice

Priority Orders deliver the most value when they are flagged before batch creation begins. If an urgent order is already part of a generated batch, its priority may be reduced since batches are processed as a unit. For truly time-sensitive requests, the most reliable approach is to use Single Order Processing as the picking method, ensuring the order is completed immediately. Clear communication between clients and warehouse management is essential to avoid delays and to make sure urgent requests are captured and fulfilled without disruption.


---

# Agent Instructions: 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:

```
GET https://docs.getlogentic.com/workflows/order-fulfillment/priority-orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
