How does DataDoe handle time zones?
Dates in columns with the DATE type, such as date, always use the marketplace's local time zone. The table below shows the time zone for each marketplace.
Dates stored with the DATETIME type use UTC. This may be different from the marketplace's local time zone and the user's local time zone.
Which date columns should I use for order data?
The amazon_order_items_with_cogs table has three date-related columns. The table below shows which column to use for different tasks.
| Column | Type | Meaning |
|---|---|---|
date | DATE | Purchase date in the marketplace's local time zone. See the table below for the time zone used by each marketplace. |
order_date | DATE | This is a copy of the date column made for easier aggregation of orders with settlement tables. Prefer using the original date column. |
order_purchased_at_utc | DATETIME | Date and time of purchase in UTC. |
You can check all column definitions in the Data Scheme reference.
What time zones does DataDoe use for each marketplace?
The table below shows the time zone DataDoe uses for each Amazon marketplace.
| Amazon marketplace country | Amazon marketplace ID | DataDoe time zone |
|---|---|---|
| Canada | A2EUQ1WTGCTBG2 | America/Los_Angeles |
| 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?
An order with an order_purchased_at_utc value of 2026-05-01T06:30:00Z has a date of 2026-04-30 in the America/Los_Angeles (PDT) time zone, but a date of 2026-05-01 in the America/New_York (EDT) time zone. Depending on the user's location and geographic exposure, you may need to normalise data to a specific time zone.
Related pages
- Data Fetch Periods - when daily order data is refreshed.
- Data Sources - where order data comes from.
- Data Scheme - full table and column reference.