Feature Request: Multiple Homes

My family shares food between multiple households, and would like to be able to see what’s in which house, and to have different default locations per product, per house.

Here’s how I see the feature fleshed out:

• Home entity (for my purposes, only needs a Name, custom fields can be used for anything else)
• A default Home should be created (it should be possible to rename it)
• If only one Home exists, Grocy does nothing behaves differently than today in terms of UI, everything defaults to the one Home that exists
• Each Location can belong to a Home, needs to allow duplicate names (one per home)
  • Update locations schema: UNIQUE INDEX on locations.name + locations.home_id instead of just locations.name
• Each Chore can belong to a Home, need to allow duplicate names (one per home, yes, this means duplicating a lot of chores, but they likely need different schedules anyway)
  • Update chores schema: UNIQUE INDEX on chores.name + chores.home_id instead of just chores.name
• Each user would be assigned a default house (but I don’t think we need to limit them to specific houses)
• Stock would have a filter for Home (or All Homes)
  • Each user has an account preference as to whether they see stock just in their house, or all houses by default
• When adding products, purchases, transferring, or consuming products, the users home locations would be top of the list.
• Each product can have one default location per home
• When tracking a chore, the users homes chores are listed first
• For Meal Plans & Calendar, those should be per Home also, but I’m not sure if we really need to see each others meal plans, so it should default to the users Home, and might have a dropdown to see other homes
• Recipes should be visible by all, but filterable by Home (maybe defaulted to users Home)
• Equipment and Batteries should also be per Home, probably needs schema updates to allow UNIQUE based on name + home_id
• Tasks are assigned per-user, so I think that can be left alone

[robocopp3r]

+1. Is the current workaround running multiple instances?

[KylesDev]

+1