X12
Outbound

Von Maur X12 856 Ship Notice/Manifest

Von Maur
The EDI 856 Advance Ship Notice notifies Von Maur that a shipment is in transit. It includes carton-level detail, pallet configurations, SSCC-18 barcodes, and carrier tracking information. Accurate ASNs are critical for receiving efficiency and compliance.
16segments
2loops
6mandatory

Schema Reference

16 segments · X12 856 Ship Notice/Manifest

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 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
BSN Beginning Segment for Ship Notice
Mandatory Max: 1
BSN01 Transaction Set Purpose Code
M ID 2-2
BSN02 Shipment Identification
M AN 2-30
BSN03 Date
M DT 8-8
BSN04 Time
M TM 4-8
HL Loop Repeat: 200,000
HL Hierarchical Level
Mandatory Max: 1
HL01 Hierarchical ID Number
M AN 1-12
HL03 Hierarchical Level Code
M ID 1-2
LIN Item Identification
Optional Max: 1
LIN02 Product/Service ID Qualifier
M ID 2-2
LIN03 Product/Service ID
M AN 1-48
SN1 Item Detail (Shipment)
Optional Max: 1
SN102 Number of Units Shipped
M R 1-10
SN103 Unit or Basis for Measurement Code
M ID 2-2
PRF Purchase Order Reference
Optional Max: 1
PRF01 Purchase Order Number
M AN 1-22
TD1 Carrier Details (Quantity and Weight)
Optional Max: 20
TD101 Packaging Code
O AN 3-5
TD102 Lading Quantity
C N0 1-7
TD106 Weight Qualifier
O ID 1-2
TD107 Weight
C R 1-10
TD108 Unit or Basis for Measurement Code
C ID 2-2
TD5 Carrier Details (Routing Sequence/Transit Time)
Optional Max: 12
TD502 Identification Code Qualifier
C ID 1-2
TD503 Identification Code
C AN 2-80
TD505 Routing
C AN 1-35
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
MAN Marks and Numbers
MAN01 Marks and Numbers Qualifier
M ID 1-2
MAN02 Marks and Numbers
M AN 1-48
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
N1 Loop Repeat: 200
N1 Name
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
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
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 Von Maur EDI 856

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

Validate
Transform
Route
Monitor
Stacksync builds and transmits 856 ASNs automatically when shipments are created in your WMS. Carton contents, pallet labels, SSCC-18 codes, and tracking numbers are pulled from your warehouse data — eliminating manual EDI entry.

Von Maur EDI 856 FAQ

Common questions about 856 Ship Notice/Manifest transactions with Von Maur.

How long does it take to set up Von Maur EDI with Stacksync?

Most suppliers are fully connected and processing live Von Maur 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 Von Maur?

No. Stacksync handles the entire EDI transport layer. We connect directly to Von Maur'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 Von Maur 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 Von Maur?

Stacksync supports all EDI document types required by Von Maur — 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 Von Maur 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 Von Maur's EDI network and your system in real time.

What happens when Von Maur updates their EDI specifications?

Stacksync monitors Von Maur'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.