> 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/settings-and-plans/timezone.md).

# Set your timezone

Choose the timezone used for scheduled starts and reverts.

Scheduled start times, revert times and recurring windows are interpreted in the timezone set here. Dates shown in the app use it too.

<figure><img src="https://1559832597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw4HtMDNMyRJ8FelzhTov%2Fuploads%2Fgit-blob-08dc0e4faf51e3a2cdc535b418ec5d6e2c48f21d%2Fsettings.png?alt=media" alt="Settings page with Timezone and Notifications cards"><figcaption><p>Settings</p></figcaption></figure>

1. Open **Settings** in the app menu.
2. Under **Timezone**, pick your zone from the list, for example **(GMT+07:00) Bangkok, Hanoi**.
3. Click **Save** in the top bar. The app shows **Settings updated**.

If you never change it, the app uses your Shopify store timezone.

{% hint style="info" %}
The schedule card on every task shows the timezone in use, for example *Timezone: (GMT+07:00) Bangkok, Hanoi*, with a **Change timezone** link that brings you here. Changing the timezone does not move tasks that are already scheduled.
{% 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://docs.samita.io/bulk-price-editor-sami/settings-and-plans/timezone.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.