Bonded vs Duty-Paid Stock, Explained

Two States That Look Identical on a Shelf and Aren’t

A case of wine sitting in a bonded warehouse and a case sitting in a merchant's own duty-paid stockroom can be physically indistinguishable: same bottles, same labels, same condition. From a tax and accounting standpoint they are entirely different things. Bonded stock has had no UK excise duty or import VAT paid on it yet; duty-paid stock has. That single difference changes what a merchant is allowed to do with the stock, what has to appear on an invoice, and what obligations attach to moving it. Confusing the two, even briefly in a spreadsheet, is one of the most consequential record-keeping mistakes a wine merchant can make. It misstates a tax liability, not just a stock count.

What "In Bond" Actually Means

Bonded storage is an HMRC-approved excise warehouse arrangement. It lets wine, and other excise goods, be stored and in many cases traded between merchants without excise duty or import VAT being paid at that point. The tax is suspended, not waived, until the wine leaves the warehouse for consumption in the UK. HMRC's own rules for what can be held in, and removed from, an excise warehouse are set out in Excise Notice 197, the authoritative reference for how the suspension and the duty point actually work. This is what makes en primeur trading practical at scale. A chateau's wine can move between merchants, be bought and sold multiple times, and sit in storage for years, without anyone in that chain paying duty on stock nobody is yet drinking. The moment wine is formally withdrawn from bond for UK consumption, that suspension ends and both duty and VAT become due. Our companion guide on how duty and VAT are calculated on wine moving out of bond explains exactly how that figure is worked out.

What "Duty Paid" Actually Means

Duty-paid stock is wine on which excise duty and VAT have already been settled. That can happen three ways: it was withdrawn from bond for a specific client, imported and cleared through customs as duty paid from the outset, or bought from a supplier who had already paid duty on it. Once wine is duty paid, it can move freely without further duty or VAT liability attaching to that specific stock again, subject to VAT on the eventual sale itself under whichever scheme applies. That also means duty paid on it once must never be recalculated and charged a second time at a later movement of the same stock. A record that cannot tell the difference between "this stock has never had duty raised on it" and "this stock already settled duty at an earlier withdrawal" risks precisely that double charge.

Why the Books Have to Track Bond Status as a Property of the Stock Itself

The practical consequence for a merchant's inventory system is that bond status is not a separate report bolted onto the stock record. It has to be a property of the individual stock unit itself. A merchant will typically hold both bonded and duty-paid stock of the exact same wine at the same time, and even the exact same original case can end up split between the two states — part sold on duty paid to a private client, part still sitting in bond for a trade buyer. Bacchus ERP tracks bond status (en primeur, in bond, duty paid, or in transit) directly on each stock unit, across every warehouse location and operator a merchant uses. So a case moving from bonded storage to duty paid is a state change on one continuous record, not a transfer between two disconnected systems that have to be reconciled by hand.

In Transit: The State Most Systems Forget

Wine doesn't move from bond to duty paid instantaneously. It is in transit for a period, sometimes days, sometimes longer for international shipments. A stock system with only two states, bonded and duty paid, has no honest way to represent stock that is neither sitting still nor yet settled. Bacchus ERP models in-transit as its own explicit bond status, and goes further: stock can be sold 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 physically lands, at which point it completes itself automatically against the newly landed position. That matters because a merchant who cannot represent "sold, but not yet landed" honestly has only bad options. Delaying the record understates the pipeline; recording it prematurely against unconfirmed stock overstates the position. Neither is an accurate picture of the business.

Multiple Operators, One Record

Most merchants of any scale use more than one bonded-warehouse operator, and the same wine can genuinely sit across several sites at once as stock is spread for logistics or client-specific reasons. A merchant tracking that across separate operator portals or spreadsheets has no single place to see a wine's total bonded position at a glance. Duty planning and client reporting both get slower and more error-prone than they need to be. The Wine and Spirit Trade Association (wsta.co.uk) represents members across exactly this multi-operator bonded-trade landscape, and is a useful ongoing reference for how the bonded side of the trade operates in practice. Bacchus ERP tracks bond status across every warehouse location and operator on one record, so a case moving between operator sites — still in bond the whole time — never needs reconciling against a second, disconnected system.

A Worked Example: One Lot, Two Bond Statuses

Take a six-case lot bought en primeur and eventually landed in bond at a London City Bond site. Two years later, a private client wants one case delivered to their home for personal drinking. A trade buyer wants the remaining five cases kept in bond, because they intend to resell before ever taking physical delivery. The single case going to the private client has to be withdrawn from bond, which triggers duty and VAT at that point, on that case only, at whatever rate is in force that day. The remaining five cases stay bonded and untouched by duty, and can continue to be bought and sold between trade buyers without triggering tax each time they change hands. A stock system built around a single wine-level status rather than a unit-level one has no honest way to represent that split: the lot as a whole is neither "bonded" nor "duty paid," because both are simultaneously true of different parts of it. This is exactly the scenario hierarchical lot/case/bottle tracking with per-unit bond status is built to handle, and it is a routine occurrence in any book that trades at meaningful volume, not an edge case.

Why This Distinction Is the Foundation the Rest of the Ledger Depends On

Bond status isn't just a stock-tracking convenience. It is the input everything downstream depends on getting right, which is why it is worth having explained carefully rather than assumed. The duty and VAT calculation on a movement depends entirely on knowing whether stock is currently bonded or duty paid — and, if duty paid, whether it already settled duty at an earlier point. The ledger entries a sale generates differ by bond status. And a client's own statement of holdings needs to distinguish bonded stock they own but cannot yet take physical delivery of duty-free from duty-paid stock sitting ready to ship. Get bond status wrong at the stock-record level, and every calculation built on top of it inherits the error: duty, VAT, ledger postings, client statements. That is the practical case for treating bond status as a first-class property of every stock unit rather than a manually maintained side note. It is the same reasoning behind our approach to what a wine trade ledger has to record, and to our own wine trade accounting and ledger software. For the full model of how stock is tracked at the lot, case, and bottle level underneath bond status, see our why the fine wine trade needs its own ERP page, and for the bonded-warehouse side specifically, see bonded warehouse stock management software.