ETA in API result is off by 23+ hours because of time zone error about shippo-php-client HOT 6 OPEN

Thanks for reporting this issue! Our team is actively investigating the UPS tracking timezones. It does look like the API incorrectly returns UTC in some cases, instead of the corresponding locations' local timezone. We have prioritized this as a high priority bug and will provide updates here as soon as we know more.

from shippo-php-client.

@simonkreuz has there been any progress on this issue?

from shippo-php-client.

So we have plans on improving the datetimes that are being returned for tracking events soon. We are just wanting to solidify instances where a carrier doesn't provide any location or timezone information for a given event, and how best to clarify that via the API.

We're always happy to hear input on this as we're working or improve what you get back.

from shippo-php-client.

Is there an update on this one?

from shippo-php-client.

Yes - we've made a lot of progress! As an example, try using UPS tracking number 1Z306A440213992774. The Delivered event, for instance, is shown by UPS as "Tuesday, 11/21/2017 at 7:19 P.M" in San Francisco CA. Our API now correctly returns this event with a status_date of 2017-11-22T03:19:00Z.

Some additional notes:

• Each carrier has a different way of handling timezone & location information. FedEx, for instance, always returns the time in UTZ, which is great. UPS and USPS always return local time. To get to the accurate timezone we look at several datapoints, including the location returned (e.g. city & zip). The more information we get the better.
• In some cases, based on the data provided by the carrier, it's not possible to determine the timezone. We use additional logic to infer the timezone, if possible. However, there will be some cases that don't have an accurate timezone.

from shippo-php-client.

Thanks for the update @simonkreuz!

from shippo-php-client.