> 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/getting-started/setup/3.-your-first-storefront.md).

# 3. Your First Storefront

A **journey** is the experience that sells a product set — a checkout, a signup flow, or a self-service portal. This is where your catalog becomes something a customer can actually buy.

{% embed url="<https://youtu.be/mFroWN1GokI>" %}

**Create a journey**

1. Go to **Content → Journeys** and create a new journey.
2. Choose the type — for a storefront, an **e-commerce** journey.
3. Point it at the **product set** you built. This coupling is what the journey sells.

**Give it a page**

A journey is built from **pages**, composed in the low-code editor. Add the pages your flow needs — a plan picker, a checkout, a confirmation — and arrange the steps.

> **Note:** the page editor is available to system administrators. If you don't see it, ask your admin to grant access or to build the pages with you.

**Publish**

When the journey and its pages look right, **publish** so the storefront is live and ready to serve customers.

**Learn more:** [Journey Basics](/product/journeys-and-pages/journey-basics.md) · [Ecommerce & Payment Pages](/product/using-peakcommerce/ecommerce-and-payment-pages.md).

**Next step →** [Going Live](/product/getting-started/setup/4.-going-live.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/getting-started/setup/3.-your-first-storefront.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.