Every part, in detail

A roastery already runs every one of these. Green arrives and has to be recorded, roasts have to be planned and then actually roasted, the cup has to be scored, orders have to be picked, and someone has to invoice for it. The work exists whether or not there is software underneath it. What usually goes missing is the thread between the parts, so a lot code in the warehouse, a batch in the roast log, and a line on an invoice describe the same coffee without ever being connected.

Every capability below writes to one record. A roast depletes the green lot it drew from and creates roasted stock in the same movement; a cupping score stays attached to the batch that produced it; a sales order is filled from stock that actually exists. Nothing here is a module that has to be reconciled with another module at month end, because there is only ever one set of numbers.

They are split across three products for one reason: where the work happens. Roasting needs a machine connection and a screen at the drum, so it lives in Pilot on the Mac. The record everyone shares lives in Cloud, on the web. Counting stock and answering a customer happen while standing up, so they live on iOS. Start with whichever area is costing you the most time. Each page below covers one, in full.