Get compliant service options
Send origin, destination, packages, dimensions, weight, service constraints, account context, and special services to eligible adapters.
Carrier and parcel integration
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
Send origin, destination, packages, dimensions, weight, service constraints, account context, and special services to eligible adapters.
Retain carrier, service, tracking number, label format, source transaction, client price, receipt, and transition evidence.
Carrier void result, reason, original purchase, provider refund, and reconciliation remain separate business states.
Carrier events are correlated to canonical shipment, package, milestone, confidence, exception, and proof context.
Cataloged adapters
The connector catalog binds each name to a concrete adapter and test suite.
Operational and security boundaries
Carrier id, client id, account number, service allowlist, base URL, and credential reference are resolved for the transaction.
Merchant quotes preserve client-visible service, surcharge, tax, total, expiry, proof, and allowed funding without exposing buy cost.
The backend authorizes the label artifact; the bound station or handheld validates the printer profile, sends locally, and reports acknowledgement.
Client shipping
Shipment facts, immutable quote, funding readiness, price lines, and label evidence remain visible in the client workspace.

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