> This page is for version Dev.
> For other versions, use one of these documentation indexes:
> - Prod (default): https://docs.chrt.com/prod/llms.txt
> - Staging: https://docs.chrt.com/staging/llms.txt
> - Dev: https://docs.chrt.com/dev/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chrt.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chrt.com/_mcp/server.

# Trackers on Orders

> Understand the tracking sources and map controls available on a Chrt order.

An order map can bring together tracking from the shipment's different legs and sources. Driver tracking, device tracking associated with cargo, Tive shipment tracking, and Reelables asset tracking are distinct sources. Review the source and its timestamps before interpreting a marker as the shipment's current position.

## Find tracking for the shipment

Open the order from [Orders](https://chrt.com/orders). Use its map to review the tracking available for that order. A source appears only when the relevant tracking record and data are available; an empty map alone does not identify a device or connection problem.

In the map's settings, opened with the **Map settings** gear 1, tracking sources are grouped by shipment segment. Depending on the order, labels can include **Driver** 2, **Cargo (Driver)** 3, **Cargo with Device**, **Session (Device)**, **Tive shipment**, **Reelables asset**, and **Provider tracking**. Use the available visibility controls to focus on the source you need. Mark 4 is **See all pings**, and mark 5 is the **Progress** | **Live** switch.

![Shipper order map settings, numbered 1 to 5: the Map settings gear, the Driver, Cargo (Driver) and See all pings options, and the Progress and Live switch](/_fern-files/_img/09d95f1ba6173ec74ee29e0b949e4657eddb1c5edd2403e1ed59ccfcbf102764.webp)

*Order map settings in the shipper view. **1** **Map settings** gear, **2** **Driver** (on, and dimmed because it is the only source shown), **3** **Cargo (Driver)** (off), **4** **See all pings** (on), **5** **Progress** | **Live** switch. Look at **2** and **3** to see which sources the map is showing.*

## Read the result

Compare the tracking source with the shipment leg and cargo you are following. Review the time associated with a data point alongside its location. A device marker and a driver marker represent different sources; neither establishes that every other source is reporting. For an onboard courier, the **Driver** and **Cargo (Driver)** route line does not join the ground points before boarding and after deboarding a flight: the trail breaks from the completed boarded-flight task until the deboarded-flight task, and stays open while the flight is still in the air. Individual pings are still plotted.

For data from a connected service, open the corresponding [integration record](/dev/trackers/integrations) to review its information. [Battery and data](/dev/trackers/battery-data) explains how to interpret the sensor values available on Tive records.

## Link tracking devices to cargo

Operators or higher can link and unlink tracking devices on an order's cargo. In the order's **Cargo** grid, the **Tracking** column shows the devices linked to each cargo. Open it and choose **Add or remove devices**, or **Register new device** to register a device that is not in your list yet. You can also open the order's **Actions** menu and choose **Add tracking devices**, which opens the **Tracking devices** dialog for the order's cargo. A device can track one cargo at a time.

A device that belongs to another party appears as **Another party's device**, with no unlink control. Archived devices are not offered.

Confirm the physical device and permitted setup path with [trackers@chrt.com](mailto:trackers@chrt.com) before adding or replacing hardware. Include the order reference and device identifier when requesting help. Review the saved association and resulting tracking view after any change. Do not use a hardware replacement as evidence that old data has been removed or that a sharing link has stopped working.

## Related guides

* [Standalone trackers](/dev/trackers/standalone) — sessions independent of orders.
* [Supported devices](/dev/trackers/supported-devices) — device labels and compatibility checks.
* [Battery and data](/dev/trackers/battery-data) — sensor readings and timestamps.
* [Integrations](/dev/trackers/integrations) — Tive and Reelables tracking records.
* [Sharing](/dev/trackers/sharing) — organization sharing and public-session controls.