Shipment Tracking Event Timeline

This dataset provides a comprehensive, event-level timeline for synthetic shipments across global supply chains, capturing detailed tracking events, statuses, and location data. It enables advanced logistics analytics, such as route optimization, delay analysis, and ETA prediction, making it ideal for supply chain visibility and performance monitoring.

  • last updated 12 Jul 2025
  • by GoMask
The brief that made it

Logistics route optimization and bottleneck identification

Sample rows

preview · 8 of 200 rows · all 19 columns
shipment_idstringstatusstringevent_typestringevent_idstringevent_timestampdatetimelocation_namestringlocation_street_addressstringlocation_citystringlocation_statestringlocation_postal_codestringlocation_countrystringlatitudefloatlongitudefloatcarrier_namestringvehicle_idstringestimated_arrival_datedateactual_arrival_datedatedelay_reasonstringnotesstring
SHIP102001in_transitpicked_upEVT-2024050210012024-05-02T08:14:22ZUPS Distribution Center1234 Commerce AveDallasTX75201USA32.7767-96.797UPSTX-UPS45672024-05-04blankblankPicked up by regional driver
SHIP102001in_transitarrived_at_hubEVT-2024050310022024-05-03T18:15:32ZUPS Houston Hub6000 West Loop SHoustonTX77081USA29.7604-95.3698UPSTX-UPS45672024-05-04blankblankblank
SHIP102001delivereddeliveredEVT-2024050410032024-05-04T09:42:11ZCustomer Residence482 Oakridge DrAustinTX78753USA30.2672-97.7431UPSTX-UPS45672024-05-042024-05-04blankDelivered to front door
SHIP102002in_transitpicked_upEVT-2024042710042024-04-27T11:25:45ZFedEx Ground Depot2100 Industrial BlvdMemphisTN38116USA35.1495-90.049FedExTN-FDXG12342024-04-29blankblankblank
SHIP102002delivereddeliveredEVT-2024042910052024-04-29T14:36:17ZSmith Electronics8900 Main StNashvilleTN37210USA36.1627-86.7816FedExTN-FDXG12342024-04-292024-04-29blankLeft at reception desk
SHIP102003in_transitpicked_upEVT-2024050710062024-05-07T07:10:58ZAmazon Fulfillment Center5000 S 5th StPhoenixAZ85040USA33.4484-112.074Amazon LogisticsAZ-AMZL21232024-05-10blankblankblank
SHIP102003in_transitarrived_at_hubEVT-2024050810072024-05-08T16:00:13ZAmazon Phoenix DC1200 S Central AvePhoenixAZ85007USA33.4484-112.074Amazon LogisticsAZ-AMZL21232024-05-10blankblankArrived at sorting hub
SHIP102003in_transitout_for_deliveryEVT-2024051010082024-05-10T11:30:00ZAmazon Van 2123On RoutePhoenixAZ85014USA33.4484-112.074Amazon LogisticsAZ-AMZL21232024-05-10blankblankOut for delivery

What the 200 rows show

from the 200-row sample
  • 14location countries
  • 15carrier names
status196 rows by value
0651302pendi…1%122in_tr…61%49deliv…25%8delay…4%12excep…6%3retur…2%
event_type196 rows with a value · 4 left blank
  1. picked_up72
  2. delivered49
  3. arrived_at_hub35
  4. exception12
  5. departed_hub10
  6. delayed8
  7. out_for_delivery5
  8. returned3
  9. in_transit2
19 columns by typefrom the column list below
  • string 14
  • float 2
  • date 2
  • datetime 1

Columns

19 columns in three groups
blueprint · 19 columns
columntypedescriptionexample
Text 14 columns
shipment_idstringUnique identifier for each shipment in the supply chain.SHIP102001
event_idstringUnique identifier for each tracking event.uniqueEVT-202405021001
event_typestringType of tracking event (e.g., picked_up, in_transit, arrived_at_hub, out_for_delivery, delivered, delayed, exception).9 valuespicked_up
statusstringCurrent status of the shipment at the time of the event (e.g., in_transit, delivered, delayed, exception).6 valuesin_transit
location_namestringName of the location where the event occurred (e.g., warehouse, city, hub).optionalUPS Distribution Center
location_street_addressstringStreet address of the event location.optional1234 Commerce Ave
location_citystringCity of the event location.optionalDallas
location_statestringState or region of the event location.optionalTX
location_postal_codestringPostal code of the event location.optional75201
location_countrystringCountry of the event location.optionalUSA
carrier_namestringName of the carrier or logistics provider handling the shipment at this event.optionalUPS
vehicle_idstringIdentifier for the vehicle (truck, van, etc.) involved in the event, if applicable.optionalTX-UPS4567
delay_reasonstringReason for delay, if the event_type or status indicates a delay or exception.optionalWeather disruption
notesstringAdditional notes or comments relevant to the tracking event.optionalDelivered to front door
Numbers 2 columns
latitudefloatLatitude coordinate of the event location.-90 to 90 · optional32.7767
longitudefloatLongitude coordinate of the event location.-180 to 180 · optional-96.797
Dates and times 3 columns
event_timestampdatetimeDate and time when the tracking event occurred.2024-05-02T08:14:22Z
estimated_arrival_datedateEstimated date of arrival at the next destination or final delivery.optional2024-05-04
actual_arrival_datedateActual date of arrival at the destination, if applicable.optional2024-05-04

Use it for

  • rows20019 columnsrows by status2pend…122in_t…49deli…8dela…

    A logistics dashboard

    A breakdown of event_type. Excel, Power BI or Tableau.

  • What pattern can you find in 200 rows?

    A class exercise

    Hand out the rows and one question. Everyone works from the same 200 rows.

  • A software demo

    Believable shipments with event_id, event_timestamp and event_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 19 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset200 rows19 columns
Yours1,000 rows19 columnslocation_name: UK only

blueprint · shipment-tracking-event-timeline

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 19 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each shipment has multiple event timestamps
  • Events: pickup, in-transit, customs, delivery
  • Status and location logged at each event
  • Delayed events flagged with reasons
  • All shipments have unique tracking IDs
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
shipment-tracking-event-timeline

What should your data show?

Preview 20 rows free
No signup. No card.