> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/theme-settings/currency-format.md).

# Currency format

Control whether the currency code (USD, EUR, GBP) appears next to prices across the storefront. Useful for stores selling in several currencies.

{% hint style="info" %}
**Theme Editor → Theme settings → Currency format**
{% endhint %}

**Show currency codes** adds the three-letter currency code next to the price.

| Setting  | Example   |
| -------- | --------- |
| Enabled  | $1.00 USD |
| Disabled | $1.00     |

{% hint style="warning" %}
**This is a storefront-wide setting.** It changes every price the theme renders — product cards, product pages, quick view, the cart drawer, the cart page, the free shipping bar, gift cards and bundles. It is not limited to the cart.
{% endhint %}

{% hint style="info" %}
**Checkout is not affected either way.** Shopify always shows currency codes at checkout, so turning this off will not remove them there — which is exactly why switching it off can make prices look inconsistent on the way to payment.
{% endhint %}

{% hint style="success" icon="lightbulb" %}
**Tip:** Keep currency codes on if you sell internationally — a customer seeing $1.00 has no way to tell US dollars from Canadian or Australian ones. For a store selling in a single currency to a single country, switching them off gives cleaner-looking prices.
{% endhint %}


---

# 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://staylime.com/docs/avante-themes/theme-settings/currency-format.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.