There is a backend for restaurants. How to work with different units of measurement for ingredients?

Question

Database

There is a system for restaurants with a lot of possibilities. On the front end, the user uses all sorts of different convenient units of measurement - kilograms, ounces, bags, teaspoons, half a glass, a pinch, and so on often appear in recipes. But in order to generate reports, inventory and other things, that is, all tasks on the backend, it is necessary to somehow translate all this into some one universal unit of measurement. And then somehow display in the reports, calculate the remainder, etc. again in "convenient" units. When translating back and forth, an error may accumulate.
What are the solutions to this tangle of problems?

Answer 1

EMNIP, for catering enterprises there is such a thing as "product layout", and everything is expressed in the same units. Conclusion - even at the stage of adding a recipe to the database, bring everything to one unit, possibly adding a non-standard unit as a note, that is, "salt - 10 g (1 tsp)". True, the problem will still remain that everyone has their own "teaspoon", someone takes it with a bang, someone takes less than a full one, etc.

Answer 2

Useless IMHO. One fig will run plus / minus, because. cooking is not math. Unless your robot works, with fine tuning. After all, you can’t figure out how many teaspoons are in a bag of sugar. Weight can change with humidity.
Well, in general, if someone pecked at the director, then everything should be translated in general to a single unit - for example, to grams.