You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2024. It is now read-only.
The possibility to "return" a specific item. A use case is when a user buys an item, before checking if it is out of stock, and then discovers that the specific item is out of stock.
Possible ideas on how to implement this:
Add a button to the screen that shows for 5 seconds after an item has been sold that cancels the purchase. This could work, but the time period should be extended as the user might use a lot of time before discovering that the item is out of stock, i.e. power king in the fridge.
Add a button to reverse a sale in the user-logged-in screen. Either to cancel the purchase altogether and have the user make a new purchase or to "restore" the shopping cart of the previous order.
The text was updated successfully, but these errors were encountered:
Hm, this is a tricky one. I guess you could hold the purchase for 30 seconds or whatever before actually commiting it, allowing people to revert the purchase, but I don't think that's a clean solution.
A big red slightly quaking box using a polyfill for good ol'
<marquee><blink>
HUSK Å SJEKKE OM ${item.name.toUpperCase()} ER INNE FØR DU KJØPER
</blink></marquee>
would be cleaner and less intrusive.
\s
Jokes aside, I think a dialog telling people to check if the item is in stock before purchasing would be the best, as the only thing that would have to be changed is the callback for the purchase button :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The possibility to "return" a specific item. A use case is when a user buys an item, before checking if it is out of stock, and then discovers that the specific item is out of stock.
Possible ideas on how to implement this:
The text was updated successfully, but these errors were encountered: