Data Exports

Set up and run data exports directly in the parcelLab App to get key insights into your operational processes.

Overview

The Data Exports functionality enables you to configure and run your own exports in the parcelLab App to export raw data, including trackings, communications, and returns, for reporting and monitoring purposes.

When setting up an export, you can choose which data should be exported and configure how the export should be run. The export settings allow you to apply filters, customize the file format and how the completed export should be delivered. Exports can be run manually when needed or scheduled to run automatically.

Take the Tour

Explore the data exports process with our interactive demo below.

Using Data Exports

This section describes the process of managing data exports in the parcelLab App.

You can access Data Exports from the Admin overview page or navigation pane to set up and run your exports.

You must have the Export Permissions role to access the Data Exports functionality.

The Data Exports page consists of the following tabs that can be accessed at the top of the page:

Export configurations

The Export configurations tab lists the exports for your account.

From the Export configurations tab, you can:

• Add and update export configurations with the required data source, columns to include, filters, and file settings
• Run export configurations on demand
• Schedule exports configurations to run automatically at defined times
• Choose how export files are delivered (download files from the App or send them by email or SFTP, where available)
• Control whether an export configuration can run
• Archive export configurations that are no longer in use while retaining their previous export runs

Export runs

The Export runs tab provides a history of generated exports.

From the Export runs tab, you can:

• View run details to check the status of an export and troubleshoot any issues
• Download export files from completed runs
• Rerun export configurations
• Restore archived export configurations to use them again

Check out the parcelLab guides

For further information on configuring data exports, see our user guide documentation.

Requesting Data Exports

Exports of raw tracking and communication data can be also requested via the parcelLab App. The link to download the export will be sent to the email address written in the email address input field.

Trackings Export

The trackings export provides you with the raw data of your trackings. Each row in the trackings export represents a tracking in the parcelLab system. The information in each row is described in the following table.

Column	Title	Description
A	client	Client of the tracking in internal encoding.
B	courier	Short code of the carrier.
C	service_level	Product or service level from carrier.
D	tracking_number	Unique tracking number.
E	order_number	Order number.
F	delivery_number	Internal delivery number.
G	transport_number	Transport number.
H	consignment_number	Consignment number.
I	destination_country	Destination country (for example: DEU or DE).
J	region	Destination region (for example: DE-BE or DE-NW).
K	zip_code	Zip code.
L	city	City of delivery.
M	customer_number	Internal customer number.
N	recipient	Name of the recipient used in the App.
O	warehouse	Warehouse the delivery was shipped from.
P	created_date	Date when data has been transmitted from the shop to parcelLab (YYYY-MM-DD).
Q	created_time	Date when data has been transmitted from the shop to parcelLab (HH:mm:ss).
R	order_date	Date when the order has been created (YYYY-MM-DD). This is provided by the shop.
S	order_time	Date when the order has been created (HH:mm:ss). This is provided by the shop.
T	pickup_scheduled_date	EDI-transmission from shop to carrier. This is the date when the tracking number was announced (YYYY-MM-DD). This falls back to "inbound scan on" if not given explicitly.
U	pickup_scheduled_time	EDI-transmission from shop to carrier. This is the timestamp when the tracking number was announced (HH:mm:ss). This falls back to "inbound scan on" if not given explicitly.
V	announced_dispatch_date	The announced dispatch date as defined by the shop (YYYY-MM-DD).
W	announced_dispatch_time	The announced dispatch time as defined by the shop (HH:mm:ss).
X	inbound_scan_date	The inbound scan of the carrier. This is the first real scan event in the carrier's network. This date also marks that the delivery was handed over to the carrier (YYYY-MM-DD).
Y	inbound_scan_time	The inbound scan of the carrier. This is the first real scan event in the carrier's network. This timestamp also marks that the delivery was handed over to the carrier (HH:mm:ss).
Z	qualified_delivery_attempt_date	Date of any qualified delivery attempt by the carrier (YYYY-MM-DD). For example: a failed attempt (rang the bell but nobody was there), a left notification card, or delivery available for collection in parcel shop. This falls back to "delivered on", if successfully delivered directly on the first attempt.
AA	qualified_delivery_attempt_time	Time of any qualified delivery attempt by the carrier (HH:mm:ss). For example: a failed attempt (rang the bell but nobody was there), a left notification card, or delivery available for collection in parcel shop. This falls back to "delivered on", if successfully delivered directly on the first attempt.
AB	delivery_date	Date the delivery was successfully handed over to the recipient. For example: direct (doorstep) delivery, delivery has been collected from parcel shop, delivery to a neighbor, or delivery deposited at a safe place (YYYY-MM-DD).
AC	delivery_time	Time the delivery was successfully handed over to the recipient. For example: direct (doorstep) delivery, delivery has been collected from parcel shop, delivery to a neighbor, or delivery deposited at a safe place (HH:mm:ss).
AD	lead_time	Time between "Pick-up scheduled on" until "Delivered on" in days.
AE	lead_time_delivery_attempt	Time between "Pick-up scheduled on" until "Qualified delivery attempt on" in days.
AF	lead_time_courier	Time between "Inbound scan on" until "Qualified delivery attempt on" in days.
AG	lead_time_since_order	Time between "Ordered on" until "Qualified delivery attempt on" in days.
AH	lead_time_inbound_scan	Time between "Pick-up scheduled on" until "Inbound scan on" in days.
AI	delta_between_announced_and_actual_dispatch	Time between "Announced dispatch" and "Inbound scan on" in days.
AJ	is_returned	A shipment is confirmed to have not been delivered and the return has already been detected. This also recognizes shipments without an explicit return status report (TRUE or empty).
AK	sla_exceeded	A retroactive consideration once a package has been delivered. It compares "Runtime Carrier" with the configured SLA, which can be defined by destination country and carrier (default times) (TRUE or empty).
AL	dispatch_delayed	The shipment was not dispatched in time. We measure it by "on the way", where the key indicator is drawn either shipment-related via the field "send_date" or generalized via a construction like "Created on" + x hours (TRUE or empty).
AM	delivery_location	Delivery location in case of a successful delivery (list of delivery locations).
AN	exceptions	Problem reports of the carriers are analyzed and assigned to problem categories (list of categories).
AO	return	If TRUE, the delivery is a return.
AP	invalid	If TRUE, we could not find this tracking number in the carrier's database and thus we were not able to track this shipment.
AQ	forgotten	If TRUE, a shipment was created and registered at the carrier, but there was no inbound scan within the usual period of time, which means that the parcels did not arrive at the carrier. This may be because it was forgotten and not loaded, the bridge has stopped somewhere, or the label was damaged during the first transport.
AR	cancelled	If TRUE, the delivery is cancelled.
AS	complete	If TRUE, the order is identified as complete. This means that no articles are pending and yet to be shipped.
AT	upgrade (deprecated)	If TRUE, the shipment has an upgrade/custom processing. Note: This field is no longer in use.
AU	branch_delivery	If TRUE, the shipment is delivered to the retailer’s store (that is: click and collect).
AV	delayed	If TRUE, the shipment is delayed in transit.
AW	failed_attempt	If TRUE, the carrier tried to deliver the parcel to the recipient but was unsuccessful.
AX	exceptions	If TRUE, there was an issue with the delivery and it could not be performed.
AY	customer_promise_exceeded	If TRUE, the delivery date promise given to the end-customer was exceeded.
AZ	is_returns_portal	If TRUE, the tracking was created via the parcelLab Returns Portal.
BA	return_reason	The reason for returning a specific article.
BB	claim_reason	The reason why a tracking was marked as claimed (for example: lost in transit).
BC	current_stage	The high-level stage in the delivery journey of the parcel (for example: last mile)
BD	cash_on_delivery	The cash on delivery amount, if applicable.

trackings_2026-08-03_to_2026-08-18.csv

42KB

Open

Sample Trackings Export

Cells are only filled if data is available at the time of export creation (for example: a tracking that is not in transit at the time of export generation will not have data in the qualified_delivery_attempt_date field).

Emails Export

The emails export provides you with the raw data of your communication. Each row in the export represents a notification (for example: email) in the parcelLab system. The information in each row is described in the following table.

Column	Column Header	Description
A	tracking_number	Unique tracking number.
B	order_number	Order number.
C	courier	Short code of the carrier.
D	email_type	Type of sent email (for example: DispatchConfirmation or Delivered).
E	sent_date	Date when the email was sent (YYYY-MM-DD).
F	sent_time	Time when the email was send (HH:mm:ss).
G	first_opened_date	Date when the email was opened for the first time (YYYY-MM-DD).
H	first_opened_time	Time when the email was opened for the first time (HH:mm:ss).
I	opened_qty	Total amount of opens.
J	clicked_qty	Total amount of clicks.
K	platform	Platform used to open the email (for example: iPhone or Microsoft Windows).

emails_2021-06-01_to_2021-06-30.csv

2KB

Open

Sample Emails Export

How to Open Export Files with MS Excel

When opening files with Microsoft Excel, the program sometimes assumes the wrong character encoding instead of UTF-8, making non-ASCII characters and certain special characters unreadable.

To fix this simply do the following:

1. Create a blank worksheet or workbook.
2. In the menu bar, click Data.
3. Select Get Data. The Text Import Wizard will display, allowing you to choose a data source.
4. Select Text/CSV. This will allow you to import a text file.
5. Click Browse and select the export file you wish to view.
6. Click Next. A preview of your file data will appear in the Text Import Wizard.
7. In the File origin field, select Unicode (UTF-8).
8. In the Delimiter field, select Tab for .tsv and .xls files or Comma as delimiter for .csv files.
9. Click Load to proceed.
10. Finally, the format of certain columns might need to be adjusted (for example: select the Text format for the tracking_number column so that Excel does not mistakenly display long tracking numbers in scientific number notation).

Automated Exports

We can provide you with an automated monthly, weekly, or daily export of all your trackings for manual review or use with your own business intelligence system. The export will contain all new trackings added since the last report and include the information for each as defined above.

Exports can be customized to include either the information about trackings created in a specific time frame or tracking updates that we received in a specific time frame.

To request the report, please specify:

• Whether you want to receive it daily or weekly.

  • If weekly, whether you want to receive the trackings of the last week or a previous week.
• Whether you want to receive it as a .tsv , .xls or a .csv file
• How you want to receive the export.

Choose from the following supported transfer methods:

Transfer Method	How it Works	Required Details
Email	Sent as email attachments to specified recipients.	Recipient email addresses.
SFTP	Uploaded to your SFTP server using username and password authentication.	SFTP host, username, password (URL-encoded if needed), and an existing target directory. For exports sent to your SFTP server, parcelLab creates a lock file (for example: data-export.csv.lock with 0 bytes) so that other processes do not modify the file being uploaded. After the transfer is completed, the lock file is deleted.
parcelLab Hub	Delivered directly to your parcelLab Hub environment, with folders created automatically.	parcelLab Hub username and target folder name.
Azure Blob Storage	Uploaded to an Azure Blob Storage container using a SAS token.	Azure Blob Storage SAS token URL with required permissions.
Google Cloud Storage	Uploaded to a specified Google Cloud Storage bucket using a service account.	Bucket name and Google Cloud Storage access configuration.
Webhook	Sent as an HTTP POST request to a specified endpoint.	Destination URL to receive the POST request.
Google Sheets	Appended as new rows to a Google Sheet.	Google Sheet URL and editor access for parcelLab’s service account.

The daily exports are generated and sent in the early morning containing the trackings of the previous day. The weekly exports are sent on Monday morning.

You can also receive the daily watchlist report. This report is available only as a daily report and will contain all trackings for which a ticket was generated as described in the watchlist documentation.

Tracking Incident Statuses