How automatic EDI 856 (ASN) sending works

Whenever a non-voided shipment is recorded against an EDI-sourced sales order in Luminous, the system automatically generates and transmits an EDI 856 Ship Notice / Manifest (ASN) to your trading partner within seconds of the shipment being saved. This happens in the background as part of the normal shipment creation flow.

There are two ways to change this behavior, depending on your goal:

Option A — Send one consolidated 856 when the entire order ships (recommended for multi-shipment orders)

If you need to send a 856, but only after every item on the order has shipped (rather than one per individual shipment), you can enable the Send 856 on Order Complete setting on your EDI integration account.

With this setting on, Luminous holds all per-shipment 856 transmissions and instead sends a single, consolidated ASN once every active fulfillment order on the sales order reaches Shipped status.

Steps:

  1. Click your name in the top-right corner, choose Settings, then click Integrations.
  2. Find your EDI integration account and click the Edit (pencil) icon.
  3. Under Settings, check the box labelled Send 856 on Order Complete.
  4. Click Save.

All future shipments on EDI orders will now wait until the full order is complete before the ASN is transmitted.

Option B — Completely suppress the automatic 856 transmission

If you need to stop Luminous from sending any 856 at all (for example, you send ASNs through a separate system), this requires removing the EDI 856 transaction configuration from your integration account's Transaction Keys JSON.

Because the Transaction Keys field is a structured JSON object and an incorrect edit can break other EDI documents (855, 810, etc.), this change should be made by the Luminous support team or an admin who is familiar with your EDI integration's credentials setup.

To request this change:

  1. Contact Luminous support and specify that you want the 856 transaction key removed from your EDI integration account.
  2. Provide the name or label of the EDI integration account in question.

Once the 856 transaction key is absent, Luminous will skip the 856 entirely for all future shipments on EDI orders — no ASN will be generated or transmitted.

Important notes

  • These settings apply only to EDI-sourced orders (orders that arrived via an EDI 850 Purchase Order). Shipments on non-EDI orders are unaffected.
  • Shipments that are voided or in Pending status never trigger an automatic 856, regardless of your configuration.
  • If a 856 fails to send, it will be retried automatically up to 5 times (with 60-second intervals between attempts) before failing permanently. You can view EDI document transmission status from the EDI Documents report or directly on a sales order's EDI details.