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

# Confirmed Journeys

> Manage confirmed trips inside the same Journey workspace you used to build and publish the trip.

## What Changed

Itineraries are no longer a separate workspace created from a proposal. A confirmed trip is now a **Confirmed Journey**.

That means:

* You keep editing the same Journey after confirmation
* The public link stays the same
* The trip is not locked after confirmation
* Operational tabs, service statuses, suppliers, purchase orders, invoices, tasks, and communications live in the Journey
* Saved changes appear publicly only after you publish again

<Note>
  If you used Odia before this update, your existing itinerary links still work. They now resolve through the unified Journey system.
</Note>

## Finding Confirmed Trips

Open **Journeys** and select the **Confirmed** view to focus on trips that are ready for operations.

Use filters to narrow by:

* Travel dates
* Owner
* Status
* Travel agent
* Search term
* Archived state

## Working Inside A Confirmed Journey

Confirmed Journeys use the same tabs as planning-stage Journeys, with more emphasis on operations.

| Tab                 | What it is for                                                                             |
| ------------------- | ------------------------------------------------------------------------------------------ |
| **Journey Builder** | Manage day-by-day services, content cards, and trip or day summaries in board or list view |
| **Areas**           | Review or update destination legs                                                          |
| **Travelers**       | Manage traveller details and assignments                                                   |
| **Pricing**         | Review revenue, cost, margin, and commission                                               |
| **Invoicing**       | Create and manage invoices                                                                 |
| **Tasks**           | Track operational work                                                                     |
| **Communications**  | Review messages and service communication where enabled                                    |

## Service Operations

Each service has its own operational status:

| Status        | When to use it                      |
| ------------- | ----------------------------------- |
| **Ready**     | Service is waiting for action       |
| **PO Sent**   | Purchase order sent to the supplier |
| **Confirmed** | Supplier confirmed the booking      |
| **To Change** | Service details need an update      |
| **Cancelled** | Service is cancelled                |
| **Completed** | Service has happened                |

Open a service to manage:

* Dates and times
* Travellers and guest count
* Supplier and supplier contact
* Address, pickup point, and meeting point
* Public description and additional information
* Files, tickets, vouchers, and confirmations
* Purchase order fields
* Tasks and communications

## Purchase Orders

Purchase orders are sent from services in a confirmed Journey.

Before sending:

1. Add the supplier
2. Add the correct supplier contact if needed
3. Fill any mandatory purchase-order fields
4. Connect the sending inbox if your administrator requires it
5. Preview and send the purchase order

Communications are logged back on the service so the team can see what has been sent.

## Publishing Confirmed Changes

Confirmed Journeys still use explicit publishing.

<Warning>
  If you save a change and the header shows **Unpublished changes**, the public Journey link has not updated yet. Publish when the traveller or agent should see the new version.
</Warning>

This applies to confirmed Journey edits such as:

* Changing dates, times, pickup details, or descriptions
* Adding or removing services
* Updating files or traveller-facing notes
* Changing display settings
* Updating the public layout in Journey Designer

## Web Journey

The public Journey is what travellers and agents see. It can include:

* Daily services and timing
* Descriptions and additional information
* Files and vouchers
* Maps and directions where addresses are set
* Supplier contact information where assigned
* Prices if display settings allow them
* Content cards and trip summaries

<Tip>
  The same link can be used from planning stage through confirmed operations. Publish again to move that link to the latest approved version.
</Tip>