Skip to main content

Measurements: how units, conversions and dimension attributes work

Measurements define how SKULaunch stores, interprets and normalises physical values such as length, weight, volume, temperature. Every dimension attribute relies on the measurement system to ensure values are consistent, comparable and exportable.

S
Written by SKULaunch Support
Updated over 4 months ago

What measurements are

A measurement is a structured category representing a physical property.

Examples:

  • Length

  • Weight

  • Volume

  • Area

  • Temperature

  • Power

  • Speed

Each measurement contains:

  1. A defined list of allowed units

  2. A standard unit (the canonical unit SKULaunch uses internally)

These definitions allow SKULaunch to convert numbers reliably when normalising or importing data.

Measurement types

Measurements define a dimensional category. Examples from your environment include:

  • Length

  • Area

  • Count

  • Coverage

  • Density

  • Force

  • Light

  • Package Type

  • Power

  • Pressure

  • Rate

  • Sound

  • Speed

  • Temperature

  • Time

  • Volume

Each of these categories behaves independently.
A length value will not be confused with a weight value, and so on.

Units

Within each measurement are one or more units.
Units include:

  • Symbol (cm, mm, ft, in, km, m)

  • Label (Centimeter, Foot, Inch)

  • Code (CENTIMETER, FOOT, INCH)

Units define how measurement values are displayed and interpreted.

Examples from the screenshot:

Length units:

  • Meter (m)

  • Kilometre (km)

  • Foot (ft)

  • Inch (in)

  • Millimetre (mm)

  • Centimetre (cm)

  • Gauge (Ga)

Each measurement can have many units depending on global usage and product domain.

Standard unit

Every measurement has a standard unit that SKULaunch uses for internal consistency.

In your example, for Length, the standard unit is:

  • Millimetre (mm)

What “standard unit” means:

  • All dimensional values are normalised to this unit internally

  • AI conversions happen relative to this unit

  • Exports can convert values into other units on demand

  • Comparisons and calculations remain consistent

Example:

If the source text says “Length: 0.34 m”, SKULaunch stores:

  • 340 mm internally

  • “0.34 m” may still be displayed to users depending on view settings

How dimension attributes use measurements

A dimension attribute (for example Length, Net Weight or Volume) is linked to a measurement.

This connection determines:

  • Which units users can enter

  • Which units AI can recognise

  • How values are converted

  • How data is validated

  • How it is exported

If an attribute is assigned the measurement “Length”, it will:

  • Accept any length unit

  • Convert to millimetres internally

  • Validate inputs based on unit behaviour

How AI uses measurements

AI enrichment uses measurements to:

1. Detect units automatically

Examples:

  • “12cm” → 12 cm

  • “0.12 m” → 120 mm

  • “3 inches” → 76.2 mm

2. Convert values into the standard unit

Regardless of the unit found in the text, SKULaunch always stores the standard-unit form.

3. Prevent incorrect assignments

If the AI mistakenly extracts a time unit for a length attribute (for example “2h”), the system rejects it.

4. Support inference (if enabled)

If inference is on and the AI finds an unlabelled number next to context clues, it may infer the measurement.

Example:
“Dimensions 10 x 20 x 5 mm” → Length = 10 mm

Best practices for measurement design

1. Use only units that you truly need

More units = more potential variation.
Avoid rarely used or ambiguous units.

2. Choose a standard unit that is easy to calculate with

Small granular units (mm, ml, g) reduce rounding errors.

3. Keep naming consistent

Use one spelling convention per measurement (Meter vs Metre).

4. Avoid domain overlap

Do not place units meant for different measurements in the same category.

5. Review measurement definitions every few months

As new products appear, ensure measurements stay relevant.

Did this answer your question?