The problem this app solves

The same product may arrive with a supplier code, an older label or a packaging barcode. A single code is not always enough for the way teams receive, search and sell the item, but ambiguous aliases can lead to choosing the wrong product.

Maintain variant-specific aliases and use supported lookup and scanning workflows to resolve them predictably. Explicit uniqueness and packaging rules distinguish a product identity from a pack quantity, while inactive aliases can remain in the history.

Features that support your daily work

• Flexible alias records. Maintain unlimited active or inactive aliases by product variant, with useful types such as supplier, legacy, packaging, and custom.
• Reliable matching. Normalize supported barcode representations and resolve backend searches through a clear, deterministic lookup.
• Conflict control. Apply a global or company-level uniqueness policy and show a clear conflict instead of selecting an arbitrary product.
• Packaging support. Store packaging quantity and unit of measure without confusing a packaging code with a product identity code.
• POS bridge. When Point of Sale is installed, the included bridge supports alternate-code search and scan resolution.
• Import and export. Import and export aliases with duplicate preview and correction files for rejected rows.

A practical example

Illustrative workflow — the available actions depend on your configuration.

A supplier changes the code printed on a product. The administrator adds the new alias to the existing variant, checks for conflicts and retains the older alias where needed. Supported searches can then identify the same product from either active code.

Manage conflicts before codes reach daily operations

Use Barcode Aliases and Barcode Alias Types in Inventory to maintain alternate identifiers. Per-company uniqueness is the default; review conflicts before changing to global uniqueness. A product smart button keeps its aliases accessible from the product record.

Conflict and coverage views help administrators review the catalog, and failed import rows can be downloaded as correction CSV/XLSX files. These are alias-management and coverage tools; the module does not include a separate PDF report.

How it works

Add aliases: Create them manually or import a prepared file.

Resolve conflicts: Review duplicate codes before they affect operations.

Search or scan: Use alternate codes in supported Odoo workflows.

Maintain history: Deactivate old codes without losing the record.

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

Alias list with product, type, quantity, and status. Supplier alias form with code history. Product form with linked barcode aliases. Packaging alias with an explicit quantity. Conflict list showing candidate products. Conflict resolution before a manager decision. Import preview with correction options. Coverage and usage reporting by product.

Compatibility

Odoo: 15.0

Required native app: stock

Optional integration: point_of_sale

Supported editions: Community and Enterprise where the declared dependencies are available.

Odoo Online: not supported. This release is a standard server-side Odoo module.