Skip to content
All projects
Web AppIn active development

ScratchCount

Catch scratch-off tickets that go missing between shifts.

Overview

A multi-tenant app for one job: flagging lottery tickets that disappear at a shift boundary. Each pack's ticket number is recorded when a shift opens and when it closes; when the next open sits above the previous close, the unaccounted tickets are flagged and a different manager countersigns the anomalous read.

The problem

Scratch-off packs are the easiest thing in a convenience store to steal from, because a missing ticket looks exactly like a sold one until somebody reconciles the pack. By the time the numbers are checked the shift is long over and there is no way to say whose it was.

The approach

A standalone edition carved out of DuoCount, keeping only the scratch-off feature and the plumbing it needs — multi-store, multi-location, PIN-per-employee, and owner, manager and employee roles. The reduction deliberately kept the multi-clerk countersign, because that is what makes a count worth anything: signed, timestamped, append-only reads, with an anomalous one signed off by somebody other than the person who recorded it.

Outcome

  • A gap between one shift's closing ticket number and the next shift's opening number is flagged automatically, with both signers named against it.
  • Counting is fast enough to actually happen: scan a ticket with the camera, walk the shelf, or type the game and pack number by hand.
  • The dashboard surfaces reorder reminders and pattern alerts — pack gaps, mass after-hours jumps, and counts still waiting on a second signature.
  • Running as its own deployment against its own Firebase project means a store can adopt the scratch-off audit without taking on the rest of DuoCount.

What it does

  • Shift-boundary audit

    Open and close reads per pack, with unaccounted tickets flagged where the sequence jumps.

  • Multi-clerk countersign

    An anomalous read is signed off by a different manager, one tap from the report.

  • Barcode scanning

    Camera scan-to-log, a shelf-walk mode, manual entry, and a sold-out final count that opens the next book of the same game at zero.

  • Owner reporting

    Per-shift ticket-sequence table with gaps and signers, a books-on-hand census reconcile, and a branded printout.

Ask about ScratchCount

Want something like this, or curious how a piece of it works? Send a note — it reaches me tagged with this project, so I have the context before I reply.

Replies within 24h on business days.