X12

Inbound

Bealls Inc. X12 860 Purchase Order Change Request

Bealls Inc (Temporary)

The EDI 860 is sent by Bealls Inc. 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.

19segments

6loops

5mandatory

Book a demo

← All Bealls Inc. transactions

Schema Reference

19 segments · X12 860 Purchase Order Change Request

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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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 Interchange Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

BCH01 Transaction Set Purpose Code

M ID 2-2

BCH02 Purchase Order Type Code

M ID 2-2

BCH03 Purchase Order Number

M AN 1-22

BCH04 Release Number

O AN 1-30

BCH06 Date

M DT 8-8

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-50

FOB01 Shipment Method of Payment

M ID 2-2

FOB02 Location Qualifier

C ID 1-2

FOB03 Description

O AN 1-80

SAC Loop Repeat: 25

SAC01 Allowance or Charge Indicator

M ID 1-1

SAC02 Service, Promotion, Allowance, or Charge Code

C ID 4-4

SAC05 Amount

O N2 1-15

SAC06 Allowance/Charge Percent Qualifier

C ID 1-1

SAC07 Percent, Decimal Format

C R 1-6

SAC12 Allowance or Charge Method of Handling Code

O ID 2-2

SAC15 Description

C AN 1-80

ITD01 Terms Type Code

O ID 2-2

ITD12 Description

O AN 1-80

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

N9 Loop Repeat: 1,000

N901 Reference Identification Qualifier

M ID 2-3

N903 Free-form Description

C AN 1-45

MTX02 Textual Data

C AN 1-4096

N1 Loop Repeat: 200

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N201 Name

M AN 1-60

N202 Name

O AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

C ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

C ID 2-3

POC Loop Repeat: 1,000

POC01 Assigned Identification

O AN 1-20

POC02 Change or Response Type Code

M ID 2-2

POC03 Quantity

C R 1-15

POC06 Unit Price

C R 1-17

POC10 Product/Service ID Qualifier

C ID 2-2

POC11 Product/Service ID

C AN 1-48

POC12 Product/Service ID Qualifier

C ID 2-2

POC13 Product/Service ID

C AN 1-48

POC14 Product/Service ID Qualifier

C ID 2-2

POC15 Product/Service ID

C AN 1-48

PID Loop Repeat: 1,000

PID01 Item Description Type

M ID 1-1

PID02 Product/Process Characteristic Code

O ID 2-3

PID05 Description

C AN 1-80

CTT Loop Repeat: 1

CTT01 Number of Line Items

M N0 1-6

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating Bealls Inc. 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.

Bealls Inc. EDI 860 FAQ

Common questions about 860 Purchase Order Change Request transactions with Bealls Inc..

What types of changes can be made with a Bealls Inc. EDI 860?

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

Should Bealls Inc. cancel and resend an 850 or use an EDI 860?

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

How does Stacksync process Bealls Inc. EDI 860 changes?

When Stacksync receives a Bealls Inc. 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 Bealls Inc. EDI 860 with an 865?

Some Bealls Inc. 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 Bealls Inc. 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 Bealls Inc. EDI 860?

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