How En Primeur Allocations Are Managed

What "En Primeur" Actually Commits a Merchant To

En primeur is a futures market. A merchant orders and pays for wine before it has been bottled, sometimes before it has finished fermenting, on the promise that a specific quantity from a specific chateau and vintage will be delivered a year or more later. The Wine and Spirit Trade Association represents the UK merchants and negociants who run these campaigns every year (see wsta.co.uk). The reason the trade treats en primeur this way is straightforward: an en primeur order is a binding commercial commitment, not a reservation that can be quietly resized once market sentiment shifts. That single fact is what makes en primeur allocation genuinely hard to manage — a real financial and contractual commitment, made against wine that does not physically exist yet. It is also why a spreadsheet tends to fail at exactly the moment it matters most: reconciling what was promised against what actually turns up.

The Three Things an Allocation Record Has to Track Simultaneously

A single en primeur allocation is really three linked records that have to stay consistent with each other for years. The first is the client's ordered quantity: what was promised and invoiced. The second is the supplier purchase order raised to source it, which may be split across more than one supplier for the same campaign. The third is the eventual physical delivery, which is very often short, split across multiple shipments, or delayed. A merchant tracking these in three disconnected places — an order spreadsheet, supplier emails, and a warehouse goods-in log — has no single point where a shortfall becomes visible. It surfaces only when someone cross-checks all three by hand, usually under time pressure, with a client already asking where their wine is.

Bacchus ERP's allocation lifecycle keeps those three records as one linked object from the start. A campaign is created, and client allocations are bound to the quantity actually ordered against it, so an allocation can never silently drift above what was ordered. One or more supplier purchase orders are then raised against the same campaign record. Everything that happens afterwards, from the first purchase order to the last bottle landing, is a continuation of that same record rather than a fresh row to be reconciled back to the original order by hand. See the full case for this approach on our en primeur allocation software page.

Short and Split Deliveries Are the Norm, Not the Exception

Anyone who has run an en primeur campaign for more than one vintage knows the pattern. A delivery landing exactly as ordered, in one shipment, on the expected date, is closer to the exception than the rule. Chateaux allocate across many merchants worldwide, shipping schedules slip, and a case ordered against one campaign can arrive months apart from the rest of the same order. This is where hand-managed allocation tracking breaks down most quietly. A short delivery that nobody flags leaves a client's account overstated, sometimes for years, until a stocktake or a client query surfaces the gap.

Bacchus ERP handles a short or partial delivery automatically, rather than depending on someone catching it during a stocktake. The landed reserve tied to the missing quantity flips state the moment the actual delivery is recorded. So the allocation record always shows the honest gap between what was promised and what has physically landed, instead of quietly writing the difference away. The remaining balance stays visible and traceable back to the same campaign until it is eventually fulfilled or resolved. This sits inside the same wine trading software that runs the rest of a merchant's book of business.

From Promise to Physical Stock, Without Starting a New Record

The moment en primeur wine actually lands, it stops being a line on an order. It becomes physical stock that has to be tracked at the lot, case, and even bottle level for the rest of its life, including every future split, merge, or repack. A campaign-and-order system that hands off to "the real inventory system" once the wine lands creates exactly the seam where allocation history gets lost, because nothing forces the new stock record to carry a link back to the campaign that produced it.

Bacchus ERP avoids that handoff entirely. Once en primeur stock lands, it enters the same hierarchical lot/case/bottle stock model the rest of the platform runs on. Every unit carries its own pack format, location, and bond status, and lineage is preserved exactly when a lot later splits or merges. The allocation is not a separate silo that stops mattering once the wine physically exists: it is the same record from campaign to bottle. The completed record even carries which specific inbound landing fulfilled it, so an allocation's route from promise to physical stock is never a matter of reconstructing events from memory or old emails.

Bond Status From the Moment It Lands

Fine wine bought en primeur almost always lands in a bonded warehouse rather than arriving duty paid at a merchant's own premises. See our companion guide to bonded vs duty-paid stock for what that distinction actually means for the books. Bacchus ERP tracks bond status — en primeur, in bond, duty paid, in transit — as a property of the stock unit itself, across multiple warehouse locations and operators. So a case moving from an en primeur allocation into bonded storage stays on one continuous record, rather than needing to be reconciled against a separate warehouse system. Stock can even be sold on while it is still in transit. The sale is recorded as a deferred claim, with no money posted and no stock moved until the shipment lands, at which point it completes itself automatically against the newly landed position.

Duty and VAT Only Become Relevant Later — But the Record Has to Be Ready

Because en primeur stock typically sits in bond after it lands, excise duty and VAT are not due at the point of allocation. They fall due later, at the point of withdrawal from bond, calculated against whichever rate was actually in force on that day. HMRC's own published Alcohol Duty rates (gov.uk/guidance/alcohol-duty-rates) are revised periodically. So an allocation landed one year and withdrawn several years later has to be calculated against the rate that applied on the actual withdrawal date, not the rate in force when the campaign was booked. Bacchus ERP's duty and VAT engine is effective-dated for exactly that reason: a movement calculated years after the original allocation still uses the correct historical rate rather than today's rate applied retroactively. See our dedicated guide on how duty and VAT are calculated on wine moving out of bond for the full mechanics.

One Ledger, From Campaign to Eventual Sale

Every purchase order, delivery, and eventual sale tied to an en primeur allocation lands in the same double-entry ledger everything else in the business runs through, so there is no separate en primeur spreadsheet to reconcile against the books at year end. That matters most for campaigns that run for years before the wine is sold. A client who bought en primeur in one year and resells through a consignment listing three years later still has a single, continuous financial trail connecting the original purchase order to the final sale. Our guide to what a wine trade ledger has to record covers the full set of entries a merchant's ledger needs to produce, or see the platform as a whole on our fine wine ERP software page.

Reselling on the Same Record

Reselling moves onto the same consignment and brokering lifecycle described in full on our en primeur allocation software page.