Wine import and distribution breaks accounting software in four specific places: landed cost, Wine Equalisation Tax, vintage as a product dimension, and one stock position across wholesale, direct-to-consumer and a 3PL. Odoo handles all four in the base product with configuration rather than add-ons, which is why it suits importers better than a general accounting package with bolt-ons. This page covers how each one works and what Odoo does not solve.
Landed cost is the one that decides your margin
If landed cost is calculated in a spreadsheet after the fact, you do not know your margin. You have an estimate that was true on the day someone last updated the sheet.
Odoo treats landed cost as part of the receiving workflow. International freight, customs duty, clearance, insurance and port charges attach to the inbound shipment and allocate across the goods on it, by quantity, value, weight or volume. That allocated cost flows into stock valuation, so margin reporting uses the real number rather than the invoice price from the supplier.
Practically, this is what lets you answer "what did we actually make on that container" without rebuilding it by hand. It also means that when freight rates or the AUD move, the effect shows up in your margin reporting on the next shipment instead of at year end.
WET and GST
Wine Equalisation Tax is 29% of the wholesale value of wine, and it sits alongside GST rather than replacing it. For importers, WET is generally payable at customs entry, with the treatment differing depending on whether wine is sold wholesale, retailed direct, or used for tastings and samples.
The problem is not that WET is complicated. It is that WET applied inconsistently produces a BAS that cannot be defended, and inconsistency is what happens when the rule lives in a person rather than the system.
In Odoo this is handled through the Australian localisation plus product classification and tax rules, so WET applies by product type and sale channel rather than by someone remembering. Landed cost and import charges map to the correct GL accounts, which gives an audit trail from the customs entry through to the BAS line.
A WET producer rebate exists for eligible producers, with specific eligibility rules. If you are purely importing rather than producing, it generally will not apply, but it is worth checking rather than assuming either way.
Vintage belongs in the product model, not the product name
The most common catalogue mistake in wine is creating a separate product for every vintage. It works until you want margin by label across five years, or until someone ships a 2021 against an order for a 2022.
In Odoo, vintage is a variant attribute alongside bottle size, with packaging handled as a hierarchy: bottle, six-pack, twelve-pack, pallet. One product, many variants. Pricing, stock and reporting all work at the level you need, and the same catalogue structure serves wholesale and the online store without duplication.
Lot tracking sits underneath this, which is what makes a recall or a quality event manageable. You can trace a batch from the inbound shipment to the customers who received it.
One stock position across every channel
Most importers sell through at least three channels: wholesale to on-premise and retail, direct to consumer online, and often through a 3PL for fulfilment. The expensive failure is when those three disagree about what is on hand.
Odoo runs all of them off one inventory. The online store checks the same stock as the wholesale order, reservations prevent the same case being sold twice, and 3PL integration syncs on-hand, allocated and held stock rather than requiring orders to be re-keyed.
Multi-warehouse and multi-location handle the physical side, including bonded and non-bonded separation where that applies to your operation.
Pricing discipline in wholesale
Margin leakage in wholesale is rarely one bad deal. It is a hundred small exceptions: a price held over from last vintage, terms extended informally, a credit issued without approval.
Customer-specific price lists and trading terms, credit limits, and approval workflows on overrides move those exceptions from memory into a system that records them. Invoicing generates from dispatch rather than as a separate step, which shortens quote-to-cash and removes the gap where invoices get forgotten.
What Odoo does not solve
WET is not a switch. The Australian localisation gives you the GST and BAS structure. WET treatment requires deliberate configuration of tax rules and product classification. Anyone who tells you it works out of the box has not configured it.
Excise is a different tax. If you deal in spirits or fortified products, excise applies rather than WET, and that is a separate configuration question.
It does not replace your customs broker. Odoo records the costs and the paperwork. It does not clear the goods.
It will not fix a catalogue you do not restructure. If ten years of one-product-per-vintage comes across as-is, you have moved the problem rather than solved it. The migration is where the product model gets rebuilt, and skipping that is the most common reason an implementation disappoints.
Production is a separate build. If you also make wine rather than only importing it, that is a manufacturing configuration with its own scope.
How we work
Ooda Consulting is based in Sydney at Level 6/201 Kent St and works with SMEs across Australia and New Zealand. We have delivered Odoo implementations for wine importation, and Ooda's Odoo developers hold Odoo certification, current to version 19.
See Odoo for Wine Importers and Distributors for what we configure, Odoo ERP Implementation for how a build is scoped and staged, or Why do most Odoo and ERP projects blow out? for what goes wrong when it is not.
Frequently asked questions
Can Odoo handle Wine Equalisation Tax?
Yes, through tax rules and product classification rather than a dedicated WET feature. WET is 29% of the wholesale value and sits alongside GST. Configured properly it applies by product type and sale channel automatically, which is what makes the BAS defensible. It requires deliberate setup and is not enabled out of the box.
How does Odoo calculate landed cost on imported wine?
Freight, duty, clearance, insurance and port charges attach to the inbound shipment and allocate across the goods by quantity, value, weight or volume. The allocated cost flows into stock valuation, so margin reporting uses actual landed cost rather than supplier invoice price.
How should vintages be set up in Odoo?
As product variants alongside bottle size, not as separate products. That keeps pricing and reporting workable at both label and vintage level, and prevents the wrong vintage being picked against an order. Packaging sits above it as a hierarchy from bottle to pallet.
Can Odoo run wholesale and direct-to-consumer from the same stock?
Yes. The online store and wholesale orders check the same inventory, with reservations preventing the same stock being sold twice. This is usually the main reason importers consolidate onto one platform.
Does Odoo integrate with a 3PL?
Yes, though integration scope varies by provider. Order release, shipment confirmation with tracking, and inventory sync covering on-hand, allocated and held stock are all standard requirements. Whether it is a built connector or a custom integration depends on the 3PL.
Is Odoo suitable for a small wine importer?
It depends on complexity rather than size. An importer with one warehouse, one channel and simple WET treatment may be better served by accounting software plus a stock add-on. The case for Odoo strengthens with multiple channels, a 3PL, or margin that needs landed cost to be accurate.