Categories should describe what a menu item is, not when or how it's served. This is the most important rule for building a category structure that stays useful long-term.
When a category is tied to an occasion — like "Morning Tea" or "Conference Lunch" — it limits where that item can appear. A scone is a scone whether it's served at 10am or 3pm, at a wedding or a board meeting. If it lives in a "Morning Tea" category, you'll find yourself duplicating items or creating workarounds every time a client wants that same item in a different context.
Instead of placing a scone in a category called "Morning Tea", place it in a category called "Baking". It can then appear on any breakfast, morning tea, lunch, or afternoon tea menu without needing to exist in multiple places.
A well-structured menu in Puree works best with:
This keeps your item library easy to navigate when building quotes, without categories becoming so broad that items are hard to find.
Here's an example of what a well-structured category list might look like, covering both office catering and events:
Notice that none of these are occasion-based. "Finger Food" works for a working lunch or a children's party. "Canapés" works for a cocktail function or a wedding pre-dinner. "Baking" works for breakfast through to afternoon tea. "Buffet – Mains" works for a corporate dinner or a Friday office lunch.
Here's how occasion-based categories compare with item-based alternatives:
| Avoid (occasion-based) | Better (item-based) |
|---|---|
| Morning Tea | Baking |
| Working Lunch | Sandwiches & Wraps |
| Cocktail Nibbles | Canapés |
| Wedding Dinner | Buffet – Mains |
| Conference Refreshments | Platters |
If your current categories are occasion-based, the Puree support team can help you transition to a cleaner structure without losing any data. Get in touch and we'll walk you through it.
As always, if you have questions or feedback, reach out to us at email@puree.app.