Odoo Inventory Consultant, Lebanon

Receipt routes and quarantine for medicines and food

In Odoo Inventory, each warehouse can receive goods in one step straight to stock, in two steps through an input area, or in three steps with a quality stage between input and stock. For a Lebanese distributor of medicines, supplements or packaged food, the three-step option often mirrors reality: goods arrive, wait in quarantine while documents and samples are checked, and only then become available to sell.

The design choices I settle with your operations and quality leads:

• Where quarantine lives. A dedicated location that sales cannot reserve from, so unreleased goods never appear as available.
• Who releases stock. A named role validates the move to stock, leaving a record of who released which batch and when.
• Storage conditions. Cold rooms or controlled areas modeled as separate locations, so a putaway rule sends each product to the right place.
• Rejected goods. A return or scrap path with a reason, so finance sees the cost and the supplier claim can follow.

Odoo's own quality checks, which can block a transfer until a test is recorded, belong to the Quality app in Enterprise; in Community the quarantine step still works, with checks recorded outside or through an added module. Regulatory duties for medicines remain with your pharmacist or regulatory lead; the system records what they decide. The pharmaceutical page describes the wider workflow.

Lots, expiry dates and tracing a recall

Lot tracking in Odoo attaches a batch number to every unit received, moved and sold. With expiry dates enabled, each lot can carry its expiry, a best before date and an alert date, and a removal strategy based on expiry tells pickers to take the earliest dates first. Feature names and placement can vary by version, so I confirm them in yours before the design depends on them.

For a food or pharmaceutical importer, the value shows up on a bad day. If a supplier warns about a batch, the traceability report shows where every unit of that lot went: which customers, which deliveries, what remains in which location. That answer takes minutes when lots were captured properly at receipt, and days when they were not.

So I focus on the moments where lot data is created:

• Receiving, where the lot and expiry are entered or scanned from the supplier's label.
• Internal transfers between the main warehouse and branches or vans.
• Customer returns, which must come back under the same lot, not a new one.
• Stock counts, where unknown lots are investigated rather than overwritten.

I run a mock recall in staging before go-live: pick a lot, trace it forward to customers and back to the purchase order, and confirm the report gives your quality lead what they need. Serial numbers follow the same logic for equipment such as generators or medical devices. The food and beverage page adds sector context.

Building materials: units, packaging and phased site deliveries

Construction materials traders in Lebanon buy cement, steel, tiles, paint and insulation in units that rarely match how they sell. A supplier invoices by the ton, the yard sells by the bag; tiles arrive on pallets and leave by the square meter. Odoo handles this through unit of measure categories with conversion factors, plus packaging definitions that tell the warehouse how many units sit in a box or on a pallet.

The pitfalls are mostly about rounding and consistency. If a bag weight is defined loosely, stock drifts every month. I agree each conversion with the person who buys and the person who counts, then test a purchase, a sale and a stocktake on the same product to show the quantities agree.

Site deliveries add a second layer. A contractor may order a full quantity and call off deliveries as the work progresses. Odoo creates a backorder when part of a delivery ships, so the remaining quantity stays visible. Where a manufacturer ships straight to the site, a dropship route avoids receiving goods that never touch your yard, while still linking the supplier bill to the customer invoice.

Some traders also store stock at a third-party warehouse or a supplier's depot. I model those as separate locations or a separate warehouse, depending on whether you control the stock, so availability and valuation include it without confusing the pickers. The trading page covers related sales and purchasing workflows.

Landed cost, valuation and the handoff to Odoo Accounting

Imported goods carry more than the supplier price. Freight, insurance, clearing, port charges and local transport all belong in the cost of the product, otherwise margins look better than they are. Odoo's landed cost feature lets the accountant attach those charges to a receipt and split them across products by quantity, weight, volume, value or equally. It relies on automated inventory valuation, so the valuation method is a finance decision taken early, not a warehouse setting changed later.

Currency adds a step. Supplier invoices may be in dollars or euros while some local charges arrive in another currency. Each landed cost line is converted at the rate Odoo holds for its date, so the rate rules agreed for Odoo Accounting in Lebanon apply here too.

Tax on sales sits with Accounting rather than Inventory. VAT on customer invoices follows the taxes and fiscal positions your accountant approves; because a ready Lebanese fiscal package may not exist for your version, confirm with Odoo or the implementer what the chosen localization covers. The same applies to delivery documents: where the localization offers no local layout, the implementer designs the delivery slip and any Arabic or French text, and your staff approve it.

Before go-live I reconcile the stock valuation report against the general ledger with the accountant, so both sides agree from day one. The inventory and warehousing page explains how valuation choices affect reporting.

Scanning, outages, editions and when a WMS fits better

The Barcode app, which guides receiving, picking and counting on scanners or phones, is part of Odoo Enterprise. Community users can still scan into standard fields with a keyboard-style scanner, but without the guided screens. Because both depend on reaching the server, outages need a plan. If Odoo is hosted in the cloud, the warehouse needs a dependable connection with a backup line; if it is self-hosted on site, the server, network switch and scanners must stay on the generator or UPS circuit.

Either way I write a short fallback routine: what is recorded on paper during an outage, who enters it afterward and how the day's counts are checked. That routine is tested once before go-live, not invented during the first cut.

The edition list for inventory is worth confirming line by line with Odoo or the implementer, since placement changes between versions. Typical items to check are the Barcode app, quality checks, advanced putaway and some shipping connectors.

Odoo Inventory may not be enough when:

• Very high pick volumes call for wave planning and labor tracking that a dedicated warehouse management system provides.
• Cold chain monitoring needs sensor data and alarms beyond what an ERP records.
• A pharmaceutical operation needs validated systems under a regulator's rules, which needs specialist review.

Platform-level questions are covered under Odoo in Lebanon; for comparisons with other systems read ERP consulting for Lebanon, and the Lebanon overview sets out market background.