Odoo App implementation
Know what stock you have, where it is and what you can promise to a customer. Connect receiving, storage, picking and delivery with purchasing, sales and production.
Official Odoo Partner
Odoo implementation, development, integration and ongoing support.
Business purpose
Odoo Inventory is the application that records products and their movements. It helps answer four everyday questions: what do we have, where is it, what is it worth and why is the quantity what it is? A warehouse represents a physical site; locations describe its receiving area, shelves, bins and packing zones. Each movement has a source and a destination, so the history explains how the balance formed. Reliable reports depend on employees recording and validating what actually happened.
Odoo Inventory in practice
Owner-supplied screenshots show the application, configuration, operations, stock availability, forecasts and valuation. All screens retain their original proportions.
Key capabilities
Selected capabilities that matter when the app is implemented as part of a real business system.
Describe the places where goods physically move. One warehouse can contain receiving, chilled storage, individual bins and packing areas. A location barcode helps an employee confirm where a product was placed.
Warehouses and storage locationsOn hand means the quantity recorded now. If 17 of 20 units are reserved, only three are free to use. Forecasts add expected receipts and subtract planned outgoing quantities; expected goods are not yet on the shelf.
On-hand, available and forecasted stockRecord what the supplier actually delivered, including quantity, lot or serial number where needed. If 18 of 20 units arrive, validate 18 and keep the remaining two on a backorder or cancel them if they are no longer expected.
Turn a customer order into warehouse work: collect the right products, check quantities, pack and dispatch. These can be one operation or separate steps. Preparing a parcel and handing it to a carrier are different events.
A route connects rules that tell Odoo how to supply a need: buy a product, manufacture it, move it from another warehouse or pass it through picking and packing. Reordering rules can trigger replenishment for configured tracked products.
Routes and replenishmentSuggest where a product or category should be stored, such as frozen goods in the freezer. Internal transfers record a change of location; moving stock between shelves does not itself increase the company’s total quantity.
Putaway and internal transfersA lot identifies a batch; a serial number identifies one unit. Trace where it came from and which customer received it. Packages identify groups of goods, such as a pallet. Expiry controls depend on the chosen tracking configuration.
Inventory holds the stock records; the separate Barcode app lets employees execute the same operations with a scanner. Scan products and locations instead of searching manually. Pack quantities and units of measure still need correct configuration.
Barcode executionCompare counted quantities with the records and apply explained adjustments. Scrap removes unusable goods from ordinary available stock. Valuation follows the costing and accounting setup; every scan does not automatically mean a new accounting entry.
Our experience
Confirmed delivery experience and supported inferences from ERPixel projects—not generic product claims.
ERPixel has implemented warehouse management in Odoo for more than ten years. We map actual goods movements, configure warehouses, locations and operation types, connect scanners and train employees on their daily tasks.
Our work includes multiple warehouses, lots, serial numbers, packages and complex routes. We investigate wrong product records and movements, including earlier periods, with attention to stock valuation and accounting consequences.
We configure product costing and develop reports on inventory turnover and ABC analysis. Landed costs allocate relevant acquisition expenses to stock; their treatment must agree with purchasing and finance.
A documented project connected five legal entities, up to 12 warehouses and seven 3PL providers with Amazon, Shopify and Xero. Orders, delivery statuses and reference numbers flow between the responsible systems.
International ecommerce and seven 3PL connectorsTypical workflow
The exact stages are adapted to the company, but ownership and handovers must remain explicit.
Open the expected receipt, identify products and record the quantity that arrived. Capture tracking details and handle any outstanding quantity.
Place goods in the correct location, apply agreed putaway rules and reserve stock against demand. Validate movements when they actually happen.
Follow the delivery task, collect the right quantity and tracking identifiers, then prepare the parcel according to the warehouse process.
Confirm the completed warehouse operation and exchange shipment details with the carrier or 3PL. Investigate discrepancies instead of hiding them with unexplained adjustments.
Implementation considerations
These decisions vary by app and determine whether users receive a controlled workflow or another disconnected tool.
Separate warehouses from locations. Goods in transit, damaged stock and count differences usually need appropriate locations and flows rather than another physical warehouse.
Check unique product and variant identifiers, barcodes, units, lots and initial counts. Give product creation a clear owner to reduce duplicate records.
Agree how employees handle partial receipts, wrong products, scrap and returns. We often separate scrap identification from final approval; this is a configured process, not a universal Odoo requirement.
Low-value consumables may not justify exact counts. In Odoo 19, goods without Track Inventory enabled do not provide the same on-hand and forecast control. If a shortage stops work, consider tracking and replenishment.
What ERPixel can do
ERPixel starts with the business process, uses standard Odoo where it fits and adds engineering only where the approved scope needs it.
Map the process, define a limited scope, configure roles and workflows, prepare data, test and support go-live.
Consult and implementAdd maintainable fields, logic, reports or modules when a verified requirement cannot be met through configuration.
Customize and developConnect external systems, migrate or upgrade existing solutions, train users and support controlled improvement.
Integrate and improveConnected Odoo Apps
These links explain the operational handovers between apps, not just technical dependencies.
Purchasing creates expected supplier receipts and supports replenishment.
Odoo PurchaseConfirmed sales create delivery demand and connect customer orders to warehouse execution.
Odoo SalesSupply components to production and record finished goods coming back into stock.
Odoo ManufacturingConnect operational stock with configured valuation, product costs and financial records.
Odoo AccountingIntegrations
Integration is included only where it serves the app’s real business process.
ERPixel connects orders, products and stock with ecommerce and marketplaces. Barcodes can support product mapping when codes are unique, match on both sides and the connector supports them. Item, variant and packaging identifiers must be distinguished.
Shopify, WooCommerce and AmazonIntegrate products, orders, transfers, stock snapshots, fulfillment confirmations and delivery references. Our experience includes Mintsoft, InfoPlus, CIRRO, AMZPrep, CSG and other logistics environments. Scope depends on each provider’s API.
External WMS and 3PL operatorsConnect the operational Odoo model with external warehouse activity using the agreed product, warehouse, account and order mappings.
Mintsoft fulfillmentShipment requests can return labels and tracking numbers where the connector and carrier support them. We work with processes involving InPost and DHL; carrier collection and warehouse validation remain distinct events.
Define which system owns each quantity and status, when updates happen and how failures are retried. Logs, duplicate controls and comparisons help uncover differences between Odoo and external stock.
Combine warehouse data with sales and finance for stock turnover, ABC analysis and management reporting. Reliable analysis starts with consistent movements, dates and identifiers.
Industry use cases
Selected industries are based on confirmed ERPixel experience and the app’s role in their processes.
Receiving, storage and shipping across internal sites and external fulfillment providers.
Availability shared across sales teams, online stores and marketplaces, with a clear distinction between physical and reserved stock.
Trace raw materials and finished goods while connecting warehouse movements with production demand.
ERPixel expertise
ERPixel is an Official Odoo Ready Partner with experience in implementation, development, integrations, migration, training and support. Our work spans standard app setup and complex environments where Odoo connects sales, operations, finance, ecommerce, warehouses and external APIs.
Odoo Inventory reading
Explore our author guide and clear glossary definitions before configuring your process.
Read Alexander Koltsov’s practical guide with screenshots and demo access.
How Odoo Inventory worksWhat a company holds and how it records stock.
InventoryCurrent recorded quantity, distinct from free or forecasted stock.
Quantity on HandThe rules that connect demand with supply and movements.
RouteThe physical site and its operation settings.
WarehouseA bin, area or movement destination within the stock model.
LocationOdoo Inventory decisions
The useful answer depends on your process, data, Odoo edition and connected systems.
Open the ERPixel demo and select Inventory. Login: demo@erpixel.com. Password: demo@erpixel.com. The demo illustrates navigation and sample operations; your company’s routes, permissions and integrations require their own setup. Open the ERPixel demo
Yes. Users can open operations in the standard interface and enter quantities manually. Barcode provides a separate scanning interface. Availability depends on the Odoo edition and configuration.
No. Some stock may already be reserved. Check free-to-use quantities and the report’s scope before promising delivery. Forecasted receipts are still expected goods.
Review what physically happened, linked documents and valuation effects. A return, reverse movement or justified inventory adjustment may be needed. Preserve an explainable history rather than treating the stock balance as an arbitrary editable number.
Yes, subject to suitable interfaces and an agreed scope. We define identifiers, warehouse mappings, data ownership, update events and error handling before configuring or developing the connection.
Yes. Training covers the team’s real receipts, transfers, counts and dispatch tasks, including discrepancies and tracking requirements. Explore Odoo Inventory training
Odoo Inventory project
Discuss a new implementation, an integration, a focused customization or an existing Odoo workflow that needs improvement.
