Understanding Time Zones and Timestamps in Tai
Learn how Tai displays shipment times in the TMS and handles timestamps through the API and reports.
Overview
Tai displays timestamps differently depending on where you’re viewing them.
- Shipment stop times — such as pickup, delivery, and appointment times — are based on the local time zone of the stop.
- Shipment Activity Logs in the TMS — are displayed in the user’s local time zone.
- API timestamps — are provided in UTC.
- Location History — lets you switch between your time zone and the stop’s time zone.
- Custom Report date filters — use UTC day boundaries, which can cause report dates to differ from the dates shown on shipment details.
- In the TMS: Activity Logs are displayed in the user’s local time zone.
- Through the API: Activity Log timestamps are provided in UTC.
- Other API time fields: Include the applicable time zone information so integrations can correctly interpret the timestamp.
- Your time zone — displays timestamps according to your local time zone.
- Stop’s time zone — displays timestamps according to the local time zone of the shipment stop.
Understanding these differences can help prevent confusion when comparing shipment times across the TMS, API, and reports.
Shipment Stop Times
Where to go: Shipment Details and Location History
Pickup, delivery, and appointment times are displayed according to the local time zone of the shipment stop.
Each timestamp includes a time zone offset, such as -08:00, so you can identify the time zone associated with the displayed time.
For example, if a delivery appointment is scheduled for 10:00 AM at a facility in California, Tai displays the appointment according to the facility’s local time zone, regardless of where you are located.
Activity Logs and API Timestamps
Activity Logs use different time zone conventions depending on where you’re viewing them.
For example, an Activity Log event may appear as your local time in the TMS but be returned as a UTC timestamp through the API.
When working with API data, use the timestamp and its associated time zone information rather than assuming it represents a specific local time zone.
Location History Time Zone Toggle
Where to go: Location History
Location History allows you to switch between:
Use your time zone when comparing events across multiple locations from a consistent perspective.
Use the stop’s time zone when coordinating with a facility or confirming when an event occurred at the shipment location.
Custom Report Date Filters
Where to go: Reports > Manage Custom Reports
Custom Report date filters and date columns use UTC day boundaries, rather than the local time zone of the shipment stop.
As a result, a shipment or event that occurs late at night in the stop’s local time may appear under a different calendar date in a Custom Report.
For example, an event that occurs late in the evening at a stop may fall on the following UTC date and therefore appear under the next day when filtered or grouped in a report.
This is expected behavior and does not change the actual shipment or event time.
Frequently Asked Questions
Can I see shipment times in my own time zone?
Yes. In Location History and other supported views, use the time zone toggle to switch between your time zone and the stop’s local time zone.
How do I know which time zone a shipment time uses?
Shipment stop times include a time zone offset, such as -08:00, alongside the timestamp.
Why would I use the stop’s time zone instead of my own?
The stop’s time zone reflects the local time at the shipment location. This is generally the most useful view when coordinating with a facility or confirming an appointment.
Why does an Activity Log show a different time in the API?
Activity Logs in the TMS are displayed in the user’s local time, while Activity Log timestamps retrieved through the API are provided in UTC.
Why does a report show a different date than the shipment page?
Custom Report date filters and date columns use UTC day boundaries. An event near midnight in the stop’s local time may therefore fall on a different calendar date in the report.
Applies to: Shipment tracking, shipment stop times, Location History, Activity Logs, Custom Reports, and API time fields
Last updated: August 18, 2026
Suggested category: Shipments
Suggested tags: time zone, UTC, local time, shipment stops, time zone offset, appointment times