Skip to content
For meal kits

Per-recipe labels at subscription-box scale

A meal-kit brand ships 10+ new recipes a week, each with its own nutrition, allergens, and packaging. NFL keeps up.

Start free
Every kit recipe in one synced library.

Bulk recipe library

Save your entire recipe rotation. Search by ingredient, tag by cuisine, sort by cost or calorie count.

Sub-recipe reuse

Your house vinaigrette is used in 12 recipes. Save it once, use it as a sub-recipe everywhere. Update the vinaigrette and every downstream recipe auto-recomputes.

Allergen roll-ups per box

Combine 3 recipes into a weekly box. Allergens roll up automatically; the box card shows the union of all recipe allergens.

Ingredient card printing

Export ingredient cards per recipe for the packaging insert. Compliance + operations in one tool.

Component allergens roll up to the box-level declaration.

A meal kit is several labeling questions in one box

Meal kits sit awkwardly across the packaged-food rules, because a kit is not one product - it is a container of products, some of which are themselves packaged foods.

The portioned sauce sachet, the pre-packed spice blend, the vacuum-sealed protein: each is a food in a package. Where those components are individually packaged and could be separated from the kit, they generally need their own labeling. Where the outer box is the retail unit and bears complete information for what is inside, the analysis is different.

Which of those situations you are in depends on how your kit is assembled and sold, and it is worth settling deliberately rather than by default - because the answer determines whether you are producing one label per kit or a dozen.

Recipe velocity is the actual constraint

Most labeling tools assume a product catalogue that changes a few times a year. A meal-kit brand ships ten or more new recipes a week, every week, and each one carries nutrition, allergens, an ingredient statement, and a card in the box.

At that rate, any per-recipe manual step becomes the bottleneck. Five minutes of arithmetic per recipe is an hour a week; a recalculation triggered by a supplier change is a day. The reason sub-recipes matter here more than in any other category is compounding: your house vinaigrette appearing in twelve recipes means one ingredient change touches twelve labels, and either that propagates automatically or somebody updates twelve things by hand and misses one.

Storage and handling statements

Kits ship chilled and arrive on a doorstep, which puts handling instructions in a different category of importance than they occupy for shelf-stable product. Keep-refrigerated statements, use-by dating, and safe-handling guidance for raw proteins travel with the box and with each component that needs them.

These sit alongside the nutrition panel rather than inside it, but they are part of the same artwork job, and they change per recipe - which is why they belong in the same system that generates the panel rather than in a separate document somebody maintains by hand.

Meal kit labeling: common questions

Does every component need its own Nutrition Facts panel?
It depends on how the component is packaged and whether it could be sold or separated on its own. Worth resolving with a regulatory consultant once, for your specific kit structure, and then applying consistently.
How do allergens work across a box?
The box-level declaration is the union of its components. NFL rolls them up automatically, so adding a sesame-containing sauce to one recipe updates the box card without anyone remembering to.
What about recipes that are only in rotation once?
They still need labeling for the weeks they ship. Saving them means the next time that recipe comes round, the work is already done.
Can I export the whole week at once?
Yes - select the week's recipes and export as a zip, in whatever format your print partner needs.

Build your first label in minutes

Free to start. No credit card required.