A racking is the most frequent movement in a cellar, and it is also where paper records usually break down: the litres that arrived, the litres lost and the vessel the wine now sits in are three facts that must stay together. In WineOS a transfer records all three and updates both vessels and the LOT in one save.
What you will do
Move all or part of the content of a vessel into another vessel, record the losses, and decide whether the moved part continues as the same LOT or becomes a child LOT of its own.
Steps
- Start the operation from the source vessel and choose the transfer. The header states what you are doing: Transfer — same LOT, change container, or Transfer — split into new LOT.
- From container is filled in for you and read-only.
- Under Destination containers, choose the To container. It must be a different vessel, and the same vessel cannot appear twice in a multi-destination transfer.
- Enter the volume to move (L). WineOS checks the destination capacity and refuses a vessel that cannot take the volume, telling you how many litres remain free — and asks you to set a capacity if none is recorded.
- If only part of the LOT moves and that part should live on as its own LOT, tick Split quantity into a new LOT, then enter the split quantity and the child LOT container.
- Record losses, as litres or as a percentage, and check the final volume after the task.
- Read the review screen — source, destination, volume after the transfer, losses and what remains in the source — and save.
Filling a row of barrels from one tank is the same operation with several destinations, and a barrel destination is recognised automatically: there is no separate "transfer to barrel" record to look for.
What WineOS updates
- Without a split, no new LOT is created: the same LOT changes vessel and keeps its code, its history and its parents.
- With a split, a child LOT is created in the destination with the split volume, while the parent keeps the remainder in the source vessel. The review shows parent before, child and parent after; LOT numbers are generated on save.
- The source volume goes down by the volume moved plus losses; the destination volume goes up by what actually arrived.
- Both the LOT history and the vessel history of the two containers show the movement, one as an exit and one as a placement.
When the destination is not empty
The check runs per destination row, before you can continue:
- Empty destination — the transfer is allowed.
- Consolidation — the vessel already holds must of the same winemaking. On save the volumes are consolidated into a single LOT of roughly the total litres; no third LOT code is invented for the same wine.
- Not allowed — the vessel holds an active LOT that cannot be consolidated automatically, because it belongs to a different winemaking or is not must. The transfer is blocked and the guidance points you to Blend / Consolidation, where you classify the resulting LOT and keep the parent LOTs visible.
The rule is deliberately strict. Joining wine from two different batches is a decision about the wine itself, and that decision belongs in the blending wizard, not in a transfer.
Practical example
Tank T-006 holds 2,400 L. You rack 1,980 L into three 330 L barrels plus a 990 L destination, declare 12 L of lees loss, and leave the rest in T-006. Because no split was ticked, the wine remains one LOT that now reads across four vessels' histories — and if you later bring the barrels back into T-006, WineOS recognises the same wine as a consolidation.