Archives
Contributors
purchasing a set of products
Hi! We have several products which we purchase together. For example some laptops are purchased together with RAM and a SSD, but which are separate products for us in Odoo. I can't expect from our purchase department to remember all the components. To make purchasing error prone and easy, we configured a laptop *kit* which BOM contains a laptop *barebone*, RAM, SSD. So our purchase department can simply buy the laptop kit and don't need to remember which components are included in which product. In general this setup works but it has the following shortcomings: The reordering rules need to be configured for the barebone product. Once the minimum amount is reached a PO will be created automatically. The purchase department needs to remember to replace the barebone laptop with the barebone kit. Obviously deactivating "Can be Purchased" can't be applied here. We support this by stating "DON'T BUY" in the product barebone's name. Generally, the amount of products and BOMs is doubling, increasing the overall complexity. Do you have any better idea how to deal with such situation? Best regards, Jan
by Jan Suhr - 03:11 - 23 Apr 2024
Follow-Ups
-
Re: purchasing a set of products
Hi Frederik! Am 23.04.24 um 15:41 schrieb Frederik Kramer: > Hi Jan, > > it seems that you simply don't right functionality for your problem. If > the product is essentially a kit (we call that Handelsstückliste in > Germany in most cases), than why you use a different product for > selling? I mean the customer doesn't necessarly need to know what the Because we manufacture new products instead of just selling the purchased one. > kit contains and how it is purchased but doubling the amount of product > data seems wired and wrong to me. Of course there are a few other down > stream issues to be handled when using Odoo E-Commerce as you do, but > generally i would still avoid (and see no reason) to build out a > replicating product structure (separated for sales and purchases). If > you really do the assembly yourself you may also want to use full > "manufacturing" instead (at least for the laptop type products). To use full manufacturing instead of a kit as part of the purchasing process would only complicate things. But instead we might register the purchased product in our stock (e.g. 1x laptop with its parts instead of 1x laptop barebone, 1x RAM, 1x SSD) and use this as a component when producing our final product. This might work if we find a solution to produce more than just one product. For example: The purchased laptop contains 250 GB SSD and the manufactured one contains a 500 GB SSD. So the 250 GB SSD will result in the stock as a by-product of the manufacturing (replaced by a 500 GB SSD). Is this possible somehow? Still I'm not convinced that this approach works for all our cases because we may end up with many BOMs, one for each purchased product variant. To stay with this example we purchase the laptop with different RAM and different SSD and each combination would require a different BOM. Bests Jan > Best Frederik > > Am 23.04.24 um 15:12 schrieb Jan Suhr | Nitrokey: >> Hi! >> We have several products which we purchase together. For example some >> laptops are purchased together with RAM and a SSD, but which are >> separate products for us in Odoo. I can't expect from our purchase >> department to remember all the components. To make purchasing error >> prone and easy, we configured a laptop *kit* which BOM contains a laptop >> *barebone*, RAM, SSD. So our purchase department can simply buy the >> laptop kit and don't need to remember which components are included in >> which product. >> >> In general this setup works but it has the following shortcomings: >> >> The reordering rules need to be configured for the barebone product. >> Once the minimum amount is reached a PO will be created automatically. >> The purchase department needs to remember to replace the barebone laptop >> with the barebone kit. Obviously deactivating "Can be Purchased" can't >> be applied here. We support this by stating "DON'T BUY" in the product >> barebone's name. >> >> Generally, the amount of products and BOMs is doubling, increasing the >> overall complexity. >> >> Do you have any better idea how to deal with such situation? >> >> Best regards, >> Jan >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com <mailto:frederik.kramer@initos.com> > Internet:www.initos.com <http://www.initos.com> > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> >
by Jan Suhr - 04:16 - 23 Apr 2024 -
Re: purchasing a set of products
Hi Jan,
it seems that you simply don't right functionality for your problem. If the product is essentially a kit (we call that Handelsstückliste in Germany in most cases), than why you use a different product for selling? I mean the customer doesn't necessarly need to know what the kit contains and how it is purchased but doubling the amount of product data seems wired and wrong to me. Of course there are a few other down stream issues to be handled when using Odoo E-Commerce as you do, but generally i would still avoid (and see no reason) to build out a replicating product structure (separated for sales and purchases). If you really do the assembly yourself you may also want to use full "manufacturing" instead (at least for the laptop type products).
Best Frederik
Am 23.04.24 um 15:12 schrieb Jan Suhr | Nitrokey:
Hi! We have several products which we purchase together. For example some laptops are purchased together with RAM and a SSD, but which are separate products for us in Odoo. I can't expect from our purchase department to remember all the components. To make purchasing error prone and easy, we configured a laptop *kit* which BOM contains a laptop *barebone*, RAM, SSD. So our purchase department can simply buy the laptop kit and don't need to remember which components are included in which product. In general this setup works but it has the following shortcomings: The reordering rules need to be configured for the barebone product. Once the minimum amount is reached a PO will be created automatically. The purchase department needs to remember to replace the barebone laptop with the barebone kit. Obviously deactivating "Can be Purchased" can't be applied here. We support this by stating "DON'T BUY" in the product barebone's name. Generally, the amount of products and BOMs is doubling, increasing the overall complexity. Do you have any better idea how to deal with such situation? Best regards, Jan
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 03:40 - 23 Apr 2024