> 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/using-peakcommerce/ecommerce-and-payment-pages/updating-subscriptions-through-e-commerce.md).

# Updating Subscriptions Through Ecommerce

Customers can change an existing subscription — upgrade, downgrade, or add and remove add-ons — through a guided flow, with no admin involved. In the new platform this is a **Customer Self-Service** journey rather than a special page mode.

## How it works

Build a journey of type **Customer Self-Service** (see [Create a journey](https://gitlab.com/peak-hercules/peak-help-docs/-/blob/main/product/using-peakcommerce/journeys-and-pages/journey-basics/adding-a-journey.md)) that loads the customer's current subscription and lets them change it. The journey applies the change to the existing subscription in your billing system, and you can add **branching** — for example a retention offer on a downgrade or cancellation.

For rep-assisted changes, use a **CSR Self-Service** journey instead.


---

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

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/ecommerce-and-payment-pages/updating-subscriptions-through-e-commerce.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.