DSW (formerly Shoes.com) X12 856 Ship Notice/Manifest

DSW (formerly Shoes.com) typically requires the EDI 856 Advance Ship Notice to be transmitted within hours of shipment — not days before delivery. The ASN must be sent after the carrier picks up the freight but before the shipment arrives at DSW (formerly Shoes.com)'s receiving dock. Late or missing ASNs often result in compliance chargebacks and can cause receiving delays at the distribution center. Stacksync triggers 856 generation automatically when your WMS or shipping system confirms dispatch, ensuring the ASN reaches DSW (formerly Shoes.com) within the required window without manual intervention from your logistics team.

DSW (formerly Shoes.com) typically requires the EDI 856 Advance Ship Notice to be transmitted within hours of shipment — not days before delivery. The ASN must be sent after the carrier picks up the freight but before the shipment arrives at DSW (formerly Shoes.com)'s receiving dock. Late or missing ASNs often result in compliance chargebacks and can cause receiving delays at the distribution center. Stacksync triggers 856 generation automatically when your WMS or shipping system confirms dispatch, ensuring the ASN reaches DSW (formerly Shoes.com) within the required window without manual intervention from your logistics team.

The DSW (formerly Shoes.com) EDI 856 uses hierarchical levels (HL segments) to describe the shipment structure from top to bottom: shipment level, order level, pack level (cartons or pallets), and item level. Each level contains specific data — the shipment level holds carrier and BOL information, the pack level includes SSCC-18 barcodes and carton dimensions, and the item level lists UPCs and quantities per package. Stacksync builds this hierarchy automatically from your WMS packing data, mapping carton contents and pallet configurations into the correct HL structure required by DSW (formerly Shoes.com).

The DSW (formerly Shoes.com) EDI 856 uses hierarchical levels (HL segments) to describe the shipment structure from top to bottom: shipment level, order level, pack level (cartons or pallets), and item level. Each level contains specific data — the shipment level holds carrier and BOL information, the pack level includes SSCC-18 barcodes and carton dimensions, and the item level lists UPCs and quantities per package. Stacksync builds this hierarchy automatically from your WMS packing data, mapping carton contents and pallet configurations into the correct HL structure required by DSW (formerly Shoes.com).

Penalties for DSW (formerly Shoes.com) ASN errors vary by the type of mistake and your compliance scorecard tier. Common chargeable errors include missing or late ASNs, incorrect carton counts, wrong item quantities, invalid SSCC-18 labels, and mismatches between the ASN and actual received goods. These penalties can range from flat fees per incident to percentage-based fines on the shipment value. Stacksync validates every 856 against the original PO data and your shipping records before transmission, catching errors that would otherwise result in DSW (formerly Shoes.com) chargebacks. The platform maintains an audit trail for dispute resolution.

Penalties for DSW (formerly Shoes.com) ASN errors vary by the type of mistake and your compliance scorecard tier. Common chargeable errors include missing or late ASNs, incorrect carton counts, wrong item quantities, invalid SSCC-18 labels, and mismatches between the ASN and actual received goods. These penalties can range from flat fees per incident to percentage-based fines on the shipment value. Stacksync validates every 856 against the original PO data and your shipping records before transmission, catching errors that would otherwise result in DSW (formerly Shoes.com) chargebacks. The platform maintains an audit trail for dispute resolution.

Most DSW (formerly Shoes.com) programs require SSCC-18 (Serial Shipping Container Code) labels on every carton and pallet, with the corresponding barcodes referenced in the 856 ASN's MAN (Marks and Numbers) segment. The SSCC-18 is a unique 18-digit identifier that links the physical package to the electronic ASN data, enabling DSW (formerly Shoes.com)'s receiving dock to scan and verify shipments against the advance notice. Stacksync generates SSCC-18 numbers that comply with GS1 standards and embeds them in the 856 automatically. If your WMS already assigns SSCC-18s, Stacksync pulls those values directly from your packing records.

Most DSW (formerly Shoes.com) programs require SSCC-18 (Serial Shipping Container Code) labels on every carton and pallet, with the corresponding barcodes referenced in the 856 ASN's MAN (Marks and Numbers) segment. The SSCC-18 is a unique 18-digit identifier that links the physical package to the electronic ASN data, enabling DSW (formerly Shoes.com)'s receiving dock to scan and verify shipments against the advance notice. Stacksync generates SSCC-18 numbers that comply with GS1 standards and embeds them in the 856 automatically. If your WMS already assigns SSCC-18s, Stacksync pulls those values directly from your packing records.

Stacksync connects to your WMS, ERP, or shipping platform and monitors for shipment confirmations. When an order is marked as shipped, Stacksync extracts the packing details — carton contents, weights, dimensions, carrier information, tracking numbers, and SSCC-18 labels — and constructs the 856 ASN document automatically. The platform maps your warehouse data to DSW (formerly Shoes.com)'s required HL hierarchy, populates the BSN, TD1, and REF segments, and validates the complete document before transmitting it. The entire process runs without manual EDI formatting, reducing ASN errors and keeping your DSW (formerly Shoes.com) compliance scores high.

Stacksync connects to your WMS, ERP, or shipping platform and monitors for shipment confirmations. When an order is marked as shipped, Stacksync extracts the packing details — carton contents, weights, dimensions, carrier information, tracking numbers, and SSCC-18 labels — and constructs the 856 ASN document automatically. The platform maps your warehouse data to DSW (formerly Shoes.com)'s required HL hierarchy, populates the BSN, TD1, and REF segments, and validates the complete document before transmitting it. The entire process runs without manual EDI formatting, reducing ASN errors and keeping your DSW (formerly Shoes.com) compliance scores high.