1. Mailing Lists
  2. Contributors
  3. Re: Awnings dimensions app

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

RE: Awnings dimensions app

Re: Awnings dimensions app

Avatar

Re: Awnings dimensions app

by
joel.patrick
- 12/12/2024 15:34:40
If they do not want to go live without it, you should workshop to make them construct the budget for multiple awning contracts using standard Odoo, and develop a price for the "Configurator".  Make sure you allow for multiple rewrites.It is really a good job for Excel with a structured handoff to Odoo.  You should have a good estimate of fabric and a degree of difficulty (simple, average, above average, very hard awning design) as a way of budgeting for the rest.  Put the logic in Excel that a company subject-matter expert owns and define the hand-offs in terms of the product defs and BOMs.  KEEP IT SIMPLE, SIMPLE, SIMPLE as possible. And if you can, do not do it because you will have many other things more important to a good project.

I have seen companies spend millions trying to put a product configurator into the ERP (SAP) only to find that they lost all flexibility in their business processes. If you can get the job done with an Excel spreadsheet, I would want to call that "Phase 1 Complete" and come back to it a year from now.  You may find they never ask for it again.

One important guideline is to avoid making anything that is more complicated than what your company does today, at least until they know Odoo and can help design it.

On Thu, Dec 12, 2024 at 8:42 AM Adam Heinz <notifications@odoo-community.org> wrote:
On Thu, Dec 12, 2024 at 5:53 AM Graeme Gellatly <notifications@odoo-community.org> wrote:
For the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.

Our manufacturers price their products in size buckets as you describe above, but we order bespoke products with precise measurements.
 
Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :

Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.

Have you experimented with the sale_product_configurator module and the product.attribute.custom.value model?

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

Reference