Timezones
Managing shipments across multiple regions means handling data in different timezones. Splice Exports is designed to keep time references consistent, reliable, and transparent. This article explains how timestamps are stored, displayed, and shared across the system.
How Splice Handles Timezones
-
All timestamps are stored in UTC.
This is intentional. It avoids confusion caused by daylight savings, regional adjustments, and provides a single universal reference. -
When possible, timestamps are displayed in the port or terminal’s local timezone.
For example, if a booking is tied to a departure from Savannah, timestamps related to that event will display in Eastern Time. If it’s from Vancouver, they will display in Pacific Time. -
Timezone labels are always shown in the UI.
Next to any displayed timestamp, the local timezone is identified, so you always know both the time and the place. -
Webhooks default to UTC.
When sending timestamps via webhook, Splice Exports provides times in UTC unless otherwise specified in your integration.
Benefits of UTC Standardization
| Benefit | Why It Matters |
|---|---|
| No Daylight Savings Issues | Eliminates confusion when countries shift their clocks at different times of year. |
| Consistent Data | A single reference point for all customers, systems, and integrations. |
| Clear Local Context | Port-based timezone display helps you understand exactly when an event occurs. |
| Reliable Automation | API and webhook integrations always receive timestamps in a predictable format. |
Example
-
A vessel departs Savannah, GA at 2025-08-22 15:00 EDT.
-
Splice stores this event as 2025-08-22 19:00 UTC.
-
In the UI, you see: 8/22/25, 3:00 PM (America/New_York).
-
In a webhook payload, the timestamp is sent as: 2025-08-22T19:00:00.000Z (UTC).
Need Help?
If you require timestamps in a different format for your integration or reporting, contact support@splice-it.com to configure custom settings.