Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
2 Odpowiedzi
3110 Widoki

Hi,


We have a client who is into multiple verticals i.e. Salon, Retail Apparel and Restaurant. However, legally he has one entity in which he wants to maintain the accounting.


The challenge is that each vertical has requirements of specific modules which if we use one database and multi companies then would impact all the companies and messes up i.e. if a salon-specific module is installed then it would unwantedly impact the Apparel and Restaurant companies and vice a versa.


So, what is the best practice for such scenarios?


Regards,

Burhan

Awatar
Odrzuć
Najlepsza odpowiedź

Maybe the "Multi-DB Synchronization" from "Serpent" is helpful?

https://apps.odoo.com/apps/modules/12.0/base_synchro/

Awatar
Odrzuć
Najlepsza odpowiedź

The question has many answers, here is my first impression of a suitable solution:

Your client may use one database with several clients setup as "Child" companies.  This provides your client with a single set of  accounting reports at year-end while allowing each vertical to be fully independent otherwise.

Each Vertical may simply ignore any modules they do not require.  If you are customizing, then simply do not customize any original code; always create a unique module that may inherit from the original.

For custom modules, my first thought is a top-level menu item for each vertical.  Users of each vertical will belong to a group, that group will have permission to SEE only the menus that they are authorized to use.  So "Restaurant" menu is visible only to "group_restaurant" staff.

Each module will have similar permissions and so each user will see only the modules and menus that their group allows.

Awatar
Odrzuć
Powiązane posty Odpowiedzi Widoki Czynność
1
kwi 21
4399
1
sty 20
6036
0
kwi 15
4247
2
sie 25
631
2
sie 25
320