What happened

Luminous runs an hourly background job that fills in costs for order lines that were recorded with a $0 cost. A bug in that job caused it to multiply the unit cost by the base UOM quantity (the number of selling units inside one case, pallet, etc.) instead of the selling quantity on the order line.

For example, if a case contains 4,800 each, the job would write:

cost = unit_cost × 4,800

instead of the correct:

cost = unit_cost × quantity_sold (e.g., 1 case)

This produced phantom COGS entries that were hundreds or thousands of times the actual sale value. The inflated values appeared on the Transaction COGS report and on individual order cost records.

A secondary issue allowed these inflated costs to be reused as 'donor' values to fill in other zero-cost lines for the same SKU, potentially spreading the error to sibling records.

What was fixed

Both issues are resolved. The hourly filler now always uses the selling quantity. A guard also disqualifies any historical cost record whose base UOM quantity exceeds its selling quantity, preventing inflated costs from propagating.

New order lines processed after this fix are correct. Pre-existing inflated rows require a targeted repair.

How to identify and repair historical rows

The repair is run by Luminous Support on a per-account basis. It identifies rows where the recorded cost matches the pattern order_item_cost × (base_uom_qty / selling_qty) (i.e., the inflation fingerprint) and resets them to the correct order-item cost.

Before running the repair, Support will provide a dry-run summary showing:

  • How many rows are affected
  • The total current (inflated) cost sum
  • The total corrected cost sum
  • The dollar overstatement that would be removed

To request a repair, contact Luminous Support and provide:

  1. The SKU(s) you believe are affected, or the approximate date range.
  2. Whether you want to see a dry-run preview first (recommended).

Note: Rows that have active cost-layer associations are not auto-repaired by this tool — they are surfaced in a separate review list during the dry run and require a cost-layer-aware correction.

How to check if you were affected

  1. Go to Insights → Reports then open the COGS Insight Dashboard (search "COGS" in the Reports Library if it isn't pinned for you)..
  2. Use the Order Date filter (a date-range picker) and the Channel filter to narrow the results, and use the internal_sku filter to focus on the SKUs you sell in cases or with a UOM conversion.
  3. In the "Total Sold W/ Cost" table, compare Total Cost against quantity for each SKU — a Total Cost far higher than (quantity × your actual landed unit cost) indicates an inflated row. There's no separate "Cost Per Unit" column on this dashboard, so divide Total Cost by quantity to get a per-unit figure and compare it to your expected landed cost.
  4. The "Units Sold w No Cost" and "Units Sold w Neg Cost" tiles at the top of the dashboard flag related data gaps, even though they don't show inflated rows directly.

If you find affected rows, contact Support to request the repair.