Skip to main content

Creating and managing measurements in SKULaunch

This article explains what measurements are, why they matter, and how to set them up correctly. You’ll learn how to create measurements, define standard and additional units.

S
Written by SKULaunch Support
Updated over 4 months ago

What is a measurement?

A measurement in SKULaunch defines a type of value that can be measured, such as length, weight, power, pressure, or area. Measurements provide the structure that ensures numeric attributes behave consistently across your catalogue.

Measurements are used whenever an attribute needs:

  • A numeric value

  • A unit of measure

  • Consistent validation and formatting

  • Clean mapping to downstream systems like PIMs, marketplaces, or ERPs

For example:

  • Length might support mm, cm, m, and inches

  • Weight might support g, kg, and lb

  • Power might support W, kW, or hp

By defining measurements centrally, SKULaunch ensures that attributes using them remain consistent, scalable, and integration-ready.

Understanding the measurement model

In SKULaunch, measurements are made up of two layers:

Measurement

  • The high-level concept, such as Length or Power

Units

  • The specific units that belong to that measurement, such as mm, cm, kg, or W

Each measurement has:

  • A unique code

  • A human-readable label

  • One standard unit

  • One or more additional units

The standard unit acts as the internal reference point for validation and conversion.

Viewing existing measurements

To view existing measurements:

  1. Navigate to Settings → Measurements

  2. You’ll see a list of all configured measurements

  3. Each row shows the measurement code, label, number of units, and whether it’s enabled

This view gives you a quick sense of how complete your measurement setup is and whether anything is missing before you start building attributes.

Viewing existing measurements

To view existing measurements:

  1. Navigate to Product Settings → Measurements

  2. You’ll see a list of all configured measurements

  3. Each row shows the measurement code, label, number of units, and whether it’s enabled

This view gives you a quick sense of how complete your measurement setup is and whether anything is missing before you start building attributes.

Creating a new measurement

To create a new measurement:

  1. Click New measurement

  2. Enter a Code

    • This should be uppercase and system-friendly

    • Example: LENGTH, WEIGHT, PRESSURE

  3. Enter a Label

    • This is what users will see in the UI

    • Example: Length, Weight, Pressure

You’ll then define the standard unit for this measurement.

Defining the standard unit

Every measurement requires a standard unit. This is the default unit SKULaunch uses internally.

When creating the measurement:

  1. Enter the Unit code

    • Example: mm, kg, W

  2. Enter the Unit label

    • Example: Millimetres, Kilograms, Watts

  3. Enter the Symbol

    • Example: mm, kg, W

Once saved, this unit becomes the anchor for all other units under the same measurement.

Adding additional units

After creating a measurement, you can add additional units:

  1. Open the measurement

  2. Click Add unit

  3. Provide:

    • Unit code

    • Label

    • Symbol

These additional units allow users to enter data in different formats while still maintaining a consistent underlying structure.

For example, a Length measurement might include:

  • mm

  • cm

  • m

  • in

Enabling and disabling measurements

Measurements can be enabled or disabled:

  • Enabled measurements are available for attribute creation

  • Disabled measurements cannot be used but remain in the system

This allows you to clean up unused or legacy measurements without breaking historical data.

Best practices

  • Define measurements before creating attributes

  • Use clear, standardised codes

  • Always set a sensible standard unit

  • Avoid creating duplicate measurements with similar meanings

  • Keep measurement scope broad and attribute scope specific

A strong measurement foundation makes everything else in your taxonomy easier to manage.

Did this answer your question?