> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/faqs/changes-not-on-storefront.md).

# Why don't changes appear on my storefront immediately?

The task completed and the admin shows the new values, but the online store still shows the old ones.

## Caching

Shopify and your browser cache storefront pages. Changes usually appear within a few minutes. Reload the page, or open it in a private window, before assuming something went wrong. Always check the value in **Shopify admin › Products** first; that is where the app writes.

## Market prices

If you use Shopify Markets with market-specific pricing, a customer in that market sees the market price, not the base price. Changing the **Price** field only changes the base price. To change what a market sees, run a task on **Price by market**. See [Price by market](/bulk-price-editor-sami/field-guides/price-by-market.md).

## Theme or other apps

Some themes and apps (currency converters, discount apps, price display apps) show a computed price instead of the product price. If the admin shows the new value and the storefront does not, disable those apps temporarily or test with a different theme.

## Sales channel and status

A product set to **Draft** or unpublished from the Online Store is hidden regardless of its price. Check [Status](/bulk-price-editor-sami/field-guides/status.md) and [Collections and sales channels](/bulk-price-editor-sami/field-guides/collections-and-sales-channels.md).


---

# 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://docs.samita.io/bulk-price-editor-sami/faqs/changes-not-on-storefront.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.