Search Help Contents:

 


 

Topics

Home

Getting Started

Data Types

Event Codes & References

Error Codes

Best Practices

Notifications

Version Policy

API Calls

 

Event Codes & References

Events

The Events request returns the same events as exp.o Visibility. An event consists of the following attributes when applicable:

  • Event Description

  • Event Time in UTC

  • Origin Name and Port Code

  • Destination Name and Port Code

  • Remarks

  • Invoice

  • Event Code

The specific events that are available via our shipment tracking API depend on the underlying services that Expeditors provides on any given shipment or customs declaration.  We refer to the events that occur in a typical shipment as “core events”.  For example, “freight received” is a core event.

 

However, not every core event applies to every shipment.  For example, “delivered to consignee” is a core event but would only apply if Expeditors is responsible for arranging the delivery of the shipment.  We strongly recommend contacting your local Expeditors representative to discuss the events that apply to your shipments while using the below list as a starting point: 

Event Code

Event Description

Event Definition

AFD

At Final Destination

At final destination port1

BKD

Booked

Estimated departure per leg

COB

Confirmed on Board

Actual departure per leg

DLV

Delivered to Consignee

Actual delivery to consignee door2

DLY

Shipment Delayed

-3

EDD

Est Arrival at Dest

Estimated arrival at final destination port

EDL

Est Delivery to Consignee

Estimated delivery to consignee door

ETA

Estimated Time of Arrival

Estimated arrival to port

FND

Freight Received No Docs

-

FRD

Freight Received w/Docs

-

POD

Proof of Delivery Rcvd

-

RDL

Requested Delivery Date

Requested delivery date to door

RLS

Import Customs Release

 -4

RTD

REQ TRNST TIME DEST

Requested arrival to final destination port

 

1. Like EDD further down the list, the AFD event is only provided if Expeditors is involved at the destination of the shipment.  Best practice is to use the ETA event unless an EDD event is available.

2. Like EDL and RDL, the DLV and POD events are included if Expeditors is responsible for arranging the delivery of the shipment.

3. The reason for the delay is found in the "remarks" field of the Type Event.

4. The RLS event is available if Expeditors acts as the import customs broker at destination.

 

References

The References request returns the following information for a single Shipment ID, if the reference is present on the shipment:

  • Reference Type

  • Reference Number

B#

Invoice Bill Number

EF

Entry File

QC

Quota Category

BF

Billing File

EN

Entry Number

 

Service Level

BN

 

Booking Number (Ocean)

FB

Onforward AWB/BL  

Service Type

C#

Consignee Code

FO

Factory Order Number

SF

US Customs ISF Number

CB

Customer Bill To Code/Name

HB

House AWB/BL

SH

Sub House Bill

CI

Commercial Invoice Number

IT

Immediate Transportation (In Bond) Number

SO

Sales Order

CN

Ultimate Consignee Name

LN

Export License Number

ST

Style Number

CO

Container Number

MB

Master AWB/BL

TP

Truck PRO Number

CR

Client Reference Number

MF

Manifest Number

TR

Trailer/Truck Number

CS

Client's Consignment Number

OM

OM Booking Number

UC

Unique Consignment Number

DC

Distribution Center

PJ

Project Number

VP

Vendor's Part Number

DP

Department

PL

Packing List Number

WE

Warehouse Entry Number

DR

Dist. Receipt Number

PO

Purchase Order

WO

Work order

DV

Division

PT

Part Number

XX

Other Trace

© 2024 Expeditors International of Washington, Inc.  

All information contained herein is business confidential and proprietary and may not be reproduced in any form without advanced

written consent of an authorized officer of the copyright holder.

 

EULA - End User License Agreement