Brands or subdivisions

We’ve got several customers that have several brands under the same company. They want their invoices to have a distinctive logo depending on the brand being used.

We’ve usually solved that with the sale_shop module or some hack but I’d like to know how others are solving this requirement.

I’m thinking that it may be interesting to have a “company.subdivision” or “company.brand”, that could be specified in sales (and invoices) and that prevented sales from different subdivisions be grouped in the same invoice.

Then, we could set the logo at this subdivision/brand model.

Opinions?

Hi Albert,

we solved likewise problems until now with multi-company. Several brands under one company didn’t occur to me until now. Usually there are more items to customize per brand, last not least the whole accounting stuff has to be done per brand. For me it is typical use case of multi-company.

That’s not the case in the customers we have. At most, they have analytic accounts to have some information about the different business lines.

One of our customers already has several companies in the system but also one of them has several brands :slight_smile:

I think we are missing a distinction within the company model. Indeed there could be two concepts for the company. The first is the one used for the accounting which ensure that all accounting entries are registered under the same chart of account. And the second is the one under which operations like sale, purchase etc. are done. The last one is of course linked to a unique accounting company.

I’m not sure how we could make evolve the current design to include this distinction. I see some options:

  • Add a type (“accounting”, "view’) on the company. For view company a link to an accounting one is required. So for document posted with a view company, the accounting linked company is used to make the entries.
    The disadvantages are no constraint at DB level for the company link in account, user may not see easily which kind of company it is, it can become complicate to write rules.
  • Replace the currency company field on the document for a new one link to a new sub-model of company (e.g. business unit).
    The disadvantages are many schema and code changes, invoice should have both field probably.
  • Add a new field next to company on most of the operational documents.
    The disadvantages are a complex setup for simple use case.