24

SOO.
I work at a grocery store, right. Cashier and all ya know, livin the dream. And whoever manages our product database. Needs to get thekr stuff together. We managed to confirm the DB isn't the same across the the registers. So now I have a bunch of stupid pictures of barcodes in my phone so I can make error reports for each and every single item that doesn't ring up. I know not ready dev related. But a dev somewhere is slacking

Comments
  • 2
    I use to have video of a debit reader malfunction, the bounding boxes for input would randomly resize making the customer think they pressed the wrong button.

    You also need all the information from the receipt such as register number and time of transaction.
  • 8
    Just remember a good bug report has three things:
    - What is the expected behavior
    - What happened instead
    - What are the steps to reproduce it?
  • 2
    @bkwilliams @juneeighteen Yep, on our report, we need to fill in the price it rung up for if at all. The expected price, why its wrong, register number, and then initial it.
  • 0
    So....that stinks. Way to go though on helping fix the issue! 👏
  • 2
    Fun fact: The barcode scanner does scan the white spaces, not the black bars.
Add Comment