Skip to content

UPS EDI
integration guide.

Plan your UPS EDI integration using 5 listed document types across 1 channel. Compare channels, map business records and test the operational handoff.

Book an EDI demo Explore EDI documents
Listed documents
5
Partner document references
Listed channels
1
UPS Plus
Implementation
Plan
Map, validate and reconcile

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Implementation guide

UPS: EDI implementation plan

Build a reliable EDI workflow for UPS. Use 5 document types across 1 channel to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 865 Purchase Order Change Acknowledgment Request Seller InitiatedListed on 1 channel: UPS Plus seller order-change response or request

original purchase order, change reference and affected line
  • Distinguish a seller-proposed change from acceptance of a buyer-requested change.
  • Reject an outdated revision that would overwrite a later agreed quantity.
X12 855 Purchase Order AcknowledgmentListed on 1 channel: UPS Plus purchase-order response

original purchase order, response revision and order line
  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 214 Transportation Carrier Shipment Status MessageListed on 1 channel: UPS Plus shipment status event

shipment reference, event code, event time and location
  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.
X12 944 Warehouse Stock Transfer Receipt AdviceListed on 1 channel: UPS Plus warehouse transfer receipt

transfer, receipt location and received item
  • Reconcile a short receipt with the shipped quantity and leave the difference open.
  • Separate damaged stock from saleable stock in the receiving balance.
X12 856 Ship Notice ManifestListed on 1 channel: UPS Plus shipment notice (ASN)

shipment, order, package and item references
  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.

Implementation steps

  1. Choose the trading account and channel

    Choose among UPS Plus. Confirm the business unit and account before copying a mapping from another channel.

  2. Map records and assign owners

    Start with seller order-change response or request, purchase-order response, shipment status event. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the UPS production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using original purchase order, change reference and affected line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for UPS

5 transactions across 1 channel.

Document flow

Example document relationships for UPS

Where each document sits in its trading cycle, based on the 5 document types listed for UPS across 1 channel. These are example relationships; the trading agreement determines the required sequence.

Logistics

Some example steps listed
  1. 204 Motor Carrier Load Tender not listed for UPS
  2. 990 Response to a Load Tender not listed for UPS
  3. 214 Transportation Carrier Shipment Status Message
  4. 210 Motor Carrier Freight Details and Invoice not listed for UPS
LEGACY EDI MIGRATION FUND

Still with a legacy EDI vendor? We cover the buyout.

Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.

Check your eligibility for the EDI migration fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more

Related references

Partners with related document listings

Compare document requirements for similar business processes.

Target 23 docs · 4 channels Williams Sonoma 10 docs · 2 channels The Home Depot 48 docs · 11 channels Walmart 32 docs · 8 channels NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels KeHE Distributors 18 docs · 5 channels United Natural Foods, Inc. (UNFI) 17 docs · 4 channels Dot Foods, Inc. 14 docs · 2 channels Starbucks Coffee Company 14 docs · 3 channels Boscov's Department Stores 13 docs · 2 channels Rivian Automotive, Inc 11 docs · 1 channel Bealls Inc. 11 docs · 2 channels Sysco 11 docs · 2 channels Google 10 docs · 1 channel Staples Inc. 9 docs · 2 channels Wayfair LLC 9 docs · 1 channel ASUSTeK Computer Inc. (dba ASUS) 8 docs · 1 channel MSC Industrial Supply Co. 8 docs · 1 channel MidwayUSA 7 docs · 1 channel Sportsman's Guide 7 docs · 1 channel QVC Group (dba Cornerstone Brands Inc) 7 docs · 1 channel

Showing 21 of 48 references

Browse the full directory

FAQ

UPS EDI questions

Which EDI documents are listed for UPS?

X12 865 Purchase Order Change Acknowledgment Request Seller Initiated; X12 855 Purchase Order Acknowledgment; X12 214 Transportation Carrier Shipment Status Message; X12 944 Warehouse Stock Transfer Receipt Advice; X12 856 Ship Notice Manifest. Confirm which documents, directions and versions apply to your account.

How should I choose the UPS EDI channel?

The directory lists 1 channels for UPS, including UPS Plus. Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the UPS mapping preserve?

For X12 865 Purchase Order Change Acknowledgment Request Seller Initiated, plan around original purchase order, change reference and affected line. For X12 855 Purchase Order Acknowledgment, use original purchase order, response revision and order line. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean UPS accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching UPS EDI?

Distinguish a seller-proposed change from acceptance of a buyer-requested change. Reject an outdated revision that would overwrite a later agreed quantity. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Get started