Skip to content
Hypamoon

For teams that run on Cassa in Cloud

Cassa in Cloud food cost per dish, from recipes

Cassa in Cloud keeps stock per product and a margin report per product sold. Its help centre says that report does not work out food cost or products made of several ingredients, so recipes and ingredient use are kept somewhere else.

How it goes today

  1. Keep the recipes and ingredient costs in a spreadsheet.
  2. Export the products sold in the week from the reports.
  3. Multiply each dish by its ingredients to see what was used.
  4. Correct the stock of each ingredient by hand.

How it can go

Ingredients leave stock as dishes are sold, and you see the food cost per dish each week.

You give each dish its ingredients and amounts once, and the recipes are kept next to Cassa in Cloud. Each night the dishes sold that day are read per shop, and the ingredients they used are booked out of stock in Cassa in Cloud. On Monday you get the food cost per dish from the cost prices in Cassa in Cloud, with the dishes whose cost rose most at the top. Waste counts only when you enter it.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Cassa in Cloud key in the portal, never in the chat.

Your request

With Hypamoon, keep the recipe of each dish I give you, with ingredients and amounts. Every night, read the dishes we sold that day per shop in Cassa in Cloud and book the ingredients they used out of stock there. Every Monday, send me the food cost per dish using the cost prices in Cassa in Cloud, with the dishes whose cost rose most at the top. Count waste only when I enter it.

You create the Cassa in Cloud key yourself in the portal under Account Settings, API, and choose what it may read and change. Cassa in Cloud offers this on the Retail Enterprise and Risto Enterprise plans. You can revoke the key there.