To start and identify an interchange of one or more functional groups and interchange-related control segments
EDI Ford Motor Company Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) 860
Ford Motor Company X12 860 Purchase Order Change Request
X12 860 (Purchase Order Change Request) is the EDI transaction exchanged between Ford Motor Company (Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 8
- Loops
- 1
- X12 860
- All partners ↗
Transaction context
Where 860 Purchase Order Change Request fits on Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)
- Ford Motor Company channels
- 1 of 1
- Trading partners
- 1
- Channels
- 1
1 of Ford Motor Company's 1 channel carries 860
partners across the Stacksync network trade 860
channels network-wide carry 860
Most common alongside 860
The 860 communicates a buyer's changes to a purchase order it has already transmitted: revised quantities, prices, delivery dates, added or cancelled lines, or cancellation of the entire order. It can also confirm buyer acceptance of changes the seller proposed. Carrying the amendment in EDI keeps the supplier's order record aligned with the buyer's, so downstream ASNs and invoices match the current version of the order and billing disputes are avoided. Sent by the buyer to the supplier against a previously transmitted 850 purchase order; the supplier typically responds with an 865 Purchase Order Change Acknowledgment.
When it fires: A buyer's purchasing or ERP system amends an open order, changing quantity, price, date, or line items, after the original 850 has already gone out.
Common 860 rejection causes
- Change references a purchase order number or line items that do not match the supplier's record of the original 850, so it cannot be applied.
- Change transmitted after the order has been picked or shipped, leaving the 856 and 810 out of sync with the amended order.
- No 865 response returned, so the buyer cannot tell whether the change was accepted before goods ship.
- Incorrect product codes or quantities in the change flow into fulfillment and produce wrong shipments.
Specification summary
X12 860 Purchase Order Change Request at the element level
The X12 860 specification defines 55 segments carrying 162 data elements, 62 of which are mandatory.
- Segments
- 55
- Data elements
- 162
- Mandatory elements
- 62
| Segment | Elements | Mandatory |
|---|---|---|
| BCH | 4 | 4 |
| CUR | 2 | 2 |
| REF | 3 | 1 |
| PER | 2 | 1 |
| FOB | 5 | 1 |
| N9 | 2 | 1 |
| N1 | 4 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
| POC | 13 | 1 |
Key identifiers in 860
- Transaction Set Purpose Code
- Purchase Order Type Code
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Contact Function Code
Full segment guideline — 8 segments 1 loop · X12 860 Purchase Order Change Request
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the purchase order change request transaction set and transmit identifying numbers and dates.
To transmit information in a free-form format, if necessary, for comment or special instruction
POC Loop Repeat: 10,000
To specify changes to a line item
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning and ending (SE) segment)
Trading partners
6+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
SH Ship Notice Manifest SH Shipping Schedule OR Order Status Report PU Purchase Order Change Acknowledgment AP Application Advice PU Purchase Order
No trading partner matches your search.
Browse the full directory
Ford Motor Company Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) EDI 860 FAQ
Common questions about 860 Purchase Order Change Request on the Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) channel.
What is X12 860 Purchase Order Change Request?
X12 860 (Purchase Order Change Request) is the EDI transaction set used to exchange purchase order change request data. Ford Motor Company's Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) channel requires it from trading partners.
Does Ford Motor Company Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) require 860 for trading partners?
Yes, Ford Motor Company (Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)) supports X12 860 Purchase Order Change Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Ford Motor Company 860 with Stacksync?
Most companies go live with Ford Motor Company 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 860 on Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)?
On Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS), X12 860 is typically exchanged alongside 856 Ship Notice Manifest, 862 Shipping Schedule, 870 Order Status Report, 865 Purchase Order Change Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Ford Motor Company EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
