UPS as a Source

July 2, 2026

Summary

UPS as a Source is a Get Shipments-only integration that pulls UPS tracking numbers, shipment status and delivery confirmations for orders fulfilled by your primary supplier source but shipped via UPS. It does not handle inventory or order operations. Connect with a Client ID and Client Secret from the UPS Developer Portal; UPS uses OAuth 2.0 and saves the refresh token automatically after the first authorization.

What this integration does

Get Shipments

Retrieves UPS tracking numbers, shipment status and delivery confirmations for orders that a primary source fulfills but ships via UPS

How to connect - credentials you need

UPS is not added as a standalone source. Open Sources (building icon on the left), configure your primary source first, then go to its Integrations and choose UPS in the Get Shipments section. Enter your UPS Developer Portal credentials and complete the OAuth 2.0 authorization.

Client IDRequired

The API application Client ID generated in the UPS Developer Portal — not your UPS account number or shipping login. Create an application there to receive the credentials, and make sure it has access to the UPS Tracking API.

Open UPS Developer Portal

Client SecretRequired

The Client Secret paired with your Client ID from the same UPS Developer Portal application. Copy both values in exactly, with no extra spaces.

Generated alongside the Client ID in the UPS Developer Portal.

OAuth 2.0 AuthorizationRequired

After entering the Client ID and Client Secret, complete the OAuth 2.0 authorization flow. Flxpoint generates an authorization code, exchanges it for a token, and saves the refresh token automatically for ongoing updates.

One-time step per connection — you do not need to re-authenticate on each run unless credentials change or the refresh token expires.

Get Shipments returning authentication errors? The refresh token may have expired — re-enter your Client ID and Client Secret and complete the OAuth 2.0 authorization again. A "redirect URI mismatch" error during setup means the redirect URI in your UPS Developer application needs to match Flxpoint's OAuth callback — contact Flxpoint Support.

Important - read before configuring

UPS as a Source only supports Get Shipments — no inventory operations

UPS is added specifically for tracking retrieval. It has no Get Inventory Primary, Get Inventory Secondary, Send Fulfillment Requests, or Get Invoices operations — all of those stay on your primary supplier source. Add UPS inside the Get Shipments section of your primary source configuration, not as a standalone source.

Credentials come from the UPS Developer Portal, not your UPS shipping account

The Client ID and Client Secret are API application credentials generated in the UPS Developer Portal (developer.ups.com), which requires a UPS business account. They are different from your UPS account number or shipping login. After you enter them and complete OAuth 2.0 authorization, the refresh token is saved automatically.

The PO Number is the match key between Flxpoint and UPS

For each shipment request Flxpoint sends the PO Number from the Fulfillment Request plus the saved OAuth token, and UPS returns the shipment tied to that PO. If the PO Number on your FR does not match what UPS is tracking, UPS returns no shipment data for that order.

Mapping - fields to know

Get Shipments

Flxpoint connects to UPS over the OAuth 2.0 API for secure, reliable tracking. In each shipment request it sends the PO Number (from the Fulfillment Request) plus the saved OAuth token, and UPS returns the matching shipment — tracking number, shipment status and delivery confirmation. UPS also supplies Service Description information so the carrier's shipping methods and services are reflected accurately in Flxpoint. No field mapping is required; UPS handles tracking retrieval only, while inventory and order operations remain on your primary source.

Common issues

Get Shipments returns no data / shipments not importing

Check three things: (1) the PO Number on the Fulfillment Request matches the UPS shipment record exactly — UPS matches by PO Number and any mismatch returns empty results; (2) the OAuth token is still valid — if the refresh token expired, re-authorize by re-entering the Client ID and Client Secret; (3) the shipment exists in UPS's system — there is a delay between when a label is generated and when UPS's tracking API returns data, so wait at least a few hours after shipment creation.

OAuth 2.0 authorization failing during setup

Verify the Client ID and Client Secret are copied correctly from the UPS Developer Portal with no extra spaces, and confirm the application has the Tracking API enabled — applications without tracking scope fail authorization. A redirect URI mismatch error means the redirect URI registered in your UPS Developer application must match Flxpoint's OAuth callback URL — contact Flxpoint Support.

Can't find Get Inventory or other operations for UPS

UPS as a Source is a Get Shipments-only integration and exposes no inventory or order operations by design. Add UPS inside the Get Shipments section of your primary source, and let that primary source handle inventory, orders and invoices.

FAQs

How does Flxpoint use UPS as a Source to retrieve shipments?▸

Flxpoint sends the PO Number from the Fulfillment Request along with the saved OAuth token to UPS's API to retrieve the shipment data associated with that PO. The PO Number is the link between your FR in Flxpoint and the UPS shipment record, so make sure the PO Number on your FR matches what UPS is tracking — if the values don't align, UPS returns no shipment data for that order.

How do I generate the Client ID and Client Secret from UPS?▸

Go to developer.ups.com and create or log into your developer account, then create a new application to generate a Client ID and Client Secret. Make sure the application has access to the UPS Tracking API. Copy both values into the UPS connection in Flxpoint and complete the OAuth 2.0 authorization to save the refresh token. UPS Developer Portal access requires a UPS business account.

Does the OAuth token expire and need to be refreshed?▸

UPS OAuth 2.0 access tokens expire periodically, but Flxpoint automatically handles token refresh using the saved refresh token. You shouldn't need to re-authorize unless your UPS Developer application credentials change, the application's access is revoked, or the refresh token itself expires. If Get Shipments starts returning authentication errors, re-enter your Client ID and Client Secret and complete the OAuth flow again.

Back to General Supplier Integrations