Unit of measure (UOM) - FAQs

Created by Shyam Sayana, Modified on Sun, 15 Nov at 11:28 PM by Shyam Sayana

TABLE OF CONTENTS


The basics

1. What does the Unit of Measure feature do?

It lets planners view and plan quantities in a different UOM from the one an item is stored in. For example, an item stored in kilograms can be viewed in pounds. The planner picks the UOM in the planning view or planner workbench, and Firstshift converts the numbers.

2. What is the difference between standard and custom UOMs?

Standard UOMs are a small set that comes with Firstshift, with their conversions already included. You do not need to send anything for them. Custom UOMs are any other UOMs. You send them to us, along with the conversions for them.

3. Which standard UOMs are included?

TypeStandard UOMs
Lengthcm (Centimeters), ft (Feet), in (Inches), km (Kilometers), m (Meters), mm (Millimeters)
Volumefl oz (Fluid Ounces), gal (Gallons), l (Liters), ml (Milliliters)
Weightg (Grams), kg (Kilograms), lb (Pound), lbs (Pounds), mt (Metric Ton), oz (Ounces), ton (Metric Ton)
Countdz (Dozens), ea (Each), each (Each)

These are the only standard UOMs. We do not add more in new releases. Every other UOM, such as case, box, pallet or bag, is a custom UOM.

Two notes on specific standard UOMs:

  • gal is the US gallon. It converts to 3.785411784 liters and to 128 fluid ounces. There is no imperial gallon in the standard list. If you need one, send it as a custom UOM.
  • ton is the metric ton, the same as mt. Both convert at 1,000 kg. If you use a US short ton (2,000 pounds), do not send it as ton. Send it as a custom UOM with its own code and conversions.

4. Does Firstshift follow ISO 80000?

Only for the standard UOMs above. Where a standard UOM has an ISO symbol, we use that symbol. Some standard UOMs are our own spellings, such as lb, lbs, ft, gal, mt, ton and the count UOMs. For example, the ISO symbol for the metric ton is t, but our standard codes are mt and ton. For any UOM you send yourself, we do not check it against ISO.

Adding your own UOMs and conversions

5. How do I add a custom UOM?

You send two sets of data, in this order:

  1. The new UOM, in the unit of measure data load.
  2. The conversions for that UOM, in the unit of measure conversion data load.

A new UOM is added automatically and is switched on by default. Your implementer does not need to set it up. The first spelling you send is the one planners see, so check the capitalization of a new UOM before you load it.

6. Why do I need to send conversions in both directions?

Firstshift does not work out the reverse conversion itself. If 1 case = 100 boxes, you also send 1 box = 0.01 case. Factors can have six or seven decimal places, and we do not want to guess by dividing and rounding.

7. What does the conversion factor mean?

The factor always means 1 From UOM = n To UOM. For example, 1 case = 100 boxes is From = case, To = box, factor 100. The reverse is a second row: From = box, To = case, factor 0.01. If your own system uses a multiply-or-divide indicator, apply it first and send the finished factor.

8. What is the base UOM, and which conversions do I need?

Every product has a base UOM. It is the UOM the product is stored in. For a planner to see the product in another UOM, you must send a conversion from the product's base UOM to that UOM. This is mandatory for each UOM you want in the UOM drop-down. If the conversion from the base UOM is missing, that UOM does not appear in the drop-down, even if other conversions for it exist.

Firstshift also needs the conversions between all the other UOMs, in every direction. This is a current limitation of the solution. If a conversion such as drum to case or bottle to drum is not loaded, it cannot be used. Firstshift does not work it out from the other conversions.

Worked example: the base UOM of a product is liter. You want planners to see the product in case, bottle and drum. That is 4 UOMs, so you need a conversion from every UOM to each of the other 3 UOMs. That is 4 × 3 = 12 conversions. Three of them start from the base UOM (liter to case, bottle and drum). The other 9 are the reverse conversions and the conversions between case, bottle and drum.

For this example, we assume 1 case = 12 bottles, 1 bottle = 1 liter and 1 drum = 200 liters. The numbers are only an illustration. Use your own factors. This is how the 12 conversion records for Product A should look. Each record has the product, the From UOM, the To UOM and the conversion factor, which means 1 From UOM = factor × To UOM:

ProductFrom UOMTo UOMConversion factor
Product Alitercase0.0833333333
Product Aliterbottle1
Product Aliterdrum0.005
Product Acaseliter12
Product Acasebottle12
Product Acasedrum0.06
Product Abottleliter1
Product Abottlecase0.0833333333
Product Abottledrum0.005
Product Adrumliter200
Product Adrumcase16.6666666667
Product Adrumbottle200

Every combination of the 4 UOMs appears, in both directions. If you leave out any of the 12 records, for example drum to case, that conversion cannot be used. The table shows one product. Send the same kind of records for each product that uses these UOMs.

9. Can I use my own conversion for a standard UOM, such as a different factor for liter to milliliter?

Yes. Ask your implementer to switch the standard UOMs off in the admin app. After that, you send every UOM and every conversion yourselves, including the ones that used to be standard. This is useful when the standard factor does not suit your products. For example, 1 liter is about 1 kg for water, but not for oil or syrup.

10. What goes in the Category column?

The category only applies to the standard UOMs (length, volume, weight and count). For your own UOMs, leave it blank, or enter "Custom". It is not used in any conversion, and a value there will not cause a rejection.

11. Do I need to send a conversion for every UOM?

No. Records with a UOM but no conversion are still loaded. A conversion is only needed when a planner wants to see or plan an item in a different UOM. If there is no conversion, the item is not converted.

12. Can I leave the UOM blank in my data loads?

It depends on where the UOM is. Two data loads always need a UOM. In the others, you can leave it blank.

WhereColumnCan it be blank?What happens
Unit of measure data loadUOM codeNoThe UOM is the key of this data load, so it cannot be blank. The record cannot be loaded.
Conversion dataFrom UOM and To UOMNoBoth are mandatory. Neither can be blank.
Product masterBase UOMYes, unless your implementer has made it mandatoryIf the base UOM is blank, no conversions apply to that product, so planners cannot see it in other UOMs. Please provide it if you want conversions (see question 8).
Sales orders, sales actuals and other transaction dataUOMYes, unless your implementer has made it mandatoryIf it is blank, Firstshift assumes the quantities are in the product's base UOM. If your implementer has made it mandatory, a record with a blank UOM is rejected with the reason that the unit of measure is required.

If you do enter a UOM, it must already exist in your UOM list. Capital and small letters do not matter. A UOM that does not exist is rejected on every data load except the unit of measure data load (see question 13).

Loading data and fixing problems

13. What happens if I enter a UOM that does not exist?

It depends on the data load:

  • Unit of measure data load: an unrecognized code is not rejected. It is added to your list as a new custom UOM.
  • All other data loads (conversions, product master, sales actuals, sales orders): the record is rejected. The message says that no such unit of measure is defined in the system.

A UOM that differs only in capital and small letters from one that already exists, such as BARREL when Barrel exists, is not an unknown UOM. It is not rejected and is not added as a new UOM.

14. Where can I see rejected records?

Open the data load history. If a data load had rejected records, click on it to see how many records were updated and how many were rejected. Download the rejected file to see the reason for each rejection.

15. I made a typo in a UOM. What happens?

If the typo is only in the unit of measure data load, it is saved as a new UOM, but it does not appear in the planning screens until it has conversions. If the same typo is also in the conversion data load, the typo appears in the planning screens. A customer cannot switch a UOM off. Please ask your implementer, who will switch that UOM off in the admin app. A difference in capital and small letters is not a typo. It is matched to the existing UOM.

16. Does capitalization matter?

No. Firstshift ignores capital and small letters when it matches a UOM, so BARREL, barrel and Barrel are the same UOM. If you send BARREL and barrel already exists, Firstshift uses the existing UOM and does not create a new one. This applies to custom UOMs as well as standard UOMs, and to every data load: the unit of measure data, conversions, product master and transaction data such as sales actuals and sales orders.

Planners always see a UOM the way it was first saved. Standard UOMs show in lowercase, for example ml and kg. A custom UOM shows the way it was first loaded in the unit of measure data load. For example, if you first send Barrel, it is saved as Barrel. If a later data load or conversion says barrel or BARREL, Firstshift still matches it to Barrel, and the screens keep showing Barrel.

Because the first spelling is the one that is kept, please check the capitalization of a new UOM before you load it for the first time. For tidy data, we recommend using the same spelling everywhere, but a difference in capital and small letters is not an error.

Using UOMs in Firstshift

17. Why doesn't my new UOM show up in the planning screens?

A UOM only appears once it has conversions. Check that you loaded the UOM first, then its conversions, and that both directions are present. Also check that each product has a conversion from its base UOM to the new UOM (see question 8).

18. Why didn't some items convert when I changed the UOM?

Those items have no conversion for the UOM you picked. Firstshift tells you how many items cannot be converted, and those items stay in their own UOM. To fix it, send the missing conversions, in both directions.

19. I edit a number while viewing a different UOM. What gets saved?

Firstshift converts the number back for you, so you do not need to convert it yourself. The audit trail shows the item's own UOM, the UOM you were viewing and the UOM the edit was entered in.

20. In what order should I load the data?

Load the unit of measure data first, then the conversion data. After that, load the product master, bills of materials and transactions such as sales actuals and sales orders. UOMs are processed before those data loads.

Reference: standard conversions

In every row, 1 From UOM = factor × To UOM.

Weight

From UOMConverts to (UOM and factor)
gkg 0.001, oz 0.0352739619
kgg 1000, lb 2.2046226218, lbs 2.2046226218, mt 0.001, oz 35.2739619496, ton 0.001
lbkg 0.45359237, oz 16
lbskg 0.45359237, oz 16, ton 0.0004535924
mtkg 1000
ozg 28.349523125, kg 0.0283495231, lb 0.0625, lbs 0.0625
tonkg 1000, lbs 2204.6226218488

Length

From UOMConverts to (UOM and factor)
cmin 0.3937007874, m 0.01, mm 10
ftin 12, km 0.0003048, m 0.3048
incm 2.54, ft 0.0833333333, m 0.0254
kmft 3280.8398950131, m 1000
mcm 100, ft 3.280839895, in 39.3700787402, km 0.001, mm 1000
mmcm 0.1, m 0.001

Volume

From UOMConverts to (UOM and factor)
fl ozgal 0.0078125, l 0.0295735296, ml 29.57352956
galfl oz 128, l 3.785411784
lfl oz 33.814022676, gal 0.2641720524, ml 1000
mlfl oz 0.0338140227, l 0.001

Count

From UOMConverts to (UOM and factor)
dzea 12, each 12
eadz 0.0833333333, each 1
eachdz 0.0833333333, ea 1

Only the pairs listed here exist as standard conversions. For example, there is no direct gal to ml and no direct lb to g. For any other pair you need, send the conversion yourself, in both directions.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article