From compliant label to recall-ready: inventory built in

Every ingredient in your recipes becomes a tracked raw material; every saved recipe becomes a finished good. There is nothing to re-enter; the catalog initialises from the recipe library you already built for labeling. Receive stock as it arrives, subtract shipments as they leave, and set reorder points so low-stock items surface before a production day gets cancelled for want of honey.

On-hand quantities and value roll up from a transaction ledger, the single source of truth every other number derives from.

Pick a recipe, set a batch size, and NFL generates a batch-control log: the scaled ingredient amounts to weigh out, with space to record what was actually used and which supplier lot each ingredient came from. It is the record a food-safety auditor asks for, produced as a by-product of simply running production.

Close the run and inventory adjusts in one motion: raw materials are consumed by the actual recorded amounts, finished goods are produced under a new lot code. No double entry, no evening spent reconciling a spreadsheet against what the kitchen says it did. Because the run is driven by the same recipe that prints your label, the product you made is by construction the product the label describes.

Every movement (receipt, production, shipment) records its lot code, which makes tracing a query rather than an archaeology project. Trace backward from a finished-good lot to every raw-material lot and supplier that went into it; trace forward from a suspect ingredient lot to every run it entered and every shipment that left the building containing it.

Recall readiness becomes a search box, not a fire drill.

When a supplier calls about a contaminated lot, the clock starts. NFL generates a recall report PDF in one click: the affected raw-material lot, every production run that consumed it, every finished-good lot produced, and every shipment that carried those lots out the door, with dates and quantities, formatted to hand to a regulator or retailer as-is.

This is the document that turns a terrifying afternoon into a contained one, and it exists because the data was captured passively during normal operation rather than reconstructed under pressure. Undeclared allergens are the most common recall trigger, which is why allergen tracking and lot tracing live in the same product: prevention and response, one system. More detail in the inventory FAQ.

For food, plain FIFO is not good enough; the lot that arrived first is not always the lot that expires first. NFL tracks expiry dates per lot and orders picking suggestions by first-expired, first-out, so the stock closest to its date is consumed before fresher deliveries, and short-dated lots are flagged before they become write-offs.

The effect compounds quietly: less shrink, fewer near-expiry firesales, and a cleaner answer when an auditor asks how you rotate stock. Expiry data also feeds production planning: if the only sufficient honey lot expires next week, you will see that when scheduling the run, not when weighing out. Waste you do not create is the cheapest margin you will ever find, a theme the cost calculator makes visible from the other direction.

Not everything ships in printed film. Farm stands, market bakers, and produce operations need small-format labels generated per batch (product name, lot code, weight, dates) and NFL prints label-on-produce batch labels straight from a closed production run. The lot code on the sticker is the same lot code in the ledger, so a label on a clamshell of berries traces back to its run like any packaged SKU.

For packaged goods, the full compliant Nutrition Facts label and the batch identity come from the same record: no re-keying between a labeling tool and a warehouse tool, because they are one tool.

Inventory lives beside your labels, recipes, allergens, and costs, saved to your account, current on every device, with per-account access control. The same recipe object that renders your Nutrition Facts panel scales your batch sheet, consumes your raw materials, and prices your product; there is no import/export dance between systems, and no version of the truth that exists only on the production office PC.

Open the inventory dashboard to see it against your own recipes, check which plans include the module on the pricing page, or start from the beginning in the label generator; the label is where you start, not where the tool stops.