X12
Inbound

Ford Motor Company X12 860 Purchase Order Change Request

Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)
The EDI 860 is sent by Ford Motor Company to modify an existing Purchase Order. Changes can include quantity adjustments, delivery date shifts, item additions, or cancellations. Suppliers must process changes promptly and confirm via an updated acknowledgment.
8segments
1loops
6mandatory

Schema Reference

8 segments · X12 860 Purchase Order Change Request

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Test Indicator
M ID 1-1
ISA16 Subelement Separator
M AN 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier
M ID 2-2
GS02 Application Sender's Code
M ID 2-12
GS03 Application Receiver's Code
M ID 2-12
GS04 Data Interchange Date
M DT 6-6
GS05 Data Interchange Time
M TM 4-4
GS06 Data Interchange Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version/Release/ Industry ID
M ID 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BCH Beginning Segment (Order Change Request)
Mandatory Max: 1
BCH01 Transaction Set Purpose
M ID 2-2
BCH02 Purchase Order Type
M ID 2-2
BCH03 Purchase Order Number
M AN 1-22
BCH06 Purchase Order Date
M DT 6-6
BCH10 Acknowledgment Date
O DT 6-6
BCH11 Purchase Order Change Request Date
O DT 6-6
NTE Note/Special Instruction
Optional Max: 100
NTE01 Note Reference Code
O ID 3-3
NTE02 Free Form Message
M AN 1-60
POC Loop Repeat: 10,000
POC Line Item Change
Optional Max: 1
POC01 Purchase Order Line Number
O AN 1-6
POC02 Line Item Change Type
M ID 2-2
POC03 Quantity Ordered
O R 1-9
POC04 Quantity Left to Receive
C R 1-9
POC05 Unit of Measurement Code
C ID 2-2
POC06 Unit Price
C R 1-14
POC08 Product/Service ID Qualifier
O ID 2-2
POC09 Product/Service ID
C AN 1-30
CTT Transaction Totals
Mandatory Max: 1
CTT01 Number of Line Items
M N0 1-6
CTT02 Hash Total
O R 1-10
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-6
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Ford Motor Company EDI 860

Stacksync validates, transforms, and delivers your 860 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync detects incoming 860 PO Changes and updates the original order in your ERP automatically. Changed fields are highlighted and your team is notified — so you can review and confirm without manually comparing documents.

Ford Motor Company EDI 860 FAQ

Common questions about 860 Purchase Order Change Request transactions with Ford Motor Company.

What types of changes can be made with a Ford Motor Company EDI 860?

A Ford Motor Company EDI 860 Purchase Order Change can modify quantities, prices, delivery dates, ship-to addresses, item substitutions, and add or cancel individual line items on an existing PO. The BCH segment specifies the change type — full replacement, partial change, or cancellation. Ford Motor Company uses 860s instead of canceling and reissuing entire 850s for efficiency, especially when only a few lines need adjustment. Stacksync processes incoming Ford Motor Company 860s by automatically updating the original PO record in your system, maintaining a change history for audit purposes.

What types of changes can be made with a Ford Motor Company EDI 860?

A Ford Motor Company EDI 860 Purchase Order Change can modify quantities, prices, delivery dates, ship-to addresses, item substitutions, and add or cancel individual line items on an existing PO. The BCH segment specifies the change type — full replacement, partial change, or cancellation. Ford Motor Company uses 860s instead of canceling and reissuing entire 850s for efficiency, especially when only a few lines need adjustment. Stacksync processes incoming Ford Motor Company 860s by automatically updating the original PO record in your system, maintaining a change history for audit purposes.

Should Ford Motor Company cancel and resend an 850 or use an EDI 860?

Ford Motor Company generally prefers EDI 860 for modifications to existing POs rather than canceling and reissuing the entire 850. The 860 is more efficient because it targets specific changes — a quantity adjustment on one line item, a revised ship date, or an added line — without disrupting the rest of the order. Canceling and reissuing creates a new PO number and can cause confusion in warehouse operations. Stacksync handles both workflows, but when a Ford Motor Company 860 arrives, it applies the changes incrementally to your existing order record rather than creating a duplicate entry.

Should Ford Motor Company cancel and resend an 850 or use an EDI 860?

Ford Motor Company generally prefers EDI 860 for modifications to existing POs rather than canceling and reissuing the entire 850. The 860 is more efficient because it targets specific changes — a quantity adjustment on one line item, a revised ship date, or an added line — without disrupting the rest of the order. Canceling and reissuing creates a new PO number and can cause confusion in warehouse operations. Stacksync handles both workflows, but when a Ford Motor Company 860 arrives, it applies the changes incrementally to your existing order record rather than creating a duplicate entry.

How does Stacksync process Ford Motor Company EDI 860 changes?

When Stacksync receives a Ford Motor Company 860, it identifies the original PO by reference number, compares the changed fields against the current order in your system, and applies the updates automatically. Quantity increases or decreases are reflected in your ERP's line items, new lines are appended, and canceled lines are flagged. Stacksync maintains a version history showing what changed and when, making it easy to trace modifications for compliance auditing. If a change conflicts with your fulfillment status (e.g., reducing quantity on items already shipped), Stacksync alerts your team immediately.

How does Stacksync process Ford Motor Company EDI 860 changes?

When Stacksync receives a Ford Motor Company 860, it identifies the original PO by reference number, compares the changed fields against the current order in your system, and applies the updates automatically. Quantity increases or decreases are reflected in your ERP's line items, new lines are appended, and canceled lines are flagged. Stacksync maintains a version history showing what changed and when, making it easy to trace modifications for compliance auditing. If a change conflicts with your fulfillment status (e.g., reducing quantity on items already shipped), Stacksync alerts your team immediately.

Do I need to respond to a Ford Motor Company EDI 860 with an 865?

Some Ford Motor Company trading programs require an EDI 865 (Purchase Order Change Acknowledgment) in response to every 860. The 865 confirms that you received the change request and indicates whether you accept the modifications, reject them, or need further negotiation. Even when not mandatory, sending an 865 is good practice because it closes the communication loop and prevents Ford Motor Company from resending the same change. Stacksync can generate 865 responses automatically based on your acceptance rules, similar to how it handles 855 PO acknowledgments.

Do I need to respond to a Ford Motor Company EDI 860 with an 865?

Some Ford Motor Company trading programs require an EDI 865 (Purchase Order Change Acknowledgment) in response to every 860. The 865 confirms that you received the change request and indicates whether you accept the modifications, reject them, or need further negotiation. Even when not mandatory, sending an 865 is good practice because it closes the communication loop and prevents Ford Motor Company from resending the same change. Stacksync can generate 865 responses automatically based on your acceptance rules, similar to how it handles 855 PO acknowledgments.

Can pricing be changed through a Ford Motor Company EDI 860?

Yes, Ford Motor Company can modify unit pricing on existing PO line items through the EDI 860. Price changes appear in the PO1 segment with updated unit price values. However, pricing changes via 860 may be subject to Ford Motor Company's vendor agreement terms — some programs restrict supplier-initiated price changes and only allow buyer-initiated modifications. Stacksync validates incoming Ford Motor Company 860 price changes against your contracted pricing and flags discrepancies. Your team can review and approve price adjustments before they flow into your billing system, preventing unexpected margin impacts.

Can pricing be changed through a Ford Motor Company EDI 860?

Yes, Ford Motor Company can modify unit pricing on existing PO line items through the EDI 860. Price changes appear in the PO1 segment with updated unit price values. However, pricing changes via 860 may be subject to Ford Motor Company's vendor agreement terms — some programs restrict supplier-initiated price changes and only allow buyer-initiated modifications. Stacksync validates incoming Ford Motor Company 860 price changes against your contracted pricing and flags discrepancies. Your team can review and approve price adjustments before they flow into your billing system, preventing unexpected margin impacts.

Ready to automate Ford Motor Company EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding