| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 140 |
| Technical Name |
eg_merge_purchase_order |
| License | OPL-1 |
| Website | https://www.inkerp.com |
| Versions | 16.0 17.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 140 |
| Technical Name |
eg_merge_purchase_order |
| License | OPL-1 |
| Website | https://www.inkerp.com |
| Versions | 16.0 17.0 |
Our Most Suggested Products
Merge Purchase Order
The Merge Purchase Order module for Odoo streamlines procurement by allowing users to combine multiple Request for Quotations (RFQs) or draft purchase orders into a single consolidated order. Designed to optimize purchasing workflows, this module saves time, reduces administrative overhead, and ensures accurate tracking of supplier engagements. With flexible merge options, users can maintain, cancel, or delete original orders while creating new, unified purchase orders tailored to business needs.
Features
Screenshots
Support
Service
Features
Multi-RFQ Merge Capability
Users can seamlessly merge two or more RFQs from the same vendor, even if they have different order dates. This feature consolidates multiple purchase requests into one comprehensive order, minimizing duplication and simplifying vendor communications.
Flexible Merge Types
The module offers three merge strategies: create a new purchase order without affecting the old orders, cancel all selected orders, or delete them entirely. This flexibility empowers users to choose the most suitable approach for their workflow, whether preserving historical data or streamlining active orders.
Vendor Selection Control
When using the merge options that leave old orders untouched, users can select a different vendor for the new purchase order. In scenarios where cancellation or deletion is required, the module enforces consistency by ensuring all merged RFQs are from the same vendor.
Screenshot
1.) Initiating the Merge Process
The purchase order overview provides a seamless way to select multiple Requests for Quotation directly from the list view. Once the desired draft orders are checked, the "Action" menu reveals the specific tool needed to begin the consolidation, allowing for a quick transition from a fragmented list to the merge configuration stage.
2.) Merge Configuration and Type Selection
A dedicated workspace appears to help define how the new purchase document should be handled. Here, the vendor and order date are confirmed, and the user can choose the specific impact the merge will have on the original documentsâwhether they should be left as they are, canceled for record-keeping, or removed entirely to keep the system tidy.
3.) Minimum Order Requirement Alert
If an attempt is made to perform a merge with only a single document selected, the system provides an immediate notification. This ensures the user understands that the operation requires at least two separate purchase orders to successfully combine them into a single entity.
4.) Vendor Consistency Validation
When a consolidation involves canceling or deleting the original records, the system verifies that all selected items belong to the same supplier. If a discrepancy is found, a notification reminds the user to align the vendors, ensuring that the final merged order correctly represents a single transaction with a specific partner.
5.) Document State Verification
The tool specifically targets orders that are still in the preliminary stages of the procurement cycle. If a user accidentally includes a confirmed or locked purchase order in the selection, the system provides a helpful reminder that only documents in the RFQ or Draft state are eligible for consolidation.
User Guide
Teams
team@inkerp.com
Suggested Products
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module