Below is a detailed breakdown of the file format:
Table 3. PTS File Format
Column Number |
Column Name |
Column Length |
Mandatory (Y/N)? |
Data Type |
Description |
---|---|---|---|---|---|
1 |
|
255 |
Y |
Text |
Metapack generic parcel status. Refer to Metapack's parcel status codes. |
2 |
|
11 |
Y |
Numeric |
Metapack generic parcel status ID (internal use only). Refer to Metapack's parcel status codes. |
3 |
|
255 |
N |
Text/Numeric |
Additional text provided by the carrier, e.g. 'Out for Delivery'. |
4 |
|
255 |
N |
Text/Numeric |
Carrier status code. |
5 |
|
255 |
N |
Text/Numeric |
Carrier reason code. |
6 |
|
255 |
N |
Text/Numeric |
|
7 |
|
255 |
Y |
Text/Numeric |
Metapack parcel code. |
8 |
|
255 |
Y |
Numeric |
ID of parcel in Metapack system (internal use only). |
9 |
|
255 |
N |
Text/Numeric |
|
10 |
|
255 |
Y |
Text/Numeric |
Metapack carrier consignment code. |
11 |
|
255 |
Y |
Text/Numeric |
Metapack internal carrier code. |
12 |
|
255 |
Y |
Text/Numeric |
Matching code of the consignment (internal use only). |
13 |
|
Y |
Date/Time |
The date and time of the status in the time zone specified in column 25. |
|
14 |
|
Y |
Date/Time |
Performance metric (internal use only). |
|
15 |
|
Y |
Date/Time |
Date/time when the status was initially processed. |
|
16 |
|
Y |
Date/Time |
Date/time when the status was initially processed. |
|
17 |
|
255 |
N |
Text/Numeric |
Destination postcode of the consignment. |
18 |
|
11 |
Y |
Numeric |
Transaction type of the consignment (e.g. delivery/pickup). |
19 |
|
255 |
Y |
Text |
Destination country code of the consignment. |
20 |
|
255 |
Y |
Text/Numeric |
System code (internal use only). |
21 |
|
11 |
Y |
Numeric |
Metapack retailer ID. |
22 |
|
255 |
Y |
Text/Numeric |
Retailer key (internal use only). |
23 |
|
255 |
Y |
Text/Numeric |
Metapack internal carrier service code. |
24 |
|
255 |
Y |
Text/Numeric |
Order reference for the consignment. |
25 |
|
255 |
Y |
Text |
|
26 |
|
N |
Date/Time |
Completed date and time of the consignment (i.e. when the final status is achieved in the time zone specified in column 25). |
Notes
-
Each PTS file is generated with a header record.
-
The information provided can vary by carrier - e.g. DepotAchievingStatus could be either a numeric or text value.
-
Empty fields should be expected - e.g. a carrier may not provide Metapack with a DepotAchievingStatus.
-
MatchedDateTime
,NotifiedBySourceDateTime
andProcessedDateTime
are always provided in the London/Europe time zone. -
AchievedDateTime
andTrackableItemCompletedDate
are linked to the AchievedTimeZone where provided. If the carrier does not provide the AchievedTimeZone, then PTS assumes that the time zone is the same as that of the origin or destination of the shipment, depending on the status. For example, a “Delivered” status will always cause the time zone of the destination to be used, whereas an “In transit” status will always cause the time zone of the origin to be used (regardless of where the actual scan took place).