Carriers integration

UPS parcel integration: shipping data out, status and invoices back

A guide for shippers moving packages with UPS who need manifests, package status and billing data to flow between UPS and their ERP, warehouse and finance systems.

At a glance

UPS integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific UPS program or a customer relationship.

Illustration of a laptop with a shopping cart and stacked parcels, representing the carriers industry that UPS operates in.
Industry. Carriers: where UPS operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with UPS through ECOM. You send documents; you receive 210; 215 and 240 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor UPS send send 210 210 215 240 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Tenders and invoices re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about UPS

Tell us which documents you exchange with UPS, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with UPS.

  • Review of UPS's requirements with you, once you have them
  • EDI and API integration with your TMS, ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
UPS

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How UPS integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringUPS developer APIs · UPS EDI · Billing files and portal
UPSIts program, documents and requirements
  1. ConfirmConfirm your UPS program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

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.

Business scenarios

Where UPS integration gets complicated

Typical requirements—confirm with your trading partner.

Parcel invoice audit

A shipper with many daily packages receives large UPS invoices. Charges for surcharges, address corrections and weight changes are hard to check by hand.

How ECOM helps: ECOM maps the 210 invoice data to your ERP or freight audit tool and matches each charge to the shipment and your contracted rate, with differences listed for review.

What you gain: Fewer overcharges paid and less manual invoice checking.

Tracking tied to orders

Customer service needs one status per order, even when an order ships in several packages.

How ECOM helps: ECOM links UPS package status (240 or the tracking API) to the order lines in your ERP or OMS and flags packages with no recent event.

What you gain: Faster answers on delivery questions and earlier warning of delays.

Label creation at warehouse speed

Warehouses create labels and manifests at pick and pack time and cannot wait on batch files.

How ECOM helps: ECOM manages the UPS API connection, credentials handling and retries in the API Gateway while EDI carries manifests and invoices.

What you gain: Labels print without delay and the manifest reaches UPS complete.

Workflows

Typical UPS business workflows

The steps summarize the documents below. Where a step is not in UPS's published documents, it reflects common practice.

Ship, track and notify

  1. 1Create shipment and label
  2. 2Send 215 manifest
  3. 3Receive 240 package status
  4. 4Update order and notify customer

Invoice to payment

  1. 1Receive 210 invoice
  2. 2Match to shipments
  3. 3Validate charges and rates
  4. 4Approve and pay

Documents and APIs

UPS documents by program

Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from UPS's published documents cited below; documents marked general guidance are common in this industry but not confirmed for UPS.

DocumentNameDirectionProgramStatusPurpose
215 Motor Carrier Pickup Manifest Both directions UPS EDI package data Named; level not stated The shipper sends package-level detail for shipments handed to UPS.
240 Motor Carrier Package Status Both directions UPS EDI package data Named; level not stated UPS reports the status of packages to the shipper.
210 Motor Carrier Freight Details and Invoice From UPS UPS billing Named; level not stated UPS sends invoice detail for the shipper to audit and pay.
997 Functional Acknowledgment Both directions Not stated General guidance Commonly used to confirm each EDI file was received and readable.
API Shipping, rating and tracking APIs Both directions UPS developer APIs Named; level not stated Create shipments and labels, quote rates and retrieve tracking events.

Connectivity

How companies connect

  • UPS developer APIs

    UPS documents APIs for shipping, rating, time in transit, address validation, pickup and tracking in its Developer Resource Center.

    From UPS's published documents

  • UPS EDI

    UPS describes batch EDI for package-level detail uploads, billing information and package tracking. Delivery methods and enrollment are agreed with UPS.

    From UPS's published documents

  • Billing files and portal

    UPS offers electronic billing and invoice management options beside EDI. Pick the one that fits your audit and payment process.

    General guidance

Challenges

Common integration challenges

  • Invoice volume and surcharges

    Daily parcel volume produces large invoices with surcharges and adjustments that cannot be audited by hand.

  • Linking tracking to orders

    Multi-package orders need each tracking number tied to the right order line and customer.

  • API changes

    Carrier API versions and authentication methods change over time, so the integration needs maintenance.

  • Manifest completeness

    Package-level detail sent to UPS must be complete and consistent with what is billed.

Automation options for UPS shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. UPS sets its own requirements; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Zero Trust for freight data exchange

Zero Trust EDI and MFT for your UPS connection

Freight exchanges with UPS carry tenders, status events, rates and freight invoices. A Zero Trust design assumes no connection, file or user is safe by default.

ECOM has implemented Zero Trust EDI and Zero Trust MFT in trucking.

For freight exchanges this means each carrier has its own scope, tenders, status messages and invoices are checked at the connection and the file, a late or missing file is noticed early, and every transfer has a record for freight billing disputes and security reviews.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up tenders, status or freight billing.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Carrier onboarding

Each carrier or broker gets its own identity and scope. A new carrier is tested before it reaches production, and a removed carrier loses access without affecting the others.

Tenders, status and invoices

Load tenders, status messages and freight invoices are checked at the connection and the file, and every transfer is logged.

Rates and contract data

Rate and accessorial files are limited to the roles that need them.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. UPS may set its own security requirements, which come first.

General EDI flow

How EDI with UPS typically works

The documents, their order and the timing are UPS's to set; this is the general sequence most programs of this kind follow.

  1. 215 Motor Carrier Pickup Manifest

    Both directions

    The shipper sends package-level detail for shipments handed to UPS.

  2. 240 Motor Carrier Package Status

    Both directions

    UPS reports the status of packages to the shipper.

  3. 210 Motor Carrier Freight Details and Invoice

    From UPS to you

    UPS sends invoice detail for the shipper to audit and pay.

  4. 997 Functional Acknowledgment

    Both directions

    Commonly used to confirm each EDI file was received and readable.

  5. API Shipping, rating and tracking APIs

    Both directions

    Create shipments and labels, quote rates and retrieve tracking events.

Working from UPS's published specification?

Tell ECOM which program and documents apply to you. We read the published specification with you, map it to your systems and test against it. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your UPS program

Each request goes to an ECOM EDI specialist with UPS's name attached, so the reply starts from your program.

  • Review UPS's requirements

    Send us UPS's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect UPS to your ERP

    Tenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each UPS document, then go live with monitoring from the first file.

    Plan testing and certification

UPS integration FAQs

Does UPS use EDI or APIs?

Both. UPS lists EDI for package-level detail, billing and package status, and publishes developer APIs for shipping, rating and tracking. Many shippers use APIs for labels and tracking and EDI or billing files for invoices.

Which EDI documents does UPS list for customers?

UPS's EDI page names the 210 invoice, the 240 package status and the 215 manifest. UPS confirms the current version and delivery method when you enroll.

Can UPS tracking update our order system automatically?

Yes. Tracking events can be retrieved through the UPS tracking API or received as package status data and linked to orders, so status updates and customer notifications happen automatically.

Is this the guide for UPS freight forwarding?

No. This guide covers UPS parcel shipping. UPS Supply Chain Solutions, which covers freight forwarding and related services, has its own guide.

Is ECOM a UPS partner?

This is an independent integration guide. It does not indicate an endorsement, partnership or approval by UPS.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. UPS sets its own requirements and can change them at any time; your UPS implementation guide, supplier portal or account contact is the authoritative source for your program.

Request UPS integration assistance

Tell us about your UPS program, documents and ERP. We will outline the connection, mapping and testing plan.