Skip to content
X12 Outbound

Fred Meyer Group X12 856 Ship Notice/Manifest

X12 856 (Ship Notice/Manifest) is the EDI transaction exchanged between Fred Meyer Group and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
16
Loops
2
X12 856
All partners ↗

Schema reference

16 segments · 2 loops · X12 856 Ship Notice/Manifest

ISA

ISA Interchange Control Header

GS

GS Functional Group Header

ST

Transaction Set Header

BSN

Beginning Segment for Ship Notice

Loop
HL

Hierarchical Level

LIN

Item Identification

SN1

Item Detail (Shipment)

PRF

Purchase Order Reference

PID

Product/Item Description

TD1

Carrier Details (Quantity and Weight)

TD5

Carrier Details (Routing Sequence/Transit Time)

REF

Reference Information

MAN

Marks and Numbers Information

DTM

Date/Time Reference

Loop
N1

Party Identification

SE

Transaction Set Trailer

Trading partners

4+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Fred Meyer Group EDI 856 FAQ

Common questions about 856 Ship Notice/Manifest with Fred Meyer Group.

What is X12 856 Ship Notice/Manifest?
X12 856 (Ship Notice/Manifest) is the EDI transaction set used to exchange ship notice/manifest data. Fred Meyer Group requires it from trading partners.
Does Fred Meyer Group require 856 for trading partners?
Yes — Fred Meyer Group supports X12 856 Ship Notice/Manifest. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Fred Meyer Group 856 with Stacksync?
Most companies go live with Fred Meyer Group 856 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.

Ready to automate your Fred Meyer Group EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.