# Tracker tracking status

## Core Tracking Statuses

### UNKNOWN

* When used: Default state when status cannot be definitively determined
* Typical triggers:
  * Invalid or unrecognized carrier scan codes
  * Missing tracking data
  * Initialization state before first scan
  * Data parsing errors from carrier API

### PENDING

* When used: Label/shipment created but not yet in carrier network
* Typical triggers:
  * Electronic shipping information sent to carrier
  * Label creation event
  * Manifested but not yet scanned
* Carrier events examples:
  * "Shipping Label Created"
  * "Electronic Notification Received"
  * "Shipment Information Received"

### PICKED\_UP

{% hint style="info" %}
Limited to a reduced list of carriers, most carriers don't have this status.
{% endhint %}

* When used: First physical scan by carrier when provided. It's rarely provided.
* Typical triggers:
  * Pickup scan at business/location
  * Drop-off scan at carrier location
  * First facility scan
* Carrier events examples:
  * "Picked Up"
  * "Accepted at Facility"
  * "Origin Scan"

### IN\_TRANSIT

* When used: Moving through carrier network
* Typical triggers:
  * Facility arrival scans
  * Departure scans
  * Movement between facilities
  * Customs processing
* Carrier events examples:
  * "Arrived at Facility"
  * "Departed Facility"
  * "In Transit"
  * "Processed at Facility"
  * "Customs Status Updated"
  * "Clearance Processing Complete"

### OUT\_FOR\_DELIVERY

* When used: On final delivery vehicle
* Typical triggers:
  * Morning departure scan from final facility
  * Loaded on delivery vehicle scan
* Carrier events examples:
  * "Out for Delivery"
  * "On Vehicle for Delivery"
  * "With Delivery Courier"

### DELIVERED

* When used: Successful delivery completed
* Typical triggers:
  * Final delivery scan
  * Signature capture (if required)
* Carrier events examples:
  * "Delivered"
  * "Signed for by: \[NAME]"
  * "Left at: \[LOCATION]"
  * "Delivered to Mail Room"

## Alternative Delivery Statuses

### AVAILABLE\_FOR\_PICKUP

* When used: Package ready for pickup at carrier location
* Typical triggers:
  * Arrival scan at pickup location
  * Failed delivery resulting in hold
* Carrier events examples:
  * "Available for Pickup"
  * "Held at Location"
  * "Ready for Pickup"
  * "Arrived at Pickup Point"

### RETURN\_TO\_SENDER

* When used: Package being returned to shipper
* Typical triggers:
  * Return process initiated scan
  * Return in transit scans
* Carrier events examples:
  * "Return to Sender Processing Started"
  * "Returning to Shipper"
  * "Return to Sender in Transit"

## Exception Statuses

### ATTEMPT\_FAILURE

* When used: Failed delivery attempt
* Typical triggers:
  * Delivery exception scan
  * Access issues noted
* Carrier events examples:
  * "Delivery Attempted - No One Home"
  * "Business Closed"
  * "Customer Not Available"
  * "No Access to Delivery Location"

### CANCELLED

* When used: Shipping terminated before pickup
* Typical triggers:
  * Cancellation request processed
  * Label voided
* Carrier events examples:
  * "Shipment Cancelled"
  * "Shipping Label Voided"

### ERROR

{% hint style="info" %}
Limited to a reduced list of carriers, most carriers don't have this status.
{% endhint %}

* When used: Systemic or processing issues
* Typical triggers:
  * Carrier API errors
  * Data inconsistencies
  * Multiple conflicting scans
* Carrier events examples:
  * "Status Update Error"
  * "Tracking Information Unavailable"

### FAILURE

* When used: Terminal shipping failure
* Typical triggers:
  * Severe damage scan
  * Prohibited item discovery
* Carrier events examples:
  * "Shipment Damaged"
  * "Delivery Impossible"
  * "Prohibited Item"

### REPLACEMENT\_LABEL

{% hint style="info" %}
Limited to a reduced list of carriers, most carriers don't have this status.
{% endhint %}

* When used: New label generated for existing shipment
* Typical triggers:
  * Label replacement scan
  * Relabel at facility
* Carrier events examples:
  * "Package Relabeled"
  * "New Tracking Number Assigned"

## Special Handling Statuses

### LOST

{% hint style="info" %}
Limited to a reduced list of carriers, most carriers don't have this status.
{% endhint %}

* When used: Package location unknown
* Typical triggers:
  * No scans for extended period
  * Lost package scan
* Carrier events examples:
  * "Package Search Initiated"
  * "Investigation Created"
  * "Item Not Found"

### STOLEN

* When used: Confirmed theft incident
* Typical triggers:
  * Security incident scan
  * Theft report processed
* Carrier events examples:
  * "Security Exception"
  * "Theft Reported"
  * "Missing - Investigation Complete"

### IN\_VAULT

{% hint style="info" %}
Limited to a reduced list of carriers, most carriers don't have this status.
{% endhint %}

* When used: Secure storage requirement
* Typical triggers:
  * High-value storage scan
  * Special handling scan
* Carrier events examples:
  * "Secured in Facility Vault"
  * "High-Value Storage"
  * "Special Handling Storage"

### DISCARDED

{% hint style="info" %}
Limited to a reduced list of carriers, most carriers don't have this status.
{% endhint %}

* When used: Package officially disposed
* Typical triggers:
  * Disposal authorization scan
  * Destruction completion scan
* Carrier events examples:
  * "Authorized for Disposal"
  * "Destruction Complete"
  * "Disposed per Regulations"


---

# 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.kublau.com/kublau-docs/guides/tracking-a-shipment-in-real-time/tracker-tracking-status.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.