4 ms·

The store I managed had a suspend/recall. Cart full of groceries only to realize you left your wallet (at home, in the car, whatever) suspend the transaction an

The store I managed had a suspend/recall. Cart full of groceries only to realize you left your wallet (at home, in the car, whatever) suspend the transaction and print a slip with a barcode on it. Move the cart out of the way and take the next customer. The customer comes back and scans the slip at any register to recall the transaction, pay and collect their cart and leave without having to hold up lines/etc... Was a nice convenience many appreciated.

dylan604 3y ago
This very thing happened to me, and I was very pleasantly surprised with how this worked. It definitely took some of the embarrassment away from being a dolt
c22 3y ago
I worked at a store that had this feature except if you reloaded the transaction on a different register it still got attributed to the originating register and caused a headache at closing :(
- DropInIn 3y ago
  Manual probably dictated that a policy of receipt transfer and (irrationally) presumed synchronous cash out times. Management just didn't RTFM/FTFM.
fy20 3y ago
When I was studying (late 00s) I worked at a large supermarket chain in the UK that had this. The system was surprisingly well designed. It was based on Windows NT (somehow hardened, as I never saw a checkout show a BSOD or fail to boot) and was designed before a time when you had a continuous internet connection. There was a mini-server in the back office, and every night it would sync with HQ. This meant all functionality, including taking credit card payments and loyalty, could be done offline. One time we had a electrical systems failure in the store, and everything - including chillers - went down. However each checkout had its own UPS and continued to operate without issue.
- adw 3y ago
  If, let's just say, every little (feature of the checkout software) helps — if you follow my drift — the architect of that system is a mate of mine. I've never worked with him (I know him through music stuff, not tech stuff), but he's a deeply thoughtful guy.

dylan604 3y ago

This very thing happened to me, and I was very pleasantly surprised with how this worked. It definitely took some of the embarrassment away from being a dolt

c22 3y ago

I worked at a store that had this feature except if you reloaded the transaction on a different register it still got attributed to the originating register and caused a headache at closing :(

DropInIn 3y ago
Manual probably dictated that a policy of receipt transfer and (irrationally) presumed synchronous cash out times. Management just didn't RTFM/FTFM.

fy20 3y ago

When I was studying (late 00s) I worked at a large supermarket chain in the UK that had this. The system was surprisingly well designed. It was based on Windows NT (somehow hardened, as I never saw a checkout show a BSOD or fail to boot) and was designed before a time when you had a continuous internet connection. There was a mini-server in the back office, and every night it would sync with HQ. This meant all functionality, including taking credit card payments and loyalty, could be done offline. One time we had a electrical systems failure in the store, and everything - including chillers - went down. However each checkout had its own UPS and continued to operate without issue.

adw 3y ago
If, let's just say, every little (feature of the checkout software) helps — if you follow my drift — the architect of that system is a mate of mine. I've never worked with him (I know him through music stuff, not tech stuff), but he's a deeply thoughtful guy.