Supply Chain Delivery Delay Logs

This dataset provides detailed logs of global supply chain delivery events, including shipment details, scheduled and actual delivery dates, delay durations, reasons for delays, and anomalies encountered. It is ideal for machine learning applications in delay prediction, risk assessment, and supply chain optimization, offering granular insights into operational bottlenecks and logistics performance.

  • opened 15 times
  • last updated 20 Aug 2025
  • by GoMask
The brief that made it

Machine learning for delivery delay prediction

Sample rows

preview · 8 of 200 rows · all 29 columns
delivery_event_idstringtransport_modestringshipment_volume_m3floatanomaly_detectedbooleanorigin_statestringshipment_idstringorder_idstringcarrier_namestringorigin_street_addressstringorigin_citystringorigin_postal_codestringorigin_countrystringdestination_street_addressstringdestination_citystringdestination_statestringdestination_postal_codestringdestination_countrystringscheduled_delivery_datedateactual_delivery_datedatedelay_duration_hoursfloatdelay_reasonstringdelay_severitystringanomaly_typestringreported_bystringevent_created_datetimedatetimeshipment_weight_kgfloattemperature_controlledbooleanhigh_value_goodsbooleancustoms_clearance_requiredboolean
DEL-00000001air6.2falseHESHIP-0101ORD-1234DHL Express11 HauptstrasseFrankfurt60311Germany200 Queen StTorontoONM5V2B6Canada2024-04-072024-04-0824weatherminornoneblank2024-04-07T10:23:00450.3falsetruetrue
DEL-00000002road0.022falseblankSHIP-0202blankFedEx25 Rue LafayetteParis75009France18 Oxford StLondonLondonW1D1BSUK2024-04-082024-04-080blanknonenoneblank2024-04-08T08:19:003.55falsefalsefalse
DEL-00000003sea200.7falseblankSHIP-0303ORD-3456Maersk88 Zhongshan RdShanghai200001China100 Pier 70 BlvdSan FranciscoCA94107USA2024-04-102024-04-1496customscriticalnoneCustoms Agent SF2024-04-10T14:37:0018000.1falsetruetrue
DEL-00000004road0.009falseMerseysideSHIP-0202blankRoyal Mail15 Abbey RdLiverpoolL189ABUK33 Market StManchesterManchesterM11DNUK2024-04-062024-04-060blanknonenoneblank2024-04-06T09:13:000.12falsefalsefalse
DEL-00000005rail67.2trueblankSHIP-0404ORD-5678China Rail100 Beijing RdBeijing100000China7 Tverskaya StMoscowblank101000Russia2024-04-132024-04-1424mechanical_failureminordamaged_goodsStation Moscow2024-04-13T15:03:008000.5falsetruetrue
DEL-00000006road0.03falseILSHIP-0505ORD-9012Amazon Logistics502 Market StChicago60607USA1010 Elm StSt LouisMO63101USA2024-04-092024-04-090blanknonenoneblank2024-04-09T11:27:001.25falsefalsefalse
DEL-00000007road0.007falseMHSHIP-0606blankBlue Dart19 MG RoadMumbai400001India2 Residency RdBangaloreKA560025India2024-04-11blankblankblanknonenoneblank2024-04-11T12:44:000.62falsefalsefalse
DEL-00000008sea190.1falseblankSHIP-0404blankCOSCO33 Xiamen PortXiamen361000China99 Yonge StTorontoONM5E1J3Canada2024-04-122024-04-1572customsseverenoneCustoms Toronto2024-04-12T17:08:0017500.9truetruetrue

What the 200 rows show

from the 200-row sample

Sea (transport mode) stands out: mean shipment_volume_m3 is 213.1, against 16.8 for the rest.

  • 12%anomaly_detected = true
  • 0.08median shipment_volume_m3
  • 5delay severities
  • 5anomaly types
  • 6delay reasons
  • 16carrier names
Mean shipment_volume_m3 by transport_mode200 rows
02004007.7air28 rows213.1sea36 rows0.02road105 rows82.0rail31 rows
shipment_volume_m3200 rows, in bands of 50
075150143134142240150300shipment_volume_m3 →

Median 0.08, from 0.00 to 259.8.

origin_state89 rows with a value · 111 left blank
  1. CA9
  2. Greater London8
  3. MH5
  4. NSW5
  5. HE4
  6. BE4
  7. Berlin4
  8. Merseyside3
  9. IL3
  10. NY3
29 columns by typefrom the column list below
  • string 19
  • float 3
  • date 2
  • datetime 1
  • boolean 4

Columns

29 columns in four groups
blueprint · 29 columns
columntypedescriptionexample
Text 19 columns
delivery_event_idstringUnique identifier for each delivery event in the supply chain.uniqueDEL-00000001
shipment_idstringIdentifier for the shipment associated with the delivery event.SHIP-0101
order_idstringIdentifier for the customer order linked to the shipment.optionalORD-1234
carrier_namestringName of the logistics carrier responsible for the delivery.DHL Express
origin_street_addressstringStreet address of the shipment origin.11 Hauptstrasse
origin_citystringCity of the shipment origin.Frankfurt
origin_statestringState or region of the shipment origin.optionalHE
origin_postal_codestringPostal code of the shipment origin.optional60311
origin_countrystringCountry of the shipment origin.Germany
destination_street_addressstringStreet address of the shipment destination.200 Queen St
destination_citystringCity of the shipment destination.Toronto
destination_statestringState or region of the shipment destination.optionalON
destination_postal_codestringPostal code of the shipment destination.optionalM5V2B6
destination_countrystringCountry of the shipment destination.Canada
delay_reasonstringPrimary reason for the delivery delay (e.g., weather, customs, traffic, mechanical failure).7 values · optionalweather
delay_severitystringSeverity level of the delay.none · minor · moderate · severe · critical · optionalminor
anomaly_typestringType of anomaly detected (if any).6 values · optionalnone
reported_bystringName or identifier of the person or system reporting the delay/anomaly.optionalCustoms Agent SF
transport_modestringMode of transportation used for the shipment.air · sea · road · rail · multimodalair
Numbers 3 columns
delay_duration_hoursfloatNumber of hours the delivery was delayed compared to the scheduled date.0 or more · optional24
shipment_weight_kgfloatWeight of the shipment in kilograms.0 or more · optional450.3
shipment_volume_m3floatVolume of the shipment in cubic meters.0 or more · optional6.2
Dates and times 3 columns
scheduled_delivery_datedatePlanned date for delivery to the destination.2024-04-07
actual_delivery_datedateActual date when the delivery was completed.optional2024-04-08
event_created_datetimedatetimeTimestamp when the delivery event was logged in the system.2024-04-07T10:23:00
True or false 4 columns
anomaly_detectedbooleanIndicates if an anomaly was detected during the delivery event.false
temperature_controlledbooleanIndicates if the shipment required temperature control.optionalfalse
high_value_goodsbooleanIndicates if the shipment contains high-value goods.optionaltrue
customs_clearance_requiredbooleanIndicates if customs clearance was required for the shipment.optionaltrue

15 SQL practice questions for the Supply Chain Delivery Delay Logs

Written for this data and checked against it: 12 SQL and 3 Power BI exercises from beginner to advanced. Try the first three free; the practice kit has all 15, a starter .sql file and an answer key with every expected result.

  1. 01BeginnerFreeSELECT · WHERE · ORDER BY

    Severe and critical delays

    Return delivery_event_id, carrier_name, delay_duration_hours and delay_severity for every event whose delay_severity is 'severe' or 'critical'. Order the results by delay_duration_hours from highest to lowest, then by delivery_event_id ascending.

    Tables: supply_chain_delivery_delay_logs · your result: 4 columns, 29 rows
  2. 02BeginnerFreeDISTINCT · WHERE · NULL

    Distinct delay reasons

    Return each distinct delay_reason that is not null, in a single column named delay_reason, sorted alphabetically.

    Tables: supply_chain_delivery_delay_logs · your result: 1 columns, 6 rows
  3. 03BeginnerFreeGROUP BY · COUNT

    Events per transport mode

    Count the events for each transport_mode. Return transport_mode and event_count, ordered by event_count from highest to lowest, then by transport_mode alphabetically.

    Tables: supply_chain_delivery_delay_logs · your result: 2 columns, 4 rows
  1. 04Average delay by carrierBeginner
  2. 05Power BI: events by anomaly typePower BI
  3. 06Reasons with many delaysIntermediate
  4. 07Weight class bucketsIntermediate
  5. 08Carriers slower than overallIntermediate
  6. 09Monthly delayed eventsIntermediate
  7. 10Power BI: delay rate measurePower BI
  8. 11Rank carriers by delayAdvanced
  9. 12Gap to previous shipment eventAdvanced
  10. 13Running delay hours by monthAdvanced
  11. 14Share of delay hours by reasonAdvanced
  12. 15Power BI: top event per carrierPower BI

Get the practice kit: the full dataset, all 15 exercises, a starter .sql and the answer key. One-time $3.99.

Get the practice kit · $3.99

Use it for

  • anomaly detect…12%24 of 200 rowsmean shipment volume …7.7air213.1sea0.02road82.0rail

    A logistics dashboard

    The anomaly_detected rate, shipment_volume_m3 by transport_mode and a breakdown of origin_state. Excel, Power BI or Tableau.

  • Why do the 36 sea rows have a mean shipment_volume_m3 of 213.1?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable delivery events with shipment_id, order_id and carrier_name to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 29 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 rows29 columns
Yours1,000 rows29 columnsorigin_street_address: UK only

blueprint · supply-chain-delivery-delay-logs

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 29 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
  • Track origin and destination nodes
  • Label delivery events with delay reason
  • Include real-world disruption patterns
  • Multi-modal carrier simulation
  • Temporal features for holiday/peak effects
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
supply-chain-delivery-delay-logs

What should your data show?

Preview 20 rows free
No signup. No card.