-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve unit handling #422
Comments
This sounds really good, thanks! |
The feature for a weight article would be very helpful and desperately needed! We are in the process of switching to FoodSoft and are confronted with the problem that there is no way to enter sub-1kg amounts for articles that are priced by the kg. So far we're worked around this by setting the unit to 100g, but then the price has to be divided by 10 and gets rounded up or down in comparison to the kg-price - not good! Not only does the supplier receive an order form with prices and units that are not quite correct, but people who pick up their orders can't rely on the price as listed in FoodSoft since it always has a rounding error. |
Has this been implemented in the mean time? We are currently searching for a new software/system for Kornkammer in Freiburg but our model is based on ordering large bulk quantities (25kg) and users "buying" stock whenever they like (eg 234g). (Lager Coop) |
Unfortunately not. Most groups just use smaller "base units" as "workaround" at the moment. That's the reason why it's so low on the priority list. |
There are some use cases, which do not work with the current system:
Example:
units
of 3kg cheese for 30EURunit
of 200g for 2EURunits
of 3.05kg for 30.5EURwe can change the
unit
from 200g to 1g, but when receiving it we can only enter 1x3kg which is not 3,05kg (or 3050 x 1g).I propose the following changes:
article_units
field to the article model (would become 3kg in the example)unit_quantity
to1
and hide it together witharticle_unit
(we usearticle_units
only)unit_quantity
is1
, otherwise the UI is like it is now[ 3050 ] x 1g
)The text was updated successfully, but these errors were encountered: