I am planning a new module to allow easy product pricing for tiered qty. This is technically possible using a Min Quantity, but the items still have to be priced individually.

In order to save some brainpower and keystrokes, I am thinking to add a price computation type to pricelists called "Tiered Price". It will mimic the operation of the "Fix Price" computation, except that the price will automatically be divided by the "Min Quantity" and apply appropriate rounding.

Following is an example:

• $5.00 for 30 units of X
  • 5/30 = .166666667 per unit with a min qty of 30 & rounding method of 0.01
• $7.00 for 60 units of X
  • 7/60 = .116666667 per unit with a min qty of 60 & rounding method of 0.01

Anyone have thoughts on this, or strategies/modules I am missing?

I was just planning this module for Medical, but realized this could apply to many other things. The intent is to provide specific handling for products that are deemed controlled in some way.

The context in medical is for drugs covered under the US Controlled Substances Act, but this would also boil over into systems such as the UN Classification of Controlled Drugs, Belgium Royal Decrees on narcotic/psychotropic substances, etc.

The context that this covers outside of drugs would be things like:

• Firearms sales (age requirement, background check, varies by country/state)
• Tobacco (age requirement, varies by country/state)
• Alcohol (age requirement, varies by country/state)
• Syringes (possible prescription needed, OTC limit, varies by state)

This specific module will only provide a core in product allowing for the storage of the regulatory information, and setting up the data models for a sale_control or similar which would provide the handling for the controls themselves when selling. To complement this could be something like a purchase_control allowing for specific handling on the purchase side of things. I'm open to discussing all of these here, as they will be relevant to the design of the core I think.

I'm thinking a fairly simplistic data model for the base, which would then allow for other modules to inherit and provide whatever context they actually need:

From there, the sale_ & purchase_ models would just add hooks into respective parts of the sale/purchase workflows. My current idea is to simply add some overrides into the methods (say action_confirm in a sale.order), then add a text column in the rule to dictate some sort of validation code to run. Something similar to partner_identification is what I see in my head.

I think the current plan lacks some elegance though. What would be nice is maybe leverage the Odoo workflows in some way. I'm a bit lost on workflows though, and the only example I know of is sale_automatic_workflow - which doesn't really help much conceptually.

Anyways, maybe someone has some pre-existing strategies or good ideas or something?

cc @LasLabs

Hi,

After installing product_gtin

I noticed that some barcodes do not work. As an example I used the following UPC-A barcode 623543740440

However the barcode is correct.

Changing the UPC-A barcode to an EAN13 format by adding a zero before the barcode work, but then I am no longer using a UPC-A barcode.

Looks to me like a bug.

Thanks for all you do.

Hi

I see a problem with the folder migration, see the screenshot
I think the problem come from Launchpad Migrations

Regards,

module: product_dimension
version: 8.0

Steps to reproduce

• ...

Current behavior

Expected behavior

Taking the hr_webcam module as a reference, I just created a new module called product_webcam in order to take pictures and store them into product table.

I created a pull request but I have some problems with coveralls check.
Where I can get any coveralls guide for passing the check ?

length field will require renaming as per underscore.js bug now linted in mqt.

Hi all,

Since v8 I've found this repo has become a combination of concepts. It's initial conception was for adding additional attributes (as in fields) to products, but with v8 and the renaming of dimensions to attributes it was the effective obsolescence of product_variant_multi and therefore the product-variant repo.

I've been working hard to supplement the old features of product_variant_multi a module I've been very active in since v5 and modernise to the current variants way of doing things.

Plus I've been modernising and open sourcing a lot of old internal code that deals with variants and still more to come giving OCA what I think are some pretty awesome variant features.

I propose that we move those modules which deal just with the control, management and enhancement of variants and variant creation into the product-variant repo.

As a minimum I'd expect this to include (with current PR's)
product_combination_exclude #255
product_attribute_group #254
product_code_builder #244, #204
product_attribute_priority #244, #204
product_attribute_multi_type (I don't know much of this module)

arguably product_price_on_variant although IMO might be time to remove this module as it's pretty well handled now in other ways.

In addition I'm working on a few other modules, such as the establishment of a product_manager role which manages products and reorganizes related menus, variant pricing manager and an all encompassing app which basically installs most of these modules for organizations that need serious variant management.

expected interested parties
@pedrobaeza chief reviewer :) and variant work in odoomrp
@jgrandguillaume PSC

Akretion Team - longtime pvm contributors
@bealdav
@alexis-via
@rvalyi
@bguillot

@lmignon current PR's

Apologies to anyone I've missed, or anyone who doesn't want to know and has been included.

After i reviewed product_brand module, i wish you add product_brand_id to sales analysis dashboard or i wish you tell me how can i do that by myself because it's asked from me.
Thanks

Hi,

I've got back into dev hard core and looking at variants on v10. They are still weak and nowhere near v7 product variant multi. However I can live with it and was looking at how we might do default code generation.

In the past its been with a code generator field stored on the template with a custom parsing algorithm. Something like TEST[o.variant_code]. As a POC, I've had a look at doing this in a wizard instead. The concept is essentially the same except it uses jinja2 for parsing in a SandBoxed environment.

The code is here: https://github.com/gdgellatly/odoo_bug_demos/blob/master/product_variant_extended/models/simple_variant_product_code.py

Interested in thoughts on this approach vs storing on template (it really is no effort to store on template either, just did wizard as I didn't want model change)

EDIT: I just noted product_code_builder module. Is funny, is almost a copy of my POC so will actively port that, with any feedback.

This module will provide ratings for products by using the rating module provided by Odoo (v10) core. It will add rating to product.product, with another computed rating on the product.template containing an aggregate rating for the variants.

It will add a new model product.rating will be created that will allow for the abstract scheduling of product rating requests. This will allow for the module to be used in all contexts of a product (sales, purchases, etc), without requiring glue modules. The model will allow for the choice of:

• Model to act on
• Domain filter for matching records that should have a rating requested (similar to the way server actions work)
• Email template used for ratings requests
• product_field_id - This is the field on the record for the product that is being rated
• rater_field_id - This will set the rating.rating.partner_id to the value of this field. The rating request email will be sent to this partner's email.
• rated_partner_field_id - if defined, this will set the rating.rating.rated_partner_id to the value of this field

A scheduled task will be added that will iterate the active product.rating records, search the model for the defined domain, then send the defined email to the rater.

If a partner has already rated the product variant, they will be ignored from this task. On that same note, a partner should not be able to rate the same product variant twice. They should, however, be able to rate two different product variants of the same template - because they are technically different products.

Plan seems simple enough IMO. Anyone know of some pre-existing code/strategies, or see a hole in the plan?

This field has been replaced in odoo with barcode but I need both since our customer has internal code (default code = barcode) and an external code (to be used in Prestashop and other external services) that should be just a valid ean13.
Is there any module that add it back? I cannot find anything in this repo.
If no module is ready I can submit one here, if anyone is interested.

Can I easily add product.brand.name/id as a group selector in report.pos.order?

Any help appreciated.

module: product_sequence
version: 8.0

Steps to reproduce

• Install Module
  Uninstall Module

Current behavior
sql constraint of uniq default code is added to the product_product_default_code table upon installation.
this sql constraint doesn't gets removed upon uninstallation.

Expected behavior
Either module should work without sql constraint or else upon uninstallation the constraint should be removed.

I've been working on building a module to achieve the functionality of product_customer_code, however I have just come across this module and it looks like it achieves what I aimed to achieve with my own module.

I'd like to know if there is any roadmap for porting this particular module to 8.0 as if there are plans to port it soon I will wait until the module is ported to 8.0 according to OCA standards.

If there are no plans from OCA to port the module in the near future I will begin work on porting the module to 8.0 myself and would be happy to submit pull requests once i'm done if community involvement outside OCA is wanted. If this is the case is there anywhere I can find a list of OCA requirements for submission so that I can try to match these requirements before submitting pull requests?

Product Brand does not work with Version 9 Enterprise, will not complete the install

module: product_multi_category
version: 9.0

Steps to reproduce

• Download the module. Unzip contents into the [odoo_path]/addons/ directory.

Current behavior
Not able to see the module in my install-able app list in my OdooErp.

Expected behavior
Module show up on the Apps list and be able to install this module into my OdooErp or able to add multiple categories on a product.

Sorry, if the question is too simple. I couldn't find a instructions so far.

Thanks, for your help :D

I've just come across an issue with Product Brand in Odoo 9 (CE).

Steps to reproduce:

1. upload a large picture as a brand image
2. view kanban view in Sales >> Product Brand

Expected Behaviour:
Logo is resized to the width of the kanban container as a thumbnail or small image.

Hello,

I'm trying the product_gtin module and work very well. But I see that need an improvement. The point of sale only read EAN13, so we can put new barcodes but it can be used in the point of sale. Is someone working in this?

Greetings

module: product_brand
version: 8.0

Steps to reproduce

• ...

Current behavior
Currently Product Brand Module Having the Logic for View the Following criteria on more options.

1. see the product wise brand (using more options)
2. see the brand wise product (using more options)

Active Window is exist but scr_model is not exist any more so that more options is right now disable.

Expected behavior

Add a new src_model attribute on active window (.xml file) for see the product wise brands and brand wise products.

so that the more options will enable for product brand and product model.

source:
https://apps.odoo.com/web/login?redirect=/loempia/download/product_brand/8.0.0.1.0/6jQofx0RPRonf60kvPkAP5.zip?deps

In the onchange function of the field base_ext, the id of the current object is set to newId.
I put a breakpoint in my code to find the error and noticed the following:

Because of this, when setting the base_ext to fixed price, the field 'other pricelist' is still required and visible.
Note: this only happens when adding an item starting from product.pricelist, then selecting the product.pricelist.version and then adding a new product.pricelist.item.
This does not happen when opening the product.pricelist.version directly and adding a new pricelist item.

After running upgrade I get this error:

openerp.sql_db: bad query: INSERT INTO "ir_sequence_type" ("id", "code", "name", "create_uid", "write_uid", "create_date", "write_date") VALUES(nextval('ir_sequence_type_id_seq'), 'product.product', 'Product', 1, 1, (now() at time zone 'UTC'), (now() at time zone 'UTC')) RETURNING id
Traceback (most recent call last):
File "/opt/odoo/odoo-server/openerp/sql_db.py", line 234, in execute
res = self._obj.execute(query, params)
IntegrityError: duplicate key value violates unique constraint "ir_sequence_type_code_unique"
DETAIL: Key (code)=(product.product) already exists.

ParseError: "duplicate key value violates unique constraint "ir_sequence_type_code_unique"
DETAIL: Key (code)=(product.product) already exists.
" while parsing /opt/odoo/custom/addons/product_sequence/data/product_sequence.xml:5, near

Product
product.product

From a client's request, I'm working on a module to add product features in a particular way:

• Features and products have a M2M relation.
• If a template has a feature, all products inherit with exactly the same value.
• A feature has an image and an alt text.

I've seen a similar development somewhere but can't find it now, so I'm starting from scratch, defining a new model.

Is this the right repo to make a PR when I'm done? Should I use some existing model? Product attributes don't fit the purpose, because all variants have the same features as the template. Product categories could do the deed, but they are not meant for this purpose and using them seems confusing.

The following errors occurs when selecting fixed price:
Odoo Server Error

Traceback (most recent call last):
File "/home/odoivlprd80/odoo/parts/odoo/openerp/http.py", line 537, in _handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/http.py", line 574, in dispatch
result = self._call_function(*_self.params)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/http.py", line 310, in _call_function
return checked_call(self.db, *args, *_kwargs)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/service/model.py", line 118, in wrapper
return f(dbname, _args, *_kwargs)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/http.py", line 307, in checked_call
return self.endpoint(_a, *_kw)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/http.py", line 803, in call
return self.method(_args, *_kw)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/http.py", line 403, in response_wrap
response = f(_args, *_kw)
File "/home/odoivlprd80/odoo/parts/odoo/addons/web/controllers/main.py", line 944, in call_kw
return self._call_kw(model, method, args, kwargs)
File "/home/odoivlprd80/odoo/parts/odoo/addons/web/controllers/main.py", line 936, in _call_kw
return getattr(request.registry.get(model), method)(request.cr, request.uid, _args, *_kwargs)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/api.py", line 256, in wrapper
return old_api(self, _args, *_kwargs)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/api.py", line 387, in old_api
result = method(recs, _args, *_kwargs)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/models.py", line 5957, in onchange
record._onchange_eval(name, field_onchange[name], result)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/models.py", line 5815, in _onchange_eval
method_res = method(self)
File "/home/odoivlprd80/odoo/parts/product_attribute/product_pricelist_fixed_price/model/product_pricelist_item.py", line 48, in change_base_ext
self.base = base[0]
File "/home/odoivlprd80/odoo/parts/odoo/openerp/fields.py", line 835, in set
value = self.convert_to_cache(value, record)
File "/home/odoivlprd80/odoo/parts/odoo/openerp/fields.py", line 1404, in convert_to_cache
raise ValueError("Wrong value for %s: %r" % (self, value))
ValueError: Wrong value for product.pricelist.item.base: product.price.type(1,)

I received a port from someone. The person who did the coding can't manage to do a PR so I will provide the port from her in a PR from my fork of OCA/product-attribute shortly

Dear All! I would like to request a new feature:

I would like to inventory and manufacture agricultural products. Lets say grain. The products I sell does not have a default weight it varies according the sale order.

My idea for solving this, but correct me if there is a better way: if I set the Unit Of Measure of a product to kg »»» odoo should automatically calculate the weight (kg) of the quoted volume.

domain filter doesn't work in other languages than English.

https://github.com/OCA/product-attribute/blob/9.0/product_dimension/product.py#L51

maybe a boolean field in product.category and changing domain would be the solution...

I'm very busy to fix, test and make a PR but something like this might work:

class ProductUomCateg(models.Model):
_inherit = 'product.uom.categ'
is_lenght = fields.Boolean()

    <record id="product.product product_uom_categ_vol" model="product.uom.categ">
        <field name="is_length" eval="True"/>
    </record>

dimensional_uom_id = fields.Many2one(
    'product.uom',
    'Dimensional UoM',
    domain="[('category_id.is_lenght ', '=', True)]",
    help='UoM for length, height, width')

-mkdir /opt/odoo/custom/addons
-cd "/opt/odoo/custom/addons"
-git clone https://github.com/OCA/product_attribute --branch 8.0 [Error 1]

[Error 1]
remote: Repository not found.
fatal: repository 'https://github.com/OCA/product_attribute/' not found
[Error 1]

-git clone https://github.com/OCA/product-attribute --branch 8.0 [Error 1 Fixed]
-sudo nano /etc/odoo/openerp-server.conf
(add) /opt/odoo/custom/addons/product-attribute
(save and exit with "ctrl + x", press "y", and "Enter")
-reboot

Go to your odoo, login, configuration, update module list(if this option is not visible, turn on technical features)

[Error 2]

Odoo Server Error

Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 539, in _handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 576, in dispatch
result = self._call_function(*_self.params)
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 312, in _call_function
return checked_call(self.db, *args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/service/model.py", line 118, in wrapper
return f(dbname, _args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 309, in checked_call
return self.endpoint(_a, *_kw)
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 805, in call
return self.method(_args, *_kw)
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 405, in response_wrap
response = f(_args, *_kw)
File "/usr/lib/python2.7/dist-packages/openerp/addons/web/controllers/main.py", line 948, in call_button
action = self._call_kw(model, method, args, {})
File "/usr/lib/python2.7/dist-packages/openerp/addons/web/controllers/main.py", line 936, in _call_kw
return getattr(request.registry.get(model), method)(request.cr, request.uid, _args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/api.py", line 268, in wrapper
return old_api(self, _args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/api.py", line 439, in old_api
result = new_api(recs, _args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/api.py", line 443, in new_api
result = [method(rec, _args, *_kwargs) for rec in self]
File "/usr/lib/python2.7/dist-packages/openerp/addons/base/module/wizard/base_module_update.py", line 15, in update_module
self.updated, self.added = self.env['ir.module.module'].update_list()
File "/usr/lib/python2.7/dist-packages/openerp/api.py", line 266, in wrapper
return new_api(self, _args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/api.py", line 508, in new_api
result = method(self._model, cr, uid, _args, *_old_kwargs)
File "/usr/lib/python2.7/dist-packages/openerp/addons/base/module/module.py", line 651, in update_list
handler.load_addons()
File "/usr/lib/python2.7/dist-packages/openerp/http.py", line 1312, in load_addons
m = import('openerp.addons.' + module)
File "/usr/lib/python2.7/dist-packages/openerp/modules/module.py", line 80, in load_module
mod = imp.load_module('openerp.addons.' + module_part, f, path, descr)
File "/opt/odoo/custom/addons/product-attribute/product_multi_image/init.py", line 7, in
from . import models
ImportError: cannot import name models

[Error 2]

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0

Modules to migrate

• base_custom_attributes : deprecated in 9.0 branch in favor of product_custom_info
• customer_context_in_product_view
• partner_custom_attributes
• product_attribute_multi_type
• product_brand - by @loxamir #191
• product_catalog_report
• product_categ_attributes
• product_custom_attributes
• product_custom_info - By @fanha99
• product_customer_code - By @PCatinean - #236 Deprecated for product_supplierinfo_for_customer
• product_dimension - By @gurneyalex #195 By @thomaspaulb - #491
• product_electronic
• product_gift
• product_gtin
• product_icecat
• product_index
• product_listprice_upgrade
• product_lot_foundry
• product_manufacturer - By @bistaray - #188
• product_multi_category - By @angelmoya - #242
• product_multi_price
• product_pricelist_fixed_price
• product_prices_on_variant
• product_qt
• product_quick_stock_rule
• product_search_reference
• product_sequence - by @SodexisTeam #194
• product_series
• product_size
• product_supplierinfo_tree_price_info Not needed anymore as the structure has changed.
• product_supplierinfo_for_customer - @aheficent - #292
• product_supplierinfo_for_customer_sale - @aheficent #280 (comment)
• product_uom - By @lasley - #213
• product_weight
• production_lot_custom_attributes

I propose to remove product-attribute/product_multi_company since it's unported from version 6.1

it would be great to have product_brands attribute related in purchase.order (.line) view also to search and select products from brand and name...

Any chance to have it implemented in search logic of that field?

This module will add the concept of a service user_id and duration on product.template.

The intent is to allow for the creation of services that are (optionally) performed by a certain user & have a standard duration in minutes.

The specific need on my end is to use as part of Physician scheduling functionality, pairing with the calendar module to allow selection of the service that is going to be performed (office visit, etc) in order to default a time block size and optional user.

This seems useful in a lot of other cases though; basically any form of job scheduling where X units takes Y minutes of time.

Assuming I'm not missing some strategy that already exists for this, am I also in the right repo?

module: product_profile
version: 1.0
branch 8.0

Steps to reproduce

• With the fields for profile_default_route_ids incorporated into the code, no routes are showing up on the product profile screen. Here's the code I have in my product.py for the product_profile_example module (which I modified)

`
from openerp import models, fields

class ProductProfile(models.Model):
_inherit = 'product.profile'

def _get_types(self):
    return [('product', 'Stockable Product'),
            ('consu', 'Consumable'),
            ('service', 'Service')]

profile_default_categ_id = fields.Many2one(
    'product.category',
    string='Default category')
profile_default_is_landed_ok = fields.Boolean(
    string='Landed Cost Product?')    
profile_default_sale_ok = fields.Boolean(
    string='Can be Sold',
    help="Specify if the product can be selected in a sales order line.")
profile_default_hr_expense_ok = fields.Boolean(
    string='Can be Expensed',
    help="Specify if the product can be selected in an expense report.")
profile_default_purchase_ok = fields.Boolean(
    string='Can be Purchased')
profile_default_route_ids = fields.Many2many(
    'stock.location.route',
    domain="[('product_selectable', '=', True)]",
    widget="many2many_checkboxes",
    string='Routes',
    help="Depending on the modules installed, this will allow "
         "you to define the route of the product: "
         "whether it will be bought, manufactured, MTO/MTS,...")
profile_default_uom_id = fields.Many2one(
    'product.uom',
    string='Unit of Measure')
cost_method = fields.Selection(
    string='Costing Method',
    selection=[('standard', 'Standard Price'), ('average', 'Average Price'), ('real', 'Real Price')])
profile_default_standard_price = fields.Float(
    string='Cost Price')
valuation = fields.Selection(
    string='Inventory Valuation',
    selection=[('manual_periodic', 'Periodical (manual)'),('real_time', 'Real Time (automated)')])
`

Current behavior
The profile_default_route_ids doesn't cause the routes to be selectable in the product profiles screen. Shown in this screenshot:

But the routes are definitely selectable on the new product screen. Shown here:

Am I missing something?
Thanks!!!

I am curious whether the modules below can be used with product_gtin

product_multi_ean
stock_inventory_barcode

https://github.com/OCA/stock-logistics-barcode/tree/8.0/product_multi_ean
https://github.com/OCA/stock-logistics-barcode/tree/8.0/stock_inventory_barcode
https://github.com/OCA/stock-logistics-barcode/tree/8.0

Thanks for your input.

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Modules to migrate

• base_custom_attributes - To be removed
• customer_context_in_product_view
• partner_custom_attributes - To be removed
• pricelist_per_product - By @BMW95 - #189
• product_attribute_multi_type - To be removed
• product_brand - PR #128
• product_catalog_report
• product_custom_attributes - It should be removed as we have product_custom_info
• product_gift
• product_categ_attributes
• product_custom_info - By @yajo - #177
• product_customer_code
• product_electronic
• product_gtin - #132
• product_dimension - By @leemannd - #159
• product_icecat
• product_index
• product_listprice_upgrade
• product_lot_foundry
• product_manufacturer - By @komsas - #152
• product_m2mcategories - Renamed to product_multi_category by @SodexisTeam - #139
• product_multi_company
• product_multi_image - By @SodexisTeam - #161 By @lasley - #199
• product_multi_price
• product_pricelist_fixed_price
• product_prices_on_variant
• product_qt
• product_quick_stock_rule
• product_size
• product_search_reference
• product_sequence - PR #109
• product_series
• product_standard_price_tax_included
• product_supplierinfo_for_customer - By @aheficent - #287
• product_supplierinfo_tree_price_info - To be removed as now there's not 2 levels of supplierinfo
• product_weight
• production_lot_custom_attributes

Context:

• v9
• template with no images, variant with no images

Issue:
If you add an image to a variant:

  File "/opt/odoo/external-src/product-attribute/product_multi_image/models/product_product.py", line 44, in _inverse_main_image_medium
    product._inverse_main_image(product.image_main_medium)
  File "/opt/odoo/src/openerp/api.py", line 248, in wrapper
    return new_api(self, *args, **kwargs)
  File "/opt/odoo/external-src/product-attribute/product_multi_image/models/product_product.py", line 29, in _inverse_main_image
    product.image_ids[0].write({
  File "/opt/odoo/src/openerp/models.py", line 5756, in __getitem__
    return self._browse(self.env, (self._ids[key],))
IndexError: tuple index out of range

We miss a safe check here https://github.com/OCA/product-attribute/blob/9.0/product_multi_image/models/product_product.py#L28

We created a module in vertical-medical that provides a concept of storage instructions for medicaments (products).

The module is rudimentary at this point, simply providing a M2M on to relate storage instructions to specific products.

In our v10 iteration we are planning to add a glue module for stock, which would add a concept of the storage possibilities of specific warehouse/bins.

In the existing module, we are also looking into a concept of storage time as part of the instructions, as well as a field allowing abstract validation (similar to partner_identification).

Our medicaments are _inherits of products, so it would be very easy to move this logic up a layer if there is interest.

Product storage is likely something other industries deal with, so I was seeing if there was any interest in this (or if some other strategies exist) before we go further.

Certified labels like "organic", 'fair-trade", controlled origin appellations etc. impose a few requirements to companies.

• the labels must be clearly indicated on the customer invoices, along with the name/code of the certification organization
• stock, receipts, deliveries, manufacturing and invoices must be auditable, to prove that the rules of the certification are respected.

It would be useful if OCA proposed at least a basic support for this feature.

Hi, I'm finishing the migration product_images to 8.0, so I put this issue for anyone looking for this module or that wants to start a new task, don't do it.

There is a bug preventing product_brand to be installed. Funny part is that I saw it installing in some cases, but in general, it's failing. Both on fresh DB and on a DB with other modules.

The error is:
`
..... exception stack trace upper part ....

  File "/Users/kani/odoo/odoo/openerp/models.py", line 1271, in _validate_fields
    raise ValidationError('\n'.join(errors))
ParseError: "Invalid view definition

Error details:
View inheritance may not use attribute 'string' as a selector.

Error context:
View `product.search.form`
[view_id: 991, xml_id: n/a, model: product.product, parent_id: 280]
None" while parsing /Users/kani/odoo/OCA-addons/product_brand/product_brand_view.xml:132, near
<record id="product_search_form_view" model="ir.ui.view">
            <field name="name">product.search.form</field>
            <field name="model">product.product</field>
            <field name="inherit_id" ref="product.product_search_form_view"/>
            <field name="arch" type="xml">
                <data><field name="categ_id" position="after">
                    <field name="product_brand_id"/>
                </field>
                <group string="Group by..." position="inside">
                    <filter string="Brand" name="groupby_brand" domain="[]" context="{'group_by' : 'product_brand_id'}"/>
                </group>
            </data></field>
        </record>

module: product_dimension
version: 9.0

Steps to reproduce

• Install module
• Create a new product template with dimension
• Save the product
• Check the dimension

Current behavior

Product dimension are not saved for product template

Expected behavior

Product dimension should be saved for product template

Reason

Product template use related fields for dimension (width, height, ...) that are bind to product.product ; during record creation related field are not persist.

When update a record, everything work as expected.

Since commit 076022b ean code with a len of 11 et 14 are no more valided using the checksum method

This is a fairly simple module that will provide a default image for products, similar to the partner avatars. This image will be configurable on both a global & a product category level.

A view will be added in the Product Configuration menu, which will allow for the configuration of the images and the categories.

The create method of product.template will be overridden. If the image key is not present, the default image will be generated based on category or global.

Anyone have any thoughts or pre-existing strategies/modules that we can base from?

Transifex is failing for this repo on the 9.0 branch.

If I'm reading these results correctly, it's failing on demo data inside of core Odoo.

@AngelMoya-Domatix

Product Sequence is causing tests on this repo to fail test. It sets a static default and then a unique constraint.

Moreover I don't understand quite why it is done this way. Could we not just use copy=False, default= and remove all the methods entirely? This would number all existing products automatically and ensure duplicates were given a new number.

Hello,

Since version 8, I see a recurrent issue for customers with big database, the native product template form view, with all the smarts button sometimes take a very long time to load. (at least for version 8 and 9)
The problem comes from the computation of fields sales_count, purchase_count and mo_count.

I think it would be greate to have 3 small modules to fix this performance issue for version 10 and I would like the opinion of the community on this.

So far, 3 potential solutions :

1. Simply replace the native logic by an sql query (nice performance improvement)

2. Store the value of these field, and delay computation (using queue_job). It should work well, but it seems a bit too much, to have to install queue_job module just to improve some performance...

3. A very nice feature to have (but I do not know if it is possible, that's why I ask the Community) would be that Odoo compute the field value, only if the user pass the mouse on the smart button.
   Indeed, most of the time, the user don't need these count information when opening the form view, so it would a lot better if this information would be computed on demand.

Obivously, the first solution is the easiest.
Feel free to share any idea on the subject!

"The reference must be unique" ,The translation becomes invalid in other languages,
#. module: product_sequence #: sql_constraint:product.product:0 msgid "The reference must be unique" msgstr "内部编号必须唯一"

This module will allow for the assigning of products to specific companies, which doesn't look to be a thing at the moment. There is a company_id on product, but I don't see it actually doing anything.

With that in mind, this module will add a restrict_company_ids to product.template. It will default to all companies that exist, in order to not change the operation of existing products.

An ACL will be added to restrict products a user can see, based on their company_id against the restrict_company_ids.

Plan seems simple enough, I'm just wondering if anything like this exists already. I feel like this is a problem that anyone using multi-company would be experiencing, so I think maybe I'm missing something.

@pedrobaeza ,

I'm planning on creating a new module for my own use and would like to know if a PR would be accepted to the OCA for an extension on the product_customer_code module to add customer barcodes in multiple formats.

The extra fields added to extend product_customer code would be:

• barcode type/format (eg. EAN13, UPC-A, etc.)
• barcode value (eg. EAN13 code)
• customer product name (eg. this is used when customers require use of their own product name or language to describe the product.)

Before I start writing it i'd like to know if the OCA has any use for this module, and whether any additional features/fields should be added, and which repository I should target before a PR is made.

For these features I would assume I should create one module purely for the barcode features, and one module for the customer's product name, for example:

product_customer_barcode
product_customer_name