We're building a Customized Commerce solution with two storefronts on one platform: same PIM category structure, but different product exposure per storefront and per customer/account. Products are currently imported as two catalogs — categories are catalog-specific, products/SKUs shared (linked entries).
1. Catalog strategy — single catalog with filtering, or multi-catalog (one per storefront, products linked into each)? Any pitfalls with shared entries, e.g. an import for one catalog overwriting data the other relies on?
2. Customer/account visibility — we need the same capability Configured Commerce provides through Restriction Groups, but on Customized Commerce: tier-based visibility (credit vs cash), per-account restrictions, and differences even within the same tier. We're leaning toward product-level restriction metadata plus customer-group/account filtering in Search & Navigation (rather than catalog/category access control). Is that the recommended approach, and how do people enforce it consistently across browse, search, cart, and checkout — including re-validation when the active account changes?
We're building a Customized Commerce solution with two storefronts on one platform: same PIM category structure, but different product exposure per storefront and per customer/account. Products are currently imported as two catalogs — categories are catalog-specific, products/SKUs shared (linked entries).
1. Catalog strategy — single catalog with filtering, or multi-catalog (one per storefront, products linked into each)? Any pitfalls with shared entries, e.g. an import for one catalog overwriting data the other relies on?
2. Customer/account visibility — we need the same capability Configured Commerce provides through Restriction Groups, but on Customized Commerce: tier-based visibility (credit vs cash), per-account restrictions, and differences even within the same tier. We're leaning toward product-level restriction metadata plus customer-group/account filtering in Search & Navigation (rather than catalog/category access control). Is that the recommended approach, and how do people enforce it consistently across browse, search, cart, and checkout — including re-validation when the active account changes?
Thanks in advance