1. Mailing Lists
  2. Contributors
  3. Re: Best model for selling unique products (used machines)

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Best model for selling unique products (used machines)

Re: Best model for selling unique products (used machines)

Avatar

Re: Best model for selling unique products (used machines)

by
dygytally.de GmbH, Bettina Pfeifer.
- 24/08/2020 15:22:17

Hi Peter,

sometimes it helps to imagine what you (your future odoo client) want to know after one, two, three ... years of sales. What would you like to know about all your sales, the products you sold. Which ones made trouble after sales, which ones made your odoo client happy, which ones led to more trades, which ones where hard to get and easy to sell or vice versa. Which ones need a lot of warehouse space, which ones need special care. How do you want to report on the past. What decisions should be made for the future.

Maybe this helps a bit to decide on your current question. Sometimes these questions make the odoo client reveal their true needs.

And if you are able to generate the "list" you mention, that might be good starting point.

And the original serial numbers of the used machines themselves should be used, as long as they have one. Otherwise you could create an own serial number.  

In general, why not start as easy as possible, until other requirements arise while using odoo.

Regards, Bettina


dygytally.de GmbH
Margarete-Steiff-Str. 7
60438 Frankfurt am Main

mobil +49 170 5423 951
WhatsApp +49 175 1042428
Tel +49 69 758 44766
Fax +49 69 758 44767 		Geschäftsführerin: Bettina Pfeifer

Handelsregister: Frankfurt HRB 106317


dygytally.de
Einfach. Digital. Wachsen.
-- Odoo Ready Partner --		 Website
Kontakt
Impressum
Datenschutz



© 2019 dygytally.de
Am 24.08.20 um 13:17 schrieb Peter Hahn:
Hi David,

thanks for your suggestion. I didn’t knew the module.

I’m still not really convinced using serial numbers is the right thing
here in general.
Sure it would be for smart phones and stuff like this, but I would
really like to hear opinions about what problems may arise in case of
just using `product.product`.

At first glance this seams to be way more simple. Especially I think
it’s intuitive for the users because in their business mindset they
don’t think of _machines_ and _instances of machines_ but just a
specific _machine_ from their list.

Our use case to me looks more like being the base machine a
`product.template` and the unique machine a `product.product`.

However I wouldn’t use all the `product.attribute` machinery  for this,
of course.

I hope to hear more opinions from the list about this.

Thanks. Regards, Peter



Am 21.08.20 um 17:02 schrieb David Beal:

> Hi Peter,

> Consider these modules

> https://github.com/OCA/sale-workflow/tree/12.0/sale_order_lot_selection [1]  https://github.com/OCA/sale-workflow/tree/12.0/sale_order_lot_generator [2]

> and in pending migration

> https://github.com/OCA/sale-workflow/pull/1144 [3]

> Note that sale_order_lot_selection in v12 and v13 are different, consider the v12 one

> Best regards

> 

> David BEAL - akretion.com [4]  Consultant

> Odoo Intégration / Développement

> Le ven. 21 août 2020 à 15:36, Peter Hahn < peter.hahn@initos.com [5] > a écrit :

> Hello,

> I have a hard time to decide which Odoo model to use for selling unique

> products.

> The products are used machines. So in general one could think of a

> generic product with manufacturer and model and a certain instance of it.

> But since these are used items, they come with a lot of customizations

> and other instance specific attributes like operation hours etc.

> So it’s more like the product == instance.

> We thought about using `product.product` for the brand/model and

> `stock.production.lot` for the instance, but after some research in the

> odoo v12 code I'm not sure if this is really the best option.

> To me it looks like `stock.production.lot` is more about tractability of

> instance of generic products **after** they have been sold, since

> `stock.production.lot` is very tightly tied to stock operations.

> We need to have product instances already during the whole CRM, Quote,

> SaleOrder process. I don’t see how to easily put `stock.production.lot`

> on `sale.order.lines`.

> The other option would be just going for `product.product` and assume

> product == product instance.

> I’m not really sure about benefits/drawbacks or maybe other/better

> approaches.

> 

> Please give me your opinions about what model is best to use as a base

> for selling unique items in odoo.

> Thanks. Regards, Peter

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [6]

> Post to: mailto: contributors@odoo-community.org [7]

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [8]

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [9]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [10]

> 

> 

> 

> [1] https://github.com/OCA/sale-workflow/tree/12.0/sale_order_lot_selection

> [2] https://github.com/OCA/sale-workflow/tree/12.0/sale_order_lot_generator

> [3] https://github.com/OCA/sale-workflow/pull/1144

> [4] http://akretion.com

> [5] mailto:peter.hahn@initos.com

> [6] https://odoo-community.org/groups/contributors-15

> [7] mailto:contributors@odoo-community.org

> [8] https://odoo-community.org/groups?unsubscribe

> [9] https://odoo-community.org/groups/contributors-15

> [10] https://odoo-community.org/groups?unsubscribe

>

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference