Your customers text, call and email their orders in. Quay puts them all in one run list and holds back anything that needs checking.
Fig. 1Quay order control system
"4 kegs sat morning, usual stuff cheers"
"2x cider kegs 1x lager fri pls"
"same as last Friday please"
"six lager kegs for Saturday"
The Riggers
Source retained · Call · 09:41
Demonstration data · Inspect any stageTap a stage to switch surface
The problem
The order that never got written down costs more than the software does.
Nothing for customers to learn, and no way to keep track.
Structured, but only if your customers play along.
Review
You get the message they actually sent, what Quay made of it, and the decision that is waiting on you.
Fig. 2Quay review cockpit
The Tramworks
Product unresolved · 78 kegs
The Riggers
Quantity 6× usual · 18 kegs
The Saltmarket
Amended after order · 6 kegs not 3
WhatsApp · 30 Jun 2026 · 16:22
"Hi / 78 kegs for tomorrow pal, 12pm"
Confirming adds this line to Run 04
Who it is for
The examples above use a drinks wholesaler. It works the same whatever you deliver.
The run sheet
Fig. 3Daily run manifest
| Stop | Window | Customer | Order | Qty | Status |
|---|---|---|---|---|---|
| South / West · AM | |||||
| 01 | 08:00 | The Rivet | Lager 30L keg | ×4 | Ready |
| 02 | 08:30 | Whiteinch Events | Lager 30L keg | ×6 | Ready |
| 03 | 09:00 | Dowanhill Hotel | IPA 30L keg | ×3 | Ready |
| City / North / East · PM | |||||
| 04 | 14:00 | The Riggers | Lager 30L keg | ×18 | Held · 6× usual |
| 05 | 14:30 | The Tramworks | Lager 30L keg | ×78 | Ready |
| 06 | 15:00 | The Saltmarket | IPA case | ×6 | Ready |