Know the cost of every serving before you price it
Ingredient costs, packaging, labor, and overhead roll up to a true cost per serving, tracked over time, so you see margin erosion before it shows up in your bank account.
Per-ingredient line totals, computed live
Enter a unit cost against each ingredient (per kilogram, per pound, per unit, however you buy it) and the Cost tab multiplies it by the amount your recipe actually uses. Every row shows its line total; the table shows the recipe subtotal, cost per batch, and the number you ultimately price against: cost per serving.
Change an amount on the Recipe tab and the costs recompute instantly; the two tabs can never disagree.
Packaging, labor, and overhead included
Ingredients are rarely the whole story. The wrapper, the printed film, the carton, the label stock; the minutes of mixing and hand-packing; the slice of rent and utilities a batch absorbs: NFL lets you add packaging, labor, and overhead costs alongside ingredients so the per-serving figure reflects what the product truly costs to make.
Each category is itemized separately, so you can see at a glance whether a margin problem is a commodity-price problem or a packaging problem. That distinction changes what you do next: renegotiate with a supplier, redesign the pack, or adjust the shelf price. A cost model that stops at ingredients hides exactly the costs that scale worst for small producers.
Cost history: watch your margins move
Ingredient prices drift, and quiet drift is how margins die. NFL keeps a history of your recipe's cost as you update prices over time, so you can see the trend, not just today's snapshot.
When honey jumps 12%, you will know which SKUs it hurt and by how much, with the data to justify a price change.
Sub-recipes carry their costs with them
Cost a sub-recipe once (your sauce, base, or blend) and every parent recipe that uses it inherits the correct proportional cost automatically. Update the price of one raw ingredient inside the sub-recipe and the change ripples through every SKU built on it.
This is where spreadsheet costing usually breaks down: a shared component's price changes and someone has to remember every workbook that references it. Here the sub-recipe is one object in your recipe library, referenced everywhere, updated once. The same structure that keeps your nutrition math consistent keeps your cost math consistent too.
Multi-currency, wherever you sell
Pick your working currency on the Cost tab (USD, EUR, GBP, CAD, AUD, JPY, INR, and more) and every line total, subtotal, and per-serving figure renders with the right symbol and formatting conventions. Producers selling into several of our 114 supported countries can keep costing in the currency their books are kept in, independent of which country's label format they are exporting.
Costing stays attached to the recipe rather than living in a separate tool, so the same record that prints your compliant label also answers "what does this cost me?" in the currency that question is actually asked in.
Connected to production, not a silo
Because costing lives on the same recipe object as everything else, it stays synchronized for free. Add an ingredient in the Recipe tab and a cost row appears; remove one and its cost disappears; no desync, no orphaned line items. Your recipe, label, and unit economics are one record, autosaved to the cloud.
When you are ready to go beyond unit economics, the inventory module tracks the raw materials behind those costs (stock on hand, production runs, lot codes) and the pricing page shows which plans include it. Cost questions? Check the recipes FAQ.