Skip to main content
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.
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

IntegrationRegional variantsDelimiterColumn countCharge structure
DHL eCommerce—,79 (no header row)One row per shipment; charges spread across named columns (Charge*, ZFuel*, ZSC*, ZRM*)
DHL Express—,153Line Type marker (I / S); charges in XC1–XC9 column groups
DPDEnglish (Dutch column aliases accepted);43One row per shipment; charges in named columns (Base price, Energy surcharge, Fuel surcharge, etc.)
FedExUS, International (UK / NL),210 (US) / 168 (International)One row per shipment; charges in repeating Label / Amount column pairs
Royal Mail—,16Trackstar-combined line-item file (not a raw carrier file); one row per tracked item
UPS—,250One row per charge; multiple rows per shipment share a tracking number
USPS—,21One 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_items schema 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.
For the normalized API that sits over all these formats, see Invoice Line Items. For the raw-file endpoint that returns presigned URLs to a customer’s actual (non-synthetic) files, see Files.