Could you post screenshots of the data you’re wanting to organize?
Hi @james4567,
For a menu database like what you have here, theres definitely lots of way of organizing based on what your needs are. I will assume that you will want to use your Airtable database to directly power the data on your website. You could structure your base something like this:
- Table of all your drinks. Here is where you would have fields for categories, the description of the drink, the image of the drink, and any other data about the drink that you want to keep.
- Table with ingredients. Here is where you would have all your ingredients. Keep metadata like calories by volume, allergens, etc. You would link these ingredients to all your drinks to create the drink’s ingredients list.
- Table with packaging template (cup sizes available). Here you would have all the packaging sizes that are available with volumes.
- Junction table of packaging with drinks. This will allow you to create 3 or as many packaging per each drink and be able to automatically calculate total calories and nutritional values based on the volume for each drink.
- Optional: If you need to keep track of changes to your drink ingredients or keep track over drink versions, then you would need a junction table of the drink version that you would link to your main table drink with the most up to date version.
This high level structure gives you the most flexibility with building and making adjustments to your drinks recipes and even cup sizes. All the data could be easily accessible for you to integrate it directly with your website using the Airtable API.
Let me know if this sounds like a good direction and if you have any questions, happy to provide more actionable details.
