Why Luminous suppresses EDI documents for cancelled orders
If your account has the cancelled-order EDI guard enabled, Luminous blocks outbound EDI 856 (Advance Ship Notice) and 810 (Invoice) documents whenever the underlying order has been cancelled. This is intentional — it prevents trading-partner chargebacks or compliance penalties from filing EDI documents against orders the retailer has already cancelled. (This guard is a feature that rolls out per tenant — contact support if you're not sure whether it's active on your account.)
What triggers the block?
A document is suppressed when either of the following is true at the time the document would be sent:
| Condition | Example |
|---|---|
| The sales order was cancelled by the source channel | Order was pulled back as cancelled from Shopify, ShipStation, or an EDI 860, regardless of what its fulfillment orders show |
| The fulfillment order tied to that specific shipment or invoice has a status of cancelled, canceled, voided, failed, or trashed | 3PL rejected the pick; the FO was manually cancelled in Luminous |
A cancelled sales order is checked first and is a hard block on its own. Separately, only the fulfillment order(s) directly tied to the specific shipment or invoice are checked for FO-level cancellation — a cancelled sibling fulfillment order on a different line of the same sales order does not suppress a legitimate document for a live, shipped fulfillment order.
Which emission paths are covered?
The guard runs inside the background job that actually sends the document, not just at the point where the job is dispatched — including forced/bulk re-sends. This means the block applies to:
- Automatic send on shipment creation
- Automatic send on invoice creation
- The nightly scheduled batch that retries pending 856 documents
- Bulk backfill commands run by support staff
- Manual resend from the sales order detail page
What should I do if the document really should have been sent?
- Verify the order and fulfillment-order status. Open the sales order and confirm whether it — or the specific fulfillment order tied to the shipment/invoice — is genuinely cancelled. If it was cancelled in error, restore it and re-attempt the send.
- Contact support for a one-off override. If the cancellation is correct but you still need to file the document with the trading partner (e.g. a partial-ship scenario where some lines shipped before cancellation), contact Luminous support. Overrides are handled at the tenant level and are auditable.
I expected a document but don't see one in the EDI Report — how do I confirm it was suppressed?
A suppressed document does not create a failed (or any) row in the EDI Report (Insights → EDI Report) — it will not appear there in any state. Instead, an informational entry is written to the server-side application log only, which is visible to Luminous support but not in the product UI. If you're missing an expected 856 or 810 for a specific order, check the order's and fulfillment order's status first; if either is cancelled and the shipment/invoice date predates the cancellation, suppression is the expected outcome.