> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/slab/getting-started/global-settings/prices-settings.md).

# Prices

Price settings in **Theme settings > Prices** control whether formatted prices show trailing zeros and whether currency notation appears.

## How to change theme prices

{% stepper %}
{% step %}

#### Open price settings

* Open **Theme settings > Prices**.
  {% endstep %}

{% step %}

#### Set formatting

* Use **Show trailing zeros** to keep or hide decimals on whole amounts (for example, `$25.00` vs `$25`).
* Use **Show currency symbol** to show or hide currency notation in formatted prices.
  {% endstep %}

{% step %}

#### Preview the storefront

* Review product cards, product pages, cart, and featured prices.
  {% endstep %}
  {% endstepper %}

### Notes on prices

* **Show trailing zeros** changes how whole-number prices are displayed where this setting applies.
* **Show currency symbol** helps when customers need explicit currency context.

## Price settings

| Setting              | What it controls                                                                 |
| -------------------- | -------------------------------------------------------------------------------- |
| Show trailing zeros  | Keeps trailing decimals such as `.00` on whole amounts when enabled. Default on. |
| Show currency symbol | Shows currency notation in formatted prices when enabled. Default off.           |


---

# 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://help.brickspacelab.com/slab/getting-started/global-settings/prices-settings.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.
