> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/business-manager/order-journey/checking-pos-status-in-the-orders-list.md).

# Checking POS Status in the Orders List

The Orders list in Atlas now includes a **POS Status** column. It shows at a glance whether each order reached the POS, so you do not have to open every order to find out.

## What the POS Status Column Shows

A new **POS Status** column in the Orders list view shows whether each order reached the POS. The column shows one of two statuses:

* **RELAYED:** The order reached the POS.
* **RELAY FAILED:** The order did not reach the POS.

![Orders list with the POS Status column showing RELAYED and RELAY FAILED statuses, the Filter panel with the POS Status option, and the failure reason shown on hover](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-a900b300985b20ce01723ef3420796bfa283e642%2Forder-journey-01-pos-status-orders-list.gif?alt=media)

## See the Reason for a Failed Relay

Hover over a **RELAY FAILED** status to see the failure reason.

## Filter Orders by POS Status

You can also filter for **RELAY FAILED** orders using the **Filter → POS Status** option.

1. Visit login.urbanpiper.com and log in using your credentials.
2. Click on the **Orders** section to view the list of orders.
3. Click **Filter**.
4. Select the **POS Status** option.
5. Choose **Relay Failed** to see only the orders that did not reach the POS.

{% hint style="info" %}
**Tip:** This is useful to start triage. Filter for **RELAY FAILED** orders for any day, then open each order to explore in detail.
{% endhint %}

## What to Do Next

Click on any order in the list and go to the **Order Lifecycle** tab to see exactly where the order stopped. Learn more in [Understanding the Order Lifecycle Tab: From Status Steps to System Hops](https://help.urbanpiper.com/business-manager/order-journey/understanding-the-order-lifecycle-tab.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.urbanpiper.com/business-manager/order-journey/checking-pos-status-in-the-orders-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
