Skip to Content
  • 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:


    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

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


    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

    _______________________________________________
    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

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


    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

    _______________________________________________
    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

    by Julie LeBrun (OCA) - 12:00 - 16 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:


    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


    by Enric Tobella Alomar - 06:46 - 15 Jan 2026
  • 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


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

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

    by Toshikimi Shigenobu - 07:10 - 13 Jan 2026
  • 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
  • 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
  • Re: Amazon connector

    Thanks Clément.

    I have just returned from some time away hence the delay in replying.

    Have you joined the Discord channel - I understand that is where the conversation will be happening: https://discord.com/channels/737652535149592587/1453036891653017620

    Best wishes,

    Stuart.



    On 23/12/2025 15:32, Clément Mombereau wrote:
    Hi Stuart!

    I just found your email after commenting Kencove's PR earlier today.

    As I say in my comment, I already worked on a POC in 2023/2024 but I didn't have the resources to finish the project. But my main point is that it seems more efficient to avoid rewriting all the connection part (already covered by the python-amazon-sp-api library) and the importation part (theoretically covered by sale_import_base and other modules in OCA/sale-channel).

    Also it's important to make the difference between Amazon Vendor and Amazon Seller in the code with 3 modules (base/seller/vendor).

    Regards,
    Clément.

    Le ven. 19 déc. 2025 à 04:42, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :

    Thanks Denis - that's timely!

    Is the author here? It would be preferred to collaborate on that base rather than start a new project.

    Best wishes,

    Stuart.


    On 19/12/2025 08:27, Roussel, Denis wrote:

    Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :

    Hello Jorge,

    Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.

    Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.

    Best wishes,

    Stuart.


    Amazon FBM Connector - Project Summary

    One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.

    Amazon Features Enabled:

        Order import from Seller Central (SP-API Orders endpoint)
        Shipment confirmation with tracking numbers
        Order status synchronisation
        Future: Inventory feed submission

    Built On:

        python-amazon-sp-api library
        Odoo 16 Community Edition
        SP-API (replaces deprecated MWS)

    Provides in Odoo:

        Automated hourly order import from Amazon UK (expandable to other marketplaces)
        Customer deduplication across sales channels (Amazon, future eBay/Shopify)
        SKU mapping lookup table
        Shipping method mapping to Odoo carriers
        Draft sale orders with gift messages, discounts, shipping as line items
        Automatic shipment notifications to Amazon on delivery validation
        Manual backlog import with date/status filters
        Order sync state tracking and error logging

    Architecture:

        Abstracted API layer (lib/) separate from Odoo models
        Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
        Bridge model tracks Amazon ↔ Odoo order state
        Transaction-safe per-order processing with error recovery
        Test coverage per milestone



    On 18/12/2025 20:47, Jorge Elena Poblet wrote:
    Hi everyone,

    I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.

    We’re also open to collaborating or co-developing a connector if there’s shared interest.

    If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.

    Thanks in advance! 

    --
    Binhex Logo
    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

    _______________________________________________
    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

    _______________________________________________
    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
  • Re: Amazon connector
    Hi Stuart!

    I just found your email after commenting Kencove's PR earlier today.

    As I say in my comment, I already worked on a POC in 2023/2024 but I didn't have the resources to finish the project. But my main point is that it seems more efficient to avoid rewriting all the connection part (already covered by the python-amazon-sp-api library) and the importation part (theoretically covered by sale_import_base and other modules in OCA/sale-channel).

    Also it's important to make the difference between Amazon Vendor and Amazon Seller in the code with 3 modules (base/seller/vendor).

    Regards,
    Clément.

    Le ven. 19 déc. 2025 à 04:42, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :

    Thanks Denis - that's timely!

    Is the author here? It would be preferred to collaborate on that base rather than start a new project.

    Best wishes,

    Stuart.


    On 19/12/2025 08:27, Roussel, Denis wrote:

    Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :

    Hello Jorge,

    Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.

    Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.

    Best wishes,

    Stuart.


    Amazon FBM Connector - Project Summary

    One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.

    Amazon Features Enabled:

        Order import from Seller Central (SP-API Orders endpoint)
        Shipment confirmation with tracking numbers
        Order status synchronisation
        Future: Inventory feed submission

    Built On:

        python-amazon-sp-api library
        Odoo 16 Community Edition
        SP-API (replaces deprecated MWS)

    Provides in Odoo:

        Automated hourly order import from Amazon UK (expandable to other marketplaces)
        Customer deduplication across sales channels (Amazon, future eBay/Shopify)
        SKU mapping lookup table
        Shipping method mapping to Odoo carriers
        Draft sale orders with gift messages, discounts, shipping as line items
        Automatic shipment notifications to Amazon on delivery validation
        Manual backlog import with date/status filters
        Order sync state tracking and error logging

    Architecture:

        Abstracted API layer (lib/) separate from Odoo models
        Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
        Bridge model tracks Amazon ↔ Odoo order state
        Transaction-safe per-order processing with error recovery
        Test coverage per milestone



    On 18/12/2025 20:47, Jorge Elena Poblet wrote:
    Hi everyone,

    I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.

    We’re also open to collaborating or co-developing a connector if there’s shared interest.

    If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.

    Thanks in advance! 

    --
    Binhex Logo
    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

    _______________________________________________
    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

    _______________________________________________
    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
  • 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
  • Re: Amazon connector

    Thanks Denis - that's timely!

    Is the author here? It would be preferred to collaborate on that base rather than start a new project.

    Best wishes,

    Stuart.


    On 19/12/2025 08:27, Roussel, Denis wrote:

    Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :

    Hello Jorge,

    Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.

    Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.

    Best wishes,

    Stuart.


    Amazon FBM Connector - Project Summary

    One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.

    Amazon Features Enabled:

        Order import from Seller Central (SP-API Orders endpoint)
        Shipment confirmation with tracking numbers
        Order status synchronisation
        Future: Inventory feed submission

    Built On:

        python-amazon-sp-api library
        Odoo 16 Community Edition
        SP-API (replaces deprecated MWS)

    Provides in Odoo:

        Automated hourly order import from Amazon UK (expandable to other marketplaces)
        Customer deduplication across sales channels (Amazon, future eBay/Shopify)
        SKU mapping lookup table
        Shipping method mapping to Odoo carriers
        Draft sale orders with gift messages, discounts, shipping as line items
        Automatic shipment notifications to Amazon on delivery validation
        Manual backlog import with date/status filters
        Order sync state tracking and error logging

    Architecture:

        Abstracted API layer (lib/) separate from Odoo models
        Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
        Bridge model tracks Amazon ↔ Odoo order state
        Transaction-safe per-order processing with error recovery
        Test coverage per milestone



    On 18/12/2025 20:47, Jorge Elena Poblet wrote:
    Hi everyone,

    I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.

    We’re also open to collaborating or co-developing a connector if there’s shared interest.

    If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.

    Thanks in advance! 

    --
    Binhex Logo
    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

    _______________________________________________
    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
  • Re: Amazon connector

    Le ven. 19 déc. 2025, 07:56, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :

    Hello Jorge,

    Just last week I started to spec out a connector as I have a client requirement Q1 2026. Below is a high level outline of my plan - does this align with your intentions? If so, I would be pleased to collaborate and contribute the modules to OCA.

    Additionally, I have outlined a print mechanism for shipping labels etc, although this is quite ambitious as it also addresses other areas of real-time data interactions.

    Best wishes,

    Stuart.


    Amazon FBM Connector - Project Summary

    One-line: Bidirectional Amazon Seller Central FBM integration for Odoo 16 Community Edition with order import, customer deduplication, and shipment tracking.

    Amazon Features Enabled:

        Order import from Seller Central (SP-API Orders endpoint)
        Shipment confirmation with tracking numbers
        Order status synchronisation
        Future: Inventory feed submission

    Built On:

        python-amazon-sp-api library
        Odoo 16 Community Edition
        SP-API (replaces deprecated MWS)

    Provides in Odoo:

        Automated hourly order import from Amazon UK (expandable to other marketplaces)
        Customer deduplication across sales channels (Amazon, future eBay/Shopify)
        SKU mapping lookup table
        Shipping method mapping to Odoo carriers
        Draft sale orders with gift messages, discounts, shipping as line items
        Automatic shipment notifications to Amazon on delivery validation
        Manual backlog import with date/status filters
        Order sync state tracking and error logging

    Architecture:

        Abstracted API layer (lib/) separate from Odoo models
        Lookup tables for cross-platform partner linking, SKU mapping, carrier mapping
        Bridge model tracks Amazon ↔ Odoo order state
        Transaction-safe per-order processing with error recovery
        Test coverage per milestone



    On 18/12/2025 20:47, Jorge Elena Poblet wrote:
    Hi everyone,

    I wanted to check with the community whether anyone has already developed (or is currently developing) an Amazon ↔ Odoo connector, ideally for Odoo Community.

    We’re also open to collaborating or co-developing a connector if there’s shared interest.

    If you’re maintaining something, experimenting with a POC, or would like to join forces on an open-source initiative, I’d love to connect and explore next steps together.

    Thanks in advance! 

    --
    Binhex Logo
    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

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

    --
    Binhex Logo
    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
  • 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! 

    --
    Binhex Logo
    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
  • Re: Odoo développement
    Hello Oumayma!
    Welcome to our community!  Did you know you can become an OCA member?

    Let us know if we can help you.

    Le mer. 17 déc. 2025 à 18:32, Oumayma Akhssassi <notifications@odoo-community.org> a écrit :
     Hi everyone,
    I am interesting in joining your odoo Developers community.
    I hope to integrate into this environment, lean from you, and grow technically with your support 

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



    --
    Julie LeBrun
    Executive Director, Content Creator & Training Manager

    by Julie LeBrun (OCA) - 03:55 - 18 Dec 2025
  • 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