Overview
Understanding UPS integration
Who this is for: Shippers, retailers and distributors that ship small packages with UPS and want shipments, tracking and invoices connected to their ERP, warehouse and freight audit systems.
Scope: UPS EDI details (current X12 version, delivery methods, enrollment steps) are confirmed with UPS during setup. Document names here come from UPS's EDI page and 210 billing manual, which dates from 2008.
If you ship parcels with UPS, three exchanges matter: the shipment data you send, the status you get back, and the invoice you pay. UPS describes its electronic data interchange service as batch processing of package-level detail uploads, billing information and package tracking. The data sets UPS lists for customers are the 210 invoice (Motor Carrier Freight Details and Invoice), the 240 package status and the 215 manifest. UPS also says shippers must send it electronic package-level detail for each shipment.
UPS publishes a separate set of REST APIs through its developer resource center for shipping and labels, rating, time in transit, address validation, pickup and tracking. Many warehouses use the APIs to create labels in real time and use EDI or billing files for invoice audit and payment. UPS freight forwarding and supply chain services have their own integration options, which are covered in the UPS Supply Chain Solutions guide.
ECOM maps UPS manifest, status and invoice data to your ERP, WMS and TMS, connects the UPS APIs through the API Gateway, tests each flow and monitors it after go-live. Finance teams get invoices matched to shipments and contracted rates, and customer service gets tracking events tied to the right order.