And quick example: at 8:12 a.m., register 3 rang up a mop as a “romance paperback,” and the guest asked if it came with a happy ending… We laughed, fixed the SKU, comped 10% for the hiccup, and now I’m double-checking our POS mappings — any other goofy mis-scans you’ve seen that turned into a good recovery moment?
Had a plunger ring up as “sheet music” once; we made a POS hotkey for a custom discount reason called Mis-Scan so the 10% comp logs cleanly and we can run a weekly report to fix the bad SKUs. Small caveat: teach the opener to do five sanity scans around 8 a.m — in the “romance paperback” and cleaning sections so it doesn’t hit register 3 at 8:12 again. Do you already track discount reasons or is it just free-text notes?
@bradford_89 8:12 a.m. checks out — pre-coffee chaos; add a ‘description confirm’ prompt on department mismatch, limited to mornings.
Quick example: our broom scanned as “frozen entrée” at 7:58 and the guest asked if it needed a microwave — . We added an ISBN/EAN guard: if a code starts 978/979 it’s forced to Books; anything else landing in Books triggers a verify pop and, if corrected, auto-applies the 10% so the recovery logs right. @bradford_89 think a nightly vendor-UPC sanity sweep would cut down the 8:12 a.m. surprises?