Why Shipped or Billed quantities may have changed
Luminous recently corrected how the Shipped and Qty Billed figures are calculated on purchase order lines that are ordered in a non-base unit of measure (for example, cases when your inventory is tracked in eaches).
If you notice a number that looks different from before, this article explains why.
What changed
When a shipment or bill line is recorded in the same unit as the PO line (for example, cases), Luminous converts it to the base unit to sum totals. That conversion looks up the correct case size for the product on the line.
Previously, if two or more products in your catalog each had their own case size defined for the same unit pair, the lookup could pick up the wrong product's case size — specifically, the one belonging to whichever product had the highest internal record ID. A product with 12 units per case might silently inherit a 48-per-case factor from a different SKU, causing the displayed Shipped quantity to be several times higher or lower than the actual amount.
Luminous now resolves the case size in the correct priority order:
- The line's own product's SKU-level rule
- The product's variant parent's rule (if it is a variant)
- The tenant-wide system rule for that unit pair
- No conversion (factor of 1) if none of the above applies
This matches the same order used when the PO line was originally written, so the displayed Shipped and Billed quantities now agree with what was actually recorded.
When will I see a different number?
| Situation | Old behavior | New behavior |
|---|---|---|
| Two or more products share a unit pair, each with a different case size | Applied whichever product's case size had the highest internal ID | Applies the case size belonging to that line's own product |
| A product has no SKU-level rule and a system-wide rule exists | May have applied another product's SKU rule instead | Correctly falls back to the system-wide rule |
| Only one SKU rule exists for the unit pair, or all lines use the same case size | No change | No change |
| PO line is ordered in the base unit (no conversion needed) | No change | No change |
Does this affect shipments created by a WMS integration?
Yes. When an inbound shipment is reconciled to a purchase order through a warehouse integration, the shipment items are written in the PO line's ordered unit automatically. Those rows go through the same conversion, so the fix applies to integration-created rows just as it does to manually entered ones.
How does this affect Line Status?
The Line Status column (Awaiting Shipment, Partially Shipped, Shipped) and the Remaining to Ship figure are derived from the same corrected Shipped quantity. If a line previously showed the wrong status because the Shipped quantity was over- or understated, the status will now reflect the accurate figure.
Does this affect the External API?
Yes. The quantity_shipped, remaining_to_ship, and quantity_billed fields on the External V1 Purchase Order Items API now return the corrected values. The field names and units are unchanged.
What should I do?
No action is required. Shipped and Billed quantities now reflect your actual shipment and bill records.
If a quantity looks unexpected after the update, verify:
- The unit conversion rule for the product — go to the product's detail page and check the UOM / conversion settings to confirm the case size is configured correctly.
- The shipment or bill record — open the linked shipment or bill to confirm the quantity and unit that was recorded.
If you believe a figure is still incorrect, contact Luminous Support via the in-app chat or email.