> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/frontend-guides/customer-account/dashboard-overview/wishlist.md).

# Wishlist

Save products to a personal wishlist and return to them later from the account dashboard.

The **Wishlist** lets customers save products they are interested in and come back to them later. From the wishlist, customers can open a saved product, check current availability and pricing, or move items to the cart when they are ready to purchase.

## Adding products to the wishlist

On the frontend, customers can add a product to the wishlist from the product details page or from product listing views.

<div align="left"><figure><img src="https://4011296124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOgeoK7nW6gEh0q1ceUZP%2Fuploads%2Fgit-blob-b7a55b68a0c2c9942153456126a2be79beef567b%2Fwishlist_pin.png?alt=media" alt="Add to wishlist"><figcaption></figcaption></figure></div>

The wishlist action is available alongside other product actions such as adding to cart.

<figure><img src="https://4011296124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOgeoK7nW6gEh0q1ceUZP%2Fuploads%2Fgit-blob-07188a139121ec7c68d365b299ef6f6548790b90%2Fadd_to_wishlist.png?alt=media" alt="Add to wishlist action on a product details page"><figcaption><p>Adding a product to the wishlist from the product page</p></figcaption></figure>

## Viewing and managing the wishlist

Saved products appear in the **Wishlist** section of the customer account. Each entry shows key product information such as image, name, quantity, and price, so customers can quickly compare items and decide what to buy next. The quantity is stored with each saved item.

Prices are shown in the currently selected currency and update when the customer changes currency. The wishlist always reflects current pricing for the active currency.

From this view, customers can remove products they no longer need or add selected items directly to the cart.

<figure><img src="https://4011296124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOgeoK7nW6gEh0q1ceUZP%2Fuploads%2Fgit-blob-57fc41411eaec64e01b47ebd1f292425e9ea0212%2Fwishlist.png?alt=media" alt="Wishlist section in the customer account listing saved products"><figcaption><p>Wishlist view in the customer account</p></figcaption></figure>

## Guest customers

Adding a product to the wishlist requires an authenticated session. When a guest customer selects **Add to wishlist**, they are prompted to sign in or create an account before the product can be saved. After logging in, the customer can add items to the wishlist and access them from the **Wishlist** section in their account.


---

# 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://developer.emporix.io/frontend-guides/customer-account/dashboard-overview/wishlist.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.
