CSV units

How to Combine CSV Data with Different Units Without Corrupting the Total

Do not total a CSV column until every value has a known unit, scale, and measurement meaning. Keep the original value unchanged, add explicit fields for the source unit and scale, convert compatible measurements into one documented reporting unit, and keep incompatible measures separate. Then reconcile known rows, converted subtotals, exception counts, and source reports. If a file does not say whether 25 means items, cases, kilograms, or thousands of units, do not guess from the number alone.

Short answer

Do not total a CSV column until every value has a known unit, scale, and measurement meaning. Keep the original value unchanged, add explicit fields for the source unit and scale, convert compatible measurements into one documented reporting unit, and keep incompatible measures separate. Then reconcile known rows, converted subtotals, exception counts, and source reports. If a file does not say whether 25 means items, cases, kilograms, or thousands of units, do not guess from the number alone.

CSV data becoming a readable analytics dashboard
A calm first view helps a reader move from raw rows to a useful question.

Upload

Bring the CSV you already use.

Understand

Start with the brief and evidence.

Act

Ask, edit, filter, and export.

A practical starting point

Do not total a CSV column until every value has a known unit, scale, and measurement meaning. Keep the original value unchanged, add explicit fields for the source unit and scale, convert compatible measurements into one documented reporting unit, and keep incompatible measures separate. Then reconcile known rows, converted subtotals, exception counts, and source reports. If a file does not say whether 25 means items, cases, kilograms, or thousands of units, do not guess from the number alone.

Concrete examples

Example 1: Kilograms and pounds share one column

Two warehouse exports both use a weight column. One records 100 kg; the other records 100 lb. Adding the raw values produces 200 with no valid unit. The reviewed workflow retains both source values, converts pounds to the chosen reporting unit with an approved factor, labels the normalized column in kilograms, and checks known shipment rows before totaling it.

Example 2: A report is stated in thousands

A finance export labels a column volume000s, where 25 means 25,000 units. Another file records raw units. Appending the files without applying the documented scale understates the first source by a factor of 1,000. The analyst records sourcescale = 1000, calculates a separate raw-unit field, and reconciles it to the source report.

Example 3: Cases have different pack sizes

A product file reports 10 cases of one SKU and 10 cases of another. The first SKU has 12 items per case; the second has 24. Applying one global case-to-item factor produces the wrong stock total. The conversion joins the correct pack size by SKU and effective date, while unmatched products remain visible as exceptions.

Example 4: Weight and volume cannot be added directly

A supplier export contains flour in kilograms and cooking oil in litres. The dashboard labels their raw sum as “total inventory,” but the result mixes dimensions. The corrected report shows separate weight and volume totals. A product-specific conversion is used only if a documented density and business need justify it.

Example 5: Matching units hide different metric meanings

Two files both report quantity in items. One row means items sold during a day; the other means items on hand at day end. Summing both creates a meaningless total even though the unit matches. The measures remain separate and are charted according to their flow or snapshot meaning.

Examples are illustrative and are not customer results.

Common questions

What is the safest way to work with this CSV problem?

Do not total a CSV column until every value has a known unit, scale, and measurement meaning. Keep the original value unchanged, add explicit fields for the source unit and scale, convert compatible measurements into one documented reporting unit, and keep incompatible measures separate. Then reconcile known rows, converted subtotals, exception counts, and source reports. If a file does not say whether 25 means items, cases, kilograms, or thousands of units, do not guess from the number alone.

Keep exploring

See what your own CSV is saying.

Try the browser workspace with a real file and keep the public guide open when you need help.

Start free