grocy
Feature Request: Allow multiple images per product
I would like to be able to have multiple images per product.
Example use case: I buy water bottles (different barcodes and brands) but have them all under one product called "water bottle" - because I don't especially care about which one it is - but to make it easy for others that are helping me with stock management it would be great if I could have the different images for easy visual identification. This goes for other products that can come in very different packages as well.
As to not break implementations that can only show one image due to constraints (such as the space allowing only for a thumbnail on lists) and to have consistent behavior there should also be a way to identify one "main" product image.
Please be so kind and put a little more thoughts into how this should work practically regarding displaying n images instead of one without destroying the complete layout. Consider each and every place where currently the product picture is shown. And consider that people will add 100 or 250 images, just because they can.
I buy water bottles (different barcodes and brands) but have them all under one product called "water bottle"
but to make it easy for others that are helping me with stock management it would be great if I could have the different images for easy visual identification
The most logical / "Grocy way" of doing it would be to simply attach all the barcodes to that product "water bottle". Manually scrolling through pictures cannot be faster than letting the barcode matching magic do its thing. Multiple barcodes per product were invented precisely for the use case described.
Please be so kind and put a little more thoughts into how this should work practically
Will do :)
...barcode matching magic...
Maybe I wasn't clear/My example was not a good one, but the idea is to be able to tell another person that I need X and for them to visually be able to quickly identify it in the stock. ps: I know this is not the intended use case, but I also use grocy to keep track of my electronics development components, thus the need for that.
I know this is not the intended use case, but I also use grocy to keep track of my electronics development components
Right, not the intended use case as you most likely already read elsewhere and this will stay like so. So you mixed up a completely unrelated water bottle example use case with that, why? Please first provide a real-world on-topic example use case problem you currently have where barcode matching is really not the way to go.
I know this is not the intended use case, but I also use grocy to keep track of my electronics development components
Right, not the intended use case as you most likely already read elsewhere and this will stay like so. So you mixed up a completely unrelated water bottle example use case with that, why? Please first provide a real-world on-topic example use case problem you currently have where barcode matching is really not the way to go.
I used that use case to make my example clearer... knowing fully it isn't the intended use case, that's why I even mentioned that...
What I said still stands, I need someone to go get something from the stock that might come in different style packaging (because they are different brands, using different colors, etc) and instead of having to try and describe what different types of packages they might be looking for, I can just open the product page and show them the pictures. I will find an ingredient later that illustrates that problem well and send some pictures if it still isn't clear enough.
There are also other reasons to having multiple images I can think of, like having a picture of the back of a box with the nutritional table and list of ingredients. And while yes, I can probably write it out in the product description, I think the images can cover some use cases that would otherwise have to be specifically implemented or end up having a clunky workaround.
I'm not bothering with unrelated examples, I was just thinking of ways this could be useful and better trying to convey the idea of: having a visual aid in identifying the product inside a crowded stock for someone that has not seen it before
knowing fully it isn't the intended use case, that's why I even mentioned that...
Not at first, only after my first response. And come on, needing n images to identify water bottles is not so much out of a real-world use case. Please base feature requests on real use case problems you encounter while actually using Grocy, don't try to invent fairy tales maybe with the intention that it's added faster for your out of scope use case. It's always noticeable (and I hate that).
I explained the use‑case already - a quick visual aid so someone who’s never seen the product can spot it in my crowded pantry. That sits squarely inside Grocy’s “ERP for the kitchen” goal. The idea wasn’t even mine at first, it was my mom’s. She uses Grocy more than anyone here and got tired of new helpers and friends grabbing the wrong jar. I’m sorry I didn’t make that background clear straight away. I also led with water bottles only because I’ve ended up with a bunch of different barcodes for the same bottle (the labels keep changing), so they were the first example that popped into my head after the explanation she gave me. And, yes, my pantry lives in a long, narrow corner, so visibility is awful.
I get that feature requests can pile up and wear you down. Still, reading that my scenario was a “fairy tale” felt pretty rough. A simple “out of scope right now - PRs welcome if you’d like to prototype” would have done the job without discouraging casual contributors like me (or, by proxy, my mum). All I hoped for was a bit of back‑and‑forth on whether the idea made sense, maybe some pointers if I ever find time to code it.
If the feature never ships, that’s fine; I mostly wanted the real‑world use‑case on record. It might help someone else later. I’d just ask that future replies focus on the problem, the possible fix, and the next step, rather than questioning motives. I just wanted to try to make Grocy better for everyone, and I believe in getting the best out of these discussions. But hey, maybe that's just me, I try to see/get the best out of things in improving as life goes on.
That’s all from me for now. Thanks for reading, and have a good day.
I explained the use‑case already a quick visual aid so someone who’s never seen the product can spot it in my crowded pantry. That sits squarely inside Grocy’s “ERP for the kitchen” goal. The idea wasn’t even mine at first, it was my mom’s. She uses Grocy more than anyone here and got tired of new helpers and friends grabbing the wrong jar.
No, it's the first time you provide a real world example use case for this. The first one was about water bottles, nothing out of reality (so "fairy tale" describes it IMHO pretty accurate). The second one was about electronic components, out of scope of this project.
would have done the job without discouraging casual contributors
What discourages me is putting (spare) time into theoretical-only "problems" or out of scope ones, and until your last response all provided looked exactly like that. This is a hobby project, not a commercial product.
An idea how to display n pictures everywhere where a product picture right now is displayed is still required.