> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/import-data/import-how-to/change-the-frequency-of-data-updates.md).

# Change the frequency of data updates

Set how often Channable updates your imported product data.

Channable automatically updates your product data once a day. This daily update keeps your product listings fresh without you having to do anything.

{% hint style="info" %}
Tip: If your inventory changes often, or you run frequent sales, you might need to update your data more than once a day.
{% endhint %}

## Edit your project schedule settings

You can edit your project **Schedule settings** in **\[your project] >** **Settings > Schedule settings***.* You can select your time zone and set up and at which scheduled time slots your project should run.

These time slots are the times all imports and **active** exports (feeds, Marketplaces, and Text Ads/Shopping Campaign generators) will run and your data will sync with these channels.

<figure><img src="https://3042294697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZa0iYflHeXmKWGnfFMAN%2Fuploads%2FgVfNtUGxi4wr8xMTmN3T%2FSchedule%201.png?alt=media&amp;token=5156810b-7a13-4c31-83c2-d8e32abe83b0" alt=""><figcaption></figcaption></figure>

**In timezone**

This is the timezone of the daily data sync. You can adjust it to the timezone of your choice or to the timezone that your webshop is based in.

**Schedule time slots**

This shows how many times per day the project is scheduled to run the imports and exports. The default setting is 1 time slot a day.

{% hint style="info" %}
With our **Core Plus** or **Core Pro** plan, we can offer extra data syncs to a maximum of 24 timeslots per day at a quarter of an hour interval. Find more about our more our [Core plans](https://www.channable.com/pricing).
{% endhint %}

{% hint style="warning" %}
**Note:** This is only applicable after your activate your project in the [project settings](/get-started/getting-started/create-a-new-project/project-settings.md).
{% endhint %}

<figure><img src="https://3042294697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZa0iYflHeXmKWGnfFMAN%2Fuploads%2Fc4tlf9pq318Moq8V9MFU%2FSchedule%202.gif?alt=media&amp;token=ae4b9b1f-784a-469a-8f27-787fabf2ac57" alt=""><figcaption></figcaption></figure>


---

# 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://helpcenter.channable.com/import-data/import-how-to/change-the-frequency-of-data-updates.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.
