Odoo Complex Product Configurator Development
Budget: $250 – $750 USD
I'm in need of a seasoned Odoo developer who can create a complex product configurator for my business. This configurator should allow for multiple customization options on various aspects of the product, including color and material, size and dimensions, features and add-ons, as well as quantity.
Key Requirements:
- Extensive experience with Odoo and product configurator development
- Ability to create a complex configurator with multiple customization options
- Understanding of integrating with an inventory management system
The product configurator will need to be integrated with our inventory management system to ensure real-time stock updates and product availability. Therefore, experience with such integrations is crucial. Ideal candidates will have a strong background in Odoo development and a comprehensive understanding of creating complex product configurators. Please provide examples of similar projects you have completed in your proposal.
The developing must been done in Odoo 17, to replace the outdated system in Odoo 13.
1. All configurators in one system. A separate configurator for each product.
2. Only display configurator after entering a customer number. Configuration is not possible without a customer number.
3. Use customer number to recognise which configurators / products are available.
4. Do not display prices on the website, no direct sales.
5. The preview image of the product should be constantly updated depending on the configuration.
6. After completing the configuration, no order should be created in the system, but an offer should be created automatically as an Excel file, which is not sent to the customer, but to the office sales department, which checks the offer and can see which parts have been added, so that prices are added and finally sent to the customer. A second Excel file must also be created for production so that they know which parts are required for construction.
7. Synchronise article and customer master data between Majesty and Odoo. Majesty can only export the data using an Excel file and has no API.
8. Design customisation so that configurations that have already been made are collapsed, so that the page remains clearer due to the large number of configurations.
9. Predefined configurations so that certain configurations are already set. Possibly as a separate product.
10. Article numbers in Odoo and Majesty must be the same, otherwise the Excel file created from the Odoo offer cannot be imported into Majesty.
11. The current Odoo 14 system does not currently know how the Excel file is created after the configuration has been completed.
12. Individual assemblies implemented as parts lists. Some assemblies can only be used for one cradle, while others can be used for many cradles.
13. There must be parts lists in the configurator. Do the parts lists exist in Odoo? Different designations for the same product.
14. There must be a text input field at the end of the configurator for the number of pieces.
15. What of the requirements can be implemented with the native configurator?
16. What cannot be implemented?
17. Where does programming need to be done?
- What of the requirements can be implemented with the native configurator?
- What cannot be implemented?
- Where does programming need to be done?
Key Requirements:
- Extensive experience with Odoo and product configurator development
- Ability to create a complex configurator with multiple customization options
- Understanding of integrating with an inventory management system
The product configurator will need to be integrated with our inventory management system to ensure real-time stock updates and product availability. Therefore, experience with such integrations is crucial. Ideal candidates will have a strong background in Odoo development and a comprehensive understanding of creating complex product configurators. Please provide examples of similar projects you have completed in your proposal.
The developing must been done in Odoo 17, to replace the outdated system in Odoo 13.
1. All configurators in one system. A separate configurator for each product.
2. Only display configurator after entering a customer number. Configuration is not possible without a customer number.
3. Use customer number to recognise which configurators / products are available.
4. Do not display prices on the website, no direct sales.
5. The preview image of the product should be constantly updated depending on the configuration.
6. After completing the configuration, no order should be created in the system, but an offer should be created automatically as an Excel file, which is not sent to the customer, but to the office sales department, which checks the offer and can see which parts have been added, so that prices are added and finally sent to the customer. A second Excel file must also be created for production so that they know which parts are required for construction.
7. Synchronise article and customer master data between Majesty and Odoo. Majesty can only export the data using an Excel file and has no API.
8. Design customisation so that configurations that have already been made are collapsed, so that the page remains clearer due to the large number of configurations.
9. Predefined configurations so that certain configurations are already set. Possibly as a separate product.
10. Article numbers in Odoo and Majesty must be the same, otherwise the Excel file created from the Odoo offer cannot be imported into Majesty.
11. The current Odoo 14 system does not currently know how the Excel file is created after the configuration has been completed.
12. Individual assemblies implemented as parts lists. Some assemblies can only be used for one cradle, while others can be used for many cradles.
13. There must be parts lists in the configurator. Do the parts lists exist in Odoo? Different designations for the same product.
14. There must be a text input field at the end of the configurator for the number of pieces.
15. What of the requirements can be implemented with the native configurator?
16. What cannot be implemented?
17. Where does programming need to be done?
- What of the requirements can be implemented with the native configurator?
- What cannot be implemented?
- Where does programming need to be done?