Managing Your Ingredient Database: Custom Ingredients and Synonyms

In professional confectionery, every calculation is only as accurate as the ingredient data behind it. Water activity predictions, shelf life estimates, recipe costing, and allergen summaries all depend on one foundational layer: knowing exactly what is in each ingredient you use. An inaccurate fat percentage in your cream, a missing allergen flag on a compound chocolate, or a stale price on a couverture block will silently corrupt every formula that references it.

Formul.io ships with a curated database of standard confectionery ingredients — covering the sugars, fats, dairy products, chocolates, stabilizers, and hydrocolloids that appear in most professional kitchens. But no universal database can anticipate every branded ingredient, regional specialty, or in-house blend you work with. The custom ingredient system exists precisely to close that gap: to let you extend the shared database with the specific ingredients that define your production, and to make those ingredients searchable, reusable, and always up to date.

Even a comprehensive default database will miss ingredients that are specific to your operation. The most common situations that require a custom ingredient entry are set out below. Understanding which scenario applies to you determines which composition data you will need to gather before adding the ingredient.

Custom ingredients are added through the Ingredient Database section of Formul.io. Each custom ingredient is private to your account — it will not appear in other users' searches. The following steps walk through the complete process of creating a well-documented custom ingredient that will serve you reliably across all your recipes.

The composition fields — fat, water, sugar, and protein percentages — are the most technically demanding part of a custom ingredient entry. They directly determine water activity calculations, and therefore shelf life predictions. Getting them wrong means getting every recipe that uses the ingredient wrong.

For dark couverture chocolate, the key values are fat (typically 38–44% depending on the recipe — cocoa butter plus any added fats), water (typically 1–2% — chocolate is a low-water product), total carbohydrate (typically 45–55%, of which 30–45% is sugars), and protein (typically 5–8%). For cream, water content is the most variable and most important value: cream at 35% fat contains approximately 59–62% water; cream at 38% fat contains approximately 56–59% water. Even a 3% error in cream water content will shift the Aw calculation in a ganache by approximately 0.015 units — enough to affect shelf life predictions meaningfully.

The Formul.io ingredient search uses fuzzy matching — it will find ingredients even if you misspell the name, use a partial match, or type a synonym rather than the primary name. Fuzzy search is only as useful as the synonym list you have built for each ingredient. An ingredient with no synonyms is only findable by its exact primary name. An ingredient with a rich set of synonyms surfaces reliably under every term your team might use.

When entering synonyms, think about every realistic search path to this ingredient. A branded single-origin dark chocolate might be found by: the brand name alone ('Valrhona'), the product line name ('Guanaja'), the cacao percentage ('70%', '70 percent'), the generic category ('dark chocolate'), the country of origin ('Madagascar chocolate'), and any internal code your kitchen uses ('VG70'). Add all of these as synonyms. There is no practical limit on the number of synonyms per ingredient.

Ingredient prices in the database are the foundation of recipe costing. When you open any recipe in Formul.io, the cost breakdown is calculated in real time from the quantity of each ingredient multiplied by its cost per kilogram. If your ingredient prices are stale, your recipe costs are wrong — and pricing decisions based on wrong costs can silently erode your margins.

Enter the price you actually pay, not the supplier's list price. For ingredients you buy in bulk — 25 kg chocolate slabs, 10 L cream containers — divide the total invoice cost by the net weight. For ingredients where you pay delivery charges, allocate those charges per kilogram of product: if you pay €8 delivery for a 10 kg order, add €0.80 per kilogram to all ingredient prices on that order. Your true landed cost per kilogram is the only figure that gives meaningful recipe costing.

Allergen flags on custom ingredients have direct consequences for food safety and legal compliance. When you add a custom ingredient to a recipe, Formul.io aggregates all flagged allergens across every ingredient in that recipe and displays the complete allergen summary. This summary is only as accurate as the flags on each ingredient. Missing an allergen flag on a custom ingredient means the allergen will not appear in your recipe summary — and may not appear on your product label.

EU Regulation 1169/2011 on the provision of food information to consumers requires clear declaration of 14 major allergens whenever they are present in a food product, whether as a deliberate ingredient or as a processing aid. These 14 allergens must be flagged in your ingredient database with the same care you would apply to a food label. There is no distinction between a major ingredient and a trace: even lecithin from soy (a processing aid in some chocolates) must be declared if it derives from a listed allergen.

Custom ingredient entries are not static. Suppliers reformulate products, change fat sources, adjust stabilizer blends, or modify production processes in ways that alter composition. When a supplier changes the recipe for a product you use, you need to update your ingredient entry — and understand what that change means for every recipe that includes it.

The most common triggers for editing a custom ingredient are: a supplier price list update (requiring a cost per kilogram change), a reformulation that changes the composition (requiring updated fat, water, or sugar percentages), a change in allergen status (a supplier adds or removes an allergen through a reformulation or sourcing change), or a correction to data you entered incorrectly at creation. All of these are routine — maintaining ingredient accuracy is an ongoing responsibility, not a one-time task.

In a team environment, ingredient naming discipline prevents a recurring problem: multiple custom entries for the same physical ingredient, each with slightly different composition data, cost, or allergen flags. When Alice adds 'Valrhona Guanaja 70%' and Bob later adds 'Guanaja 70 Valrhona', both will appear in search results and different team members' recipes will reference different entries — leading to divergent cost calculations and inconsistent allergen summaries.

Establish and document a naming convention for your kitchen before you build a significant ingredient library. Agree on a format and apply it consistently. The specific format matters less than the consistency: the goal is that any team member searching for an ingredient will find the same canonical entry, regardless of how they phrase the search.

Adding a custom ingredient for every branded product you use is not always the right decision. The standard database exists to reduce that maintenance burden. Before creating a custom entry, evaluate whether the standard equivalent is accurate enough for your purpose.