Skip to Content

Contributors

Multiple customers on Purchase Orders

Hello,


I am dealing with a scenario where 2 sister companies share parts of their operations and make purchase orders together with split ratio between them. The way they do it is 3-party agreements, where there are 2 customers and 1 supplier and for purchase orders there are instructions for suppliers on how to split the invoicing (i.e. the supplier sends 2 separate invoices - each to individual company according to the split ratio).


Anyone faced anything similar? I am thinking of using 2 companies to model it and tinkering with visibility in each according to split. Because where there is a split, they want to see the document in both. Where there is not (it belongs to single company), should ony be visible there. However how to model in a best way that there should be 2 customers (maybe more for future extensions) on each document?


Any advice is highly welcome. Thank you very much.


Best regards


    Radovan Skolnik


by Radovan Skolnik - 12:06 - 23 Sep 2024

Follow-Ups

  • Re: Multiple customers on Purchase Orders

    Thanks Holger,


    the idea of "consortium" instead of trying to put multiple customers into PO is a good one and also naturally extendable beyond more than 2 companies.


    Best regards


        Radovan


    On pondelok 23. septembra 2024 12:37:45 CEST Holger Brunn wrote:

    > > Anyone faced anything similar? I am thinking of using 2 companies to model

    > > it and tinkering with visibility in each according to split. Because where

    > > there is a split, they want to see the document in both. Where there is

    > > not

    > > (it belongs to single company), should ony be visible there. However how

    > > to

    > > model in a best way that there should be 2 customers (maybe more for

    > > future

    > > extensions) on each document?

    >

    > I have a customer with a similar requirement the other way around, where

    > multiple suppliers invoice the same customer:

    > https://github.com/tosccolors/vertical-professional-services/tree/16.0/

    > ps_partner_multi_relation

    > They solved this by defining a partner relation "consortium", and every time

    > an invoice for a consortium partner is posted, this invoice is split by the

    > weights ("distribution key") on the consortium relation and new invoices

    > are created for the involved partners.

    > This concept should extend quite naturally to the purchase side, where you

    > split the supplier invoices and deliveries according to the distribution key

    > on the partner relation.

    > --

    > Your partner for the hard Odoo problems

    > https://hunki-enterprises.com

    > _______________________________________________

    > Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

    > Post to: mailto:contributors@odoo-community.org

    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

    >

    >

    >

    > [1] https://odoo-community.org/groups/contributors-15

    > [2] https://odoo-community.org/groups?unsubscribe




    by Radovan Skolnik - 02:46 - 23 Sep 2024
  • Re: Multiple customers on Purchase Orders
    > Anyone faced anything similar? I am thinking of using 2 companies to model
    
    > it and tinkering with visibility in each according to split. Because where
    
    > there is a split, they want to see the document in both. Where there is not
    
    > (it belongs to single company), should ony be visible there. However how to
    
    > model in a best way that there should be 2 customers (maybe more for future
    
    > extensions) on each document?
    
    I have a customer with a similar requirement the other way around, where 
    multiple suppliers invoice the same customer:
    https://github.com/tosccolors/vertical-professional-services/tree/16.0/
    ps_partner_multi_relation
    
    They solved this by defining a partner relation "consortium", and every time an 
    invoice for a consortium partner is posted, this invoice is split by the 
    weights ("distribution key") on the consortium relation and new invoices are 
    created for the involved partners.
    
    This concept should extend quite naturally to the purchase side, where you 
    split the supplier invoices and deliveries according to the distribution key 
    on the partner relation.
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    by Holger Brunn - 12:32 - 23 Sep 2024