Odoo Inventory Barcode: Scanning-Driven Warehouse Workflows Receiving, Picking, Transfers & Counts

What Odoo Inventory Barcode Means

Odoo inventory barcode is the practice of running warehouse operations — receipts, deliveries, internal transfers, and inventory counts — by scanning barcodes through Odoo's Barcode app, which sits on top of the Inventory app's transfer model. Every stock movement in Odoo is a picking: a receipt (WH-IN), a delivery (WH-OUT), or an internal transfer (WH-INT). The Barcode app exposes each picking as a guided, scanner-driven workflow so workers confirm what they actually touch instead of typing quantities on a keyboard.

The scanning layer is hardware-agnostic. Any USB or Bluetooth scanner that emulates a keyboard works, the Odoo mobile app can scan with the smartphone camera for light use, and rugged mobile-computer terminals handle heavy warehouse duty. This is distinct from the Barcode app overview, GS1 nomenclature fundamentals, and hardware basics, which are covered on our /learn/barcode page — this guide focuses on the operational scanning workflows inside Inventory.

• →Inventory app ‣ Configuration ‣ Settings → Barcode section: enable the Barcode Scanner to turn on scanning for receipts, deliveries, transfers, and counts.
• →Every operation type (Internal Transfers code WH-INT, etc.) has its own scannable operation-type barcode that routes the worker to that workflow.
• →Command barcodes (Validate, Add quantity, Remove quantity) can be printed and scanned instead of tapping the screen — useful when hands are busy.
• →Hardware is independent of vendor: USB-HID, Bluetooth keyboard-emulating scanners, mobile computers, or the Odoo mobile-app camera scanner.

Enabling and Configuring Inventory Barcode

Barcode-driven warehouse operations are enabled from Inventory app ‣ Configuration ‣ Settings. Scroll to the Barcode section and check the Barcode Scanner box. The Barcode app then provides the scanner interface for receipts, deliveries, transfers, and inventory counts.

From that same Barcode section you can print command-barcode sheets (Validate, Add quantity, Remove quantity) and the operation-type barcodes, choose the barcode nomenclature (default EAN/UPC or GS1), and configure how lots and serial numbers behave during scanning.

Per-operation-type configuration lives under Inventory ‣ Configuration ‣ Operation Types. There you can make lot or serial-number scanning mandatory for a given operation, forcing workers to scan a lot or serial barcode before a line can be validated — important for tracked products such as pharmaceuticals, electronics, or food.

1. 01
   Turn on the Barcode Scanner

   In Inventory app ‣ Configuration ‣ Settings, scroll to the Barcode section and enable the Barcode Scanner. This activates the Barcode app as the scanning interface for Inventory operations.

2. 02
   Print command and operation-type barcodes

   From the same Barcode section, use 'Print barcode commands and operation types' to produce sheets for Validate, Add quantity, Remove quantity, and each operation type (WH-IN, WH-OUT, WH-INT, etc.).

3. 03
   Choose a nomenclature

   Keep the default nomenclature for EAN/UPC barcodes, or select GS1 encoding if your products carry GS1-128 / GTIN barcodes with lot, expiry, or catch-weight application identifiers.

4. 04
   Enforce lot/serial scanning where required

   Under Inventory ‣ Configuration ‣ Operation Types, set lots or serial numbers to mandatory so workers must scan a lot/serial barcode before a line can be validated on tracked products.

Receiving and Picking with Barcode (Receipts and Deliveries)

To process warehouse receipts and deliveries with barcodes in Odoo, workers open the Barcode app, where the Barcode Scanner screen lists the available operations. Scanning a product barcode adds the product to the receipt or delivery and increments the quantity; when the demanded lines are confirmed, the document is validated and the stock move posts.

The receiving flow is: open the Barcode app → scan the receipt's barcode (or the WH-IN operation-type code) → scan each product to add or increment the demanded line → scan lots or serials if the product is tracked → press Validate, or scan the printed Validate command barcode, to confirm the goods receipt.

Outgoing deliveries follow the same pattern against a delivery order: scanning the product confirms the picked quantity, and validating the document consumes stock and confirms the shipment. Because every quantity is scanner-confirmed, picking errors and over-ships drop materially compared with manual entry.

Internal Transfers, Batch Transfers, and Inventory Counts

Internal transfers move stock between locations within the same warehouse (operation type WH-INT). Workers scan the WH-INT operation-type barcode to open the transfer, scan the source product and lot, and validate — the goods are moved in Odoo without any keyboard entry.

Transfers can also be created and processed from scratch using the barcode scanner, with the same configuration under Inventory settings. When a lot or serial-number barcode is scanned, Odoo automatically increases the quantity of the matching product on the line.

Batch transfers — for example, grouped delivery orders — can be processed through the Barcode app's Operations screen, letting workers scan through multiple transfers in a single session instead of opening each one individually.

Inventory counts (cycle counts and full stock takes) run from Barcode app ‣ Count Inventory. Workers scan a location barcode to open its stock, scan the products on the shelf, and save the inventory adjustment directly from the scanner interface. This turns physical counts from a clipboard exercise into a guided, audit-ready scan sequence.

• →Internal transfers (WH-INT): scan the operation-type code, scan the source product/lot, validate.
• →Batch transfers: process grouped pickings in one scanning session from the Operations screen.
• →Inventory counts: Count Inventory → scan location → scan products → save the adjustment on-device.
• →Adjustments made via Count Inventory post directly to stock as a validated inventory adjustment.

GS1 Barcodes in Inventory Operations

GS1 barcodes carry multiple data elements in a single scan using Application Identifiers (AIs) — 2 to 4 digit prefixes such as (01) for GTIN, (10) for batch/lot, and (17) for expiry date. When the Odoo GS1 nomenclature is selected, Odoo parses these AIs to fill product, quantity, lot, and weight fields automatically during scanning, instead of requiring one scan per field.

Odoo does not create or issue GS1 barcodes. Businesses must purchase a unique 14-digit GTIN from GS1 and enter it on the product's Barcode field (General Information tab). Odoo then reads and combines those existing GS1 identifiers during warehouse operations.

When a GS1 barcode with a weight or quantity AI is scanned and configuration is correct, the parsed quantity is displayed (for example, '52.1 / 52.1 kg') and the Validate button turns green; pressing Validate completes the operation in a single scan rather than a multi-step entry.

Odoo's default barcode nomenclature supports EAN and UPC encodings; GS1 encoding must be selected separately to parse GS1 barcodes. For the full GS1 and nomenclature reference, see /learn/barcode.

The Dynamics 365 Equivalent: Warehouse Management Mobile App

Dynamics 365 Supply Chain Management's equivalent is the Warehouse Management mobile app (the successor to the older Warehousing app), paired with Advanced / Warehouse management processes. Where Odoo's Barcode app is a single scanning interface driven by Inventory's transfer types, D365 exposes warehouse work through configurable mobile-device menu items.

Administrators configure the menu items workers see under Warehouse management ‣ Setup ‣ Mobile device ‣ Mobile device menu items, each mapped to a work-creation process: purchase-order receiving, sales-order picking, transfer, cycle counting, put-away, replenishment, and more. Workers install the Warehouse Management mobile app on an Android (and now iOS) device, connect to the SCM environment, and step through guided prompts.

Barcode scanning is supported natively with automatic intent-output on supported rugged Android scanners, with advanced scanner configuration (symbologies, prefixes/suffixes, intent delivery) controlled at the device profile level. Microsoft documents the Android devices tested and supported for barcode scanning, including ruggedized Zebra- and Honeywell-class handhelds typical of enterprise warehouse environments.

Step-level flow behavior — including prompts, inputs, and detours that let a worker pause one task to perform another and return — can be tailored per menu item, so organizations customize the scanning experience workers actually see.

Choosing the Right Scanning Model for an SME Warehouse

The two platforms serve different operating points. Odoo Inventory + Barcode is a lightweight, fast-to-deploy scanning layer that runs on any keyboard-emulating scanner or a phone camera — well suited to SME warehouses that need receiving, picking, transfer, and count scanning without the overhead of full WMS license-plate direction.

Dynamics 365 SCM with the Warehouse Management mobile app is the better fit for mid-to-enterprise operations whose competitive edge depends on advanced warehousing: wave processing, work cycles, license-plate and container handling, directed put-away, and slotting tied to a configurable mobile menu-item engine. Its scanning configuration is enterprise-grade and admin-controlled, at the cost of more setup.

Both are legitimate answers; the right one depends on warehouse complexity, volume, existing ERP footprint, and how much directed WMS logic the operation actually needs. As a dual-platform implementer, Flectic scopes both options against your real warehouse processes before recommending a path.

• →Pick Odoo Inventory + Barcode when you want scanner-driven receiving, picking, transfers, and counts live in weeks, on inexpensive hardware.
• →Pick Dynamics 365 SCM when you need directed put-away, license plates, wave processing, and granular mobile menu-item configuration across a large warehouse.
• →Both support GS1 barcodes and rugged hardware — the difference is WMS depth and configuration weight, not barcode capability.
• →For most SMEs, the deciding factor is existing ERP direction and warehouse complexity, not the scanner itself.