> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/payments/the-shop-page.md).

# The Shop Page

### Overview

The **Shop** is a new page on the Dashboard where your Club can charge Customers for products purchased at the front desk.

<figure><img src="/files/gnky7MK42ZnwqXGM5AOx" alt=""><figcaption></figcaption></figure>

There are **three main areas** on this page:

1. **Location**: toggle between Club venues; available if you have more than one location in your system
2. **Product Catalog**: products are loaded into the Shop; drafting space for products
3. **Shop**: products are added to a shopping cart and charged to a Customer; public facing products

<figure><img src="/files/cgxAV9jwdxYOKwqD4KIX" alt=""><figcaption></figcaption></figure>

***

### Locations

If your Club only has one venue, only the single Location will appear in the top left corner of the page.

<figure><img src="/files/rNBroBDEXUkX1CUAKbDW" alt=""><figcaption></figcaption></figure>

If your Club has several venues, then clicking on the Location name will show all of the available venues and their associated Location names.

<figure><img src="/files/ICJ3FECBRXtQioNeSyRs" alt=""><figcaption></figcaption></figure>

Each venue Location:

1. Can view all products inside the Product Catalog
2. Has a unique Shop list

This means that when [**Adding to the Product Catalog**](/payments/the-shop-page/add-to-the-product-catalog.md), these products are not automatically added to the Shop, and thus are not visible on the Shop area of the page. If you are reviewing a new venue Location added to your Dashboard, there will not be any products in the Shop.

As an example:

* The Club has a venue location named Lower East Side
* Items were previously added to the Product Catalog and then added to the Shop area
* The Club opens a new location named Williamsburg
* When reviewing the Williamsburg location, the Shop area of the page will be empty
* An Admin will need to [**Add to Shop from the Product Catalog**](/payments/the-shop-page/add-to-shop-from-product-catalog.md)

{% hint style="warning" %}
If you are a **Location-specific Club owner** and can only view one (or a few) of many Locations inside the system, or are a **franchisee Club owner**, *you cannot add products to the Product Catalog area of the page*. You can only review the Product Catalog and add items from there to your venue Location’s Shop.
{% endhint %}

***

### Product Catalog

Products loaded into the Shop are first added to the Product Catalog. Once there, products can then be moved from the Product Catalog to the Shop.

Think about it like this:

* **Product Catalog**: This is a drafting space to add products which are not visible
* **The Shop**: This is a public space where products can be added to a shopping cart and charged to the Customer

**NOTE:** If you are a **Location-specific Club owner** and can only view one (or a few) of many Locations inside the system, or are a **franchisee Club owner**, *you cannot add products to the Product Catalog area of the page*.

To begin adding products to your Product Catalog, check out the article [**Add to the Product Catalog**](https://help.podplay.app/en/articles/8071233).


---

# 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.podplay.app/payments/the-shop-page.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.
