GS1 Barcodes
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds GS1 barcode encoding to products and lots, so Odoo can generate GS1-128 and GS1-Datamatrix codes containing the product barcode, lot number and expiry date.
This module extends the GS1 barcode encoding capability to products and stock lots. It does not add new menus or screens; instead it makes existing product and lot records able to produce GS1-encoded values.
- For a product (
product.product), the encoding includes the product's barcode under the GS1 application identifier 01 (GTIN). - For a stock lot (
stock.production.lot), the encoding combines the product's values with the lot's own values: the lot name is added under identifier 10 (batch/lot number), and if the lot has an expiration date, it is added under identifier 17 (expiry date).
These encoded values are produced by the shared GS1 encoding mechanism inherited from the base_gs1_barcode module, which this module depends on. The module also depends on stock, so it works with inventory products and lots.
No automatic checks, restrictions, emails or scheduled jobs are added by this code. The module simply supplies the data mapping needed so that GS1 barcodes for products and lots can be generated by the underlying GS1 encoding tools.
Depends on
Models and fields (2)
- product.product · new model
- stock.production.lot · new model
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/stock-logistics-barcode.
terminal Installation and usage
OCA documentation · Odoo 14.0Usage
Source · Odoo 14.0You can use the functionality provided by this module in your own customization or other OCA modules.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.