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.

Counting Inventory in a Specific Warehouse or Location, Step by Step

The most common warehouse-barcode question is how to run an inventory count — a cycle count or a full stock-take — scoped to one location inside a specific warehouse, using the Barcode app instead of a clipboard. In Odoo 16, 17, 18, and 19 the flow is identical, because it rests on the same stock-move model and the Barcode app's Count Inventory screen. The finished count becomes a validated inventory adjustment that posts to that exact location.

The fastest, most audit-friendly path is to assign the count first and then scan. A manager opens Inventory app ‣ Operations ‣ Physical Inventory, selects the specific location and the products to count, and assigns them to a user. That user then sees a pending count — with the number of products to count shown on the Count Inventory button — the moment they open the Barcode app.

If you would rather count ad hoc without a pre-assigned task, open the Barcode app, tap Count Inventory directly, and scan the location to begin. Both routes end at the same validated adjustment; assigning first simply adds the worker, the scheduled date, and an audit trail.

• →A count scoped to one location changes stock only at that location — other warehouse locations and other warehouses stay untouched, which is precisely why scanning the location barcode is what makes a specific-warehouse count accurate.
• →Blind counting (Show Expected Quantity off) yields the most honest physical number; showing the expected quantity speeds up recounts but can bias a worker toward the system value.
• →Each confirmed count becomes a dated, user-stamped inventory adjustment in Inventory ‣ Operations ‣ Physical Inventory, giving a clean audit trail for a recurring cycle-count programme.

1. 01
   1. Assign the count to a location (optional but recommended)

   In Inventory app ‣ Operations ‣ Physical Inventory, tick the products or location to count and click Request a Count. In the Inventory Request window set Assign to (the worker), Scheduled at (the date), and — if you want the scanner to display the on-hand quantity next to the counted quantity — tick Show Expected Quantity. By default Odoo hides the expected quantity, giving a blind count so workers record what is physically on the shelf rather than copying the system number.

2. 02
   2. Open Count Inventory and scan the location

   Open the Barcode app and tap Count Inventory. Walk to the storage location (for example WH/Stock/Shelf 1) and scan its location barcode. The app highlights that location and lists every product Odoo believes is stored there. If the multi-location feature is not enabled, skip the location scan and scan the first product barcode to start the adjustment instead.

3. 03
   3. Scan each product to record the counted quantity

   Scan each product's barcode to add it to the adjustment and increment its count — scan repeatedly for multiples, or tap the edit icon and use the on-screen keypad, the +1 and -1 buttons, or the number pad to set the exact counted quantity. Products the system expected but that are missing, and products found that were not expected, are both visible on the screen, which is exactly how discrepancies surface during the count.

4. 04
   4. Count an entire location in one pass

   To count everything in a location at once, use Count Entire Locations: from Barcode app ‣ Count Inventory, tap the actions icon, enter or scan the location barcode, tick the Count Entire Locations box, and tap Apply. The app then loads every assigned product in that location so a worker can walk the aisle and scan sequentially. This requires the Storage Locations setting enabled under Inventory ‣ Configuration ‣ Settings.

5. 05
   5. Add unbarcoded products by hand if needed

   If a product or location has no barcode, tap the white Add Product button at the bottom of the Count Inventory screen, pick the product, enter the counted quantity, choose the source location, and Confirm. The line joins the same adjustment, so a mix of scanned and manually entered products validates in a single step.

6. 06
   6. Confirm (validate) the count

   Review the counted quantities, then click Confirm — or scan the printed Validate command barcode to keep both hands free. Odoo writes the inventory adjustment to stock for that location immediately, and a green banner confirms the count is recorded. The adjustment honours lot and serial-number tracking, so counted quantities post to the correct lot or serial where those are mandatory for the operation.

Odoo Barcode Operations and Command Barcodes at a Glance

Every Barcode-app workflow starts by scanning an operation-type barcode that routes the worker to the correct screen. By default Odoo prints barcodes for Receipts, Delivery Orders, and Manufacturing; Internal Transfers and Pick appear only after the Storage Locations and Multi-Step Routes settings are switched on. Because each operation type carries a distinct code, a worker at a dock door can scan one printed label and land directly in the right workflow.

One behaviour is worth planning around: scanning a Receipts operation-type barcode always creates a brand-new receipt — it will not match an existing scheduled receipt even if the contents are identical. To scan into a specific scheduled receipt, first print that receipt's individual picking barcode (a PDF of its reference number) and scan that instead. Delivery Orders behave differently: their operation-type barcode opens the list of currently scheduled deliveries rather than creating a new one.

• →Command barcodes (MAIN MENU, VALIDATE, CANCEL, PRINT PICKING OPERATION, PRINT DELIVERY SLIP, PUT IN PACK, SCRAP) are printed from Inventory ‣ Configuration ‣ Settings → Barcode section, and appear on the sheet whether or not their underlying feature is enabled.
• →Print the picking-operation barcode for any individual receipt, delivery, or transfer to let workers scan straight into that exact document by its reference number — essential on high-volume docks where many orders are scheduled at once.

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.

Barcode Scanner Hardware That Works with Odoo Inventory

Odoo's Barcode app is hardware-agnostic on purpose: it reads scanned characters as keyboard input, so any scanner that emulates a keyboard works without special drivers or an integration project. Odoo's scanner-setup documentation recognises three main scanner families, plus the smartphone camera, and each fits a different warehouse footprint.

USB scanners plug into a computer and suit fixed scanning points — a goods-in desk or a packing station — where a worker brings items to the scanner. Bluetooth scanners pair with a phone or tablet and are the cost-effective portable choice; Odoo runs on the paired device, so the worker walks the aisle scanning and checking stock on the same screen. Mobile-computer scanners are rugged handhelds with a built-in scanner and screen, built for all-day warehouse duty; they must run the Odoo mobile app cleanly, so test recent Android-with-Chrome or Windows-with-Edge units before a fleet rollout.

For light or occasional scanning, the Odoo mobile app can scan using the phone's own camera — no extra hardware — which is often enough for an SME validating a handful of receipts or counts a day. The broader Barcode app overview, nomenclature fundamentals, and command-barcode basics live on the /learn/barcode page.

• →Two device settings matter for every scanner: keyboard-layout match, so special characters inside barcodes are interpreted correctly, and an automatic carriage return after each scan. Odoo applies a default 100-millisecond minimum gap between scans to prevent accidental double-reads, and it reads the carriage return as the end of one scan and the start of the next.
• →Device-specific setup is documented for the brands most common in warehouses: Zebra (set the keyboard wedge via the DataWedge app), Honeywell (Settings → Scanning → Internal Scanner → Default Profile → Data Processing Settings → Wedge Method set to Keyboard), and Cipherlab (ReaderConfig → Default Profile → Data Output → Keyboard Emulation → Input Method set to KeyEvent).
• →Odoo publishes a Compatible Hardware page listing scanners and mobile computers tested with the Inventory and Barcode apps — check it before buying a fleet, because model and operating-system variety means individual testing is still required.

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.

Frequently asked questions