UPS

Carrier-specific setup for UPS in Shipping Labels.

Purpose

This page describes the UPS-specific setup in Shipping Labels. It focuses on service type, return-service behavior, international shipment handling, units of measure, and the transition from older authentication fields to preferred OAuth-based access.

Prerequisites

The shared Shipping Labels setup is complete.
UPS shipping account data and the required environment URL are available.
The chosen UPS service type is known for the origin and destination corridor.
Fallback package weight is available where item weight is not maintained.

Recommended sequence

Maintain the UPS URL and the preferred authentication method.
Maintain shipper number and the required credential fields.
Select the UPS service type and return-service behavior.
If international shipping is required, maintain the international-shipment settings and description.
Validate one domestic and, if relevant, one international scenario.

Setup components

Prefer OAuth-based access when available

UPS can still contain older access-license-style fields, but the preferred direction is OAuth-based access with client ID and client secret. Keep older values only where a supported compatibility scenario still requires them.

In the older authentication model, Shipper Number, User ID, Password, and License Key belong together. In the preferred OAuth model, the access consists of Shipper Number, Client ID, and Client Secret. Once OAuth is fully maintained, it should be the primary model and the older fields should remain only as a compatibility path.

Maintain service type against the real corridor

UPS service type is not only a label on the setup line. It must match the actual origin and destination corridor. This is especially important for international scenarios because an otherwise correct request can still fail if the chosen service does not fit that corridor.

For international shipments, the International Shipment flag alone is not sufficient. The selected service type must explicitly support the origin-destination corridor, for example Germany to the United States; otherwise the request will be rejected despite correct credentials.

Keep units, limits, and return behavior aligned

The UPS setup should keep the units consistent with the carrier expectation, in particular CM and KGS, and maintain the required package limits such as maximum package length and girth. If return service is used, maintain it as a deliberate business option rather than a generic default.

Add international shipment details only when needed

If a setup is used for international shipments, maintain the dedicated international-shipment indicator and the required description. Keep this logic on the setups that really need it instead of turning it into a global default.

Process Important UPS notes UPS setup depends mainly on the right authentication model and a service type that matches the shipping corridor.

Prefer OAuth 2.0 credentials where possible.
Keep older authentication fields only for supported compatibility scenarios.
Match the UPS service type to the actual origin and destination corridor.
Maintain CM and KGS consistently on the setup.
Add return-service and international-shipment settings only where the business process requires them.

UPS