This release is a pre-release and may not be stable for production use.
Generate Barcodes for Partners
This module expends Odoo functionality, allowing user to generate barcode depending on a given barcode rule for Partners.
For exemple, a typical pattern for partners is “042………” that means that: * the EAN13 code will begin by ‘042’ * followed by 0 digits (named Barcode Base in this module) * a 13 digit control
With this module, it is possible to:
Affect a pattern (barcode.rule) to a res.partner
- Define a Barcode base:
manually, if the base of the barcode must be set by a user. (typically an internal code defined in your company)
automaticaly by a sequence, if you want to let Odoo to increment a sequence. (typical case of a customer number incrementation)
Generate a barcode, based on the defined pattern and the barcode base
Configuration
To configure this module, see the ‘Configuration’ Section of the description of the module ‘barcodes_generator_abstract’
Usage
To use this module, you need to:
Go to a Product form (or a template form):
- 1 for manual generation
Set a Barcode Rule
Set a Barcode Base
click on the button ‘Generate Barcode (Using Barcode Rule)’
- 2 for automatic generation
Set a Barcode Rule
click on the button ‘Generate Base (Using Sequence)’
click on the button ‘Generate Barcode (Using Barcode Rule)’
Try this module on Runbot
Known issues / Roadmap
Dependency to point_of_sale is required because barcode field, defined in ‘base’ module (in the res.partner model), is defined in a ‘point_of_sale’ view.
It’s a relative problem, because barcodes generation for partners will occures mostly in a Point of Sale context, to give barcodes to customers.
You could comment ‘point_of_sale’ dependencies if you want to use this module without point of sale installed.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Credits
Images
Icon of the module is based on the Oxygen Team work and is under LGPL licence: http://www.iconarchive.com/show/oxygen-icons-by-oxygen-icons.org.html
Contributors
Sylvain LE GAL (https://twitter.com/legalsylvain)
Maintainer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit https://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo9-addon-barcodes-generator-partner 9.0.1.0.0.99.dev2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo9_addon_barcodes_generator_partner-9.0.1.0.0.99.dev2-py2-none-any.whl | Python 2 | none | any | Details for odoo9_addon_barcodes_generator_partner-9.0.1.0.0.99.dev2-py2-none-any.whl |
Release files / odoo9_addon_barcodes_generator_partner-9.0.1.0.0.99.dev2-py2-none-any.whl
| Download URL | odoo9_addon_barcodes_generator_partner-9.0.1.0.0.99.dev2-py2-none-any.whl |
|---|---|
| Size | 68.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
6703ee86ab7707eb96808ed0bf1812a387b46be74a736489a9584053c71405ae
|
|
BLAKE2b-256 checksum How to use checksums |
c22f16ee2dbddadb2e6864ab8022064d4364b93b7f1a4e09275573093bc591c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo9-addon-barcodes-generator-partner 9.0.1.0.0.99.dev2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
