The Tracking File allows customer systems to be populated with tracking data. This data may be used to update order statuses, update internal reporting tools, trigger consumer messaging (SMS, email, etc.), or populate customer support tools.
-
The Tracking File collects tracking events for all labels created in Delivery Manager for all tracked carrier services, and translates them into 61 normalised sets of Parcel Status IDs and Parcel Status Names.
-
Tracking data is provided at a parcel level to allow for the mapping of both single and multi-parcel consignments.
-
The Tracking File contents can be configured to include certain data and to filter out events based on specific Parcel Status IDs, specific carriers and origin warehouses.
-
The Tracking File contains all new events for all live parcels (without an 'end-of-life' event) since the last file was generated.
-
The Tracking File can be generated at a time interval defined by the customer, e.g. every 15, 30 or 60 minutes. A file can be configured to be generated or cancelled when there are no carrier events to communicate.
-
Tracking Files are in CSV format with UTF8 encoding and can only be collected by Secure File Transfer Protocol (SFTP). Multiple Tracking Files can be set up for a third party and populated on a single SFTP user account.
In order to work effectively, the Tracking File has some configuration prerequisites:
-
The Customer must provide an IP address for whitelisting, so that this SFTP site can be accessed.
-
The Tracking File is only available to Metapack Shipping customers for shipments created on the Metapack platform.
-
Metapack is reliant on carriers for the timeliness and quality of the tracking data. Metapack will help identify issues and work with customers and carriers to resolve any tracking data quality issues.
Note
Click here to find out more about the Tracking File.