> 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.md).

# Order Journey

Order Journey gives you a complete view of how an order travelled between systems, from the moment it was placed to the moment it was delivered, completed or cancelled. It is available through the new **Order Lifecycle** tab on every order in Atlas.

In addition to the order status, you can now see the hops that occurred between systems and easily spot failures when they occur.

## What You Can Do with Order Journey

* Check whether each order reached the POS directly from the Orders list.
* Expand every order status to see the system-to-system hops that happened under it.
* Understand why some events are greyed out (muted) on an order.
* View every retry attempt for an event, one by one.
* Spot failed hops at a glance and open them to find the exact cause.
* Understand how cancelled orders and modified orders are shown.
* Follow the rider's journey at the bottom of the Order Lifecycle.

## Articles in This Section

Read the articles below in order, or jump straight to the one you need.

1. [**Checking POS Status in the Orders List**](https://help.urbanpiper.com/business-manager/order-journey/checking-pos-status-in-the-orders-list.md): See whether each order reached the POS and filter for failed orders.
2. [**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): Expand every status to see the system-to-system hops under it.
3. [**Understanding Muted Events in the Order Lifecycle**](https://help.urbanpiper.com/business-manager/order-journey/understanding-muted-events.md): Learn why some events appear greyed out.
4. [**Viewing Retries for an Event, Attempt by Attempt**](https://help.urbanpiper.com/business-manager/order-journey/viewing-retries-for-an-event.md): See every retry Atlas made for a hop.
5. [**Spotting Failed Hops at a Glance**](https://help.urbanpiper.com/business-manager/order-journey/spotting-failed-hops-at-a-glance.md): Identify failures quickly and open the failed hop to debug it.
6. [**Understanding Cancelled Orders**](https://help.urbanpiper.com/business-manager/order-journey/understanding-cancelled-orders.md): See the reason, the cancelling system and the time of cancellation.
7. [**Understanding Modified Orders: Parent and Child Orders**](https://help.urbanpiper.com/business-manager/order-journey/understanding-modified-orders.md): See how Atlas links an original order with the order that replaced it.
8. [**Tracking Rider Status in the Order Lifecycle**](https://help.urbanpiper.com/business-manager/order-journey/tracking-rider-status.md): Follow the rider's updates and debug delayed deliveries.


---

# 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.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.
