Everything you buy. Invoices feed this list, recipes draw from it, and food cost is the result.
The list
Name, supplier, category, price, on hand, tax.
Filter by category or supplier, or search. Five hundred ingredients is normal for a full kitchen.
Add Ingredient for something you have never bought. Most of the time you will not need to — validating an invoice creates what it does not find.
Names come from your suppliers
1 LITRE/SEALTEST 35% WHIP CREAM. 12/BUNCH/CORIANDER. 22LB/SPANISH ONION-PEELED.
These are not names anyone chose. They are what the supplier prints, and NexReps keeps them because that is what makes an invoice line match next time.
Ugly and matching beats tidy and broken.
Duplicates
Potential Duplicates finds ingredients that are probably the same thing bought twice.
This happens on its own. A supplier changes their description, an invoice creates a new ingredient, and now you have two corianders — each with half your purchase history and half your recipes pointing at it.
Merge them. Merge History shows what was merged, in case you need to check.
Run this occasionally. Duplicates do not announce themselves; they quietly split your data in two.
Opening one
Pricing & Package — price per unit, unit, package, package price, package size, SKU, tax rate.
Package size is the one that matters. A case of six 750ml yogurts is 6 × 750 ml. Get it wrong and every recipe using it is wrong by the same factor.
Recipe — wastage, and every recipe using this ingredient, with quantity. Used in 1 recipe with the list underneath.
That list is the blast radius. Change this ingredient's price and those recipes move.
Recipe Units — which units appear in recipe dropdowns for this ingredient. By default, only units of the same dimension as the purchase unit. See Units and conversions.
Inventory — inventory unit, on hand, on hand value.
Purchase unit and inventory unit
They can differ, and often should.
You buy flour by the case. You count it by the kilo. Purchase unit is how it arrives; inventory unit is how you count it.
Empty fields
— everywhere means the ingredient exists but has never been on a validated invoice. It was created — by an import, by hand, by a matched line — and no price has arrived yet.
An ingredient with no price counts as zero. Not as an error, not as a warning — as zero.
Which means a recipe containing it shows a cost that is too low. A dish costed at $4.10 that should be $7.80 will price itself and sell itself.
The recipe list flags this. A card carrying an Incomplete badge under its cost has at least one line with no price — see Recipes. It is the fastest way to find them: scan the list, and every badge is an ingredient waiting for a price.
Most of the time the fix is an invoice. Price arrives, badge goes, cost is true.
Next
Units and conversions — why the kilo and the case must agree.