🚀 Release notes
🚀

Procuros <> Odoo integration :  

Release notes

17.0.0.9.0 - 01 Sep 2026

Summary: You can now choose exactly who receives Procuros connector notification emails — and switch them off entirely — and invoices with an ambiguous source document now give you a clear message instead of a technical error.

New Features 🎉

* Choose who gets connector notification emails Every Procuros connector now has its own "Notifications" section, with an "Email Notifications" switch and a "Notification Contact". Transaction notification emails go to the contact you pick there, instead of to the Salesperson on the connector as they always did before. Turn the switch off — or leave the contact empty — and the connector stops sending these emails altogether. While the switch is off, the Notification Contact field is hidden. Both fields can be changed while the connector is in draft.

But Also...

Improvements 🔬

  • Nothing changes for your existing connectors when you upgrade. Whoever was set as Salesperson is copied into the new Notification Contact for you, so the same people keep receiving the same emails and there is nothing to reconfigure. If you had previously cleared the Salesperson to stop the emails, that connector stays quiet.

Bug Fixes 🔨

  • Invoices in multi-company databases now find the right sales order. Sales order numbers restart per company, so the same number can exist in more than one of them. Sending an invoice whose Source Document matched an order in another company could fail with a technical error, or in the worst case send the wrong company's order details to Procuros. The connector now looks only at orders belonging to the invoice's own company.

  • A clear message when a source document is ambiguous. If the Source Document on an invoice genuinely matches two or more sales orders within the same company, that invoice still cannot be sent — no single order identifies it — but instead of an unexplained technical error you now get a readable message naming the invoice, the source document, how many orders it matched, the company, and the IDs of the conflicting orders, along with what to do about it: rename the duplicate order, or point the invoice at the correct one.

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀

18.0.0.6.0 - 01 Sep 2026

Summary: You can now choose exactly who receives Procuros connector notification emails — and switch them off entirely — and invoices with an ambiguous source document now give you a clear message instead of a technical error.

New Features 🎉

  • Choose who gets connector notification emails Every Procuros connector now has its own "Notifications" section, with an "Email Notifications" switch and a "Notification Contact". Transaction notification emails go to the contact you pick there, instead of to the Salesperson on the connector as they always did before. Turn the switch off — or leave the contact empty — and the connector stops sending these emails altogether. While the switch is off, the Notification Contact field is hidden. Both fields can be changed while the connector is in draft.


But Also...

Improvements 🔬

  • Nothing changes for your existing connectors when you upgrade. Whoever was set as Salesperson is copied into the new Notification Contact for you, so the same people keep receiving the same emails and there is nothing to reconfigure. If you had previously cleared the Salesperson to stop the emails, that connector stays quiet.



Bug Fixes 🔨

  • Invoices in multi-company databases now find the right sales order. Sales order numbers restart per company, so the same number can exist in more than one of them. Sending an invoice whose Source Document matched an order in another company could fail with a technical error, or in the worst case send the wrong company's order details to Procuros. The connector now looks only at orders belonging to the invoice's own company.
  • A clear message when a source document is ambiguous. If the Source Document on an invoice genuinely matches two or more sales orders within the same company, that invoice still cannot be sent — no single order identifies it — but instead of an unexplained technical error you now get a readable message naming the invoice, the source document, how many orders it matched, the company, and the IDs of the conflicting orders, along with what to do about it: rename the duplicate order, or point the invoice at the correct one.

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀

19.0.1.6.0 - 01 Sep 2026

Summary: You can now choose exactly who receives Procuros connector notification emails — and switch them off entirely — and invoices with an ambiguous source document now give you a clear message instead of a technical error.

New Features 🎉

  • Choose who gets connector notification emails Every Procuros connector now has its own "Notifications" section, with an "Email Notifications" switch and a "Notification Contact". Transaction notification emails go to the contact you pick there, instead of to the Salesperson on the connector as they always did before. Turn the switch off — or leave the contact empty — and the connector stops sending these emails altogether. While the switch is off, the Notification Contact field is hidden. Both fields can be changed while the connector is in draft.

But Also...

Improvements 🔬

  • Nothing changes for your existing connectors when you upgrade. Whoever was set as Salesperson is copied into the new Notification Contact for you, so the same people keep receiving the same emails and there is nothing to reconfigure. If you had previously cleared the Salesperson to stop the emails, that connector stays quiet.

Bug Fixes 🔨

  • Invoices in multi-company databases now find the right sales order. Sales order numbers restart per company, so the same number can exist in more than one of them. Sending an invoice whose Source Document matched an order in another company could fail with a technical error, or in the worst case send the wrong company's order details to Procuros. The connector now looks only at orders belonging to the invoice's own company.
  • A clear message when a source document is ambiguous. If the Source Document on an invoice genuinely matches two or more sales orders within the same company, that invoice still cannot be sent — no single order identifies it — but instead of an unexplained technical error you now get a readable message naming the invoice, the source document, how many orders it matched, the company, and the IDs of the conflicting orders, along with what to do about it: rename the duplicate order, or point the invoice at the correct one.

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀



19.0.1.5.0 - 02 Jul 2026

Summary: Incoming Procuros documents now understand carton (unit-of-measure) barcodes, keeping quantities and totals correct automatically.

New Features 🎉
- Carton barcode recognition 
Incoming orders, invoices, vendor credit notes and shipping notices can now be matched using carton barcodes (GTINs), not just the individual product barcode. When a document refers to a carton, the connector carries the carton unit of measure natively so Odoo converts to base units for you, and keeps prices and totals correct. A recognised carton barcode also takes priority over the unit of measure sent in the document, so lines are booked in the right packaging.

But Also...

Improvements 🔬
- When a barcode can't be matched, the reported issue now tells you exactly which barcodes were checked (both the product and the unit-of-measure barcode), making it easier to fix the data.

Bug Fixes 🔨
- None in this release

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


18.0.0.5.0 - 02 Jul 2026

Summary: Incoming Procuros documents now understand carton (packaging) barcodes, and incoming orders now honour your customer records more faithfully.

New Features 🎉
- Carton barcode recognition 
Incoming orders, invoices, vendor credit notes and shipping notices can now be matched using carton/packaging barcodes (GTINs), not just the individual product barcode. When a document refers to a carton, the connector automatically works out how many base units that represents and keeps prices and totals correct. Order responses also compare quantities in cartons, so an unchanged carton order is no longer reported as a change by mistake.

But Also...

Improvements 🔬
- When a barcode can't be matched, the reported issue now tells you exactly which barcodes were checked (both the product and the packaging barcode), making it easier to fix the data.

Bug Fixes 🔨
- Incoming orders now respect your customer data : the salesperson is taken from the customer first (the connector default is only a fallback). If a delivery or invoicing address code (GLN) is ambiguous or unknown, the order is stopped and a clear data issue is raised instead of silently shipping to the default address.

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


17.0.0.8.0 - 05 Jul 2026


Summary: Incoming Procuros documents now understand carton (packaging) barcodes, keeping quantities and totals correct automatically.

New Features 🎉
- Carton barcode recognition 
Incoming orders, invoices, vendor credit notes and shipping notices can now be matched using carton/packaging barcodes (GTINs), not just the individual product barcode. When a document refers to a carton, the connector automatically works out how many base units that represents and keeps prices and totals correct. Order responses also compare quantities in cartons, so an unchanged carton order is no longer reported as a change by mistake.

But Also...

Improvements 🔬
- When a barcode can't be matched, the reported issue now tells you exactly which barcodes were checked (both the product and the packaging barcode), making it easier to fix the data.



💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


19.0.1.4.1 - 15 Jun 2026

Summary: Incoming orders now follow your customer data more closely, assigning the right salesperson and matching delivery and invoice addresses safely.

Bug Fixes 🔨

- Incoming orders now respect your customer data. Each order is assigned to the customer's own salesperson, falling back to the connector's default salesperson only when the customer has none. Delivery and invoice addresses are now matched strictly by their GLN: if an address code is ambiguous (used by more than one partner) or unknown, the order is held with a clear data issue instead of silently using the wrong partner or the default address. Orders without delivery/invoice address codes keep using the default address as before.


💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


18.0.0.4.1 - 15 Jun 2026

Summary: Incoming orders now follow your customer data more closely, assigning the right salesperson and matching delivery and invoice addresses safely.

Bug Fixes 🔨

- Incoming orders now respect your customer data. Each order is assigned to the customer's own salesperson, falling back to the connector's default salesperson only when the customer has none. Delivery and invoice addresses are now matched strictly by their GLN: if an address code is ambiguous (used by more than one partner) or unknown, the order is held with a clear data issue instead of silently using the wrong partner or the default address. Orders without delivery/invoice address codes keep using the default address as before.


💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


17.0.0.7.1 - 15 Jun 2026

Summary: Incoming orders now follow your customer data more closely, assigning the right salesperson and matching delivery and invoice addresses safely.

Bug Fixes 🔨

- Incoming orders now respect your customer data. Each order is assigned to the customer's own salesperson, falling back to the connector's default salesperson only when the customer has none. Delivery and invoice addresses are now matched strictly by their GLN: if an address code is ambiguous (used by more than one partner) or unknown, the order is held with a clear data issue instead of silently using the wrong partner or the default address. Orders without delivery/invoice address codes keep using the default address as before.


💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


16.0.0.1.1 - 15 Jun 2026

Summary: Two reliability fixes — incoming orders now correctly pick up the customer's own salesperson and payment terms, and documents that receive a "no action needed" response from Procuros will no longer keep retrying unnecessarily.

Bug Fixes 🔨

- Incoming orders now respect the customer's salesperson and payment terms

When Procuros sends a new order, the system now uses the salesperson assigned to the customer and the customer's payment terms — rather than always taking them from the connector configuration. The connector settings still act as a fallback when the customer has no salesperson or payment terms set. Additionally, if an order references an address identifier (GLN) that matches more than one partner or no partner at all, the order is now rejected with a clear log entry instead of silently shipping to the wrong address.

- No more unnecessary retries after "no action" responses from Procuros 

When Procuros replies that no action is needed for a document (invoice, delivery, purchase order), the connector now marks that document so it will not be sent again. This prevents retry loops that could generate duplicate or invalid transaction references on the Procuros side.


💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


19.0.1.4.0 - 12 May 2026

Summary: You can now edit the Order Identifier on sales orders you create manually, while orders received through Procuros EDI keep their identifier locked for safety.

New Features 🎉

- Editable Order Identifier on manual orders

On sales orders that were not received through Procuros EDI, the Order Identifier field is now editable. This lets you set or correct the reference used in downstream documents (such as invoices) for orders you create by hand. Orders that come from a Procuros transaction remain locked, so EDI references can't be changed by accident.

💡

Question or feedback on this release? Reach out to product@erp.muchconsulting.de 🚀




18.0.0.4.0 - 12 May 2026

Summary: You can now edit the Order Identifier on sales orders you create manually, while orders received through Procuros EDI keep their identifier locked for safety.

New Features 🎉

- Editable Order Identifier on manual orders

On sales orders that were not received through Procuros EDI, the Order Identifier field is now editable. This lets you set or correct the reference used in downstream documents (such as invoices) for orders you create by hand. Orders that come from a Procuros transaction remain locked, so EDI references can't be changed by accident.

💡

Question or feedback on this release? Reach out to product@erp.muchconsulting.de 🚀



17.0.0.7.0 - 12 May 2026

Summary: You can now edit the Order Identifier on sales orders you create manually, while orders received through Procuros EDI keep their identifier locked for safety.

New Features 🎉

- Editable Order Identifier on manual orders

On sales orders that were not received through Procuros EDI, the Order Identifier field is now editable. This lets you set or correct the reference used in downstream documents (such as invoices) for orders you create by hand. Orders that come from a Procuros transaction remain locked, so EDI references can't be changed by accident.

💡

Question or feedback on this release? Reach out to product@erp.muchconsulting.de 🚀



19.0.1.3.0 - 10 Apr 2026

Summary: This release adds support for incoming Remittance Advice (REMADV), improves discount handling across documents, and enriches invoice payloads with order line references.

New Features 🎉

  • Incoming Remittance Advice (REMADV)

Receive remittance advice documents from your trade partners via Procuros. The connector automatically identifies the paying partner, matches referenced invoices and credit notes, creates a payment, and reconciles it — all in one step. A detailed chatter note is posted on each payment with the remittance line breakdown. To get started, set a Payment Journal in your connector settings.

  • Order Line Reference on Invoices

Outgoing invoices now include the original order line number and ordered quantity for each item, making it easier for your trade partners to match invoice lines back to the corresponding purchase order.


But Also..

Improvements 🔬

  • Comprehensive test suite added covering all major connector flows (remittance advice, invoices, orders, deliveries, parsing, and more).


Bug Fixes 🔨

  • fixed discount handling so that invoices send the gross unit price with allowances broken out separately, and incoming orders correctly apply discounts to SO lines. 
  • Notes and Section Lines Excluded from EDI

Section headers and note lines on Sales Orders, Purchase Orders, and Invoices are no longer sent to Procuros, preventing unnecessary or invalid data from reaching your trade partners.



💡

Question or feedback on this release? Reach out to product@erp.muchconsulting.de 🚀




18.0.0.3.0 - 10 Apr 2026

Summary: This release adds support for incoming Remittance Advice (REMADV), improves discount handling across documents, and enriches invoice payloads with order line references.

New Features 🎉

  • Incoming Remittance Advice (REMADV)

Receive remittance advice documents from your trade partners via Procuros. The connector automatically identifies the paying partner, matches referenced invoices and credit notes, creates a payment, and reconciles it — all in one step. A detailed chatter note is posted on each payment with the remittance line breakdown. To get started, set a Payment Journal in your connector settings.


  • Order Line Reference on Invoices

Outgoing invoices now include the original order line number and ordered quantity for each item, making it easier for your trade partners to match invoice lines back to the corresponding purchase order.


But Also...


Improvements 🔬

- Comprehensive test suite added covering all major connector flows (remittance advice, invoices, orders, deliveries, parsing, and more).


Bug Fixes 🔨

- Fixed discount handling so that invoices send the gross unit price with allowances broken out separately, and incoming orders correctly apply discounts to SO lines. 

- Notes and Section Lines Excluded from EDI

Section headers and note lines on Sales Orders, Purchase Orders, and Invoices are no longer sent to Procuros, preventing unnecessary or invalid data from reaching your trade partners.


💡

Question or feedback on this release? Reach out to product@erp.muchconsulting.de 🚀



17.0.0.6.0 - 10 Apr 2026

Summary: This release adds support for incoming Remittance Advice (REMADV), improves discount handling across documents, and enriches invoice payloads with order line references.

New Features 🎉

  • Incoming Remittance Advice (REMADV)

Receive remittance advice documents from your trade partners via Procuros. The connector automatically identifies the paying partner, matches referenced invoices and credit notes, creates a payment, and reconciles it — all in one step. A detailed chatter note is posted on each payment with the remittance line breakdown. To get started, set a Payment Journal in your connector settings.


  • Order Line Reference on Invoices

Outgoing invoices now include the original order line number and ordered quantity for each item, making it easier for your trade partners to match invoice lines back to the corresponding purchase order.


But Also...


Improvements 🔬

- Comprehensive test suite added covering all major connector flows (remittance advice, invoices, orders, deliveries, parsing, and more).


Bug Fixes 🔨

- Fixed discount handling so that invoices send the gross unit price with allowances broken out separately, and incoming orders correctly apply discounts to SO lines. 

- Notes and Section Lines Excluded from EDI : Section headers and note lines on Sales Orders, Purchase Orders, and Invoices are no longer sent to Procuros, preventing unnecessary or invalid data from reaching your trade partners.


💡

Question or feedback on this release? Reach out to product@erp.muchconsulting.de 🚀






19.0.1.2.0 - 5 Feb 2026


Summary: This release introduces several new functionalities, including enhanced order response handling and automated carrier assignment for delivery orders, alongside crucial bug fixes to improve system stability and efficiency.

New Features 🎉

  • Implement ORDER_RESPONSE Transaction

 The connector now supports sending Order Reponse transaction type, enabling supplier to control incoming order processing.

  • Utilise Mixins

Refactored codebase to utilize mixins for better code organization and reusability. 

  • Auto-set Carrier on Delivery Orders

Automates the assignment of carriers to delivery orders, reducing manual effort. 


Bug Fixes 🔨


  • Prevent Retry Loops & Invalid UUIDs

Resolved bugs that caused infinite retry loops and issues with invalid UUIDs in transactions. 


💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


18.0.0.2.0 - 5 Feb 2026


Summary: This release introduces several new functionalities, including enhanced order response handling and automated carrier assignment for delivery orders, alongside crucial bug fixes to improve system stability and efficiency.

New Features 🎉

  • Implement ORDER_RESPONSE Transaction

 The connector now supports sending Order Reponse transaction type, enabling supplier to control incoming order processing.

  • Utilise Mixins

Refactored codebase to utilize mixins for better code organization and reusability. 

  • Auto-set Carrier on Delivery Orders

Automates the assignment of carriers to delivery orders, reducing manual effort. 


Bug Fixes 🔨


  • Prevent Retry Loops & Invalid UUIDs

Resolved bugs that caused infinite retry loops and issues with invalid UUIDs in transactions. 

  • Filter Done Pickings for Invoice

Corrected the logic to properly filter 'done' pickings when generating invoices.

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


17.0.0.5.0 - 5 Feb 2026


Summary: This release introduces the Order Response transaction type.

New Features 🎉

  • Implement ORDER_RESPONSE Transaction

 The connector now supports sending Order Reponse transaction type, enabling supplier to control incoming order processing.

💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀


17.0.0.4.4 - 15 Dec 2025

Summary: This release focuses on improving the stability and reliability of the connector.

New Features 🎉

  •  Utilized Mixins : this change improves the code structure and reusability.

Improvements 🔬

  • This release includes internal improvements to the connector's performance and stability.

Bug Fixes 🔨

  • Fixed a bug where cron jobs were not running correctly.
  • Fixed a bug that could cause retry loops and invalid UUIDs.
💡

Question or feedback on this release? Reach out to product@muchconsulting.de 🚀