Skip to main content

Receive and parse an EDI 856 ASN

Inbound ASN flow: webhook payload for EDI 856, normalized JSON fields, and mapping tips for WMS/ERP ingestion.

Quick answer

Can I poll instead of using webhooks?

Webhooks are recommended for near-real-time receipts. You can also inspect inbound documents in the dashboard while building your handler.

More common questions

Inbound flow overview

When a partner sends an 856 ASN, SignalEDI validates structure and emits a webhook with normalized JSON for WMS/ERP ingestion.

  • HL hierarchy: shipment → order → pack → item
  • Ties to the original 850 PO when present

Example webhook envelope

Verify X-SignalEDI-Signature before trusting the body.

{
  "event": "document.validated",
  "documentId": "doc_01H…",
  "partnerId": "retailmart",
  "documentTypeCode": "856",
  "payload": {
    "shipmentId": "SHP-2201",
    "cartons": [{ "sscc": "00012345678901234567", "lines": [{ "sku": "SKU-100", "quantity": 24 }] }]
  }
}

Mapping to your system

Map shipmentId and SSCC barcodes to warehouse receipts. Keep idempotency on documentId because webhook retries are expected on 5xx responses.

Common questions

© 2026 SignalEDI Inc. All rights reserved.