The file reports one declared unit of the product
EveryInput_Quantity, Input_Weight and Input_kgCO2e in the file is what one declared unit of the product you exported consumes or emits. A nested row is multiplied through every line above it — each ancestor contributes the number of its own source element’s declared units that the line consumes.
The model page does the opposite, deliberately. A row there shows the quantity as you entered it on its parent, because a bill-of-materials line is edited in its parent’s terms (“this frame takes four legs”). That’s the number you need while modeling; the file’s is the number you need when reporting.
Level tells you which basis a row is on. Level 1 is a top-level line of the exported product, and every step deeper adds one. On a Level 1 row the two surfaces agree, because there’s nothing above it to multiply through.
A worked example
A factory model takes 6.05 kg of an element that is itself a model, declared per kg. Two of that element’s own lines:
Every figure here is right. Multiply an
Input_Quantity on the page by the quantity on each line above it and you land on the file’s.
Input_Weight is the one column that won’t always reconcile that way. The file derives every line’s weight from its quantity and its source element’s weight, while the model page shows a weight recorded on the line itself whenever there is one. Where those two disagree, the gap is the recorded weight, not the basis.
Related topics
- Data quality rating — the DQR columns the file carries
- Versioning — which version each row reports
- Life-cycle stages — which stage a nested line is reported under