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

Best module combination for maintenance of sold equipment

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

Avatar

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

by
InitOS GmbH, Pete Hahn
- 26/08/2020 10:09:28 
Dear all, thanks for all the input.

Am 26.08.20 um 09:52 schrieb Roussel, Denis:

> From my point of view and from near experience of customer of ours, we advise as some said to not change too much the Odoo base objects purpose as, along project life, you'll need to twist all the Odoo flows to adapt to your changes. 

That’s interesting, because that’s the main thing I am thinking about:
Which approach will break the most/need the most customization?

What flows do you think of exactly?

In my use case I only intend to add informative information to the
products, so my current impression is, that using products will give me
all the flows I need out of the box, while `stock.production.lot` will
be at least a bit cumbersome in the UI for users and need customizations
to make it work as expected for the user. (E.g. I think one would expect
the sold machine (lot) named on the invoice)


> As Graeme said, the lots are the good place to extend modelization for one product instance.
Ok. This seams to be somewhat common sence among the list.


Ok. I think I don’t need to bother you anymore but just make a decision.

So to get to more concrete question:
What could be possibly go wrong using product.product?
What do you expect to break?

The only thing I can think off that would be strange is, if they one day
decide to sell something completly different things too. Than all the
machine specific information won’t make much sense.

Reference