Created Date/Time is after the first Delivery Tracking Update [Information]

Modified on Wed, 10 Dec at 4:05 PM

When reviewing tracking details in techTRACK, users may notice that the Created on timestamp appears later than the first carrier tracking update (e.g., "Label Created").


This article explains the technical reasons why the techTRACK creation date may differ from the initial carrier events.

 

NOTE: The Created on field is only visible to users who are logged in. If you are accessing the page as a guest, this field is hidden. 

 

In some cases, the Label Created event appears chronologically earlier than the creation date. Consider a tracking number with the following details: 

  • Created on: March 11th, 11:26 PM
  • Label Created: March 11th, 06:18 PM


In this scenario, the label was created several hours before the tracking record was officially generated in techTRACK.



There are two primary reasons why the Created on date may appear chronologically after the first tracking event:

  1. Timezone Differences:
    techTRACK records the Created on timestamp using the UTC timezone. When the system receives tracking information from techSHIP or another source, it logs the current server time in UTC. In contrast, carrier events (such as "Label Created" or "Picked Up") are often displayed in the local time of the event location. This timezone difference can cause the creation time to appear later than the event time, even if they occurred simultaneously.
     
  2. Data Synchronization Latency
    A carrier may physically record events before the tracking record is created in techTRACK.

    For example, a label may be generated and scanned by the carrier ("Label Created") hours before the data is transmitted to and processed by techTRACK. The system generates the Created on timestamp only when the record is successfully created in the database, not when the label was physically printed.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article