YHWong20
commented
6 months ago Team's Response
Indeed, we recognize and accept that this is a flaw of our notification feature (hence why we've changed this bug type from a Functionality Bug to a Feature Flaw).
While we find that this will pose a minor inconvenience for users, we feel that it is not too severe, and ultimately, a user will still receive the notification of their low stock levels. Allow us to elaborate.
In the context you've provided, the user has increased the threshold of a specific item. Perhaps they might've found that this specific product/item is hot-selling, and they'd like to keep more stock of it in their inventory. They've thus increased the threshold to a level greater than their current stock level.
Even though they do not receive a notification immediately, suppose that eventually they make another sale on this same item. In which case, they will definitely receive the notification which informs them of low stock levels (as their current stock level for the item is indeed, lower than the threshold value).
Our point is, if we were to assume the normal, logical flow of events for a small retail business, what we've just described is generally quite likely to occur under normal usage of our application.
Assuming that they do not sell off all of their existing stock, they will still receive a (slightly late) notification of low stock levels, which can still aid them in being more proactive in restocking their items (which is the intended aim of this feature).
The delayed notification thus means that this issue poses a minor inconvenience.
Therefore, given our reasoning, we find that this issue is not too severe, and we will reduce its severity level from Medium to Low.
Duplicate status (if any):
--
updated threshold of item to greater than current stock but there is no warning to restock item
[original: nus-cs2113-AY2324S2/pe-interim#1595] [original labels: type.FunctionalityBug severity.Medium]