UPS Integration & Shipping Software Development Shipment Processing, Labels & Tracking

UPS Shipment Creation & Package Processing

Shipment creation starts with the information supplied by the existing business application. Sender, receiver, contact and package information are prepared before the carrier-specific request is built. If sender or receiver phone information is missing, the application can use the configured user contact number as a fallback.

The selected delivery service is retrieved from the application's service configuration. The configured UPS shipper number is validated and the application's service identifier is converted into the numeric UPS service code required by the carrier.

Package information is first constructed in a common representation containing dimensions, weight and quantity. Those packages are then converted into the UPS-specific package structure before the shipment is submitted.

Shipment construction:

Prepare order data → retrieve UPS service → validate shipper number → map service code → build common packages → build common shipment → convert packages to UPS format → submit shipment.

UPS API Integration — C# / .NET

The application separates the common shipping workflow from the carrier-specific UPS implementation. Shipment information is prepared in the application and passed to a dedicated shipping client responsible for communicating with UPS.

The carrier-specific service receives the prepared shipment information together with the configured UPS shipper number and submits the shipment through the UPS integration. The returned carrier result is then converted into the application's standard shipment result so the rest of the application does not need to depend directly on UPS-specific response structures.

Carrier communication flow:

Application shipment model → UPS-specific shipment structure → UPS shipping client → UPS API → carrier response → application shipment result.

This approach keeps UPS-specific processing inside the carrier integration layer while allowing the surrounding shipping application to work with a consistent shipment result.

UPS Services, Service Codes & Shipping Rates

The quoting workflow begins by normalizing the incoming shipment request. The application then determines applicable UPS delivery services using sender and receiver information, postal codes, cities, package dimensions, weight and quantity.

The service discovery process handles both standard and non-standard UPS services. The resulting service information is collected into the application's quote list before the available services are processed through the UPS rate API.

The application also maintains a carrier-specific service-code mapping layer. Business-facing service names are translated into the numeric codes required by UPS. For example, UPS Express Saver and Express Saver use service code (65), UPS Next Day Air Early uses (14), UPS Next Day Air uses (01), UPS Next Day Air Saver uses (13), UPS 2nd Day Air A.M. uses (59), UPS 2nd Day Air uses (02), UPS 3 Day Select uses (12) and UPS Ground uses (03).

International services are mapped in the same way, including UPS Worldwide Express (07), UPS Worldwide Express Plus (54), UPS Worldwide Expedited (08) and UPS Worldwide Saver (65).

Quote workflow:

Normalize request → determine applicable services → retrieve standard and non-standard services → process UPS rates → return available services and rates.

UPS Shipping Labels & Paperless Documents

UPS shipment creation can return label information together with the shipment result. The application processes the returned label information and associates it with the corresponding shipment.

The integration also supports UPS Paperless customs and export documentation. When an export document is supplied, the application uploads the document through the UPS Paperless API before creating the shipment. UPS returns a Document ID, which can then be associated with the shipment information.

Paperless document workflow:

Export document supplied → upload document to UPS → receive Document ID → associate Document ID with shipment → continue shipment creation.

This allows customs documentation to remain part of the automated shipping workflow rather than requiring a separate manual document-processing step.

UPS Tracking, Labels & Carrier Response Handling

After successful shipment creation, the UPS response is processed to obtain the tracking numbers and label information. The tracking numbers are associated with the corresponding shipment so that the business application can continue to manage the shipment after the UPS request has completed.

The integration also handles unsuccessful UPS responses. When shipment creation fails, the returned carrier error is used to update the shipment status and is returned to the calling application together with the available carrier response information.

For successful shipments, the application creates the required label and tracking records and preserves the carrier result, including tracking numbers, label information and relevant shipment configuration.

Response workflow:

UPS response → determine success → process tracking numbers and labels → persist shipment information. If unsuccessful → capture UPS error → update shipment status → return carrier error to the application.