Skip to main content

​
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.

​
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.
  • Data Fetch Periods — daily sync timing and marketplace-local 2:00 pulls
  • Data Sources — where each platform’s data comes from
  • Data Schema — full table and column reference in the product