Carrier integration guide
Carrier/service availability is account-specific. PAB exposes customer-friendly carrier/service names while keeping backend translation inside PAB.
Service identifiers
Use the exact serviceId configured for the PAB account. A service identifier is an integration value, not a value an external system should invent or modify.
Service mapping
Managed order sources may map familiar source-system delivery values to an enabled PAB shipping service. Unmatched behaviour is controlled by the client configuration.
Carrier display names
Customer-facing names are normalised by PAB. Backend provider identifiers are not part of the customer API contract.
Package rules
Weight, dimensions, package type and option validation can vary by enabled service. Validate a request before live creation.
Rate limiting
Integrations should avoid burst polling. Honour 429 responses and do not compensate for throttling by increasing concurrency.
Operational correction
If a carrier/service cannot allocate the shipment, correct the existing order/shipment through the supported workflow. Do not create a second shipment merely to work around an allocation error.
