Odoo out of the box stores exactly one barcode per product.product variant, in the barcode field, under a single-value uniqueness constraint. That breaks down the moment reality is messier than the master data: the same SKU arrives from two suppliers with different EAN-13 codes, a manufacturer changes the pack barcode between production runs, a legacy system and your carton labels each carry their own identifier, or a case and its inner unit need to scan to the same item. When a scanner reads a code Odoo does not recognize as the primary barcode, the POS, Inventory, and Sales flows simply fail to find the product — and staff fall back to manual name search, which is slow and error-prone at the counter and on the warehouse floor.

We build a made-to-order module that adds a proper one-to-many barcode model to your products. A new product.multi.barcode model (a models.Model with product_tmpl_id / product_id relations, a name barcode field, an optional barcode_type selection such as EAN-13, UPC-A, or internal, and a sequence for priority) lets you register any number of alternate barcodes against a template or a specific variant. We override the product name_search and _search methods so that scanning or typing any registered barcode — not just the native barcode field — resolves to the correct product everywhere the standard search widget is used: POS, stock transfers, inventory adjustments, and sales/purchase order lines.

Technically, the implementation is careful about the parts that matter. A SQL-level uniqueness index (or a @api.constrains guard) prevents the same barcode from mapping to two different products, so scans stay deterministic. Access is governed by ir.model.access.csv plus optional record rules for multi-company setups, and the alternate-barcode list is surfaced as an editable one-to-many tab on the product form via inherited XML views (OWL-compatible for 17/18/19). Where you scan against the Point of Sale, we extend the POS load and the JS barcode-lookup so the alternate codes are available offline in the browser cache, not just server-side. Optional extras we quote on request include printing selected alternate barcodes on QWeb product-label reports, exposing the barcodes over the XML-RPC/JSON-RPC API for external systems, and an automated action to import barcodes in bulk from a spreadsheet.

Delivery is build-to-order: this is not an existing apps.odoo.com download. After a short scoping call we confirm exact scope, your Odoo edition (Community or Enterprise) and version (17.0 / 18.0 / 19.0), then build on a staging copy, run UAT with you, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company record rules, POS-offline lookup, label-report printing, and bulk data-migration volume increase the quoted scope. You receive a fixed quote after the scoping call.