-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
consumption-related fields - special cases of bulk products #1090
Comments
Good catch ! Indeed for now we ask for price data, not actual "amount bought" data. |
So in #974 we added the Product.receipt_quantity field. But in the backend it only allowed "Positive integer" numbers. I changed the backend here - openfoodfacts/open-prices#666 - to now allow any "Positive decimal" numbers ! |
So for bulk product the UI will look like Abricots in the screenshot above ? what about just plain weight for products sold by weight ? 2500g or 2.5 kg in the above example. |
You're still talking about receipts right ? Improvements we could do, in line with your comment (correct me if I'm wrong !)
added in the todo of #1169 |
Thanks, that sounds about right ( optional display in grams instead of kg - but I agree it's cosmetic bordering OCD 😄 ) |
In relation with #974 and after #1071 it feels like we'll need an evo to display and take into account the amount of products bought and inputted under Category.
In the screenshot I bought around 3.3 kg but there's no field yet to input that value, so for now the chip display is off ( for clarity and completeness, there's another product ( sold per item ) on that proof but it's missing from the list of bulk products available for now ).
If we want user to be able to keep track of all the bulk products they bought over a period of time.
There's also something in connection with discounted price here - I bought it discounted on account of buying by 2 kg ( cheaper than per 1 kg but more expensive than per 10 kg - ideally I'd want to able to store that info and be able to make use of it later ).
The text was updated successfully, but these errors were encountered: