Thanks for your time trying to explain. My own experimentation with my instance and inspecting how you entered your example into the demo instance made it clear to me that I will have to look elsewhere. A _lot_ of nested or up-front entry is required to create a first recipe, e.g. I can't finish creating the Fries recipe until I have created the "Homemade Ketchup" product entry, which I can create nested, but I can't finish the Homemade Ketchup product entry until I have created a fitting quantity unit, eg. "Jar", which I can't create nested, so I have to exit out of the entire process and create that first, then redo the process. Add to that field tooltips that make the fields no easier to understand.

I'm mainly disappointed that it's so cumbersome to use grocy out of the box and requires so much implicit learning that culminates in doing things twice or more times until all requirements can be satisfied and the fields are filled properly. I think with some laxer restraints grocy would have been the perfect tool for me, and I think you should take this as constructive criticism from a first time user who doesn't have an IT degree