Recipe Grouping & Display Logic
To keep the menu easy to browse, recipe categories are organized and displayed based on their Group Code. Each Group Code follows a structured pattern that determines:
-
Which parent group a recipe or package belongs to (e.g., Breakfast, Lunch & Dinner, Desserts).
-
The order in which groups appear in the portal menu.
-
Sub‑category hierarchy (e.g., Starters → Entrees → Sides).
How the Grouping Works
-
Each category has a Group Code (A, AB, AC, BB, etc.).
These codes follow an alphabetical pattern that defines the display order.
-
Parent groups use single‑letter codes
Example:
A → Menu
B → Desserts
C → Beverages
-
Sub‑groups use expanded codes based on their parent
Example under parent A (Menu):
AB → Breakfast
AC → Lunch & Dinner
ABA → Breakfast Bowls
ABG → Breakfast Entrees (Exact subs depend on your dataset.)
-
The portal reads these codes alphabetically
That’s why categories appear in the order seen in the menu display — not manually ordered, but automatically sorted by the Group Code
- If you want packages and recipes to display together, both items must have the exact same:
-
- Group Name, and
- Group Code
Matching both values ensures the portal groups them into a single category instead of separating them.
What Users See in the Portal
On the left‑side navigation, groups appear like this:
-
Breakfast
-
Lunch & Dinner
-
Starters
-
Side Salads
-
Entrees
-
etc.
-
-
Desserts
-
Beverages

This order is entirely driven by the underlying Group Code structure shown in the management table:

How to Create or Edit Recipe Groups:
To manage recipe groups in the Core application:
-
Go to Data Items
-
Select Food Management
-
Open Recipe Group Management
-
To create a new group: click New
-
To edit an existing group: double‑click on any group in the list