Custom Recipes

Use together with Custom Nutritional Indicators and Manual Intakes to cover company menus and prescribed meal plans.

Plan & Token Requirements

Feature available in the following LogMeal Plans:

Accessible by the following User Types:

What It Does

Custom Recipes let your organization define its own dishes with a fixed ingredient list and quantities, optional added‑sugar flag, and translations. These recipes are private to your company and can be assigned or logged by your users, ensuring consistent nutrition across your apps.

✕

✕

When to Use It / Outcomes

• You need to standardize menus (corporate canteens, clinics, programs) with company‑approved recipes.
• Managers want to prescribe meals or make cataloged dishes available for quick logging.
• You want tighter nutritional control than using only generic dish classes.
• Output: JSON confirming creation/update/deletion and endpoints to list/fetch custom recipes; plus nutrition calculations from ingredient lists.

Feature-Specific Details

• Recipe fields: each recipe includes a name, whether it contains added sugar, a list of ingredients with their amounts, optional nutritional values, and translations for different languages.
• Visibility: recipes are scoped to your company; other tenants cannot see them.
• Nutrition computation: use compute nutrients to obtain nutrition from any ingredient list before saving, or to validate modifications.
• Downstream flows: custom recipes can be used in Manual Intakes, assignments, manual dish confirmations or editions, and appear in history and reports like regular dishes.

Related Endpoints

• POST /custom_recipe → ⚫ 🔵 Create a custom recipe (name, ingredients, options, translations).

• GET /custom_recipe → ⚫ 🔵 🔴 List active custom recipes with basic info.

• GET /custom_recipe/{custom_recipe_id} → ⚫ 🔵 🔴 Get details for a specific custom recipe.

• PATCH /custom_recipe/{custom_recipe_id} → ⚫ 🔵 Edit fields of an existing custom recipe.

• DELETE /custom_recipe/{custom_recipe_id} → ⚫ 🔵 Deactivate (delete) a custom recipe.

• Helper:

  • POST /nutrition/recipe/compute_nutrients → 🔴 🔵 Compute nutrition from a list of ingredients (before creating or updating a recipe).

Typical Workflow

Note, this is only necessary if no related Use case exists yet for this feature.

1. Draft the recipe: define dish_name, ingredient_list, has_added_sugar, optional translations and indicator values.
2. Validate nutrition: call POST /nutrition/recipe/compute_nutrients to compute kcal & nutrients.
3. Create the recipe: call POST /custom_recipe.
4. List or fetch details: use GET /custom_recipe and GET /custom_recipe/{custom_recipe_id}.
5. (Optional) Update or deactivate: use PATCH /custom_recipe/{custom_recipe_id} or DELETE /custom_recipe/{custom_recipe_id}.
6. Use in intakes: surface the recipe in Manual Intakes and assignments; it will appear in history and reports like any other dish.