Carrier and parcel integration

Keep rate, label, tracking, void, and evidence on one shipment.

Available with configuration

XMS Cloud exposes one carrier contract for rate shopping, label generation, label void, and tracking. Each carrier account, service, region, credential, format, and failure path still requires qualification.

Canonical carrier contract

One orchestration shape; vendor-specific capability remains visible.

RATE

Get compliant service options

Send origin, destination, packages, dimensions, weight, service constraints, account context, and special services to eligible adapters.

LABEL

Generate a shipment artifact

Retain carrier, service, tracking number, label format, source transaction, client price, receipt, and transition evidence.

VOID

Cancel without erasing history

Carrier void result, reason, original purchase, provider refund, and reconciliation remain separate business states.

TRACK

Normalize shipment status

Carrier events are correlated to canonical shipment, package, milestone, confidence, exception, and proof context.

Cataloged adapters

Configuration status does not mean every service is qualified.

The connector catalog binds each name to a concrete adapter and test suite.

ChronopostColissimoDPDGLSGLS ItalyUPSDHL ExpressDHL PaketFedExMondial RelayRelais ColisColis PrivéCiblexDelivengoFrance ExpressIMXSDADB SchenkerCIRROAmazon ShippingGeneric REST
Qualification unit: carrier + account + region + service code + package type + label format + special service + adapter build. A different combination is a different scope.

Operational and security boundaries

Buying the label and printing it are different authorities.

ACCOUNT

Client and carrier context

Carrier id, client id, account number, service allowlist, base URL, and credential reference are resolved for the transaction.

COMMERCE

Exact client sell price

Merchant quotes preserve client-visible service, surcharge, tax, total, expiry, proof, and allowed funding without exposing buy cost.

DEVICE

Warehouse-local printing

The backend authorizes the label artifact; the bound station or handheld validates the printer profile, sends locally, and reports acknowledgement.

Client shipping

Confirm the exact amount before purchase.

Shipment facts, immutable quote, funding readiness, price lines, and label evidence remain visible in the client workspace.

  • One idempotency key per purchase intent.
  • Reprint does not repurchase.
  • Void and refund remain explicit reconciliation paths.
Client shipping workspace with shipment facts, exact price lines, wallet coverage, and label purchase
Price and shipment stay together.1 Carrier service and package state remain visible.2 Exact charge retains surcharge, tax, proof, and funding.

Carrier compatibility review

Bring the accounts, lanes, services, packages, labels, and exception cases.

Qualify live rate, purchase, print, track, void, retry, and reconciliation behavior for each proposed carrier scope.