Bonded Warehouse Stock Management Software Across Every Operator and Site

Bond Status Tracked Across Multiple Operators and Sites

Stock is tracked at multiple locations with an explicit bond status: en primeur, in bond, duty paid, or in transit. Those sit across an operator-and-site hierarchy of distinct bonded-warehouse operators, each with their own storage sites underneath them. In-transit is modelled as a genuine state of a movement rather than a fake location. A case doesn't just have "a warehouse" in the system. It has an operator, a site, and a bond status that all travel with it.

Movement Instructions Raised the Moment Stock Is Released

When a shipment carrying a bonded line is released, Bacchus ERP automatically creates and confirms the movement instruction to the relevant bonded-warehouse operator. There is no separate step to remember, and the confirmed queue is visible. That internal instruction record is the platform's own side of the movement. The outward transport connection to an individual operator's own system is a per-operator integration, detailed on the integrations page.

Selling Stock Before It Even Lands

Stock can be sold while it's still in transit into bond. The sale is held as a deferred claim, with no money posted and no stock moved, and it completes automatically the moment the matching stock is recorded as landed. A partial landing settles what actually arrived and leaves the rest of the claim waiting for the next one, with no manual reconciliation required.

Duty and VAT Calculated at Withdrawal, Not Before

Stock held in bond has no duty or VAT due against it. Both are only raised on the withdrawal invoice, generated automatically the moment a dispatch out of bond is recorded. The figure is calculated from the unit's own bond status at an effective-dated UK ABV duty rate. Stock that already settled duty at a prior withdrawal is never charged it a second time. Full detail on the duty and VAT engine.

Cellarage Cost-Recovery, Automated on a Schedule

Storage charges from the warehouse are matched to client holdings by stock-unit UID, recharged with your own margin, and posted to the ledger as accruals or deferred income. Itemised storage and withdrawal invoices are generated automatically as each storage rate's own charging period closes — exactly once per period, even if a check runs twice or is also triggered by hand.

The Same Bonded Stock, From Allocation to Sale

Stock that lands into bond from an en primeur allocation stays on the same lot/case/bottle record the whole way through to sale, with full lineage preserved through any split or merge. It is not handed off between a separate warehouse system and "the real ERP" at any point — one continuous record from purchase order to withdrawal. See the full fine wine ERP picture, or how this fits wine trading software more broadly.

Every Unit Tracked to the Bottle, With Its Own History

Bonded stock in Bacchus ERP isn't tracked as one undifferentiated quantity per warehouse — every unit carries its own bond status and location down to the individual bottle, and a read-only timeline traces how it got there rather than just reporting where it currently sits.

Detection Is Automatic; the Write-Off Decision Is a Person's

Where capitalised purchase cost gets stranded by an inconsistent posting history, the platform detects it automatically. The correction itself is always operator-triggered, with a required reason logged against it, rather than an automatic silent sweep that adjusts figures without a human decision behind them. The two background workers that would otherwise ingest a real bonded-warehouse feed and reconcile discrepancies are shown in the admin UI exactly as they are, running or stopped, rather than presented as active when a real interface hasn't been configured. Every scheduled worker in the platform is opt-in per deployment, not switched on by default.

Storage Invoices That Can't Double-Bill a Period

Each storage rate has its own charging period. The platform holds a lock across the entire check-then-generate step for a given client and period, so a scheduler tick racing a manual trigger, or two overlapping runs, still produces exactly one invoice for that period rather than two. A preview mode returns what an invoice run would produce without ever opening a transaction, so a warehouse manager can see the numbers before anything is raised.

What This Page Covers, and What It Doesn't

This page is about warehouse-operator and site management around bonded stock — bond status across operators, movement instructions, and cellarage billing — and not the lot/case/bottle inventory record itself, which now has its own dedicated page, or the trading and execution screen the platform runs on top of that same stock.

For the inventory model in full, including duty status attached to each unit, see wine merchant inventory system.