X12
Inbound

Lipari Foods X12 860 Purchase Order Change Request

Lipari Foods (via SPS Commerce)
The EDI 860 is sent by Lipari Foods 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.
27segments
8loops
5mandatory

Schema Reference

27 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 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
GS GS Functional Group Header
Mandatory Max: 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
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BCH Beginning Segment for Purchase Order Change
Mandatory Max: 1
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
BCH06 Date
M DT 8-8
BCH11 Date
O DT 8-8
REF Reference Information
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
FOB F.O.B. Related Instructions
FOB01 Shipment Method of Payment
M ID 2-2
FOB02 Location Qualifier
C ID 1-2
SAC Loop Repeat: 25
SAC Service, Promotion, Allowance, or Charge Information
Optional Max: 1
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
SAC08 Rate
O R 1-9
SAC12 Allowance or Charge Method of Handling Code
O ID 2-2
SAC15 Description
C AN 1-80
ITD Terms of Sale/Deferred Terms of Sale
Optional Max: 5
ITD03 Terms Discount Percent
O R 1-6
ITD05 Terms Discount Days Due
C N0 1-3
ITD07 Terms Net Days
O N0 1-3
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
TD5 Carrier Details (Routing Sequence/Transit Time)
Optional Max: 12
TD504 Transportation Method/Type Code
C ID 1-2
N9 Loop Repeat: 1,000
N9 Extended Reference Information
Optional Max: 1
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-50
MTX Text
MTX02 Textual Data
C AN 1-4096
N1 Loop Repeat: 200
N1 Party Identification
Optional Max: 1
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
N3 Party Location
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
PER Administrative Communications Contact
PER01 Contact Function Code
M ID 2-2
PER02 Name
O AN 1-60
PER03 Communication Number Qualifier
C ID 2-2
PER04 Communication Number
C AN 1-256
PER05 Communication Number Qualifier
C ID 2-2
PER06 Communication Number
C AN 1-256
PER07 Communication Number Qualifier
C ID 2-2
PER08 Communication Number
C AN 1-256
PER09 Contact Inquiry Reference
O AN 1-20
POC Loop Repeat: 1,000
POC Line Item Change
Optional Max: 1
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
POC07 Basis of Unit Price Code
O ID 2-2
POC08 Product/Service ID Qualifier
C ID 2-2
POC09 Product/Service ID
C AN 1-48
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
POC16 Product/Service ID Qualifier
C ID 2-2
POC17 Product/Service ID
C AN 1-48
CTP Pricing Information
CTP08 Monetary Amount
O R 1-18
MEA Measurements
Optional Max: 40
MEA02 Measurement Qualifier
O ID 1-3
MEA03 Measurement Value
C R 1-20
PID Loop Repeat: 1,000
PID Product/Item Description
Optional Max: 1
PID01 Item Description Type
M ID 1-1
PID02 Product/Process Characteristic Code
O ID 2-3
PID05 Description
C AN 1-80
PO4 Item Physical Details
PO401 Pack
O N0 1-6
PO402 Size
C R 1-8
PO403 Unit or Basis for Measurement Code
C ID 2-2
SAC Loop Repeat: 25
SAC Service, Promotion, Allowance, or Charge Information
Optional Max: 1
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
SAC08 Rate
O R 1-9
SAC12 Allowance or Charge Method of Handling Code
O ID 2-2
SAC15 Description
C AN 1-80
N9 Loop Repeat: 1,000
N9 Extended Reference Information
Optional Max: 1
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-50
MTX Text
MTX02 Textual Data
C AN 1-4096
CTT Loop Repeat: 1
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
CTT02 Hash Total
O R 1-10
CTT03 Weight
C R 1-10
CTT04 Unit or Basis for Measurement Code
C ID 2-2
CTT05 Volume
C R 1-8
CTT06 Unit or Basis for Measurement Code
C ID 2-2
AMT Monetary Amount Information
Optional Max: 5
AMT01 Amount Qualifier Code
M ID 1-3
AMT02 Monetary Amount
M R 1-18
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Lipari Foods 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.

Lipari Foods EDI 860 FAQ

Common questions about 860 Purchase Order Change Request transactions with Lipari Foods.

How long does it take to set up Lipari Foods EDI with Stacksync?

Most suppliers are fully connected and processing live Lipari Foods EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Lipari Foods?

No. Stacksync handles the entire EDI transport layer. We connect directly to Lipari Foods's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Lipari Foods compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Lipari Foods?

Stacksync supports all EDI document types required by Lipari Foods — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Lipari Foods EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Lipari Foods's EDI network and your system in real time.

What happens when Lipari Foods updates their EDI specifications?

Stacksync monitors Lipari Foods's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.