> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-basics/editing-a-journey.md).

# Edit a journey

Open **Content → Journeys**, then choose **Edit** from the journey's row menu (**⋯**) — or click **Edit** on the journey's view page. This opens the journey builder.

<figure><img src="https://318941401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaVlEqhLl6KbOCFwAQfmr%2Fuploads%2Fgit-blob-217f4e1a1a31ea4a904ba63f03fe1a5cfe6f5900%2Fscreen_journey_edit.png?alt=media" alt="The journey builder: the journey&#x27;s type, status, and structure up top, then the Steps tab listing each step with its page, output variables, and commerce actions, and Steps / Flow / Settings tabs"><figcaption><p>The journey builder — edit the journey's details and manage its steps; opening a step launches the full-page step editor.</p></figcaption></figure>

Adding a step — or opening an existing one — launches the **full-page step editor**, which organizes the step's settings into sections you switch between (see [Managing journey steps](/product/journeys-and-pages/journey-steps/managing-journey-steps.md)).

## Edit details

Click **Edit details** to change the journey's top-level settings:

* **Name**
* **Type** — E-Commerce, Customer Self-Service, or CSR Self-Service
* **Status** — draft or active
* **Order Structure** — how the journey's orders are described. Its only option is **Single order with multiple line items** (or leave it at **None**), and it does not change how lines are booked. To book a line as its own order action, use [Order grouping](/product/using-peakcommerce/products-and-bundles/product-sets.md#line-booking-settings) on the product set and [Honor order grouping](/product/journeys-and-pages/journey-steps/commerce-actions.md#honor-order-grouping) on the create-order action
* **Subscription term** — Evergreen or Termed

## Build the flow

The builder has three tabs:

* **Steps** — add, reorder, and configure the pages a customer passes through. Each step maps data in and out and can run [commerce actions](/product/journeys-and-pages/journey-steps/commerce-actions.md) (create order, update account, fraud check, …). See [Managing journey steps](/product/journeys-and-pages/journey-steps/managing-journey-steps.md).
* **Flow** — connect steps and add branching logic.
* **Settings** — set the subscription term, the **profile assignments** that control who can enter the journey, and SEO & metadata for the public page. See [Journey Settings](/product/journeys-and-pages/journey-settings.md).

Click **Done** to save your changes. **Publish** the journey to make the changes live for customers.


---

# 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://docs.peakcommerce.com/product/journeys-and-pages/journey-basics/editing-a-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.
