Module 5: Recipe Linking & Sharing

Wireframe - UX Design Reference

Module Overview

Purpose: Hierarchical recipe structure with multi-venue sharing and version control

Primary Users: Chefs, Recipe developers, Multi-venue managers

Key Features: Recipe hierarchy (Bases → Sub-recipes → Final Dishes), Multi-venue sync, Version control, Auto cost cascading, GP% tracking

Screen 1: Recipe Library with Hierarchy

UX Note: Tree view shows recipe relationships. Filter by type (Base/Sub-recipe/Final Dish) and status.
Recipe Library
All (156)
Bases (23)
Sub-recipes (48)
Final Dishes (85)
🟦 Base: Tomato Sauce
Base Active
Cost: £2.40/L
🟨 Sub: Bolognese Sauce
Sub-recipe
Cost: £4.80/portion
🟩 Final: Spaghetti Bolognese
Final Dish
GP: 72%
🟦 Base: Chicken Stock
Base Active
Cost: £1.20/L • 8 sub-recipes
Collapsible tree shows recipe dependencies. Color coding helps identify recipe types at a glance.

Screen 2: Recipe Detail with Cost Cascade

UX Note: Show ingredients, costs, and how changes cascade to dependent recipes. Auto-calculate GP% based on selling price.
Spaghetti Bolognese
Gross Profit %
72%
Cost: £4.80
Sell: £17.00
Profit: £12.20
✓ Excellent GP
Ingredients & Costs
🟨 Bolognese Sauce (Sub-recipe)
250g portion
£2.40
Spaghetti
200g
£0.60
Parmesan Cheese
25g
£0.80
Fresh Basil
10g
£0.15
Total Cost per Portion
£4.80
💡 Cost Cascade Impact
This recipe depends on Bolognese Sauce (sub-recipe). If Bolognese cost changes, this dish's cost and GP% will auto-update.
Cost cascade visualization helps chefs understand ingredient dependencies. GP% prominently displayed for profitability awareness.

Screen 3: Multi-Venue Sharing

UX Note: Share recipes across venues. Track which locations use each recipe and sync status.
Share Recipe
3 Venues
Spaghetti Bolognese
Base: Tomato Sauce → Sub: Bolognese Sauce → Final Dish
Select Venues to Share With:
⚠️ Sync Dependencies
This recipe depends on Bolognese Sauce and Tomato Sauce. These will also be synced to selected venues.
Sync status clearly shown. Dependencies automatically handled to prevent broken recipes at other locations.

Screen 4: Version Control & Forking

UX Note: Track recipe changes over time. Allow venues to "fork" recipes for local customization without breaking shared version.
Version History
Current: v1.2
Spaghetti Bolognese
5 versions • Created June 1st, 2024
v1.2 (Current) Active
Updated parmesan quantity • June 12th by Chef Mario
Cost: £4.80 • GP: 72%
v1.1
Changed pasta portion size • June 8th by Chef Mario
Cost: £4.65 • GP: 73%
v1.0
Initial version • June 1st by Chef Mario
Cost: £4.90 • GP: 71%
🔀 Fork this Recipe?
Create a local copy that won't be affected by updates from other venues. Perfect for location-specific customizations.
Version history tracks all changes with costs and GP%. Forking allows customization without breaking shared recipes.

Design Guidelines - Module 5

Recipe Type Color Coding

🟦 Base Recipes
Blue - Foundation items
🟨 Sub-recipes
Yellow - Intermediate components
🟩 Final Dishes
Green - Customer-facing items

Key Features