Contributors

contributors@odoo-community.org

Request for Removal from Mailing List – Persistent Unsubscribe Issue

Dear Odoo Community Team,

I am writing to request  removal of my email address from the 
contributors mailing list. Despite multiple attempts to unsubscribe 
using the provided unsubscribe link 
(https://odoo-community.org/groups/unsubscribe), I continue to receive 
emails from this list. I want to switch for my professional address 
nls@robin4consulting.com

Details:

Email Address: rob.a@posteo.net

Issue: Continued receipt of contributor updates despite attempting to 
unsubscribe

Frequency: Receiving unwanted emails on a recurring basis

The standard unsubscribe mechanism does not appear to be functioning 
correctly for my address. I would appreciate it if a moderator could 
manually remove my email from the distribution list.

Thank you for your prompt attention to this matter.

Best regards,
Robin Angelé

by Robin Angelé - 07:16 - 23 Jan 2026

1 replies 1 replies

Weighing scales

Hey Everyone,

I'm a fairly new member to the OCA (joined half 2025) and I didn't had much time to catch up.

I've been in the mailing and I see sometimes questions popping up & people helping eachother, which is great !

At the moment when you want a weighscale for the POS system for odoo EE a IOT is recommended and a ariva-S model.

These scales are sometimes too expensive for customers , did anyone else had success with other scales which also work with an IOT box or any other connection.
Mind you i'm looking for SaaS solutions also, so while i'm open to costume modules for other scales.
I'm also looking for scales that would work with SaaS enterprise solution.

Thank you all , and keep up the good work !

Sincerely
Kristof

Kristof Gommers

Gomworx BV

T: +3215141242

E: kristof@gomworx.com

W: www.gomworx.com

by Kristof Gommers - 08:11 - 22 Jan 2026

11 replies 11 replies

Re: Weighing scales

Hi!

Check l10n_eu_iot_scale_cert.

I only saw the internal message below on 25.09.2025, claiming that this was valid in all Europe.

Dear colleagues,

I’m pleased to share that we have received LNE certification for the use of scales in the Point of Sale. This certification applies to version 18.0 across all EU countries. While mandated by an EU directive, this was particularly important for countries such as France, Switzerland, and Germany.

Our R&D team is already working on certifying version 19.0 as soon as possible.

Please note:

The module is not auto-installed; clients will need to install it themselves. See screenshot below.
This module certifies the Point of Sale with the LNE (Laboratoire national de métrologie et d’essais), which is a legal requirement in certain EU countries. It enforces specific settings and generates a checksum to ensure the code has not been tampered with.
Note that we are currently integrated only with Mettler Toledo scales using the 8217 communication protocol. To enable integration (so the weight is automatically recorded in Odoo), an IoT is required. We strongly recommend using the physical IoT rather than the virtual one, as the physical IoT includes the necessary drivers and interfaces. The virtual IoT relies on drivers installed on the client’s Windows PC.

Avec mes plus sincères salutations,

Jean-Marc Vandel · Associé

Open Net Sàrl · Odoo Gold Partner

Rue de la Tour 5

1004 Lausanne

www.open-net.ch

+41 21 701 42 45

Le 2026-02-09T09:46:48.000+01:00, Jan-Marten Veddeler <notifications@odoo-community.org> a écrit :

Hi all

thanks @Laurence for this very helpful clarity that seems to settle the uncertainty for now at least for the German case, given you spoke directly with the German measuring authorities/Eichamt.

As I had written, my theory was" more a guess/feeling" from the bits and pieces of information that my last research on this had yielded, including some (shaky) statements of Odoo customer support like these

"I've looked into this and found that the certification is twofold: one being the software (Odoo), and the other being the hardware (scale manufacturer). Odoo is certified to weigh items, so one half is covered, but the hardware itself must also be covered."

As for for your surprise on any "legal or logical connection" between TSE and scale, this was a misunderstanding. I did not mean to suggest: From TSE certifications follows scale certification. I meant to suggest: If you use a TSE certified POS, and plugin a certified scale (which the Mettler Toledo Arriva S recommend by Odoo is, as a standalone scale), then your total setup may be Ok certification wise in terms of tax and weighing regulations. Your research shows: this is not the case, according to Eichamt, the whole systems needs to be certified together.

From a "common sense" perspective however (which risk is bigger: the human typing wrong from scale display, or the software grabbing the data wrong), and for smaller customers willing to take the legal risk (customers who may have multiple other non 100% compliant processes in their organisations given their small size and degree of professionalism), using these two "standalone certified components" (Odoo POS and scale) connected might still be an option some customers/Odoo users may chose to go for, having been warned about the legal risks and that the legally safe alternative would be the label printing workaround.

Thank you for this valuable contribution and clarity,
and joining you in the hope that regulations will be upgraded to 21st century

Jan

PS: As for the OCA Spring Sprint of the German Odoo community on April 23rd and 24th 2026: Warmely invited. More info here: https://odoo-community.org/event/spring-sprint-hamburg-2026-04-23-2026-04-24-213/register
Will also drop you a direct eMail on that.

On 2/4/2026 11:13 AM, Laurence Labusch wrote:
Hi all,

thanks Frederik for looping me in – happy to share what I know.

MY LAST OFFICIAL INFORMATION FROM ODOO:

About a year ago (maybe a bit less), I was told by Odoo that they were in the certification process for scales in Paris. Since then: radio silence. Nothing public, no announcement, no certificate number, nothing I could show to a customer or an authority. So as far as I'm concerned, the certification status is still "pending" at best.

WHAT THE GERMAN AUTHORITIES TOLD US:

We had direct conversations with the Eichamt (weights and measures authority) here in Germany, and they were very clear:

The ENTIRE SYSTEM needs to be certified and calibrated together:
- The scale itself
- The IoT box / communication layer
- The POS hardware
- The POS software

All of it. As one integrated, sealed system.

Now, if you know Odoo... that's almost impossible to achieve. Odoo's strength is flexibility – you can configure almost anything, install community modules, customize freely. And if you're on Odoo.sh or SaaS, you're getting continuous updates. That's the exact opposite of what calibration authorities want: a frozen, audited, unchangeable system.

REGARDING JAN'S THEORY (FISKALY TSE = SCALE OK?):

I would be EXTREMELY INTERESTED to hear more about what Jan found out, because frankly, I don't see how this could be correct.

The fiskaly TSE certification and scale/weighing certification are:

1. Two completely different legal frameworks – TSE is about fiscal compliance (GoBD, KassenSichV), weighing is about legal metrology (MessEG, MessEV, NAWI/MID directive)
2. Two completely different authorities – Finanzamt (tax office) vs. Eichamt (weights and measures office)
3. Two completely different purposes – One ensures tax transparency, the other ensures consumers aren't cheated on weight-based pricing

I don't see any legal or logical connection where certifying the cash register for tax purposes would automatically certify the weighing system for trade use. These authorities don't even talk to each other.

MY SUSPICION ABOUT THE DOCUMENTATION CHANGE:

Looking at the diff between Odoo 17.0 and 18.0 docs – yes, they removed the explicit warning about France, Germany, and Switzerland. But removing a warning from documentation is not the same as obtaining certification. I suspect this was a commercial/marketing decision rather than a reflection of any legal change.

If Odoo actually got certified somewhere, I would expect:
- A proper announcement
- A certificate number we can reference
- Updated documentation that says "certified in X countries" rather than just removing the negative statement

MY POSITION FOR CUSTOMERS:

Until I see an official certificate, I continue to advise customers in Germany to use the workaround: a standalone certified scale that prints labels with barcodes, which are then scanned into Odoo POS. Not elegant, but legally safe.

LOOKING FORWARD:

That said, I do think this whole situation is outdated for 2026. The current calibration laws were written for a world of standalone, unchanging devices – not cloud-connected, continuously updated software systems. I hope regulators will modernize this eventually, but that's a slow process.

Jan – if you have any concrete documentation or official statement that supports the "fiskaly = scale OK" theory, I'd genuinely love to see it. Maybe I'm missing something, and I'm always happy to be proven wrong if it means we can finally use integrated scales legally.

P.S.: Frederik, thanks for the hint about the Hamburg OCA Sprint – Jan-Marten, feel free to send me the details!

Best,

Laurence Labusch

Geschäftsführer

lala@labiso.de www.labiso.de

+49 1525 4291514

Labiso GmbH · Von-Seckendorff-Platz 1 · 97539 Wonfurt

🎙️ Der ERP-Stammtisch Podcast
Höre unseren Odoo Podcast auf deiner bevorzugten Plattform:
Apple Podcasts Spotify RTL+ Deezer Website
Am 26.01.2026 um 10:20 schrieb Frederik Kramer <frederik.kramer@initos.com>:
Hi all,

well the latest i heard on this was from fellow Odooer Laurence Labusch (and his company Labiso GmbH). He has spent considerable time to narrow down that issue with the authorities and afaik it is still not allowed to use an electronic wheiging scale even if the POS itself is working according to the national standard which in Germany is implemented using fiskaly TSE unless the whole POS is certified with the weighing scale but maybe Laurence (which i am putting on copy can answer himself).

Best Frederik

P.S.: Jan-Marten maybe you can make Laurence aware of the Hamburg OCA Sprint ;-)

Am 26.01.26 um 10:12 schrieb Jan-Marten Veddeler:

My latest information (more a guess/feeling) from Odoo customer service (and some online research) on this was that if the POS is certified (like e.g. Odoo POS via fiscaly is in Germany), then the scale itself does not need to have an additional certification, and that this may explain why Odoo removed the below notice from its later documentation from v18 on
"Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration into your Odoo database. Alternatively, you can acquire a non-integrated certified scale that prints certified labels, which can then be scanned into your Odoo database."

Anyone has more clarity on this scale certification part in Germany or other EU countries?

Best
Jan

On 1/26/2026 11:37 AM, hugues de keyzer wrote:

, to use a scale connected to a

--

Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany

Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany

www.humanilog.org

Gemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden

_______________________________________________
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
--

Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany

Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany

www.humanilog.org

Gemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Jean-Marc Vandel - 02:11 - 16 Feb 2026

Re: Weighing scales

Hi all

thanks @Laurence for this very helpful clarity that seems to settle the uncertainty for now at least for the German case, given you spoke directly with the German measuring authorities/Eichamt.

As I had written, my theory was" more a guess/feeling" from the bits and pieces of information that my last research on this had yielded, including some (shaky) statements of Odoo customer support like these

"I've looked into this and found that the certification is twofold: one being the software (Odoo), and the other being the hardware (scale manufacturer). Odoo is certified to weigh items, so one half is covered, but the hardware itself must also be covered."

As for for your surprise on any "legal or logical connection" between TSE and scale, this was a misunderstanding. I did not mean to suggest: From TSE certifications follows scale certification. I meant to suggest: If you use a TSE certified POS, and plugin a certified scale (which the Mettler Toledo Arriva S recommend by Odoo is, as a standalone scale), then your total setup may be Ok certification wise in terms of tax and weighing regulations. Your research shows: this is not the case, according to Eichamt, the whole systems needs to be certified together.

From a "common sense" perspective however (which risk is bigger: the human typing wrong from scale display, or the software grabbing the data wrong), and for smaller customers willing to take the legal risk (customers who may have multiple other non 100% compliant processes in their organisations given their small size and degree of professionalism), using these two "standalone certified components" (Odoo POS and scale) connected might still be an option some customers/Odoo users may chose to go for, having been warned about the legal risks and that the legally safe alternative would be the label printing workaround.

Thank you for this valuable contribution and clarity,
and joining you in the hope that regulations will be upgraded to 21st century

Jan

PS: As for the OCA Spring Sprint of the German Odoo community on April 23rd and 24th 2026: Warmely invited. More info here: https://odoo-community.org/event/spring-sprint-hamburg-2026-04-23-2026-04-24-213/register
Will also drop you a direct eMail on that.

On 2/4/2026 11:13 AM, Laurence Labusch wrote:

Hi all,

thanks Frederik for looping me in – happy to share what I know.

MY LAST OFFICIAL INFORMATION FROM ODOO:

About a year ago (maybe a bit less), I was told by Odoo that they were in the certification process for scales in Paris. Since then: radio silence. Nothing public, no announcement, no certificate number, nothing I could show to a customer or an authority. So as far as I'm concerned, the certification status is still "pending" at best.

WHAT THE GERMAN AUTHORITIES TOLD US:

We had direct conversations with the Eichamt (weights and measures authority) here in Germany, and they were very clear:

The ENTIRE SYSTEM needs to be certified and calibrated together:
- The scale itself
- The IoT box / communication layer
- The POS hardware
- The POS software

All of it. As one integrated, sealed system.

Now, if you know Odoo... that's almost impossible to achieve. Odoo's strength is flexibility – you can configure almost anything, install community modules, customize freely. And if you're on Odoo.sh or SaaS, you're getting continuous updates. That's the exact opposite of what calibration authorities want: a frozen, audited, unchangeable system.

REGARDING JAN'S THEORY (FISKALY TSE = SCALE OK?):

I would be EXTREMELY INTERESTED to hear more about what Jan found out, because frankly, I don't see how this could be correct.

The fiskaly TSE certification and scale/weighing certification are:

1. Two completely different legal frameworks – TSE is about fiscal compliance (GoBD, KassenSichV), weighing is about legal metrology (MessEG, MessEV, NAWI/MID directive)
2. Two completely different authorities – Finanzamt (tax office) vs. Eichamt (weights and measures office)
3. Two completely different purposes – One ensures tax transparency, the other ensures consumers aren't cheated on weight-based pricing

I don't see any legal or logical connection where certifying the cash register for tax purposes would automatically certify the weighing system for trade use. These authorities don't even talk to each other.

MY SUSPICION ABOUT THE DOCUMENTATION CHANGE:

Looking at the diff between Odoo 17.0 and 18.0 docs – yes, they removed the explicit warning about France, Germany, and Switzerland. But removing a warning from documentation is not the same as obtaining certification. I suspect this was a commercial/marketing decision rather than a reflection of any legal change.

If Odoo actually got certified somewhere, I would expect:
- A proper announcement
- A certificate number we can reference
- Updated documentation that says "certified in X countries" rather than just removing the negative statement

MY POSITION FOR CUSTOMERS:

Until I see an official certificate, I continue to advise customers in Germany to use the workaround: a standalone certified scale that prints labels with barcodes, which are then scanned into Odoo POS. Not elegant, but legally safe.

LOOKING FORWARD:

That said, I do think this whole situation is outdated for 2026. The current calibration laws were written for a world of standalone, unchanging devices – not cloud-connected, continuously updated software systems. I hope regulators will modernize this eventually, but that's a slow process.

Jan – if you have any concrete documentation or official statement that supports the "fiskaly = scale OK" theory, I'd genuinely love to see it. Maybe I'm missing something, and I'm always happy to be proven wrong if it means we can finally use integrated scales legally.

P.S.: Frederik, thanks for the hint about the Hamburg OCA Sprint – Jan-Marten, feel free to send me the details!

Best,

Laurence Labusch

Geschäftsführer

lala@labiso.de www.labiso.de

+49 1525 4291514

Labiso GmbH · Von-Seckendorff-Platz 1 · 97539 Wonfurt

🎙️ Der ERP-Stammtisch Podcast
Höre unseren Odoo Podcast auf deiner bevorzugten Plattform:
Apple Podcasts Spotify RTL+ Deezer Website
Am 26.01.2026 um 10:20 schrieb Frederik Kramer <frederik.kramer@initos.com>:
Hi all,

well the latest i heard on this was from fellow Odooer Laurence Labusch (and his company Labiso GmbH). He has spent considerable time to narrow down that issue with the authorities and afaik it is still not allowed to use an electronic wheiging scale even if the POS itself is working according to the national standard which in Germany is implemented using fiskaly TSE unless the whole POS is certified with the weighing scale but maybe Laurence (which i am putting on copy can answer himself).

Best Frederik

P.S.: Jan-Marten maybe you can make Laurence aware of the Hamburg OCA Sprint ;-)

Am 26.01.26 um 10:12 schrieb Jan-Marten Veddeler:

My latest information (more a guess/feeling) from Odoo customer service (and some online research) on this was that if the POS is certified (like e.g. Odoo POS via fiscaly is in Germany), then the scale itself does not need to have an additional certification, and that this may explain why Odoo removed the below notice from its later documentation from v18 on
"Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration into your Odoo database. Alternatively, you can acquire a non-integrated certified scale that prints certified labels, which can then be scanned into your Odoo database."

Anyone has more clarity on this scale certification part in Germany or other EU countries?

Best
Jan

On 1/26/2026 11:37 AM, hugues de keyzer wrote:

, to use a scale connected to a

--

Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany

Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany

www.humanilog.org

Gemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden

_______________________________________________
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

Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany

Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany

www.humanilog.org

Gemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden

by Jan-Marten Veddeler. - 09:45 - 9 Feb 2026

Re: Weighing scales

Hi all,

thanks Frederik for looping me in – happy to share what I know.

MY LAST OFFICIAL INFORMATION FROM ODOO:

About a year ago (maybe a bit less), I was told by Odoo that they were in the certification process for scales in Paris. Since then: radio silence. Nothing public, no announcement, no certificate number, nothing I could show to a customer or an authority. So as far as I'm concerned, the certification status is still "pending" at best.

WHAT THE GERMAN AUTHORITIES TOLD US:

We had direct conversations with the Eichamt (weights and measures authority) here in Germany, and they were very clear:

The ENTIRE SYSTEM needs to be certified and calibrated together:
- The scale itself
- The IoT box / communication layer
- The POS hardware
- The POS software

All of it. As one integrated, sealed system.

Now, if you know Odoo... that's almost impossible to achieve. Odoo's strength is flexibility – you can configure almost anything, install community modules, customize freely. And if you're on Odoo.sh or SaaS, you're getting continuous updates. That's the exact opposite of what calibration authorities want: a frozen, audited, unchangeable system.

REGARDING JAN'S THEORY (FISKALY TSE = SCALE OK?):

I would be EXTREMELY INTERESTED to hear more about what Jan found out, because frankly, I don't see how this could be correct.

The fiskaly TSE certification and scale/weighing certification are:

1. Two completely different legal frameworks – TSE is about fiscal compliance (GoBD, KassenSichV), weighing is about legal metrology (MessEG, MessEV, NAWI/MID directive)
2. Two completely different authorities – Finanzamt (tax office) vs. Eichamt (weights and measures office)
3. Two completely different purposes – One ensures tax transparency, the other ensures consumers aren't cheated on weight-based pricing

I don't see any legal or logical connection where certifying the cash register for tax purposes would automatically certify the weighing system for trade use. These authorities don't even talk to each other.

MY SUSPICION ABOUT THE DOCUMENTATION CHANGE:

Looking at the diff between Odoo 17.0 and 18.0 docs – yes, they removed the explicit warning about France, Germany, and Switzerland. But removing a warning from documentation is not the same as obtaining certification. I suspect this was a commercial/marketing decision rather than a reflection of any legal change.

If Odoo actually got certified somewhere, I would expect:
- A proper announcement
- A certificate number we can reference
- Updated documentation that says "certified in X countries" rather than just removing the negative statement

MY POSITION FOR CUSTOMERS:

Until I see an official certificate, I continue to advise customers in Germany to use the workaround: a standalone certified scale that prints labels with barcodes, which are then scanned into Odoo POS. Not elegant, but legally safe.

LOOKING FORWARD:

That said, I do think this whole situation is outdated for 2026. The current calibration laws were written for a world of standalone, unchanging devices – not cloud-connected, continuously updated software systems. I hope regulators will modernize this eventually, but that's a slow process.

Jan – if you have any concrete documentation or official statement that supports the "fiskaly = scale OK" theory, I'd genuinely love to see it. Maybe I'm missing something, and I'm always happy to be proven wrong if it means we can finally use integrated scales legally.

P.S.: Frederik, thanks for the hint about the Hamburg OCA Sprint – Jan-Marten, feel free to send me the details!

Best,

Laurence Labusch

Geschäftsführer

lala@labiso.de	www.labiso.de

	+49 1525 4291514

Labiso GmbH · Von-Seckendorff-Platz 1 · 97539 Wonfurt

🎙️ Der ERP-Stammtisch Podcast
Höre unseren Odoo Podcast auf deiner bevorzugten Plattform:
Apple Podcasts Spotify RTL+ Deezer Website

Am 26.01.2026 um 10:20 schrieb Frederik Kramer <frederik.kramer@initos.com>:
Hi all,
well the latest i heard on this was from fellow Odooer Laurence Labusch (and his company Labiso GmbH). He has spent considerable time to narrow down that issue with the authorities and afaik it is still not allowed to use an electronic wheiging scale even if the POS itself is working according to the national standard which in Germany is implemented using fiskaly TSE unless the whole POS is certified with the weighing scale but maybe Laurence (which i am putting on copy can answer himself).
Best Frederik
P.S.: Jan-Marten maybe you can make Laurence aware of the Hamburg OCA Sprint ;-)

Am 26.01.26 um 10:12 schrieb Jan-Marten Veddeler:

My latest information (more a guess/feeling) from Odoo customer service (and some online research) on this was that if the POS is certified (like e.g. Odoo POS via fiscaly is in Germany), then the scale itself does not need to have an additional certification, and that this may explain why Odoo removed the below notice from its later documentation from v18 on
"Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration into your Odoo database. Alternatively, you can acquire a non-integrated certified scale that prints certified labels, which can then be scanned into your Odoo database."

Anyone has more clarity on this scale certification part in Germany or other EU countries?

Best
Jan

On 1/26/2026 11:37 AM, hugues de keyzer wrote:

, to use a scale connected to a

--
Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany

Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany

www.humanilog.org
Gemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden

_______________________________________________
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 Laurence Labusch - 09:11 - 4 Feb 2026

Re: Weighing scales

Hi all,

thanks Frederik for looping me in – happy to share what I know.

MY LAST OFFICIAL INFORMATION FROM ODOO:

About a year ago (maybe a bit less), I was told by Odoo that they were
in the certification process for scales in Paris. Since then: radio
silence. Nothing public, no announcement, no certificate number,
nothing I could show to a customer or an authority. So as far as I'm
concerned, the certification status is still "pending" at best.

WHAT THE GERMAN AUTHORITIES TOLD US:

We had direct conversations with the Eichamt (weights and measures
authority) here in Germany, and they were very clear:

The ENTIRE SYSTEM needs to be certified and calibrated together:
- The scale itself
- The IoT box / communication layer
- The POS hardware
- The POS software

All of it. As one integrated, sealed system.

Now, if you know Odoo... that's almost impossible to achieve. Odoo's
strength is flexibility – you can configure almost anything, install
community modules, customize freely. And if you're on Odoo.sh or SaaS,
you're getting continuous updates. That's the exact opposite of what
calibration authorities want: a frozen, audited, unchangeable system.

REGARDING JAN'S THEORY (FISKALY TSE = SCALE OK?):

I would be EXTREMELY INTERESTED to hear more about what Jan found out,
because frankly, I don't see how this could be correct.

The fiskaly TSE certification and scale/weighing certification are:

1. Two completely different legal frameworks – TSE is about fiscal
compliance (GoBD, KassenSichV), weighing is about legal metrology
(MessEG, MessEV, NAWI/MID directive)
2. Two completely different authorities – Finanzamt (tax office) vs.
Eichamt (weights and measures office)
3. Two completely different purposes – One ensures tax transparency,
the other ensures consumers aren't cheated on weight-based pricing

I don't see any legal or logical connection where certifying the cash
register for tax purposes would automatically certify the weighing
system for trade use. These authorities don't even talk to each other.

MY SUSPICION ABOUT THE DOCUMENTATION CHANGE:

Looking at the diff between Odoo 17.0 and 18.0 docs – yes, they
removed the explicit warning about France, Germany, and Switzerland.
But removing a warning from documentation is not the same as obtaining
certification. I suspect this was a commercial/marketing decision
rather than a reflection of any legal change.

If Odoo actually got certified somewhere, I would expect:
- A proper announcement
- A certificate number we can reference
- Updated documentation that says "certified in X countries" rather
than just removing the negative statement

MY POSITION FOR CUSTOMERS:

Until I see an official certificate, I continue to advise customers in
Germany to use the workaround: a standalone certified scale that
prints labels with barcodes, which are then scanned into Odoo POS. Not
elegant, but legally safe.

LOOKING FORWARD:

That said, I do think this whole situation is outdated for 2026. The
current calibration laws were written for a world of standalone,
unchanging devices – not cloud-connected, continuously updated
software systems. I hope regulators will modernize this eventually,
but that's a slow process.

Jan – if you have any concrete documentation or official statement
that supports the "fiskaly = scale OK" theory, I'd genuinely love to
see it. Maybe I'm missing something, and I'm always happy to be proven
wrong if it means we can finally use integrated scales legally.

P.S.: Frederik, thanks for the hint about the Hamburg OCA Sprint –
Jan-Marten, feel free to send me the details!

Best regards,
Laurence


--
Laurence Labusch
LABISO GmbH

by Laurence Labusch - 09:11 - 4 Feb 2026

Re: Weighing scales

there are indeed different regulations for the pos from country to country. one of these is only related to connecting a weighing scale to a pos and applies to all member states of the european union (afaik).

odoo has recently been certified by the lne (a french certification instance) regarding this. the certificate (in french) can be found here (search for “odoo” as certificate holder or “40724” as certificate number).

this certificate applies to odoo 18 and later. unfortunately, to comply, you will need to use the l10n_eu_iot_scale_cert module, which is part of odoo enterprise.

afaik, this certificate is valid for all member states of the european union.

it would be great if we could have a similar certificate for the oca. the problem is that getting one requires a lot of work (painful documents to produce) and is expensive (at least €10k as fees), and only valid for parts of code that cannot be changed later (checksums are checked) without requiring a (paying) revision. there are some discussions in progress (at coop it easy) around this with a current certificate owner that could possibly be revised, but nothing decided yet.

kind regards,

hugues

Le 2026-01-26 à 16:12, Oficina CriptoMart a écrit :

El 26/1/26 a las 11:52, Kristof Gommers escribió:

So just to be clear , even if I have a certified weighing scale, odoo itself isn't certified enough as POS in european setting?

AFAIK, there is not an european cert for PoS, at least for weighing, in some regions of Spain we must certificate our accounting software in local tax authority but in others regions not...

When a client of ours (a supermarket) has had an inspection by the consumer authority, they have checked with a known weight the scale and the final result in the PoS, they validate the whole set is measuring fine in display and final ticket. They asked for the certificates of the scales, but they didn't say anything about the software.

I think we are mixing two different legal issues in PoS:

1. Accounting, each region has its own rules.

2. Consumers, each scale must be certificated, revised properly, measuring fine and must communicate reliably with PoS software.

Regards.

santi noreña

criptomart servicios informáticos

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by hugues - 06:50 - 3 Feb 2026

Complete Visitors List for Learning Technologies France 2026
Hi,
The pre-registered attendee list for the Learning Technologies France 2026 is now available.
It includes 14,650 contacts that may be useful for your outreach and communication plans.
Event Details:
Date: January 28-29, 2026
Venue: Paris Expo Porte de Versailles, Paris, France
List Includes:
Full Name & Email Address
Job Title & Company Name
Mobile Number (where consented)
Would you like to receive additional information about this attendee list at an exclusive price?
Please let us know if you would like to proceed:
· I’m Interested, please send me the exclusive fee and more information.
· No, thank you.
Looking forward to hearing from you.
Thanks & Regards
Bella Cooper
by "Bella Cooper" <bella.cooper.leadsphere@gmail.com> - 09:25 - 21 Jan 2026
Update weblate

Hi everyone,

I just upgraded https://translation.odoo-community.org to weblate 5.15.

I could not pinpoint the root cause of recent instabilities, so I hope the upgrade will resolve the issue. If not, I'll dig deeper.

Best regards,

-Stéphane

by Stéphane Bidoul - 06:56 - 18 Jan 2026
addon name length limit for weblate

Hi everyone,

While investigating weblate issues I found that the component names are limited to 100 characters.

I don't think there is a workaround for that so at the moment the component generator is skipping them.

If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.

Best regards,

-Stéphane

by Stéphane Bidoul - 05:56 - 18 Jan 2026
4 replies 4 replies
Re: addon name length limit for weblate

Component length is defined as a constant in https://github.com/WeblateOrg/weblate/blob/main/weblate/trans/defines.py
COMPONENT_NAME_LENGTH = 100

Since Weblate is a django application:
python manage.py makemigrations
python manage.py migrate
should be enough to fix the issue

The main drawback is that it should be reapplied after each update

--
Yann PAPOUIN

Le dim. 18 janv. 2026 à 19:56, Moises Lopez <notifications@odoo-community.org> a écrit :
Excellent!

Check the following new check:
- https://github.com/OCA/odoo-pre-commit-hooks/pull/175

And the following dummy PR to test it:
- https://github.com/OCA/stock-logistics-release-channel/pull/49

El dom, 18 ene 2026 a la(s) 11:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:
Hi Moises,

Nice!

Here is the one that caused problem: stock-logistics-release-channel-18.0-sale_stock_release_channel_delivery_date_plan_shipment_lead_time

Best regards,

-Stéphane

On Sun, Jan 18, 2026 at 6:41 PM Moises Lopez <notifications@odoo-community.org> wrote:
Hi Stéphane,

I can do the linter.

Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?

El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:
Hi everyone,

While investigating weblate issues I found that the component names are limited to 100 characters.

I don't think there is a workaround for that so at the moment the component generator is skipping them.

If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.

Best regards,

-Stéphane

_______________________________________________
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

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Yann Papouin - 05:36 - 19 Jan 2026

Re: addon name length limit for weblate

Excellent!

Check the following new check:
- https://github.com/OCA/odoo-pre-commit-hooks/pull/175

And the following dummy PR to test it:
- https://github.com/OCA/stock-logistics-release-channel/pull/49

El dom, 18 ene 2026 a la(s) 11:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:
Hi Moises,

Nice!

Here is the one that caused problem: stock-logistics-release-channel-18.0-sale_stock_release_channel_delivery_date_plan_shipment_lead_time

Best regards,

-Stéphane

On Sun, Jan 18, 2026 at 6:41 PM Moises Lopez <notifications@odoo-community.org> wrote:
Hi Stéphane,

I can do the linter.

Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?

El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:
Hi everyone,

While investigating weblate issues I found that the component names are limited to 100 characters.

I don't think there is a workaround for that so at the moment the component generator is skipping them.

If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.

Best regards,

-Stéphane

_______________________________________________
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 Moisés López Calderón - 07:56 - 18 Jan 2026

Re: addon name length limit for weblate

Hi Moises,

Nice!

Here is the one that caused problem: stock-logistics-release-channel-18.0-sale_stock_release_channel_delivery_date_plan_shipment_lead_time

Best regards,

-Stéphane

On Sun, Jan 18, 2026 at 6:41 PM Moises Lopez <notifications@odoo-community.org> wrote:
Hi Stéphane,

I can do the linter.

Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?

El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:
Hi everyone,

While investigating weblate issues I found that the component names are limited to 100 characters.

I don't think there is a workaround for that so at the moment the component generator is skipping them.

If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.

Best regards,

-Stéphane

_______________________________________________
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 Stéphane Bidoul - 06:56 - 18 Jan 2026

Re: addon name length limit for weblate

Hi Stéphane,

I can do the linter.

Could you share me the result of a "addon_component_name" in order to know what words are considered (team/repo or only repo)?

El dom, 18 ene 2026 a la(s) 10:57 a.m., Stéphane Bidoul (notifications@odoo-community.org) escribió:
Hi everyone,

While investigating weblate issues I found that the component names are limited to 100 characters.

I don't think there is a workaround for that so at the moment the component generator is skipping them.

If anyone feels like implementing a linter for addon names length this could be helpful. For weblate the addon name + repo name should not be over 90 characters or so.

Best regards,

-Stéphane

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Moisés López Calderón - 06:40 - 18 Jan 2026
OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth

Hello dear OCA members and contributors,

I hope 2026 is starting good for you, your business and your families!

I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/

It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.

It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!

For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.

I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)

Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.

Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

I'll get in touch with the volunteers a bit before the event starts.

Have a nice week, everyone!

--

by Konsilia SRL - 03:40 - 18 Jan 2026

1 attachments 1 attachments

Logo-no-IAg.jpg
4 replies 4 replies
Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth

Hello everyone,

This is a reminder in case you come to FOSDEM this weekend, come and see us at the OCA booth (F-02)!

And if you can join and spare 1 or 2 hours with us, please add your name here:

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

Have a nice end of week,

Virginie

Le 18/01/26 à 15:37, Virginie Dewulf a écrit :

Hello dear OCA members and contributors,

I hope 2026 is starting good for you, your business and your families!

I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/

It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.

It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!

For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.

I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)

Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.

Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

I'll get in touch with the volunteers a bit before the event starts.

Have a nice week, everyone!

--

--

by Konsilia SRL - 10:51 - 29 Jan 2026

1 attachments 1 attachments

Logo-no-IAg.jpg

Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth

Hello,

Please people fill the spreadsheet with the hours you can help at the OCA booth!

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

Virginie: might it help if the granularity is one hour shifts, so it will be easier for people to put in a shift between talks they want to attend?

Kind regards, Ronald

On 18-01-2026 15:42, Virginie Dewulf wrote:

Hello dear OCA members and contributors,

I hope 2026 is starting good for you, your business and your families!

I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/

It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.

It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!

For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.

I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)

Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.

Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

I'll get in touch with the volunteers a bit before the event starts.

Have a nice week, everyone!

--

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Ronald Portier - 03:36 - 22 Jan 2026

Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth

Hi,

I scrapped one session to at least do one full two hour shift.

Kind regards, Ronald

On 21-01-2026 15:51, Ronald Portier wrote:

Hi Virginie,

I will be attending FOSDEM, and would like to help at the booth. Only there are also a lot

of talks I would like to attend, not leaving any two hour gap.

But I can help on Saturday afternoon from 17:00 to 18:00 (in between PyInfra and sovereign digital workplace). And Sunday morning from opening to about 10:20 (after that going to the GnuPG talk). And Sunday afternoon from 15:45 to 16:45 (in between Jupyter Books and IBM 3278).

I hope that is still useful, and anyway look forward to see you and the other OCA friends!

Kind regards, Ronald

On 18-01-2026 15:42, Virginie Dewulf wrote:

Hello dear OCA members and contributors,

I hope 2026 is starting good for you, your business and your families!

I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/

It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.

It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!

For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.

I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)

Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.

Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

I'll get in touch with the volunteers a bit before the event starts.

Have a nice week, everyone!

--

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Ronald Portier - 03:35 - 22 Jan 2026

Re: OCA will be at FOSDEM (31Jan/1st Feb)--> help us on the booth

Hi Virginie,

I will be attending FOSDEM, and would like to help at the booth. Only there are also a lot

of talks I would like to attend, not leaving any two hour gap.

But I can help on Saturday afternoon from 17:00 to 18:00 (in between PyInfra and sovereign digital workplace). And Sunday morning from opening to about 10:20 (after that going to the GnuPG talk). And Sunday afternoon from 15:45 to 16:45 (in between Jupyter Books and IBM 3278).

I hope that is still useful, and anyway look forward to see you and the other OCA friends!

Kind regards, Ronald

On 18-01-2026 15:42, Virginie Dewulf wrote:

Hello dear OCA members and contributors,

I hope 2026 is starting good for you, your business and your families!

I am happy to share that the OCA will be officially represented for the first time during the biggest open source event in the world, the well known FOSDEM. If you don't know about it, you'll find more about it here : https://fosdem.org/2026/

It's in Brussels (Belgium), on Saturday 31st January and Sunday 1st February.

It's a great experience, even if you are not a developer. I've been attending this event for many years and it's something to see once in your life: the city of Brussels become full of geeks and open source enthusiasts. The event takes place in the university (ULB) in many different rooms in 6 different buildings. It's also a good way to take your 10.000 steps a day ;) I particularly appreaciate the Community Dev Room, as well as the "Funding the FOSS ecosystem" Dev Room. There is a Python Dev Room, topics about Securyity, Performance, Testing... so many interesting things to learn!

For the first time, the OCA will be at FOSDEM with a booth (a stand), located in " F-02" together with Dolibarr ERP CRM.

I am looking for volunteers to help on the booth. That means: you need to be there for one or more shifts of 2h and talk to people who ask questions about Odoo, the OCA and open source ERP in general. We are already a small bunch of people (I can name hugues from Coop IT Easy, Sébastien Beau and Benoit Guillot from Akretion France, and even a developer working at Odoo, Stéphane Bidoul might join for a bit on Sunday.. and you?!)

Even if you are new in the community, your perspective will be good to share at the booth. No need to be an old-timer to come and help. It's also a nice way to meet other people of the community in real life.

Julie helped me set up this shared document so that you can indicate when you are happy to join the booth:

https://docs.google.com/spreadsheets/d/1xmOLcXD1uG3TvIXDs4X7wx9_I9-nmR5kCP5uTG6uVVo/edit?gid=0#gid=0

I'll get in touch with the volunteers a bit before the event starts.

Have a nice week, everyone!

--

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Ronald Portier - 03:55 - 21 Jan 2026
Odoo Community Association Stats

Hello,

During the last years, I have made the extraction of the stats for the community that have been shared.

Originally, I extracted the data manually, later on, I used a process that pushed all data to an Elastic search. Finally, on christmas I made a small personal project for porting all the logic to Odoo.

You can see the final results on the following repository:

https://github.com/OCA-contributors/contributors-module/pull/1

Anyways, I think this modules should be inside OCA as it has sense to use it (it can be used by any organization using github). Would be useful to port the repository directly to OCA with contributors-stats name. WDYT?

Also, anyone can make their own dashboard with OCA data or any other organization using the provided code.

If anyone is interested, I can share the link I am using with a public site with the information (is under invitation, as I am still making changes)

Kind regards

--
Enric Tobella Alomar
CEO & Founder

www.dixmit.com

by Enric Tobella Alomar - 06:46 - 15 Jan 2026
3 replies 3 replies
Re: Odoo Community Association Stats

Dear Enric,

That's great! Indeed, I +1 to push your repository under OCA umbrella.

Many thanks

Le jeu. 15 janv. 2026 à 18:47, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :
Hello,

During the last years, I have made the extraction of the stats for the community that have been shared.

Originally, I extracted the data manually, later on, I used a process that pushed all data to an Elastic search. Finally, on christmas I made a small personal project for porting all the logic to Odoo.

You can see the final results on the following repository:

https://github.com/OCA-contributors/contributors-module/pull/1

Anyways, I think this modules should be inside OCA as it has sense to use it (it can be used by any organization using github). Would be useful to port the repository directly to OCA with contributors-stats name. WDYT?

Also, anyone can make their own dashboard with OCA data or any other organization using the provided code.

If anyone is interested, I can share the link I am using with a public site with the information (is under invitation, as I am still making changes)

Kind regards

--
Enric Tobella Alomar
CEO & Founder

www.dixmit.com

_______________________________________________
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. - 09:10 - 16 Jan 2026

Re: Odoo Community Association Stats

Great job Enric, thank you :D

Recuerda visitar nuestro blog para ver contenido gratuito de calidad.

Valentín Vinagre Urteaga
CTO
Sygel Technology S.L

+34 613 04 66 67
valentin.vinagre@sygel.es
https://www.sygel.es
C/ Àlaba 61, 5ª planta, 08005, Barcelona

El El vie, 16 ene 2026 a las 0:02, Julie LeBrun <julie@odoo-community.org> escribió:
Great work Enric! So eager to use it! Thank you very much!

Le jeu. 15 janv. 2026 à 12:48, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :
Hello,

During the last years, I have made the extraction of the stats for the community that have been shared.

Originally, I extracted the data manually, later on, I used a process that pushed all data to an Elastic search. Finally, on christmas I made a small personal project for porting all the logic to Odoo.

You can see the final results on the following repository:

https://github.com/OCA-contributors/contributors-module/pull/1

Anyways, I think this modules should be inside OCA as it has sense to use it (it can be used by any organization using github). Would be useful to port the repository directly to OCA with contributors-stats name. WDYT?

Also, anyone can make their own dashboard with OCA data or any other organization using the provided code.

If anyone is interested, I can share the link I am using with a public site with the information (is under invitation, as I am still making changes)

Kind regards

--
Enric Tobella Alomar
CEO & Founder

www.dixmit.com

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--
Julie LeBrun
Executive Director, Content Creator & Training Manager
Odoo Community Association (OCA)
GitHub : https://github.com/TumbaoJu

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Valentín Vinagre - 08:41 - 16 Jan 2026

Re: Odoo Community Association Stats

Great work Enric! So eager to use it! Thank you very much!

Le jeu. 15 janv. 2026 à 12:48, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :
Hello,

During the last years, I have made the extraction of the stats for the community that have been shared.

Originally, I extracted the data manually, later on, I used a process that pushed all data to an Elastic search. Finally, on christmas I made a small personal project for porting all the logic to Odoo.

You can see the final results on the following repository:

https://github.com/OCA-contributors/contributors-module/pull/1

Anyways, I think this modules should be inside OCA as it has sense to use it (it can be used by any organization using github). Would be useful to port the repository directly to OCA with contributors-stats name. WDYT?

Also, anyone can make their own dashboard with OCA data or any other organization using the provided code.

If anyone is interested, I can share the link I am using with a public site with the information (is under invitation, as I am still making changes)

Kind regards

--
Enric Tobella Alomar
CEO & Founder

www.dixmit.com

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--
Julie LeBrun
Executive Director, Content Creator & Training Manager
Odoo Community Association (OCA)
GitHub : https://github.com/TumbaoJu

by Julie LeBrun (OCA) - 12:00 - 16 Jan 2026
RFC: Manual ordering of pickings in Shipment Advice (One2many)
Hello OCA contributors,

We are using shipment_advice, an OCA addon from stock-logistics-transport, which groups stock.picking records via a One2many relation.

Constraints

One Shipment Advice → many pickings

Each picking belongs to exactly one Shipment Advice

The One2many relation is core to the addon and cannot be changed

Problem
We need to implement a manual, user-defined ordering of pickings within a Shipment Advice.

Order is arbitrary

Not derived from existing fields (dates, priority, state, etc.)

Must be persistent and respected in views and business logic

Native One2many does not support manual ordering

RFC
What is the recommended Odoo/OCA pattern to:

Persist a manual order per Shipment Advice

While keeping the existing One2many relation untouched

Feel free to challenge any of the assumptions or constraints above if you see a better approach.

Thanks,

\rrebollo
by Ing. Rolando Pérez Rebollo - 02:50 - 14 Jan 2026
1 replies 1 replies
Re: RFC: Manual ordering of pickings in Shipment Advice (One2many)

Hello rrebollo,

As you created an issue, here is the link for anyone that would like to comment on this

https://github.com/OCA/stock-logistics-transport/issues/206

kr
J-E

Le mer. 14 janv. 2026 à 14:52, Rolando Pérez Rebollo <notifications@odoo-community.org> a écrit :

Hello OCA contributors,

We are using shipment_advice, an OCA addon from stock-logistics-transport, which groups stock.picking records via a One2many relation.

Constraints

One Shipment Advice → many pickings

Each picking belongs to exactly one Shipment Advice

The One2many relation is core to the addon and cannot be changed

Problem
We need to implement a manual, user-defined ordering of pickings within a Shipment Advice.

Order is arbitrary

Not derived from existing fields (dates, priority, state, etc.)

Must be persistent and respected in views and business logic

Native One2many does not support manual ordering

RFC
What is the recommended Odoo/OCA pattern to:

Persist a manual order per Shipment Advice

While keeping the existing One2many relation untouched

Feel free to challenge any of the assumptions or constraints above if you see a better approach.

Thanks,

\rrebollo

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Jacques-Etienne Baudoux - 03:41 - 14 Jan 2026
OCA weblate has 502 error.

When I try to access OCA Weblate (https://translation.odoo-community.org), 502 error occurs.
If you have time, I’d appreciate it if you could fix it.

--
重信俊公 Toshikimi Shigenobu
コタエル株式会社 / Quartile
Phone: +81-92-707-3087
nobu@quartile.co
https://www.quartile.co

by Toshikimi Shigenobu - 07:10 - 13 Jan 2026
1 replies 1 replies
Re: OCA weblate has 502 error.

+1. Been down also before christmas, not sure if the downtime is since then.

On 1/13/2026 7:12 AM, Toshikimi Shigenobu wrote:

When I try to access OCA Weblate (https://translation.odoo-community.org), 502 error occurs.
If you have time, I’d appreciate it if you could fix it.

--

重信俊公 Toshikimi Shigenobu

コタエル株式会社 / Quartile

Phone: +81-92-707-3087

nobu@quartile.co

https://www.quartile.co

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

Jan-Marten Veddeler
+49 15158887067
j.veddeler@humanilog.org
linkedin.com/in/jmveddeler
Berlin | Germany

Humanitarian Logistics Organisation e.V. | Humanilog
Tel.: Zentrale +49 40228686750
Post: Winsbergring 2 | 22525 Hamburg | Germany
Büro: Schnackenburgallee 11 | 22525 Hamburg | Germany

www.humanilog.org

Gemeinsam können wir mehr erreichen.
Unterstützen Sie uns: humanilog.org/spenden

by Jan-Marten Veddeler. - 02:00 - 13 Jan 2026
Question about PR contribution rules
Hi all, question - I've been told several times on OCA PR's that any PR should satisfy the following rules: 1. It needs to deal with only one module at a time, otherwise it should be split up 2. It needs to deal with one change only, otherwise it should be split up 3. It needs to be in one commit (unless there is good reason to have several commits, eg multiple authors or separating pre-commit from functional changes) However, I can't find these rules in our contribution guidelines: https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#review Can someone point me to where this is written? Or is this not formalized and subject to PSC preference? -Tom
by Tom Blauwendraat - 01:46 - 5 Jan 2026
2 replies 2 replies
Re: Question about PR contribution rules

Hi, Tom, I think you are trying to make a gold thumb rule out of context of all the things people told you in the PRs.

There aren't hard-written rules, as this depends on the context and the things you are doing. It may be good to set use cases on the contribution guidelines for those possibilities, but others also said in the past that the contribution guidelines are very long and hard for adding more things...

In general, common sense should prevail, and more if you want the PR to be accepted. Put it easy to the reviewers! If the changes are a logical set, put it in one PR. Don't mix in a PR a module migration with other improvements, unless they are justified due to the version change. Don't put several unrelated improvements/fixes in the same PR for easing the reviewing/merging. Is this last one mandatory? No, you can pack them in several commits in the same PR, but then, that implies more effort for the reviewers to check it, so less chances to get it merged. What is not allowed (implicitly) is to mix in just one commit several unrelated things.

And the contrary case: when you are splitting one logical set into several commits because it follows your development flow, committing little changes of several few lines, then you are asked to squash together those commits, as split they make no sense when you are reviewing/blaming the commit history.

Please specify the links of such specific PRs to put the comments in context, but I have tried to make an overall landscape, and the summary is that... it depends on the context, hehe.

Regards.

by Pedro M. Baeza - 02:25 - 5 Jan 2026

Re: Question about PR contribution rules

Hello Tom,

1. -> I would say it should. This depends on:

- If both modules should be bumped differently (e.g.: one patch and one minor), they should be split in different PR's.
- Changes in modules should be grouped per module in PR's commits.

2. -> It can be done in the same PR if atomic (and/or functional) changes have been grouped in separate commits.

3. -> This is not mandatory IMHO, as said above, changes are grouped in separate commits (See: https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#commit-message)

It's not written explicitly as it is linked to general development flows with git apart for the bump flow with ocabot. I would say it is maybe easier to understand for newcomers (the one thing for all) but should not be enforced like that.

My two cents

Le lun. 5 janv. 2026 à 13:47, Tom Blauwendraat <notifications@odoo-community.org> a écrit :
Hi all, question - I've been told several times on OCA PR's that any PR should satisfy the following rules: 1. It needs to deal with only one module at a time, otherwise it should be split up 2. It needs to deal with one change only, otherwise it should be split up 3. It needs to be in one commit (unless there is good reason to have several commits, eg multiple authors or separating pre-commit from functional changes) However, I can't find these rules in our contribution guidelines: https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#review Can someone point me to where this is written? Or is this not formalized and subject to PSC preference? -Tom

_______________________________________________
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. - 02:06 - 5 Jan 2026
mis_builder_budget 16.0 and analytic accounts

hello,

i don’t know much about mis_builder and mis_builder_budget, but i’m upgrading a database to 16.0 which has multiple mis.budget.item records for the same budget and the same kpi, but different analytic accounts. in 16.0, the analytic_account_id field has been removed and the model restricts creating multiple similar lines (since that field was the only difference between them).

how am i supposed to change the data to have the same results as before? is this documented somewhere maybe?

kind regards,

hugues de keyzer

by hugues - 10:01 - 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 4406

Offices:
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

by Jorge Elena Poblet - 08:45 - 18 Dec 2025

5 replies 5 replies

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:

Hi all,

I see this: https://github.com/OCA/connector/pull/512

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 4406

Offices:
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

Web: https://opendigital.cc

IM: xmpp: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

Web: https://opendigital.cc

IM: xmpp: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

Open Digital Consulting Co Logo

UK: +44 20 36 27 90 40

FR: +33 1 89 48 00 40

Email: sjm@opendigital.cc

Web: https://opendigital.cc

IM: xmpp:sjm@opendigital.cc

by Stuart J Mackintosh - 04:30 - 28 Dec 2025

1 attachments 1 attachments

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:

Hi all,

I see this: https://github.com/OCA/connector/pull/512

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 4406

Offices:
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

Web: https://opendigital.cc

IM: xmpp: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

Web: https://opendigital.cc

IM: xmpp: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:

Hi all,

I see this: https://github.com/OCA/connector/pull/512

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 4406

Offices:
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

Web: https://opendigital.cc

IM: xmpp: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

Open Digital Consulting Co Logo

UK: +44 20 36 27 90 40

FR: +33 1 89 48 00 40

Email: sjm@opendigital.cc

Web: https://opendigital.cc

IM: xmpp:sjm@opendigital.cc

by Stuart J Mackintosh - 08:40 - 19 Dec 2025

1 attachments 1 attachments

Re: Amazon connector

Hi all,

I see this: https://github.com/OCA/connector/pull/512

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 4406

Offices:
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

Web: https://opendigital.cc

IM: xmpp: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 4406

Offices:
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

Open Digital Consulting Co Logo

UK: +44 20 36 27 90 40

FR: +33 1 89 48 00 40

Email: sjm@opendigital.cc

Web: https://opendigital.cc

IM: xmpp:sjm@opendigital.cc

by Stuart J Mackintosh - 07:56 - 19 Dec 2025

1 attachments 1 attachments

Odoo développement

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

by Oa.akhssassi - 12:30 - 18 Dec 2025
1 replies 1 replies
Re: Odoo développement

Hello Oumayma!
Welcome to our community! Did you know you can become an OCA member?
https://odoo-community.org/get-involved/become-a-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 LeBrun
Executive Director, Content Creator & Training Manager
Odoo Community Association (OCA)
GitHub : https://github.com/TumbaoJu

by Julie LeBrun (OCA) - 03:55 - 18 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
https://odoo-community.org/get-involved/become-a-member
subscribe to the Newsletter
https://odoo-community.org/
subscribe to specific mailing lists
https://odoo-community.org/groups

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 LeBrun
Executive Director, Content Creator & Training Manager
Odoo Community Association (OCA)
GitHub : https://github.com/TumbaoJu
by Julie LeBrun (OCA) - 05:15 - 15 Dec 2025
Exclusive Look at the Open Source Experience 2025 Visitor List

Hi,

I hope you're doing well.

We are pleased to present an opportunity to expand your professional engagement at the Open Source Experience 2025, scheduled for 10 - 11 Dec 2025 at The Palais des Congres in Paris, Paris, France.

A verified list of 6,638 pre-registered attendees is available to support your outreach, helping you connect with industry professionals, solution providers, and potential business partners throughout the exhibition.

The list includes:

Contact information and professional emails

Company names and websites

Job titles, designations, and mobile numbers etc.

Would you be interested in receiving details about accessing the attendee list along with the fee information?

Please confirm your interest:

Yes, I'm interested, please share the exclusive fee and additional information

No, thank you

Looking forward to your response.

Thanks & Regards
Scott Andrew

by "Scott Andrew" <scott.andrew.leadsnova@gmail.com> - 12:11 - 4 Dec 2025

Implementing Real Cost

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

by Daniel Reis - 08:31 - 4 Dec 2025

7 replies 7 replies

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 Tashiro

Quartile

On 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 deMeester

Development QA

+61 3 9135 1900

+61 403 767 676

richard.demeester@willdooit.com

www.willdooit.com

WilldooIT 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 Cost
Hi 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

_______________________________________________
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

Re: Implementing Real Cost

Hi Pedro,

just to get it right / complete, even though valuation by lots i more 
precisely what most companies would use today, LIFO still isn't among 
the list of options if i am not mistaken. So companies that use this 
valuation method still have no other choice then to switch to one of the 
supported methods

- AVCO

- FIFO and

- Valuation by Lots

right? Or are you aware of any LIFO implementation

Best Frederik

Am 04.12.25 um 09:02 schrieb Pedro M. Baeza:

> Odoo has implemented cost by lot in Odoo 18+, so nothing extra to do 

> except configuring it AFAIK.

>

> https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/inventory_valuation/valuation_by_lots.html

>

> Regards.

>

> _______________________________________________

> 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. - 09:21 - 4 Dec 2025

Re: Implementing Real Cost

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 deMeester

Development QA

	+61 3 9135 1900
	+61 403 767 676
	richard.demeester@willdooit.com
	www.willdooit.com

WilldooIT 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 Cost

Hi 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

_______________________________________________
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

by "Richard deMeester" <richard.demeester@willdooit.com> - 09:01 - 4 Dec 2025

12 attachments 12 attachments

Re: Implementing Real Cost

Odoo has implemented cost by lot in Odoo 18+, so nothing extra to do except configuring it AFAIK.

https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/inventory_valuation/valuation_by_lots.html

Regards.

by Pedro M. Baeza - 09:01 - 4 Dec 2025

Model hr_work_entry for LATAM (RRHH)

Hello Community, I have a question that you may have already seen.

I'm currently evaluating the adoption of the hr.work.entry module in my company (inHuman Resources :), but after reviewing its workflow and features, I'm wondering if this module is primarily designed with European regulations in mind. Is it truly suitable for the Latin American work context, where time and schedule management is more flexible?

Are there any adaptations or best practices for its implementation in Latin America?

I've reviewed some documentation and the app store, and I see that there aren't many third-party modules that have customized this model.

I would greatly appreciate your help and comments.

Regards

--
Cordialmente:
Daniel Carrión
dcarrionh@est.unap.edu.pe

by DANIEL CARRION - 11:06 - 3 Dec 2025
Scrapping returned items

Hello,

I have a use case where a customer return is being processed.
A Delivery Order was shipped, and then multiple lines of that shipment were returned into a specific Returns locations.
At the return location the items are inspected, and they can be put back into stock or scraped.

Scraping is done with the Action menu option, but that works one item at a time.
If there are many items to scrap this is painful.

As it seems like a basic request, I wonder if there is any OCA feature out there allow selecting multiple items to be scraped at the same time, similar to what the Return button already does?

Thank you
Daniel

--

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

by Daniel Reis - 11:20 - 1 Dec 2025
3 replies 3 replies
Re: Scrapping returned items

Hi Daniel

Which Odoo version do you use? I think start from 17/16, there is a configuration for the domain at Locations. You have to enable the location to be "Is a Return Location".

Many thanks

On Tue, 2 Dec 2025, 14:17 Daniel Reis, <notifications@odoo-community.org> wrote:
Thank you for the suggestions Yoshi.

Changing the return location has the limitation that scrap locations are not selectable; only internal and vendor locations are.
I guess we could fudge the configuration and create a "Scrap" vendor location.
Or perhaps a customization tweaking that domain filter.

The stock_move_location is a nice suggestion for the case the above doesn't work.

/Daniel

On 02/12/2025 01:32, Yoshi Tashiro wrote:

Hello Daniel,

I tend to think the standard functionality is sufficient in 18.0/19.0. You can change the destination location in the "return" you create to turn it into a scrap transfer.

Otherwise, stock_move_location could be useful. You can create a transfer to the scrap location upon selecting quants. You can also create a dedicated operation type for this purpose.

Best regards,

--

Yoshi Tashiro

Quartile

On Tue, Dec 2, 2025 at 7:21 AM Daniel Reis <notifications@odoo-community.org> wrote:

Hello,

I have a use case where a customer return is being processed.
A Delivery Order was shipped, and then multiple lines of that shipment were returned into a specific Returns locations.
At the return location the items are inspected, and they can be put back into stock or scraped.

Scraping is done with the Action menu option, but that works one item at a time.
If there are many items to scrap this is painful.

As it seems like a basic request, I wonder if there is any OCA feature out there allow selecting multiple items to be scraped at the same time, similar to what the Return button already does?

Thank you
Daniel

--

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

_______________________________________________
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

--

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

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Lin Nur Inayati - 09:36 - 2 Dec 2025

Re: Scrapping returned items

Thank you for the suggestions Yoshi.

Changing the return location has the limitation that scrap locations are not selectable; only internal and vendor locations are.
I guess we could fudge the configuration and create a "Scrap" vendor location.
Or perhaps a customization tweaking that domain filter.

The stock_move_location is a nice suggestion for the case the above doesn't work.

/Daniel

On 02/12/2025 01:32, Yoshi Tashiro wrote:

Hello Daniel,

I tend to think the standard functionality is sufficient in 18.0/19.0. You can change the destination location in the "return" you create to turn it into a scrap transfer.

Otherwise, stock_move_location could be useful. You can create a transfer to the scrap location upon selecting quants. You can also create a dedicated operation type for this purpose.

Best regards,

--

Yoshi Tashiro

Quartile

On Tue, Dec 2, 2025 at 7:21 AM Daniel Reis <notifications@odoo-community.org> wrote:

Hello,

I have a use case where a customer return is being processed.
A Delivery Order was shipped, and then multiple lines of that shipment were returned into a specific Returns locations.
At the return location the items are inspected, and they can be put back into stock or scraped.

Scraping is done with the Action menu option, but that works one item at a time.
If there are many items to scrap this is painful.

As it seems like a basic request, I wonder if there is any OCA feature out there allow selecting multiple items to be scraped at the same time, similar to what the Return button already does?

Thank you
Daniel

--

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

_______________________________________________
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

--

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

by Daniel Reis - 08:15 - 2 Dec 2025

Re: Scrapping returned items

Hello Daniel,

I tend to think the standard functionality is sufficient in 18.0/19.0. You can change the destination location in the "return" you create to turn it into a scrap transfer.

Otherwise, stock_move_location could be useful. You can create a transfer to the scrap location upon selecting quants. You can also create a dedicated operation type for this purpose.

Best regards,
--
Yoshi Tashiro
Quartile

On Tue, Dec 2, 2025 at 7:21 AM Daniel Reis <notifications@odoo-community.org> wrote:
Hello,

I have a use case where a customer return is being processed.
A Delivery Order was shipped, and then multiple lines of that shipment were returned into a specific Returns locations.
At the return location the items are inspected, and they can be put back into stock or scraped.

Scraping is done with the Action menu option, but that works one item at a time.
If there are many items to scrap this is painful.

As it seems like a basic request, I wonder if there is any OCA feature out there allow selecting multiple items to be scraped at the same time, similar to what the Return button already does?

Thank you
Daniel

--

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

_______________________________________________
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 - 01:31 - 2 Dec 2025
Only 2 seats available for the Runboat training!

Dear contributors!
If you want to install Runboat in your organization, register to an hands-on training with Stéphane Bidoul next week!

Hurry! Only 2 seats available!

⏰ December 3, 2025 from 1h00 to 4h00 pm UTC

Registration, testimonials and more info: https://odoo-community.org/event/online-training-installing-runboat-in-your-organization-high-level-overview-2025-12-03-196/register

by Julie LeBrun (OCA) - 03:59 - 28 Nov 2025

1 attachments 1 attachments

December 3- Runboat training.png
Open Source Experience Visitor List

Greetings Exhibitor,

Checking back to see if you’d like the Open Source Experience 2025 attendee list.

The event, held 10 - 11 Dec 2025 in The Palais des Congres in Paris, Paris, France gathered 5,356 registrants, and we have each one’s full contact info.

Let me know if you’d like to use this list for your next digital push!

Thanks & Regards,

Debra

by "Debra Richman" <debra.richmaan@gmail.com> - 07:46 - 28 Nov 2025

Archives

Contributors

Valentín Vinagre Urteaga