Skip to main content

Eaternity App Usage Tips

Best practices and important guidelines for working effectively with the Eaternity App.

Recipe Structure Fundamentals​

Understanding Recipe Relationships​

An important aspect of working with the Eaternity App is understanding how recipes can be used as sub-recipes (ingredients in other recipes). This creates a hierarchical recipe structure:

Main Recipe: Lasagne
├── Sub-recipe: Bechamel Sauce
│   ├── Milk
│   ├── Flour
│   └── Butter
├── Sub-recipe: Tomato Sauce
│   ├── Tomatoes
│   ├── Onions
│   └── Garlic
└── Ingredient: Pasta sheets

Key Principle: Unique Naming​

CRITICAL RULE: Since all recipes can automatically be used as sub-recipes, naming must be unique and specific.

Recipe Modification Best Practices​

The Duplicate Problem​

When you modify a sub-recipe that's already being used in another recipe, the app behavior depends on whether you change the name:

❌ Without Name Change (Creates Duplicates)​

1. You have: "Bechamel Sauce" used in "Lasagne"
2. You modify: "Bechamel Sauce" ingredients
3. Result: App creates a NEW recipe also called "Bechamel Sauce"
4. Problem: Now you have TWO recipes with identical names

This creates confusion and clutter in your recipe database.

✅ With Name Change (Recommended)​

1. You have: "Bechamel Sauce" used in "Lasagne"
2. You modify AND rename: "Bechamel Sauce 2024-09-26"
3. Result: Clear distinction between original and modified version
4. Benefit: No duplicates, clear version history

Add the date when making modifications:

Original: Bechamel Sauce
Modified: Bechamel Sauce 2024-09-26
Further modified: Bechamel Sauce 2024-10-15

Alternative naming patterns:

Bechamel Sauce - Low Fat
Bechamel Sauce - Vegan
Bechamel Sauce - Winter Menu

Duplicate Detection​

Warning Message​

When duplicates exist, you'll see this message in the recipe heading:

⚠️ There is another recipe with the name "Bechamel Sauce"

This indicates that the sub-recipe was modified without changing its name, creating a duplicate entry.

Recipe Deletion Guidelines​

Deleting Main Recipes​

Main recipes (like "Lasagne") can be deleted at any time, but sub-recipes behave differently:

Clean Deletion (No Duplicates Left)​

If the sub-recipe has not been modified:

  • Main recipe is deleted
  • Sub-recipe remains available for use in other recipes
  • No duplicate warning message appeared
  • ✅ Clean deletion, no issues

Problematic Deletion (Duplicates Remain)​

If the sub-recipe was modified but name wasn't changed:

  • Main recipe is deleted
  • Modified sub-recipe remains as a duplicate
  • Warning message was present
  • ⚠️ Duplicate remains in system

Before deleting a main recipe:

  1. Check for duplicate warnings in sub-recipes
  2. Remove or rename problematic sub-recipes first
  3. Then delete the main recipe
  4. Result: Clean deletion without orphaned duplicates

Summary of Best Practices​

DO ✅​

  • Add dates to modified recipe names: "Bechamel Sauce 2024-09-26"
  • Use descriptive modifiers: "Bechamel Sauce - Low Fat"
  • Check for duplicate warnings before deleting recipes
  • Remove/rename sub-recipes before deleting main recipes
  • Keep naming consistent across your team

DON'T ❌​

  • Modify recipes without changing the name
  • Ignore duplicate warnings in the interface
  • Delete main recipes without checking sub-recipe status
  • Use generic names that could easily conflict
  • Leave orphaned duplicates in the system

Recipe Version Management​

Tracking Changes Over Time​

The date-based naming convention serves as simple version control:

Timeline of recipe evolution:
├── Bechamel Sauce (Original - 2024-01-15)
├── Bechamel Sauce 2024-03-20 (Spring menu adjustment)
├── Bechamel Sauce 2024-06-12 (Summer light version)
└── Bechamel Sauce 2024-09-26 (Current version)

Benefits​

  • Clear history of recipe changes
  • Easy rollback to previous versions
  • Team communication about which version is current
  • Audit trail for recipe development

Common Scenarios​

Scenario 1: Seasonal Menu Update​

Situation: You want to adjust "Tomato Sauce" for winter menu

Wrong approach:

1. Edit "Tomato Sauce" ingredients
2. Save without renaming
3. Result: Duplicate "Tomato Sauce" in system

Correct approach:

1. Edit "Tomato Sauce" ingredients
2. Rename to "Tomato Sauce - Winter 2024"
3. Result: Clear distinction, no duplicates

Scenario 2: Creating Variations​

Situation: You want both regular and vegan versions

Wrong approach:

1. Create "Bechamel Sauce"
2. Copy and modify without renaming
3. Result: Multiple recipes named "Bechamel Sauce"

Correct approach:

1. Create "Bechamel Sauce - Dairy"
2. Create "Bechamel Sauce - Vegan"
3. Result: Clear naming, easy selection

Scenario 3: Deleting Old Menu Items​

Situation: Removing "Summer Lasagne" from menu

Wrong approach:

1. Delete "Summer Lasagne" immediately
2. Ignore warning about "Pesto" sub-recipe
3. Result: Orphaned "Pesto" duplicate remains

Correct approach:

1. Check "Summer Lasagne" for modified sub-recipes
2. Rename or delete "Pesto - Summer 2024" first
3. Then delete "Summer Lasagne"
4. Result: Clean deletion

Team Collaboration Tips​

Communication Protocols​

When working with multiple team members:

  1. Establish naming conventions upfront
  2. Document recipe modifications in team chat
  3. Coordinate deletions to avoid confusion
  4. Regular cleanup of old recipe versions
  5. Assign ownership for recipe categories

Example Team Protocol​

Recipe Modification Protocol:
- Format: [Recipe Name] - [Modifier] [YYYY-MM-DD]
- Announce changes in #kitchen-updates Slack channel
- Archive old versions quarterly
- Owner approval required for base recipe changes

Troubleshooting​

Problem: Many Duplicate Recipes​

Solution:

  1. Identify all duplicate sets
  2. Rename each version with date/modifier
  3. Mark current version clearly
  4. Archive or delete old versions

Problem: Can't Find Latest Recipe Version​

Solution:

  1. Implement consistent date format: YYYY-MM-DD
  2. Most recent date = current version
  3. Consider "CURRENT" tag in description field

Problem: Accidental Recipe Modification​

Solution:

  1. If renamed with date: Previous version still exists
  2. Can revert by using earlier dated version
  3. Delete the accidental modification

Need Help?​

If you encounter issues with recipe management:

  • Enterprise customers: Contact via Slack support channel
  • Professional license: Email support
  • General questions: Check FAQ section or contact your account manager

Key Takeaway: Always rename recipes when modifying them if they're used as sub-recipes. Adding dates ensures uniqueness and provides version history.