Formulating lozenges and pastilles in software: slow-release actives in the mouth

Lozenges and pastilles deliver actives the slow way: dissolved over minutes in the mouth, bathing the throat as they go. The format is beloved in immune, throat and oral-care positioning — and it is manufactured like confectionery, which means the formulation inherits candy problems: heat, sugar chemistry and a base that dwarfs the actives. Here is how software keeps a candy process delivering a supplement claim.

The base is ninety-something percent of the piece

A hard lozenge is overwhelmingly its base — sucrose and glucose syrup in the classic version, isomalt or other polyols in sugar-free lines. The actives are a small payload inside it. That ratio means the base ingredients dominate the cost, the carbohydrate declaration, the sugar or sugar-free positioning and, with polyols, the laxative-effect warning thresholds. Modelling the base as real ingredients with real shares is what makes the piece's label and cost accurate.

Heat is a formulation input

Hard candy is cooked at high temperature; deposited pastilles are warm too. Heat-sensitive actives — vitamin C, probiotics, some botanicals — lose potency in the kettle, so the formula needs explicit overages or, for the most fragile actives, a different format entirely. Software that separates the input quantity from the per-piece label claim turns process loss into a managed number, documented per active, instead of folklore on the production floor.

Dose per piece, pieces per day

A lozenge serving is usually one piece, repeated through the day. The daily-intake math therefore multiplies: the per-piece dose times the maximum recommended pieces must stay inside safe and permitted daily levels for every active — and the directions must say so clearly. Anchoring the formula in per-piece content, with the daily scenario calculated on top, keeps both the panel and the directions consistent.

Dissolution time is the product

The lozenge's mechanism is its dwell time. Base composition, piece weight and shape set how long it lasts, and changes made for cost or taste reasons can quietly change the experience. Keeping piece weight and base composition as deliberate, versioned values means a reformulation that shortens the dissolve shows up as a decision, not a surprise.

Because sweetener warning thresholds, permitted actives and daily limits differ by market, confirm the current requirements for your specific lozenge rather than relying on a general summary.

Where Lemoniq fits

Lemoniq models the lozenge whole: base ingredients with their shares and warning thresholds, actives with input overages and per-piece claims, piece weight as a managed number. The panel, the warnings, the cost per piece and the daily-intake check all update together when the formula moves.

The takeaway

A lozenge is confectionery with a supplement's obligations. The base drives the label, the heat drives the overage, and the per-piece dose drives the daily math. Software that holds all three is what lets a candy process carry a compliant claim.

Lemoniq manages the base, the overages and the per-piece dose of your lozenges in one formula. We solve this exact problem. See how it works