Capture the requirement at the recipe
Start with the equipment name shown for a dish. Link that requirement to the actual item, installation space and venue. A screenshot of a kitchen appliance does not establish that every visually similar object serves the same function.
- Record exact displayed name and purchase source.
- Check whether one item supports several recipes.
- Keep decorative furniture separate from functional equipment.
Account for setup separately
A durable equipment purchase belongs in a setup-cost record. If you allocate it across expected servings for a planning scenario, state the assumed serving count. Do not mix the full purchase cost into every future service period.
- Vendor / greenhouse / catch
- Kitchen stock
- Recipe + equipment
- Menu serving
Confirmed broad connections; exact ingredient and equipment mappings remain unverified.
Greenhouse machinery has its own context
The March 2025 greenhouse blog describes specialized machinery and cultivation controls. This supports a separate farming-equipment relationship, not a kitchen appliance list. Record the crop and module dependency in the correct system so search can distinguish growing equipment from cooking equipment.
What we’ll check at launch
- Names, functions and costs
- Placement restrictions
- Maintenance or recurring costs if present
Compare dishes, serving contribution and a revenue-weighted menu margin.
Follow the evidence
Checked Fri, 11 Sep 2026 04:27:05 GMT · No released build verified. Official previews can change before launch.
- What's on the menu in Nivalis Nights? 2026-08-14
- MARCH 2025 COMMUNITY BLOG 2025-03-07
