Unit price comparer
Compare packaged items using matching volume, mass or count units.
How to use Unit price comparer
The unit price comparer takes the price and quantity of two packages, calculates the price per unit for each, and names the better value as A, B or equal. Both quantities must use the same unit, such as grams, milliliters or items, which you record in the Matching unit field. It does not convert between units.
- Enter the requested values in the settings panel.
- Set package a price, package a quantity, package b price, package b quantity, matching unit.
- Run unit price comparer, review the output, then use the available copy or download controls.
What this tool supports
Compare packaged items using matching volume, mass or count units.
- Package A price
- Range: 0 to 1000000000000
- Package A quantity
- Range: 0.000001 to 1000000000000
- Package B price
- Range: 0 to 1000000000000
- Package B quantity
- Range: 0.000001 to 1000000000000
- Matching unit
- Set this value for your task.
Limits and processing
Local bounded calculations. Numeric inputs must be finite and within the visible ranges. Lists and tables have operation-specific limits. Models, estimates and supplied rates must be checked against your intended use.
Frequently asked questions
How do I compare prices of different package sizes?
Enter each package's price and quantity. With the defaults, 5 for 500 g and 7 for 800 g, the prices per unit are 0.01 and 0.00875, so package B is the better value.
Can I compare a package in ounces with one in grams?
Not directly. The comparer divides price by quantity without converting units, so convert one package to the other's unit first. The Matching unit field works as a label and reminder only.
What if both packages cost the same per unit?
When the two unit prices are exactly equal, the Better value result reads equal. Otherwise it names the package with the lower price per unit, A or B, alongside both calculated unit prices.
Where is my input processed?
This operation processes its source in your browser. Copy and download are explicit actions; source input is not saved in an account or history.
What are the input limits?
Local bounded calculations. Numeric inputs must be finite and within the visible ranges. Lists and tables have operation-specific limits. Models, estimates and supplied rates must be checked against your intended use.