Background
A bug caused cost layer analysis and rebuild jobs to crash silently whenever a purchase order shipment carried extra costs (freight, duty, handling fees, etc.). Because the crash was silent, the rebuild appeared to complete, but those shipment-level charges were not folded into the landed cost of received items.
This has been fixed. All future cost layer analysis runs and rebuilds will correctly include shipment extra costs.
Who is affected?
You are likely affected if all three of the following are true:
- You enter extra costs (freight, duty, surcharges) on purchase order shipments — the typical workflow for recording real carrier and customs invoices.
- You have run a cost layer rebuild or relied on cost layer analysis at any point.
- Those receipts have not had a rebuild triggered since today's fix.
If you enter extra costs only on individual receiving reports (not on the shipment), you are not affected.
What is the impact?
For affected receipts, your cost layers did not include the shipment surcharges, so:
- Inventory valuation (balance sheet) was understated by the missed charges.
- COGS / profit margins on any units already sold from those receipts were understated at the time of sale. Units already sold keep the cost recorded at sale time — a rebuild cannot retroactively fix sold units, but it will correct on-hand inventory values.
- Cost layer reports and analysis screens showed landed cost without the shipment extras.
What should I do?
Step 1 — Identify affected receipts
Review receiving reports linked to shipments that had extra costs (freight, duty, etc.) entered at the shipment level, particularly if those receipts were processed before today's fix.
Step 2 — Contact Luminous support to run the backfill and rebuild
Because of how the fix works, a self-serve cost layer rebuild is not enough on its own for most affected receipts. Many affected receiving-report lines are missing an internal link back to their shipment record, and without that link a rebuild has no way to find the shipment's extra costs, no matter how many times it's run.
Contact Luminous support with the affected SKUs or receiving reports. Support will run a one-time backfill to restore that link, then trigger the cost layer rebuild, which will re-read all shipment extra costs and recompute each item's true landed cost.
For a full walkthrough of the rebuild process and what it recalculates, see Cost Layer Rebuild: What It Does and Why It Matters.
Step 3 — Review your cost layer reports
After the rebuild completes, compare before/after landed costs for affected SKUs. Any previously missing freight or duty charges will now appear as part of the per-unit cost.
Going forward
No configuration changes are needed. Shipment extra costs are now automatically included in all cost layer calculations. The typical workflow of recording freight and duty on the shipment (and letting them flow through to receiving) works as intended.
Related: Where to enter extra costs: PO vs shipment vs receiving report