Why aren't my component quantities registering (tiny decimals)?
Last updated: July 10, 2026
Luminous tracks quantities to six decimal places. If a build material's base unit is large, a small per-unit consumption can fall below what the system can register — so it shows as zero or doesn't deplete.
Short answer
Set the build material's base unit to the smallest unit you actually consume in (for example grams, occasionally milligrams — not kilograms), and use unit conversions for purchasing.
Why it happens
Teams sometimes set a large base unit (like kilograms) because that's how the supplier sells it. But breaking a kilogram down per finished unit can produce a value like 0.000043 kg, below the 6-decimal limit.
How to fix it
Make the base unit of the class small (e.g. grams).
Set up unit conversions so purchasing and consumption convert cleanly.
Use the supplier SKU's purchase unit for how you buy (e.g. 20 kg increments), while consuming in the small base unit.
Rule of thumb: optimize your base unit for how you consume, not for how you purchase.
Related articles
Still stuck? Contact support if consumption still shows as zero after fixing the base unit and conversions.