What Is an EDI 860 (Purchase Order Change Request)?

X12 lists the 860 and the 865 as two additional transaction sets that may be used in the purchase order process. Together with the 850 and 855, they enable the initial ordering process and updates to it, from both the buyer and the seller.

For the processes in its supply chain overview, X12 assumes a 997 Functional Acknowledgment is issued in response to each transaction set received, unless otherwise noted.

Not every trading partner implements the 860. X12 says partners without the 860 or 865 may send several rounds of the 850 and 855 under the same purchase order number, up to an agreed cut-off point, or handle changes by telephone, fax or email.

X12 publishes an example 865 that rejects a buyer's 860, and it notes that all POC segments from the buyer's 860 are included in that 865. In the example, each POC line describes one line item change:

• The line item number
• The type of change, such as a quantity increase or a quantity decrease
• The original order quantity and the quantity after the change
• The unit of measure and the unit price
• The part number, such as a manufacturer or buyer part number

The 865 in that example also names the purchase order number and the change order sequence number it is responding to.

In X12's example, one POC line is a quantity decrease: the original order quantity was 75 each at a contract unit price of $6.95, revised to 50.

• Before the change: 75 x $6.95 = $521.25
• After the change: 50 x $6.95 = $347.50
• Difference: 25 fewer units, $173.75 less on that line

In that example the seller rejected the whole 860, because the line items it identified had already been deleted from the purchase order. The seller would not act until it received a confirming 860 or an 850 purchase order cancellation.

• Missing the cut-off. Purchase orders have cut-off dates. X12 warns that missing one may mean an order ships without the latest information from one of the trading partners.
• Changes made outside EDI. When a change arrives by telephone or email, the new information has to be added to the right system in a timely manner. Otherwise, what gets delivered may not be what the buyer expects.
• Changes that no longer match the order. In X12's example, an 860 targeted lines that were already deleted, so the seller rejected it.

Shopify lets you edit orders after they're placed to make adjustments before fulfillment. You can add or remove products, adjust item quantities, update shipping fees, and apply or remove manual discounts. If the order total decreases, you can issue a refund. If more payment is required, you can send the customer an updated invoice.

Apps follow a three-step workflow in the GraphQL Admin API: begin the edit with orderEditBegin, apply changes with mutations such as orderEditAddVariant or orderEditSetQuantity, then save with orderEditCommit. The orderEditSetQuantity mutation can increase, decrease or remove items by adjusting their quantities. The POC lines in X12's example are quantity increases and decreases.

Uncap's Shopify EDI integration guide advises you to verify that the integration handles all document types your trading partners require: 850, 855, 856 and 810 at minimum. Some partners also require 846, 860 (Purchase Order Change Request) or 824 (Application Advice).

• EDI (electronic data interchange)
• EDI 850
• EDI 855
• EDI 856
• EDI 997
• Purchase order

• X12 Transaction Sets
• X12 Supply Chain Transaction Flow
• X12 Example: Rejected PO Change (865)