There are several ways to tackle this, each of which increases in complexity:
Don't store unit information:
The item record can store it in the description.
Item Table:
ID | Description
---+---------------------------------
09 | Red Sox Tee Shirt (Case of 12)
10 | Red Sox Tee Shirt (each)
11 | 500lb Nylon Rope (per foot)
Then on the order table, you simply need to store an Item ID
+ Quantity
where quantity is a decimal value.
Store the unit as part of the item
Description | Unit | UnitPrice
------------------+------+----------
Red Sox Tee Shirt | Case | 45.00
500lb Nylon Rope | Foot | 0.25
Then on the order table, you simply need to store an Item ID
+ Quantity
where quantity is a decimal value.
Store convertible units as related child table of Item
Item Table:
ID | Description
---+----------------
10 | Red Sox Tee Shirt
11 | 500lb Nylon Rope
Item_Unit table
ID | Unit | UnitPrice
---+--------+----------
10 | Each | 6.00
10 | Case12 | 60.00
11 | Foot | 0.25
11 | Spool | 250.00
In this case, the order record would need to have Item ID
+ Unit
+ Quantity
Most flexible and complicated -- convertible units
This would be an extension of the last form, but one where you have a "Unit" table that stores units, their unit type (length, volume, etc...) and their relation to a common unit. That way you could actually convert from one unit to another (1000 feet == 1 spool) for example.
But it is unlikely that you are in need of that level of complexity.