How Luminous sets the unit of measure on outbound EDI documents
When Luminous generates an outbound EDI 856 (Advance Ship Notice) or 810 (Invoice), the unit of measure (UOM) on each line item is taken directly from the original inbound EDI 850 purchase order that created the sales order — not from Luminous's internal base unit.
Why this matters
Retailers frequently order in a non-base unit (e.g. CS for case, DZ for dozen) even though Luminous tracks inventory in individual units (EA). If the 856 or 810 was filed in EA instead of CS, the retailer's receiving system would flag a quantity discrepancy, potentially triggering a chargeback or a manual reconciliation request.
How the match works
For each line on the outbound document, Luminous looks up the corresponding line from the stored 850 and copies its UOM fields. The match is performed by SKU and by internal SKU. If no match is found (e.g. the 850 is missing from the document store), the line falls back to EA.
Troubleshooting a UOM mismatch
| Symptom | Likely cause | Action |
|---|---|---|
Outbound 856/810 shows EA but 850 was in CS | Original 850 document not found in storage | Contact support to re-ingest the 850 |
| UOM is correct but quantity looks wrong | Quantity may not have been converted to the retailer's UOM | Verify the UOM conversion rule for the SKU (Inventory → SKUs → open the SKU → Unit Conversions) |
| UOM differs between 856 and 810 for the same order | Rare; check whether both documents resolved the same 850 source | Contact support with the order number and document IDs |
Checking the UOM on a sent document
Go to Insights → EDI Report, filter by the sales order number, and open the raw document. The UOM field appears on each IT1 line (856) or IT1/PO1 line (810). Compare it against the original 850 document in the same report to confirm they match.