Cask Manager

FeaturesDocsBlog
Log inGet early access
For warehousekeepers and bottlers

A compliant bottling run, notice to despatch

Notice, start, bottle and complete — every stage a hard server-side gate — turning a completed vatting or an agreed trade specification into traceable case lots and FIFO sales orders, without ever touching a cask’s duty-suspended status.

Get early access
Capabilities

Bottling & finished goods

The compliance stepper

Notice, start, bottle and declare outturn, then complete — every stage a hard server-side gate. EWER reg 14(3)’s 24-hour prior-notice wait is shown on screen, with an admin-only override that’s always audited.

Two source routes

A run consumes a completed vatting or an agreed, warehouse-reviewed SCB bottling specification — the trade pipeline’s agreed spec becomes a real compliant run, not a re-entry of the same data.

Outturn → case lots

One case lot per outturn line, carrying its own stock number, duty status and a provenance trail back to the run and every source cask that fed it.

FIFO sales orders

Confirm, allocate on a first-in-first-out basis, despatch and complete — for a platform owner account or an external buyer with no account here.

Suspension-safe by construction

Bulk-to-cases conversion never touches W1 Section B — the spirit just changes container, still under suspension. Run losses are recorded as loss observations, the same mechanism maturation losses use.

Third-party bottling

Goods travelling to an external bottler go under a W8 record, or — when the bottler holds its own EMCS approval — a real EMCS movement the run links straight to.

How it fits

Part of the same chain of custody

See it running on your own bond

Join the design partner programme, or read the docs to see how every workflow is put together.

Get early accessRead the docs