Define in product configuration, the field to be used as barcode for product. This can be one of the following:
One specific Type of Identifier.
Also we should define the desired Barcode format, which should be one of the implemented in Barcode Reports
Once the user selects such configuration we can have a libreoffice template which prints the product name and barcode. The report can be printed directly from products or from variants, so users with single product do not need to open the variant action.
Print the EAN code to a product to be able to scan it latter.
Sorry but I do not understand what do you understand. Could you please clarify?
I think we can have a small barcode format. Probably just 4cms width. One may adjust the format if needed.
Because users just need to pick the desired configuration and they will have a barcode with a sample format.
From there they can just adjust the template to their needs.
Otherwise they won’t know which functions they need to call nor which fields to use (sometimes even they won’t know how to create the report).
Sorry but I do not not understand. What do you mean about product packaging?
No you just need to setup which code to use and format.
Any better proposal?
Better to have an ERP to adapt than create a new one from scratch, no?
Then why we have standard templates for invoices/sales if they need to adapt them?
Why do you say its broken? I just want to have something flexible that may work on more case.
Do you mean that are report templates are broken? Because we are adapting them for every instalation we do as they do not fix the user needs.
Still in my learning period. Reading this thread befor making my own opinion.
My point was about standard Tryton installation with no service. A generic view-point, but probably not an answer to what you proposed.
I like the idea of a general configuration for representing product barcodes. But IMHO an implementation based on save _eval which could allow all product fields could be more sufficient, as there are
Also as an additional functionality, matching could be user definable, as
But I can’t see a good general implementation for a report for now. Your idea
reminds me too much of the party label report. It was implemented for printing address labels for parties.
But IMHO the using on special labelling paper with self-adhesive stickers (Avery, Zweckform,…) is very limited, because the vertical size of a label is variable and defined by the label text and a waste of resources, as a management for empty labels on a page is missing… Serial label printer with endless stickers are also not supported, as these printers usually work very different (ZPL2, ESC-P, …). So the party labels can be printed on plain paper, cut with scissors and glued manually… but for cutting there are crop marks missing and the result is limited in use… So we don’t use the party label report in any of our projects and deactivate it.
OTOH it would be excellent if Tryton supports the users, to use barcodes in their own custom Product/Party Label reports.
For this it would be very helpful if Tryton provides a field or property with the bar code binary data.
Indeed barcodes can be also generated and shown on forms using binary widgets.
I always thought that is a good idea to show them on the user interface to let users aware that they can create a custom report for printing them.