3
To day a blocked product can create an empty cart that then needs to be deleted when the user logs off, if the user does not tries to sell other items and then tries to log off.
It's a strange user experience to delete an empty cart, just to be able to log off.
Today, POS makes two calls, the first one with the transactionId to create a cart and then next AddCartLines.
.../Commerce/Carts?api-version=7.3
.../Commerce/Carts('8001-800132-2974')/AddCartLines?api-version=7.3
Would be cleaner if the POS could call one time (AddCartLines) instead of two times (Carts, AddCartLines), and AddCartLines would create the Cart if needed on a successful validation of the cartlines and other validation needed. The transaction id is anyway sent as part of the url when adding cartlines.
It's a strange user experience to delete an empty cart, just to be able to log off.
Today, POS makes two calls, the first one with the transactionId to create a cart and then next AddCartLines.
.../Commerce/Carts?api-version=7.3
.../Commerce/Carts('8001-800132-2974')/AddCartLines?api-version=7.3
Would be cleaner if the POS could call one time (AddCartLines) instead of two times (Carts, AddCartLines), and AddCartLines would create the Cart if needed on a successful validation of the cartlines and other validation needed. The transaction id is anyway sent as part of the url when adding cartlines.
STATUS DETAILS
Needs Votes