Sub-formulas and premixes: building formulas from formulas

Real products are rarely built from raw ingredients alone. A formula often contains a premix — a blend bought from a supplier or made in-house — which is itself a formula of ingredients. A vitamin premix, a flavour system, a base blend: these are formulas inside formulas. Software that handles these sub-formulas properly turns complex products into manageable building blocks; software that doesn't forces you to flatten everything and lose the structure. Here is why nested formulas matter.

What a sub-formula is

A sub-formula, or premix, is a formula used as an ingredient in another formula. Instead of listing every individual vitamin in your multivitamin's premix separately in every product, you define the premix once — as its own formula — and use it as a single building block in the products that contain it.

This mirrors how products are actually made. Premixes are real things: you buy or blend them, and they go into formulas as units. Software that models sub-formulas matches reality, rather than forcing you to pretend a premix is a flat list of loose ingredients.

Why this saves enormous work

The power of sub-formulas is reuse. Define a premix once, and every product that uses it inherits its full composition — every nutrient, allergen, and contaminant — automatically. Use the same premix in ten products, and you have defined it once, not ten times.

More importantly, update the premix once — a supplier changes its composition, say — and every product containing it updates. Without sub-formulas, you would have to find and change that premix's ingredients in every single product by hand, which is slow and error-prone. Sub-formulas make the change propagate.

Composition rolls up through the layers

The key capability is that everything rolls up through the nesting. The nutrients, elemental amounts, allergens, contaminants, and cost of the sub-formula flow up into the parent formula automatically, so the finished product's totals correctly include everything in its premixes. A premix's allergen appears in the product's allergen declaration; a premix's cost appears in the product's cost — all without manual aggregation.

This roll-up through layers is exactly the kind of calculation that is tedious and error-prone by hand and reliable when the software does it.

Premixes you buy vs premixes you make

Sub-formulas handle both cases. A premix you buy from a supplier is defined by the composition they provide, used as a building block. A premix you blend in-house is its own formula you maintain, used in your products. Either way, the premix is a reusable unit with its full data, and products built on it inherit that data.

This also supports the way contract manufacturers and larger operations work — standard base blends and premixes reused across many products, defined once and maintained centrally.

Why flattening is a trap

Software that cannot handle sub-formulas forces you to flatten — to list every individual ingredient of every premix directly in every product. This loses the structure, multiplies the data entry, and makes updates a nightmare: a premix change means editing every product by hand. Flattening might work for one simple product, but it collapses under the complexity of a real catalogue.

Proper sub-formula support preserves the structure and keeps the data consistent across everything.

Where Lemoniq fits

Lemoniq supports sub-formulas and premixes as reusable building blocks. Define a premix once — bought or blended — and use it across many products, with its full composition, allergens, contaminants, and cost rolling up into every parent formula automatically. Update the premix once, and every product containing it updates. Complex, multi-level products are built from clean building blocks rather than flattened into unmanageable lists.

The takeaway

Premixes and sub-formulas are how real products are built — formulas inside formulas — and software that handles them lets you reuse building blocks, roll composition up through the layers, and update once to change everywhere. Without sub-formula support, you flatten everything and drown in duplicated data and manual updates. Building formulas from formulas is what keeps a complex catalogue manageable and consistent.

Lemoniq builds products from reusable sub-formulas and premixes — define once, roll up automatically, update everywhere. We solve this exact problem. See how it works