By Core Bracket

How a laundry shop keeps unpaid orders visible

Unpaid laundry work is usually quiet: a deposit at drop-off, an estimated weight, a jacket marked ready, and a balance that lived only on a stub. The clothes are found; the till disagrees. Fixing that starts by making the remainder a field on the order, not a memory.

Ready and unpaid answer different questions. The collection queue is finished work waiting for pickup. An order can sit there with money still due. An order can be paid in full and still be in processing. Staff who only watch the rail hand over unsettled work; staff who only watch the till cannot see what is actually finished.

When payment can be partial, the remaining balance has to travel with the order through notices and collection. Reports of outstanding balances beat a drawer of tickets. Search by customer, order, or tag is how the desk recovers that balance when the customer is standing there.

This is not a collection-rate promise. It is the record design: one balance, a ready queue that is not the same list, and an identifier that reaches both. How the wider counter path works, and how to evaluate software for it, are covered separately.