ShelfSprint

Leaving Stocky · Guide

One restock list, several people

Two of us work the floor. How do we not duplicate each other?

01

The problem with a printed list

Two staff, one list, and no way to know what the other has done. Either you split the list up front and lose the ability to help each other, or you accept that some shelves get filled twice and others get missed.

02

How a shared run avoids it

Everyone works the same run, and each item carries a version. When two devices submit the same item, one write succeeds and the other is told the work is already done — not shown an error, because nothing went wrong. The units really are on the shelf; a colleague put them there.

That check happens in the database in a single operation, so it holds even when both submissions land in the same second.

03

Progress that does not lie

Progress shows items and units, not a percentage. A run’s total genuinely changes while you walk it — a fresh sale can add work — and a percentage that goes backwards reads as a bug even when it is telling the truth.

Common questions

What if someone brings fewer units than asked?
Record what was actually placed. The item stays open for the remainder, and the shelf estimate reflects what really went out. Partial progress recorded honestly is worth more than a tidy completion that is wrong.

See what your own Stocky export is missing before the shutdown.

Run the readiness check

Other guides