# How does Nova handle time zones?

Source: https://novadata.io/docs/your-data/time-zones
Checked against Nova's code on 2026-10-29

Nova counts every sale, fee and unit on the local day of its marketplace: Pacific time for the US and Canada, Paris time for most European marketplaces. Ad metrics follow the time zone of your Amazon Ads profile, as in the Ads console. Your dashboard shows today in the time zone set for your workspace.

## Which time zone does each marketplace use?

| Marketplace | Marketplace ID | Time zone |
|---|---|---|
| United States | `ATVPDKIKX0DER` | `US/Pacific` |
| Canada | `A2EUQ1WTGCTBG2` | `US/Pacific` |
| Mexico | `A1AM78C64UM0Y8` | `America/Mexico_City` |
| Brazil | `A2Q3Y263D00KWC` | `America/Sao_Paulo` |
| United Kingdom | `A1F83G8C2ARO7P` | `Europe/Paris` |
| Ireland | `A28R8C7NBKEWEA` | `Europe/Dublin` |
| France | `A13V1IB3VIYZZH` | `Europe/Paris` |
| Germany | `A1PA6795UKMFR9` | `Europe/Paris` |
| Italy | `APJ6JRA9NG5V4` | `Europe/Paris` |
| Spain | `A1RKKUPIHCS9HS` | `Europe/Paris` |
| Netherlands | `A1805IZSGTT6HS` | `Europe/Paris` |
| Belgium | `AMEN7PMS3EDWL` | `Europe/Paris` |
| Sweden | `A2NODRKZP88ZB9` | `Europe/Paris` |
| Poland | `A1C3SOZRARQ6R3` | `Europe/Paris` |
| Turkey | `A33AVAJ2PDY3EV` | `Europe/Paris` |
| Egypt | `ARBP9OOSHTCHU` | `Africa/Cairo` |
| Saudi Arabia | `A17E79C6D8DWNP` | `Asia/Riyadh` |
| United Arab Emirates | `A2VIGQ35RCS4UG` | `Asia/Dubai` |
| South Africa | `AE08WJ6YKNBMC` | `Africa/Johannesburg` |
| India | `A21TJRUUN4KGV` | `Asia/Kolkata` |
| Japan | `A1VC38T7YXB528` | `Asia/Tokyo` |
| Singapore | `A19VAU5U5O7RUS` | `Asia/Singapore` |
| Australia | `A39IBJ37TRP1C6` | `Australia/Sydney` |

The European marketplaces share Paris time, so a day covers the same hours across a pan-European account. A UK day therefore runs from 23:00 to 23:00 London time.

## Which day does an order fall on?

The purchase time in the marketplace's time zone decides. Amazon stamps orders in UTC; Nova converts them before counting.

An order placed at `2026-05-01T06:30:00Z`:

| Marketplace | Local time | Counted on |
|---|---|---|
| United States | 30 April, 23:30 | 30 April |
| Germany | 1 May, 08:30 | 1 May |
| Japan | 1 May, 15:30 | 1 May |

The same rule sets the exchange rate: an amount converts at the rate of its local day. See [Currencies](/docs/your-data/currencies).

## Why can ad spend and sales use different days?

Amazon reports advertising by day in the time zone of each Ads profile, and Nova keeps those days as Amazon serves them, so your figures match the Ads console. Where the profile's time zone differs from the marketplace's in the table above, ad days and sales days are offset by the difference: a UK Ads profile counts on London time, UK sales on Paris time, one hour apart.

## How does the dashboard decide which day is today?

Each workspace has a **Reporting day** setting, in Settings, Workspace, General. By default it uses the westernmost time zone among the workspace's marketplaces: a workspace selling in the US and Germany shows today in Pacific time. The owner can choose another zone from the workspace's marketplaces.

At 06:00 in Paris, a US and Germany workspace still shows the previous day as today: the US day has not started yet.

## Where you see it

- **App**: every daily figure, the date filters and Today.
- **MCP**: dates in answers are marketplace-local days.
- **Data Share**: `metric_date`, `purchase_day` and `posted_day` are marketplace-local days; `purchase_at_utc` is the UTC instant.

## Ask your AI

> Compare my US sales yesterday by hour in Pacific time, and tell me which UTC hours they cover.