-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Misleading notification when updating stock for a variant that is not tracking inventory #2946
Comments
Which of these two expected behaviors is ideal? I feel like if a product is set to "do not track" then we shouldn't allow changes to the count, but does anyone else feel different? |
I agree with that @jacobherrington, having a product that does not track inventory to actually count the inventory might be a very special use case |
Disabling or removing the edit button on non-tracked products makes sense to me. |
@seand7565 maybe disabling the count on hand input field is better? The edit button is still needed if you need to change the |
from working with people who manage the products but are very tech averse, I would say that if you disable or remove the ability to edit the count, please also add a tooltip or something explaining why. it's a tiny thing that would go a long way. |
I'll have a look at this one 😸 |
Steps to reproduce
You'll see the something like this:
Expected behavior
I expect one of 2 things to happen:
Option A: The stock count is updated successfully
Option B: The message tell me as a user that the count was not updated because the variant is set to not track inventory.
Actual behavior
What actually happens is that I get a success message telling me the count was updated, when it wasn't, which is misleading to a regular user, especially if it wasn't the same person who unchecked the track inventory option.
System configuration
Solidus Version: 2.7.0.alpha (we're using edge, tracking the master branch, but haven't updated a few weeks)
Extensions in use:
The text was updated successfully, but these errors were encountered: