Odoo Inventory Consultant in Nigeria

Factory, central warehouse and depots as one route network

A typical Nigerian distribution setup has a production site or import warehouse feeding a central store, which resupplies depots in other states, which in turn serve distributors and key accounts. In Odoo Inventory, each of those sites can be its own warehouse with its own stock locations, and resupply routes define which warehouse refills which.

The design choices I settle with your operations team:

• Resupply direction. Whether depots pull stock through reordering rules or the central warehouse pushes planned loads. Pull rules suit steady demand; planned loads suit full-truck dispatches.
• Transit locations. A dedicated transit location per route, so goods dispatched but not yet received are visible as stock on the road rather than disappearing for days.
• Two-step receipts at depots. The depot receives against the dispatch, records any shortage or damage, and only then moves goods into saleable stock.
• Reordering rules per depot. Minimum and maximum levels that reflect the time a truck really takes, not an optimistic figure from a planning sheet.

Odoo also supports multi-company stock where depots belong to a separate legal entity, with intercompany rules creating the matching documents. Whether that structure is right is a decision for your accountant. The global Odoo Inventory page explains routes and steps in general terms.

Expiry-first picking and returns from the trade

Food, beverage and household products sold through Nigerian distributors carry expiry dates, and the cost of a recall or a pile of expired stock at a depot is real. Odoo Inventory supports lot numbers and expiry dates on products set for tracking, with removal strategies that propose the earliest expiry first when a picker prepares an order.

Returns are where the setup is usually thinnest. Distributors and retailers send back goods for many reasons: damaged in transit, near expiry, wrong product, unsold promotional stock. Each reason needs a different outcome. I design return operations that route goods into separate locations:

• Resaleable stock that passes inspection and goes back on the shelf.
• Damaged stock awaiting a decision to rework, sell as seconds or scrap.
• Expired stock awaiting destruction under your quality team's procedure.

Each return also needs a commercial outcome, usually a credit note or replacement, which Odoo can link to the original order. The credit policy is your sales director's decision; the system records it consistently. Scrap and destruction then post through stock valuation, so finance sees the cost of returns by reason and by customer. My inventory and warehousing page covers return design more generally.

Landed costs on dollar imports

Many Nigerian businesses import raw materials, packaging or finished goods paid in dollars, then sell in naira. The cost of a received item is more than the supplier invoice: freight, insurance, port charges, clearing agent fees and duty all belong in the product cost if margins are to mean anything.

Odoo can allocate these extra costs to receipts through landed costs, splitting them by quantity, weight, volume or value. Whether it behaves the way your finance team expects depends on the edition and release, so I try it in a test database before the costing approach leans on it. With your accountant, I settle:

• Valuation method per product category, such as average cost for traded goods whose purchase prices vary.
• Exchange rate source for the supplier invoice and for each cost line, which may be billed in different currencies on different dates.
• Timing, because clearing charges often arrive after goods are sold, and late landed costs affect stock already shipped.
• Reconciliation of landed costs against the clearing agent's statements at each month end.

How duty and import charges are treated for tax remains your advisor's call. Revaluation and the exchange rate trail sit with Odoo Accounting in Nigeria.

Scanning and dispatch when power or the network fails

Odoo's Barcode app, which is an Enterprise feature, lets warehouse staff receive, pick, pack and count with scanners or phones. It works in a browser and needs a connection to the database. In a Nigerian depot, that connection depends on grid or generator power, the local network and the internet link, and any of them can fail during a dispatch.

The hosting choice changes what fails. A server on the warehouse network keeps scanning running through an internet cut, provided the server and network stay powered. A cloud database survives a local power cut on the server side but stops scanning the moment the depot loses its link. I compare these with your IT lead and write the result into the go-live plan.

Whatever the hosting, each depot needs a fallback procedure:

• Printed pick lists generated at the start of each shift for confirmed orders.
• Manual dispatch notes numbered in sequence and signed by the driver.
• Catch-up entry by a named person when Odoo returns, in the order goods actually moved.
• A reconciliation check comparing system stock with a spot count for affected products.

We rehearse the fallback before go-live so it is a routine, not an improvisation. The Odoo in Nigeria page discusses hosting options in more depth.

Delivery documents, VAT on invoices and localization gaps

Odoo Inventory produces delivery slips and transfer documents, while VAT appears on the customer invoice created by Sales and Accounting. That split matters in Nigeria because distributors may expect specific information on a waybill or delivery note, and the tax treatment on the invoice depends on the product and customer.

Here is what I check, and with whom:

• Fiscal localization. Whether a Nigerian localization exists for your version and what it installs. Coverage varies, so confirm with Odoo or your partner rather than assuming.
• Delivery note content. Fields such as vehicle number, driver name, seal number and depot are added to the transfer and printed on the slip, as your logistics team specifies.
• Invoice timing. Whether invoices follow ordered or delivered quantities, which affects how shortages and returns flow into tax documents.
• Electronic invoicing. How the federal e-invoicing direction reaches your company is for your tax advisor. On the Odoo side, the invoice data must be clean enough for whatever connector is later used.

Where the localization lacks something, the gap is closed by configuration first, then a maintained module, then custom work. Third-party logistics providers and dropship from manufacturers can also be modeled as routes; I agree how their stock reports reconcile with Odoo. Broader context is on my ERP consultant Nigeria page and the Nigeria overview.