EC Pro/HRSD - Comparative Analysis: Separate Taxonomies vs. Unified Taxonomy

NizarT — Thu, 20 Nov 2025 11:53:36 GMT

Hi everyone,

I have a choice to make with regards to whether to use a unified EC Pro taxonomy or separate taxonomies for a Customer that run through an M&A of Company1 and Company2.

I have created this table to assess both choices.

Criterion	Separate Taxonomies	Unified Taxonomy
Governance	Each portal has its own structure with distinct governance and content owners aligned to each legal entity.	Complex to manage if business rules and content owners differ. Shared governance is slower.
Scalability	Each entity manages its own content and updates. Clear RACI. Each portal can evolve at its own pace.	Every modification must be jointly validated by Company1 and Company2. High risk of blocking if the two entities diverge in needs.
Audience Targeting	Simplified targeting. Company1 users only see Company1 content, same for company2. Very low risk of audience-configuration errors.	Strong dependence on audience rules. High risk of unauthorized cross-portal content visibility.
Technical Configuration	APN synchronization triggers impact only one portal at a time.	Double impact during APN synchronization for any portal.

Please feel free to advise/comment.

Thanks,

Nizar

question EC Pro/HRSD - Comparative Analysis: Separate Taxonomies vs. Unified Taxonomy in Community Central forum

EC Pro/HRSD - Comparative Analysis: Separate Taxonomies vs. Unified Taxonomy