> ## Documentation Index
> Fetch the complete documentation index at: https://marrow-docs.hologrow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Timezones

# How does Marrow handle time zones?

Marrow stores and exposes dates in two common ways:

* **Business dates (`DATE`)** — Calendar days such as order date or report date follow the **marketplace or store local time zone** when the source is marketplace-based. For Amazon, that means each marketplace’s local zone (see the table below). For Shoplazza, analytics and day boundaries follow the **shop time zone** when available.
* **Timestamps (`DATETIME`)** — Date-time values are stored in **UTC**. They may not match your laptop’s local zone or a marketplace’s local zone.
* **`_synced_at`** — When Marrow last wrote or updated the row. This is a sync metadata timestamp in UTC, not a business event time.

You can confirm column types and meanings in **Data Schema**.

## What time zones does Marrow use for each Amazon marketplace?

Marrow uses these IANA time zones when interpreting Amazon marketplace-local days and scheduling marketplace-aligned syncs (about **2:00 local**). Unlisted marketplaces fall back to `Etc/UTC`.

| Amazon marketplace country | Amazon marketplace ID | Marrow time zone      |
| -------------------------- | --------------------- | --------------------- |
| Canada                     | `A2EUQ1WTGCTBG2`      | `America/Toronto`     |
| United States              | `ATVPDKIKX0DER`       | `America/Los_Angeles` |
| Mexico                     | `A1AM78C64UM0Y8`      | `America/Mexico_City` |
| Brazil                     | `A2Q3Y263D00KWC`      | `America/Sao_Paulo`   |
| Ireland                    | `A28R8C7NBKEWEA`      | `Europe/Dublin`       |
| Spain                      | `A1RKKUPIHCS9HS`      | `Europe/Madrid`       |
| United Kingdom             | `A1F83G8C2ARO7P`      | `Europe/London`       |
| France                     | `A13V1IB3VIYZZH`      | `Europe/Paris`        |
| Belgium                    | `AMEN7PMS3EDWL`       | `Europe/Brussels`     |
| Netherlands                | `A1805IZSGTT6HS`      | `Europe/Amsterdam`    |
| Germany                    | `A1PA6795UKMFR9`      | `Europe/Berlin`       |
| Italy                      | `APJ6JRA9NG5V4`       | `Europe/Rome`         |
| Sweden                     | `A2NODRKZP88ZB9`      | `Europe/Stockholm`    |
| South Africa               | `AE08WJ6YKNBMC`       | `Africa/Johannesburg` |
| Poland                     | `A1C3SOZRARQ6R3`      | `Europe/Warsaw`       |
| Egypt                      | `ARBP9OOSHTCHU`       | `Africa/Cairo`        |
| Turkey                     | `A33AVAJ2PDY3EV`      | `Europe/Istanbul`     |
| Saudi Arabia               | `A17E79C6D8DWNP`      | `Asia/Riyadh`         |
| United Arab Emirates       | `A2VIGQ35RCS4UG`      | `Asia/Dubai`          |
| India                      | `A21TJRUUN4KGV`       | `Asia/Kolkata`        |
| Singapore                  | `A19VAU5U5O7RUS`      | `Asia/Singapore`      |
| Australia                  | `A39IBJ37TRP1C6`      | `Australia/Sydney`    |
| Japan                      | `A1VC38T7YXB528`      | `Asia/Tokyo`          |

## Why do time zones matter?

A purchase at `2026-05-01T06:30:00` UTC is still **April 30** as a business date in `America/Los_Angeles` (PDT), but **May 1** in `America/New_York` (EDT).

If you compare “today’s orders” across marketplaces, or mix a UTC timestamp column with a marketplace `DATE` column, totals can disagree by a day near midnight. Prefer:

* Marketplace `DATE` columns when you want Seller Central–style daily totals
* UTC timestamps when you need an exact instant or are joining events across regions
* One chosen business time zone when you intentionally roll multi-marketplace data into a single calendar

## How do other platforms treat dates?

* **Amazon Ads** — Report dates follow Amazon’s reporting conventions for the profile/marketplace; treat daily metrics as business days for that ads profile, and use UTC for any full timestamps.
* **Google Ads, GA4, and Google Search Console** — Sync windows and many daily reports are planned on **UTC calendar days**. Convert or re-bucket if your team reports in a local zone.
* **Shoplazza** — Prefer the shop’s configured time zone for store-local daily analytics when the shop zone is set; otherwise expect UTC fallbacks.

## Related pages

* [Data Fetch Periods](./Data%20Fetch%20Periods.md) — daily sync timing and marketplace-local 2:00 pulls
* [Data Sources](./Data%20Sources.md) — where each platform’s data comes from
* Data Schema — full table and column reference in the product