# Data Exports

## 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.

<table><thead><tr><th width="150">Column</th><th>Title</th><th>Description</th></tr></thead><tbody><tr><td>A</td><td>client</td><td>Client of the tracking in internal encoding.</td></tr><tr><td>B</td><td>courier</td><td>Short code of the carrier.</td></tr><tr><td>C</td><td>service_level</td><td>Product or service level from carrier.</td></tr><tr><td>D</td><td>tracking_number</td><td>Unique tracking number.</td></tr><tr><td>E</td><td>order_number</td><td>Order number.</td></tr><tr><td>F</td><td>delivery_number</td><td>Internal delivery number.</td></tr><tr><td>G</td><td>transport_number</td><td>Transport number.</td></tr><tr><td>H</td><td>consignment_number</td><td>Consignment number.</td></tr><tr><td>I</td><td>destination_country</td><td>Destination country (for example: <code>DEU</code> or <code>DE</code>).</td></tr><tr><td>J</td><td>region</td><td>Destination region (for example: <code>DE-BE</code> or <code>DE-NW</code>).</td></tr><tr><td>K</td><td>zip_code</td><td>Zip code.</td></tr><tr><td>L</td><td>city</td><td>City of delivery.</td></tr><tr><td>M</td><td>customer_number</td><td>Internal customer number.</td></tr><tr><td>N</td><td>recipient</td><td>Name of the recipient used in the App.</td></tr><tr><td>O</td><td>warehouse</td><td>Warehouse the delivery was shipped from.</td></tr><tr><td>P</td><td>created_date</td><td>Date when data has been transmitted from the shop to parcelLab (<code>YYYY-MM-DD</code>).</td></tr><tr><td>Q</td><td>created_time</td><td>Date when data has been transmitted from the shop to parcelLab (<code>HH:mm:ss</code>).</td></tr><tr><td>R</td><td>order_date</td><td>Date when the order has been created (<code>YYYY-MM-DD</code>). This is provided by the shop. </td></tr><tr><td>S</td><td>order_time</td><td>Date when the order has been created (<code>HH:mm:ss</code>). This is provided by the shop. </td></tr><tr><td>T</td><td>pickup_scheduled_date</td><td>EDI-transmission from shop to carrier. This is the date when the tracking number was announced (<code>YYYY-MM-DD</code>). This falls back to "inbound scan on" if not given explicitly.</td></tr><tr><td>U</td><td>pickup_scheduled_time</td><td>EDI-transmission from shop to carrier. This is the timestamp when the tracking number was announced (<code>HH:mm:ss</code>). This falls back to "inbound scan on" if not given explicitly. </td></tr><tr><td>V</td><td>announced_dispatch_date</td><td>The announced dispatch date as defined by the shop (<code>YYYY-MM-DD</code>).</td></tr><tr><td>W</td><td>announced_dispatch_time</td><td>The announced dispatch time as defined by the shop (<code>HH:mm:ss</code>).</td></tr><tr><td>X</td><td>inbound_scan_date</td><td>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 (<code>YYYY-MM-DD</code>).</td></tr><tr><td>Y</td><td>inbound_scan_time</td><td>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 (<code>HH:mm:ss</code>).</td></tr><tr><td>Z</td><td>qualified_delivery_attempt_date</td><td>Date of any qualified delivery attempt by the carrier (<code>YYYY-MM-DD</code>). 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.</td></tr><tr><td>AA</td><td>qualified_delivery_attempt_time</td><td>Time of any qualified delivery attempt by the carrier (<code>HH:mm:ss</code>). 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.</td></tr><tr><td>AB</td><td>delivery_date</td><td>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 (<code>YYYY-MM-DD</code>).</td></tr><tr><td>AC</td><td>delivery_time</td><td>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 (<code>HH:mm:ss</code>).</td></tr><tr><td>AD</td><td>lead_time</td><td>Time between "Pick-up scheduled on" until "Delivered on" in days.</td></tr><tr><td>AE</td><td>lead_time_delivery_attempt</td><td>Time between "Pick-up scheduled on" until "Qualified delivery attempt on" in days.</td></tr><tr><td>AF</td><td>lead_time_courier</td><td>Time between "Inbound scan on" until "Qualified delivery attempt on" in days.</td></tr><tr><td>AG</td><td>lead_time_since_order</td><td>Time between "Ordered on" until "Qualified delivery attempt on" in days.</td></tr><tr><td>AH</td><td>lead_time_inbound_scan</td><td>Time between "Pick-up scheduled on" until "Inbound scan on" in days.</td></tr><tr><td>AI</td><td>delta_between_announced_and_actual_dispatch</td><td>Time between "Announced dispatch" and "Inbound scan on" in days.</td></tr><tr><td>AJ</td><td>is_returned</td><td>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 (<code>TRUE</code> or empty).</td></tr><tr><td>AK</td><td>sla_exceeded</td><td>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 (<a href="../../../engage/customer-service/watchlist#service-level-agreement-sla-defaults">default times</a>) (<code>TRUE</code> or empty).</td></tr><tr><td>AL</td><td>dispatch_delayed</td><td>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 (<code>TRUE</code> or empty).</td></tr><tr><td>AM</td><td>delivery_location</td><td>Delivery location in case of a successful delivery (list of delivery locations).</td></tr><tr><td>AN</td><td>exceptions</td><td>Problem reports of the carriers are analyzed and assigned to problem categories (<a href="../logistics-analysis#delivery-problems">list of categories</a>).</td></tr><tr><td>AO</td><td>return</td><td>If <code>TRUE</code>, the delivery is a return.</td></tr><tr><td>AP</td><td>invalid</td><td>If <code>TRUE</code>, we could not find this tracking number in the carrier's database and thus we were not able to track this shipment.</td></tr><tr><td>AQ</td><td>forgotten</td><td>If <code>TRUE</code>, 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.</td></tr><tr><td>AR</td><td>cancelled</td><td>If <code>TRUE</code>, the delivery is cancelled.</td></tr><tr><td>AS</td><td>complete</td><td>If <code>TRUE</code>, the order is identified as complete. This means that no articles are pending and yet to be shipped.</td></tr><tr><td>AT</td><td>upgrade (deprecated)</td><td>If <code>TRUE</code>, the shipment has an upgrade/custom processing.<br><strong>Note:</strong> This field is no longer in use.</td></tr><tr><td>AU</td><td>branch_delivery</td><td>If <code>TRUE</code>, the shipment is delivered to the retailer’s store (that is: click and collect).</td></tr><tr><td>AV</td><td>delayed</td><td>If <code>TRUE</code>, the shipment is delayed in transit.</td></tr><tr><td>AW</td><td>failed_attempt</td><td>If <code>TRUE</code>, the carrier tried to deliver the parcel to the recipient but was unsuccessful.</td></tr><tr><td>AX</td><td>exceptions</td><td>If <code>TRUE</code>, there was an issue with the delivery and it could not be performed.</td></tr><tr><td>AY</td><td>customer_promise_exceeded</td><td>If <code>TRUE</code>, the delivery date promise given to the end-customer was exceeded.</td></tr><tr><td>AZ</td><td>is_returns_portal</td><td>If <code>TRUE</code>, the tracking was created via the parcelLab Returns Portal.</td></tr><tr><td>BA</td><td>return_reason</td><td>The reason for returning a specific article.</td></tr><tr><td>BB</td><td>claim_reason</td><td>The reason why a tracking was marked as claimed (for example: lost in transit).</td></tr><tr><td>BC</td><td>current_stage</td><td>The high-level stage in the delivery journey of the parcel (for example: last mile)</td></tr><tr><td>BD</td><td>cash_on_delivery</td><td>The cash on delivery amount, if applicable.</td></tr></tbody></table>

{% file src="<https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2FajhnTWukJCsdzfK4TooC%2Ftrackings_2025-04-01_to_2025-04-04.csv?alt=media&token=e0bd6839-35f9-4dec-88ab-124c622b3ef1>" %}
Sample Trackings Export
{% endfile %}

{% hint style="info" %}
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).
{% endhint %}

### 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.&#x20;
9. Click **Load** to proceed.&#x20;
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).

## 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). |

{% file src="<https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LPf1Lv1YUuLYva6LrXQ%2F-Mctawl8ODiZa5g_vqac%2F-McxFd0ZrgCxqjGMoAt0%2Femails_2021-06-01_to_2021-06-30.csv?alt=media&token=f789ce97-6615-4c0a-af1a-df4df307e931>" %}
Sample Emails Export
{% endfile %}

## 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.

{% hint style="info" %}
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.
{% endhint %}

To request the report, please specify:

* Whether you want to receive it daily or weekly.&#x20;
  * 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:

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

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.

{% content-ref url="../../engage/customer-service/watchlist" %}
[watchlist](https://docs.parcellab.com/docs/engage/customer-service/watchlist)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.parcellab.com/docs/platform/overview/data-exports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.