Managing Your Ingredient Database: Custom Ingredients and Your Own Prices

Why Your Ingredient Database Matters

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.

When You Need a Custom Ingredient

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.

Adding a Custom Ingredient: Step by Step

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.

Composition Data: Getting the Numbers Right

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.

Making Your Ingredients Easy to Find

The Formul.io ingredient search is forgiving: it tolerates typos and transpositions, matches partial names, and searches the brand, the category and the recorded properties as well as the name itself. On the shared catalogue it also knows a good deal of trade vocabulary, because alternative names are curated centrally and maintained by Formul.io. What it cannot invent is a name you never entered — and on your own custom ingredients, the primary name and the manufacturer are the whole of what you gave it. Name them as the supplier does, record the brand, and the search does the rest.

The stronger lever is preference. Give an ingredient a heart and it becomes a Favorite ingredient; mark a brand under the Brands tab of the ingredients library and it becomes a Favorite brand — “Choose the brands you use. Suitable products from these brands appear first across the app and in AI suggestions.” Both outrank relevance. A hearted ingredient sorts above a suitable product from a favourite brand, which sorts above everything else, and that order applies wherever ingredients are listed: search, the recipe editor’s picker, and what a connected AI assistant is offered.

My Prices: What You Pay, Kept Separately

Price is not a property of an ingredient the way fat content is. Composition is the same for everyone holding the same block of couverture; the price is yours alone, and it changes every time you reorder. Formul.io keeps the two apart. Composition lives on the ingredient; what you pay lives under My prices, private to your account — never shared when you share or clone a recipe, and never visible to anyone else. Costing and margins are part of the Pro plan.

There are three ways in, and they write to the same place. On an ingredient’s page, the My price card takes the price without touching composition — “Only you can see this price. It is used in your recipes and products.” Inside a recipe’s costing, any ingredient row missing a price opens the same editor in place, so you are never sent away mid-calculation. And the library page at My prices holds them all together, with search, an Add price button and an Import path for a supplier price list.

You enter a purchase, not a rate: the pack size and the pack price as they appear on the invoice — a 3 kg block at €54.00, a 10 kg bag at its real cost — and Formul.io derives the per-kilogram figure. Optional details cover the rest of the landed cost honestly: the purchase date (today by default), an optional source, the purchase tax rate with a note of whether it is included in what you typed and whether you can recover it, and a preparation yield for anything that loses weight before it ever reaches a recipe. The result is a cost per usable kilogram rather than a sticker price.

Managing Allergen Data: Accuracy Is Non-Negotiable

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.

Editing and Updating Existing Custom Ingredients

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 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.

Naming Conventions for Teams

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 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 costs, because each entry carries its own saved price, 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.

Best Practices: Custom Ingredient vs. Standard Equivalent

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.

Quick Reference: Custom Ingredient Checklist

1. Search the default database first — add a custom entry only if no close equivalent exists
2. Use the official product name as the primary name, following your team’s naming convention
3. Record the manufacturer, and mark the brand as a favourite if you buy from it regularly
4. Enter composition data from the supplier CoA or technical data sheet — not from general tables
5. Verify that fat + water + carbohydrate + protein + fiber + ash ≈ 100%
6. Enter water activity if you have a measured value; leave blank if estimating from composition
7. Save what you pay under My price — pack size and pack price from the invoice, not the list price
8. Flag every applicable EU allergen — cross-reference the product label and supplier allergen statement
9. Save and test by adding to a recipe — verify that Aw and the allergen summary are correct
10. Heart the ingredient if it is one you use constantly, so it leads every list you search

Frequently Asked Questions