Why a SKU Can Show Zero Valuation
In Luminous, every unit of on-hand inventory must have a cost layer — a record of how many units arrived and at what landed cost. When a cost layer exists but its unit cost is $0.00 (and it is not a deliberate variance entry), the SKU's valuation will appear as zero in stock snapshots, balance-sheet reports, and margin calculations.
The most common root causes are:
| Cause | Why it happens |
|---|---|
| Receipt with no purchase price | A Receiving Report was submitted with a $0.00 unit price, so no cost was attached to the incoming stock. |
| Inventory count adjustment | Stock was added via a count adjustment without specifying a per-unit cost. |
| Beginning-balance or data import | Starting inventory was seeded (e.g., during onboarding or a bulk import) without cost information. |
| Assembly order with zero-cost components | A finished good was assembled from components that themselves had no cost, so the finished-good layer inherited a $0.00 cost. |
| Cost layers out of sync | Rare edge cases after manual corrections or multi-warehouse transfers can leave a layer with a cost of $0.00. |
Kit (bundle) SKUs are a separate case. Kits are virtual products in Luminous and intentionally carry no valuation of their own — value lives on the component SKUs. See Why Don't My Kits (Bundles) Appear in the Inventory Valuation Report? for details.
How to Identify Affected SKUs
- Navigate to Inventory and open the product record for the SKU in question.
- Select the Costs tab (the Cost Layers grid).
- Look for rows where Unit Cost is $0.00 and Remaining Qty is greater than zero. Those are the layers dragging the valuation to zero.
You can also check the Variance column — a layer flagged as a Variance entry is intentional and will not count toward valuation in the usual sense.
How to Fix It
Option 1 — Run a Cost Layer Analysis on a single SKU (recommended first step)
This is the safest approach because it shows you a before-and-after preview before making any changes.
- Open the product in Inventory.
- Go to the Costs tab.
- Click the Cost Layer Analysis button (top-right of the Cost Layers section).
- In the dialog that opens, note your Costing Method (FIFO or Weighted Average).
- If you are on Weighted Average, you can optionally enable FIFO multi-warehouse distribution to split quantities across warehouses by current on-hand stock.
- The analysis runs automatically when the dialog opens (click Run Analysis Again after changing options). The system runs a read-only preview and shows:
- On-hand units — total current stock for the SKU
- Current cost — the $0.00 unit cost stored today
- New cost — the proposed unit cost derived from your receiving history
- Receipts included / excluded — the shipment layers feeding the rebuilt cost
- Detailed log — a full breakdown of the calculation
- Review the proposed cost. If it looks correct, click Recalculate Cost Layers to apply the changes.
Tip: Running the analysis is always safe — no data is changed until you click Recalculate.
Option 2 — Enable the Nightly Cost Layer Rebuild (Weighted Average accounts)
If your account uses Weighted Average costing and you frequently add costs to older shipments after receiving, turning on the nightly rebuild keeps all cost layers current automatically.
- Go to Settings → Inventory.
- Under Cost Layers Settings, enable Rebuild Cost Layers Nightly.
- Optionally enable Nightly rebuild: FIFO multi-warehouse distribution if you want layer quantities split across warehouses proportional to on-hand stock (requires the nightly rebuild to be active).
- Click Save Settings.
The rebuild runs overnight and re-derives each SKU's cost from your actual receiving history, correcting zero-cost layers and recording all changes in the audit trail.
Option 3 — Bulk zero-cost repair (contact support)
If many SKUs are affected — for example after a large data import — Luminous support can trigger a bulk repair job that:
- Finds every cost layer with a $0.00 unit cost, remaining quantity, and no variance flag.
- For each affected SKU, looks for the most recent non-zero cost layer for the same product and uses that cost as the replacement.
- If no non-zero cost layer exists, falls back to the product's base price.
- Skips any SKU where neither a non-zero layer nor a base price can be found (these require manual correction of the original receipt).
The job runs asynchronously and produces a summary of how many layers were updated, skipped, or encountered errors. Contact your Luminous support team to initiate this.
Preventing Zero Valuation Going Forward
- Always enter a unit price on Receiving Reports. Even a placeholder cost is better than $0.00 — you can correct it later and run Cost Layer Analysis to propagate the update.
- Specify a cost on inventory count adjustments when you are adding net new units.
- For beginning balances, include landed cost data in the import file before the import is processed.
- If you frequently add extra costs (freight, duties) to shipments after the fact, consider enabling the Nightly Cost Layer Rebuild so those costs always flow into your valuation.