Each carrier delivers invoice data in its own CSV format. The pages in this group document those formats individually — what columns appear, what each column means, how multi-row shipments are structured, and where line-item charges live. Each integration has a downloadable synthetic CSV you can parse against without needing a live integration. Most of these files are the raw carrier file served as-is, so they keep each carrier’s own column names and casing. Royal Mail is the exception: its invoice and tracking data arrive separately, so Trackstar combines them into a single line-item file with normalized column names.Documentation Index
Fetch the complete documentation index at: https://docs.trackstarhq.com/llms.txt
Use this file to discover all available pages before exploring further.
All sample data on these pages is synthetic. Tracking numbers, account numbers, addresses, and reference fields are fabricated and do not correspond to any real shipments or customers.
Integrations
| Integration | Regional variants | Delimiter | Column count | Charge structure |
|---|---|---|---|---|
| DHL eCommerce | — | , | 79 (no header row) | One row per shipment; charges spread across named columns (Charge*, ZFuel*, ZSC*, ZRM*) |
| DHL Express | — | , | 153 | Line Type marker (I / S); charges in XC1–XC9 column groups |
| DPD | English (Dutch column aliases accepted) | ; | 43 | One row per shipment; charges in named columns (Base price, Energy surcharge, Fuel surcharge, etc.) |
| FedEx | US, International (UK / NL) | , | 210 (US) / 168 (International) | One row per shipment; charges in repeating Label / Amount column pairs |
| Royal Mail | — | , | 16 | Trackstar-combined line-item file (not a raw carrier file); one row per tracked item |
| UPS | — | , | 250 | One row per charge; multiple rows per shipment share a tracking number |
| USPS | — | , | 21 | One row per transaction (1:1 with line items) |
How to use these samples
- Prototype your integration without needing a live carrier connection. Download the CSV, run it through your own ingestion code, and compare against the schema documented on each page.
- Understand the Trackstar
invoice_line_itemsschema in context. Each page lists which raw columns Trackstar maps to which normalized field (tracking_number,invoice_id,charge_description,gross_cost,net_cost, etc.). - Test your downstream systems against realistic-shaped data, including multi-row shipments, multi-currency invoices, and empty optional columns.