← Integration Hub

Carrier network

Action requiredSetup requiredMOCK

Delivery performance, incidents and cost across DHL, DPD, GLS and freight partners, behind one adapter.

How it connects
Configured on the server
Health
healthy
Integration status
connected
Credential
Not configured
Last sync
never
Connected
not yet

0 of 1 steps done

Setup

  1. Per-carrier adapters have to be built

    You are hereNot done yet
    Administrator (once)Automatic

    Mock-only. `carriers` is an aggregation layer, not one provider: a real implementation is one adapter per carrier (DHL, DPD, GLS, Dachser) behind a single connector, selected by PAXX_CARRIER_ADAPTERS with one credential each. Cost realistically arrives from invoice feeds rather than tracking APIs, so the two capabilities above are likely to land separately.

Configured on the server

Connect

Nothing — the business cockpit runs on fixtures until a real connector exists.

Setup required

Mock-only. `carriers` is an aggregation layer, not one provider: a real implementation is one adapter per carrier (DHL, DPD, GLS, Dachser) behind a single connector, selected by PAXX_CARRIER_ADAPTERS with one credential each. Cost realistically arrives from invoice feeds rather than tracking APIs, so the two capabilities above are likely to land separately.

Live check

Connection test

This provider declares no connection test — it makes no external call, so there is nothing to probe and a green result here would mean nothing.

2 declared

Permissions

What PAXX asks the provider for. The provider's own consent screen is the authoritative grant — this list is what will be requested, and after connecting, what was actually returned.

  • readRead trackingnot requested yetPer-shipment status events used to derive on-time performance.
  • readRead costoptionalnot requested yetCarrier invoices and surcharges for cost-per-shipment.

Capabilities

What you get

  • Tracking events

    readNot available

    Per-shipment status events, which is what on-time performance is derived from rather than asserted.

    Available once this provider is connected.

    /paxx/operations/carriers/paxx/operations

  • Cost and surcharges

    readNot available

    Carrier invoices, for cost-per-shipment. Invoices are keyed by carrier and never by tenant, which is why a share of operational cost is reported as unattributable rather than spread.

    Available once this provider is connected.

    /paxx/operations/carriers/paxx/operations/customers

Requirements

Diagnostics

Administrator requirements

One-time work for whoever administers this PAXX instance.

  • Per-carrier adapters have to be built

    Not satisfied
    Administrator (once)Automatic

    Mock-only. `carriers` is an aggregation layer, not one provider: a real implementation is one adapter per carrier (DHL, DPD, GLS, Dachser) behind a single connector, selected by PAXX_CARRIER_ADAPTERS with one credential each. Cost realistically arrives from invoice feeds rather than tracking APIs, so the two capabilities above are likely to land separately.

Your requirements

Per-person steps — the authorization is yours, not the deployment's.

None.