Item Units, Conversions, and Packaging
Item setup includes several measurement concepts. They control how the item is entered, scaled in recipes, ordered, priced, and tracked in inventory.
Base Measurement
The base measurement is the amount used to enter the item's initial nutrition information. It is typically the amount printed on the item label, or 100 grams as a default. Base measurement is required for every item.
Conversions
Conversions link different measurements to the base measurement so the item can be used in different units across recipes, orders, and inventory. There are two types:
Weight to Volume: examples include spices, fruits, vegetables, and oils. Setting one weight-to-volume conversion (such as 1 tablespoon = 15 grams) makes all weight and volume variations available.
Custom Conversion: a custom conversion must be linked to a standard volume or weight measurement that is already active. Examples include individually wrapped items (IW), serving units such as meatballs or tots, or container sizes for pantry staples.
Measurements
Measurements are meaningful quantities or variations of the base measurement and active conversions. They are used to display nutrition facts for that specific measurement. For example, a USDA canned bean item with a base measurement of 100 grams and a conversion of 1/2 cup = 130 grams will not automatically show nutrition facts in ounces. Adding an ounces measurement makes nutrition facts available in ounces for recipes built in that unit.
Packaging
Packaging units track multiple case sizes and inventory tracking units. Always create the smallest custom or packaging unit first before building the hierarchy. For example, for a case of vinegar bottles:
Add the base measurement (e.g., 100 g).
Add a volume conversion (e.g., 1 tbsp = 15 g).
Add the container (e.g., Bottle of 1 gallon).
Add the case hierarchy (e.g., Case of 6 Bottles, Crate of 10 Cases).
Shopping Measurement
The shopping measurement determines how an item's price per serving is calculated and displayed. It is the denominator in cost calculations, defining what the system counts when determining pricing and quantities.
For example, when an item's shopping unit is set to case, Gaia displays the price per case on the vendor product. If the unit is switched to each, the system recalculates by dividing the total cost by the new unit count.
For an individually wrapped item, the shopping measurement is typically the same as the base unit (e.g., 1 each = 57 grams). For a bulk raw ingredient such as rice, it could be cups, pounds, or container.
Setting Them Up
Units, conversions, and packaging are managed on the Units tab of the item page. A reliable order to follow:
Confirm the base measurement on the main item page.
Open the Units tab.
Add a weight-to-volume conversion if the item has one.
Add any custom conversions (such as each, meatballs, slices).
Add the smallest packaging unit, then build up the hierarchy (container, case, crate).
Set the shopping measurement.
Click Save after adding each entry.
Fixing "No conversion path found" errors
Sometimes a recipe or production record shows a No conversion path found error — often between two units such as tablespoon and gram. It means the item doesn't have a conversion linking the units being used. To fix it:
Open the item showing the error.
Go to the Units tab.
Add the missing conversion (for example, 1 tablespoon = 15 grams) so Gaia can translate between the units.
Save.
The error clears once a path exists between the units. Gaia now blocks many of these mismatches when items are first entered, but items created earlier may still need a conversion added.