Archives
Contributors
contributors@odoo-community.org
-
Re: Amazon connector
Thanks Clément.
I have just returned from some time away hence the delay in replying.
Have you joined the Discord channel - I understand that is where the conversation will be happening: https://discord.com/channels/737652535149592587/1453036891653017620
Best wishes,
Stuart.
On 23/12/2025 15:32, Clément Mombereau wrote:
Hi Stuart!
I just found your email after commenting Kencove's PR earlier today.
As I say in my comment, I already worked on a POC in 2023/2024 but I didn't have the resources to finish the project. But my main point is that it seems more efficient to avoid rewriting all the connection part (already covered by the python-amazon-sp-api library) and the importation part (theoretically covered by sale_import_base and other modules in OCA/sale-channel).
Also it's important to make the difference between Amazon Vendor and Amazon Seller in the code with 3 modules (base/seller/vendor).
Regards,Clément.
Le ven. 19 déc. 2025 à 04:42, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :
Thanks Denis - that's timely!
Is the author here? It would be preferred to collaborate on that base rather than start a new project.
Best wishes,
Stuart.
On 19/12/2025 08:27, Roussel, Denis wrote:
Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :
Hello Jorge,
Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.
Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.
Best wishes,
Stuart.
Amazon FBM Connector - Project Summary
One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.
Amazon Features Enabled:
Order import from Seller Central (SP-API Orders endpoint)
Shipment confirmation with tracking numbers
Order status synchronisation
Future: Inventory feed submission
Built On:
python-amazon-sp-api library
Odoo 16 Community Edition
SP-API (replaces deprecated MWS)
Provides in Odoo:
Automated hourly order import from Amazon UK (expandable to other marketplaces)
Customer deduplication across sales channels (Amazon, future eBay/Shopify)
SKU mapping lookup table
Shipping method mapping to Odoo carriers
Draft sale orders with gift messages, discounts, shipping as line items
Automatic shipment notifications to Amazon on delivery validation
Manual backlog import with date/status filters
Order sync state tracking and error logging
Architecture:
Abstracted API layer (lib/) separate from Odoo models
Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
Bridge model tracks Amazon ↔ Odoo order state
Transaction-safe per-order processing with error recovery
Test coverage per milestone
On 18/12/2025 20:47, Jorge Elena Poblet wrote:
Hi everyone,
I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.
We’re also open to collaborating or co-developing a connector if there’s shared interest.
If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.
Thanks in advance!--
Jorge Elena Poblet
Founder & CEO
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
by Stuart J Mackintosh - 04:30 - 28 Dec 2025 -
Re: Amazon connector
Hi Stuart!I just found your email after commenting Kencove's PR earlier today.As I say in my comment, I already worked on a POC in 2023/2024 but I didn't have the resources to finish the project. But my main point is that it seems more efficient to avoid rewriting all the connection part (already covered by the python-amazon-sp-api library) and the importation part (theoretically covered by sale_import_base and other modules in OCA/sale-channel).Also it's important to make the difference between Amazon Vendor and Amazon Seller in the code with 3 modules (base/seller/vendor).Regards,Clément.Le ven. 19 déc. 2025 à 04:42, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :Thanks Denis - that's timely!
Is the author here? It would be preferred to collaborate on that base rather than start a new project.
Best wishes,
Stuart.
On 19/12/2025 08:27, Roussel, Denis wrote:
Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :
Hello Jorge,
Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.
Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.
Best wishes,
Stuart.
Amazon FBM Connector - Project Summary
One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.
Amazon Features Enabled:
Order import from Seller Central (SP-API Orders endpoint)
Shipment confirmation with tracking numbers
Order status synchronisation
Future: Inventory feed submission
Built On:
python-amazon-sp-api library
Odoo 16 Community Edition
SP-API (replaces deprecated MWS)
Provides in Odoo:
Automated hourly order import from Amazon UK (expandable to other marketplaces)
Customer deduplication across sales channels (Amazon, future eBay/Shopify)
SKU mapping lookup table
Shipping method mapping to Odoo carriers
Draft sale orders with gift messages, discounts, shipping as line items
Automatic shipment notifications to Amazon on delivery validation
Manual backlog import with date/status filters
Order sync state tracking and error logging
Architecture:
Abstracted API layer (lib/) separate from Odoo models
Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
Bridge model tracks Amazon ↔ Odoo order state
Transaction-safe per-order processing with error recovery
Test coverage per milestone
On 18/12/2025 20:47, Jorge Elena Poblet wrote:
Hi everyone,
I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.
We’re also open to collaborating or co-developing a connector if there’s shared interest.
If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.
Thanks in advance!--
Jorge Elena Poblet
Founder & CEO
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Clément Mombereau - 03:30 - 23 Dec 2025 -
Re: Amazon connector
Thanks Denis - that's timely!
Is the author here? It would be preferred to collaborate on that base rather than start a new project.
Best wishes,
Stuart.
On 19/12/2025 08:27, Roussel, Denis wrote:
Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :
Hello Jorge,
Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.
Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.
Best wishes,
Stuart.
Amazon FBM Connector - Project Summary
One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.
Amazon Features Enabled:
Order import from Seller Central (SP-API Orders endpoint)
Shipment confirmation with tracking numbers
Order status synchronisation
Future: Inventory feed submission
Built On:
python-amazon-sp-api library
Odoo 16 Community Edition
SP-API (replaces deprecated MWS)
Provides in Odoo:
Automated hourly order import from Amazon UK (expandable to other marketplaces)
Customer deduplication across sales channels (Amazon, future eBay/Shopify)
SKU mapping lookup table
Shipping method mapping to Odoo carriers
Draft sale orders with gift messages, discounts, shipping as line items
Automatic shipment notifications to Amazon on delivery validation
Manual backlog import with date/status filters
Order sync state tracking and error logging
Architecture:
Abstracted API layer (lib/) separate from Odoo models
Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
Bridge model tracks Amazon ↔ Odoo order state
Transaction-safe per-order processing with error recovery
Test coverage per milestone
On 18/12/2025 20:47, Jorge Elena Poblet wrote:
Hi everyone,
I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.
We’re also open to collaborating or co-developing a connector if there’s shared interest.
If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.
Thanks in advance!--
Jorge Elena Poblet
Founder & CEO
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
by Stuart J Mackintosh - 08:40 - 19 Dec 2025 -
Re: Amazon connector
Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :Hello Jorge,
Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.
Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.
Best wishes,
Stuart.
Amazon FBM Connector - Project Summary
One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.
Amazon Features Enabled:
Order import from Seller Central (SP-API Orders endpoint)
Shipment confirmation with tracking numbers
Order status synchronisation
Future: Inventory feed submission
Built On:
python-amazon-sp-api library
Odoo 16 Community Edition
SP-API (replaces deprecated MWS)
Provides in Odoo:
Automated hourly order import from Amazon UK (expandable to other marketplaces)
Customer deduplication across sales channels (Amazon, future eBay/Shopify)
SKU mapping lookup table
Shipping method mapping to Odoo carriers
Draft sale orders with gift messages, discounts, shipping as line items
Automatic shipment notifications to Amazon on delivery validation
Manual backlog import with date/status filters
Order sync state tracking and error logging
Architecture:
Abstracted API layer (lib/) separate from Odoo models
Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
Bridge model tracks Amazon ↔ Odoo order state
Transaction-safe per-order processing with error recovery
Test coverage per milestone
On 18/12/2025 20:47, Jorge Elena Poblet wrote:
Hi everyone,
I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.
We’re also open to collaborating or co-developing a connector if there’s shared interest.
If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.
Thanks in advance!--
Jorge Elena Poblet
Founder & CEO
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel. - 08:26 - 19 Dec 2025 -
Re: Amazon connector
Hello Jorge,
Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.
Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.
Best wishes,
Stuart.
Amazon FBM Connector - Project Summary
One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.
Amazon Features Enabled:
Order import from Seller Central (SP-API Orders endpoint)
Shipment confirmation with tracking numbers
Order status synchronisation
Future: Inventory feed submission
Built On:
python-amazon-sp-api library
Odoo 16 Community Edition
SP-API (replaces deprecated MWS)
Provides in Odoo:
Automated hourly order import from Amazon UK (expandable to other marketplaces)
Customer deduplication across sales channels (Amazon, future eBay/Shopify)
SKU mapping lookup table
Shipping method mapping to Odoo carriers
Draft sale orders with gift messages, discounts, shipping as line items
Automatic shipment notifications to Amazon on delivery validation
Manual backlog import with date/status filters
Order sync state tracking and error logging
Architecture:
Abstracted API layer (lib/) separate from Odoo models
Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
Bridge model tracks Amazon ↔ Odoo order state
Transaction-safe per-order processing with error recovery
Test coverage per milestone
On 18/12/2025 20:47, Jorge Elena Poblet wrote:
Hi everyone,
I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.
We’re also open to collaborating or co-developing a connector if there’s shared interest.
If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.
Thanks in advance!--
Jorge Elena Poblet
Founder & CEO
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
by Stuart J Mackintosh - 07:56 - 19 Dec 2025 -
Amazon connector
Hi everyone,
I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.
We’re also open to collaborating or co-developing a connector if there’s shared interest.
If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.
Thanks in advance!--Jorge Elena Poblet
Founder & CEO
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran CanariaThis email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy
by Jorge Elena Poblet - 08:45 - 18 Dec 2025 -
Re: Odoo développement
Hello Oumayma!Welcome to our community! Did you know you can become an OCA member?Let us know if we can help you.Le mer. 17 déc. 2025 à 18:32, Oumayma Akhssassi <notifications@odoo-community.org> a écrit :Hi everyone,I am interesting in joining your odoo Developers community.I hope to integrate into this environment, lean from you, and grow technically with your support_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Julie LeBrunExecutive Director, Content Creator & Training ManagerGitHub : https://github.com/TumbaoJu
by Julie LeBrun (OCA) - 03:55 - 18 Dec 2025 -
Re: Address format in SEPA XML files
My understanding was that vanilla odoo can only support the hybrid format, because for the more detailed format you need street and housenumber separated, which you either need to guessculate or you need to use an oca module to have the data differently in your db, which not all customers have. So i think the hybrid format is a better default. But Alexis might have a different view?
by Tom Blauwendraat - 09:15 - 17 Dec 2025 -
Re: Address format in SEPA XML files
Le mar. 16 déc. 2025 à 10:57, Victor Champonnois <notifications@odoo-community.org> a écrit :--We are not ready to deploy your "big" PR in production yet. So we will isolate the part of the code that makes the correction in a separate PR. Is it OK for you if we propose this PR to the OCA ?
Of course ! Feel free to take code from OCA/bank-payment-alternative to improve OCA/bank-payment !BTW, you don't need to ask my permission, the AGPL licence permits you to do that ; you just have to keep the name of the authors of the code.Alexis de Lattre
by Alexis de Lattre - 04:06 - 17 Dec 2025 -
Re: Address format in SEPA XML files
Yes sorry for not responding, we worked from Alexis's PR and made this PR : https://github.com/OCA/bank-payment/pull/1535
This enforces the structured format, not the hybrid format as in your PR. I don't know which is best though.
Victor Champonnois - Coop IT Easy
On 16/12/25 14:03, Tom Blauwendraat wrote:
Victor, it would be nice if you can respond to the comment that I made on there. So that maybe the PR can be simplified
by Victor Champonnois - 04:41 - 16 Dec 2025 -
Re: Address format in SEPA XML files
Yes, it's my colleague's PR, it's the work I mentionned. He was quicker than I planned ^^
Victor Champonnois - Coop IT Easy
On 16/12/25 14:02, Pedro M. Baeza wrote:
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Victor Champonnois - 04:41 - 16 Dec 2025 -
Re: Address format in SEPA XML files
We had started on something here:
https://github.com/OCA/bank-payment/pull/1528
Victor, it would be nice if you can respond to the comment that I made on there. So that maybe the PR can be simplified
On 12/16/25 10:57, Victor Champonnois wrote:
Thank you for your reply Alexis.
We are not ready to deploy your "big" PR in production yet. So we will isolate the part of the code that makes the correction in a separate PR. Is it OK for you if we propose this PR to the OCA ?
Have a nice day,
Victor Champonnois - Coop IT Easy
On 30/10/25 11:12, Alexis de Lattre wrote:
Dear Victor,
I was aware of this change from unstructured addresses to structured addresses in SEPA XML files, as described in the EPC specs. To anticipate this change, I worked on it in august 2024, cf this commit on account_banking_pain_base https://github.com/akretion/banking/commit/e0ccf2d734c1aaea5e26f826c030eb57d392b04f
On v16.0, structured addresses in SEPA credit transfer XML files and SEPA direct debit XML files is implemented in my "big" PR here : https://github.com/OCA/bank-payment/pull/1174I am fully aware of the problem with the separation of street name and number. I didn't want account_banking_pain_base to depend on base_address_extended, because it would be a very big impact for a very small need.My implementation strategy was the following :- if base_address_extended is installed, it use the fields added by that module- if base_address_extended is not installed, I separate street number and street name "on the fly" with code. It's not always perfect, it works most of the time and, when it doesn't work, the street number is empty and the street name has the whole street field.Cf the code :you can have a look at the method _improved_street_split() at line 99.
Look at the test suite to see the result with real life content :
In 18.0, it is implemented in OCA/bank-payment-alternative (which was created from my "big" PR on 16.0 #1174) :The only change is that the module account_banking_pain_base has been renamed to account_banking_sepa_base.
Porting this on OCA/bank-payment should be pretty easy.
Alexis
Le jeu. 30 oct. 2025 à 10:27, Victor Champonnois <notifications@odoo-community.org> a écrit :
Hello OCA Contributors,
There is an ongoing change in the european regulation regarding the format of address in Sepa direct debit and Sepa credit transfer XML files. See here for the presentation of the regulation and here for the full spec.Banks in Belgium are already rejecting some XML files generated from the version 12 and 16 of account_banking_sepa_credit_transfer.
There are two possible formats : structured and hybrid. Using the structured format doesn't seem possible because it requires the street name and number to be separated. In Odoo both pieces of information are in the same field. The hybrid format should therefore be used, but from what I see, the XML files already seem to be consistent with this format.
Have you encountered the same problems ? Or do you have more information about this issue ?
Thank you and have a nice day,
-- Victor Champonnois - Coop IT Easy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 02:00 - 16 Dec 2025 -
-
Re: Address format in SEPA XML files
Thank you for your reply Alexis.
We are not ready to deploy your "big" PR in production yet. So we will isolate the part of the code that makes the correction in a separate PR. Is it OK for you if we propose this PR to the OCA ?
Have a nice day,
Victor Champonnois - Coop IT Easy
On 30/10/25 11:12, Alexis de Lattre wrote:
Dear Victor,
I was aware of this change from unstructured addresses to structured addresses in SEPA XML files, as described in the EPC specs. To anticipate this change, I worked on it in august 2024, cf this commit on account_banking_pain_base https://github.com/akretion/banking/commit/e0ccf2d734c1aaea5e26f826c030eb57d392b04f
On v16.0, structured addresses in SEPA credit transfer XML files and SEPA direct debit XML files is implemented in my "big" PR here : https://github.com/OCA/bank-payment/pull/1174I am fully aware of the problem with the separation of street name and number. I didn't want account_banking_pain_base to depend on base_address_extended, because it would be a very big impact for a very small need.My implementation strategy was the following :- if base_address_extended is installed, it use the fields added by that module- if base_address_extended is not installed, I separate street number and street name "on the fly" with code. It's not always perfect, it works most of the time and, when it doesn't work, the street number is empty and the street name has the whole street field.Cf the code :you can have a look at the method _improved_street_split() at line 99.
Look at the test suite to see the result with real life content :
In 18.0, it is implemented in OCA/bank-payment-alternative (which was created from my "big" PR on 16.0 #1174) :The only change is that the module account_banking_pain_base has been renamed to account_banking_sepa_base.
Porting this on OCA/bank-payment should be pretty easy.
Alexis
Le jeu. 30 oct. 2025 à 10:27, Victor Champonnois <notifications@odoo-community.org> a écrit :
Hello OCA Contributors,
There is an ongoing change in the european regulation regarding the format of address in Sepa direct debit and Sepa credit transfer XML files. See here for the presentation of the regulation and here for the full spec.Banks in Belgium are already rejecting some XML files generated from the version 12 and 16 of account_banking_sepa_credit_transfer.
There are two possible formats : structured and hybrid. Using the structured format doesn't seem possible because it requires the street name and number to be separated. In Odoo both pieces of information are in the same field. The hybrid format should therefore be used, but from what I see, the XML files already seem to be consistent with this format.
Have you encountered the same problems ? Or do you have more information about this issue ?
Thank you and have a nice day,
-- Victor Champonnois - Coop IT Easy_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Victor Champonnois - 09:56 - 16 Dec 2025 -
OCA news + New mailing lists
Dear contributors,
In the future, we won't use the contributor mailing list to promote OCA events and activities.We want this mailing to keep its main goal :This group is meant for both OCA contributors (members or not) to discuss the development of OCA projects. It can serve as a place to exchange on project roadmaps, discuss cross project issues...If you want to be informed about the OCA and its activities, you can:- become a member and receive the emails sent to our members
- subscribe to the Newsletter
- subscribe to specific mailing lists
NEW MAILING LISTS
Crowdfunding news
This mailing list is dedicated to follow the news regarding the challenges of the Crowdfunding platform. Receive information about the new challenges and the evolution of an ongoing challenges.
Support Group Sessions | Consultants
This mailing list is dedicated to the communications around the OCA Support Group Sessions for Consultants
Webinars for members
This mailing list is dedicated to exchanges around the webinars past and future.
Thank you and have a great day.--Julie LeBrunExecutive Director, Content Creator & Training ManagerGitHub : https://github.com/TumbaoJu
by Julie LeBrun (OCA) - 05:15 - 15 Dec 2025 -
Re: Implementing Real Cost
Hello Daniel,In case you are on 16.0, we have added major improvements to stock_valuation_fifo_lot to achieve specific identification in https://github.com/OCA/stock-logistics-workflow/pull/1676. It's been in production use with no major issues.Best regards,--Yoshi TashiroQuartileOn Thu, Dec 4, 2025 at 5:02 PM Richard deMeester <notifications@odoo-community.org> wrote:Hi Daniel,
On version 18.0+, there is a field "lot_valuated" (only visible for products with tracking).
lot_valuated = fields.Boolean(
"Valuation by Lot/Serial number",
compute='_compute_lot_valuated', store=True, readonly=False,
help="If checked, the valuation will be specific by Lot/Serial number.",
)I think that is what you are looking for?Richard
Kind regards,Richard deMeesterDevelopment QAWilldooIT is a member of the PNORS Technology Group.
This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not disclose or use the information in this email in any way. If you have received this email in error please notify the sender. Although reasonable precautions have been taken to ensure no viruses are present in this email, no responsibility is accepted by PNORS Technology Group Pty Ltd or its related entities for any loss or damage arising from the use of this email or attachments. Any views expressed in this email or file attachments are those of the individual sender only, unless expressly stated to be those of PNORS Technology Group Pty Ltd or any of its related entities.
From: Frederik Kramer <notifications@odoo-community.org>
Sent: Thursday, 4 December 2025 6:52 PM
To: Contributors <contributors@odoo-community.org>
Subject: Re: Implementing Real CostHi Daniel,
afaik there is also AVCO (Average Costing) but there is no LIFO (even if that would be allowed in many localisations). I am not aware of anyone or any module that has touched this and i personally would issue that reqirement directly to Odoo instead of developing something one by one, because that is very core to accounting compliance
Best Frederik
Am 04.12.25 um 08:32 schrieb Daniel Reis:
Hello,
Odoo supports FIFO costing, but this is not the same as real cost.
For example, when using Lots, I can buy lot A and then Lot B.
If I choose to consume Lot B first, it will carry the purchase cost of Lot A.
As far as I know this is a common request from customers, but I couldn't find an existing implementation for it.
Is there anything I missed out there?
Thank you!
--
DANIEL REIS
MANAGING PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais![[Logo OpenSourceIntegrators.com]](https://www.opensourceintegrators.com/images/opensource-logo-2022.svg)
_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yoshi Tashiro - 10:15 - 4 Dec 2025 -
Re: Implementing Real Cost
Daniel wasn't asking for LIFO, but for what he calls "real cost", which seeing the description, I think it's a valuation by lots.Regards.
by Pedro M. Baeza - 09:26 - 4 Dec 2025
