Google X12 860 Purchase Order Change Request

A Google 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. Google uses 860s instead of canceling and reissuing entire 850s for efficiency, especially when only a few lines need adjustment. Stacksync processes incoming Google 860s by automatically updating the original PO record in your system, maintaining a change history for audit purposes.

A Google 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. Google uses 860s instead of canceling and reissuing entire 850s for efficiency, especially when only a few lines need adjustment. Stacksync processes incoming Google 860s by automatically updating the original PO record in your system, maintaining a change history for audit purposes.

Google 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 Google 860 arrives, it applies the changes incrementally to your existing order record rather than creating a duplicate entry.

Google 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 Google 860 arrives, it applies the changes incrementally to your existing order record rather than creating a duplicate entry.

When Stacksync receives a Google 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.

When Stacksync receives a Google 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.

Some Google 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 Google from resending the same change. Stacksync can generate 865 responses automatically based on your acceptance rules, similar to how it handles 855 PO acknowledgments.

Some Google 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 Google from resending the same change. Stacksync can generate 865 responses automatically based on your acceptance rules, similar to how it handles 855 PO acknowledgments.

Yes, Google 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 Google's vendor agreement terms — some programs restrict supplier-initiated price changes and only allow buyer-initiated modifications. Stacksync validates incoming Google 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.

Yes, Google 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 Google's vendor agreement terms — some programs restrict supplier-initiated price changes and only allow buyer-initiated modifications. Stacksync validates incoming Google 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.