# Journey Steps Overview

### Overview

Steps represent the “pages” that a customer goes through in the e-Commerce flow or in the portal. These steps can include Sign Up, Category, Confirmation and Details, Payment Details, Subscription Terms, and Cancellation.  

The look and feel of these steps can be determined in the e-Commerce template assigned to the page.  For additional information on e-Commerce pages, view the articles Templates, and E-Commerce Page Concepts.

Steps can be found in Journeys by navigating to Subscribe > Journeys > View Journey. 

### Step Actions

From here, steps can either be added, edited, or deleted. For additional information on these actions, view:

* [Adding a Journey Step](https://support.peakcommerce.com/en/articles/870528)
* [Editing a Journey Step](https://support.peakcommerce.com/en/articles/870464) 

### Types of Steps

There are several types of steps available in PeakCommerce. For details about each, view the article on [Types of Journey Steps.](https://support.peakcommerce.com/en/articles/870336)

### Step Requirements

Certain steps are required for each of the journey types. If missing a required step, the journey will not load the in-app experience or in the e-Commerce page.

| New Order     | Sign Up, Category, Payment Details, and Thank You steps |
| ------------- | ------------------------------------------------------- |
| Change Order  | Category, Payment Details, and Thank You steps          |
| Renewal Order | Category, Payment Details, and Thank You steps          |
| Cancel Order  | Cancellation step                                       |


---

# 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.peakcommerce.com/product/journeys-and-pages/journey-steps/journey-steps-overview.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.