Custom catalog projects become difficult when every exception creates another customer group. A cleaner model uses reusable catalogs for shared assortments, direct customer assignments for account contracts, direct product relations for small exceptions, and store views only where the storefront truly changes the result.
Start with reusable catalogs
A named catalog should represent a recognizable product set: dealer equipment, approved spare parts, a regional range, or a service portfolio. Assign the same catalog to every buyer who needs that set. Copying a catalog is useful when a new assortment begins mostly the same but will be maintained independently.
Avoid one catalog per customer when many customers share the same products. That creates unnecessary records and makes future SKU changes repetitive.
Use customer groups for broad segments
Customer-group assignment works well when membership already reflects access. Examples include wholesalers, certified partners, and service centers. The catalog follows the customer's current group.
Groups are less suitable for a single negotiated exception. Moving one account into a new group can also affect tax, prices, promotions, payment methods, or other extensions that use the same Magento group.
Use direct customer assignment for key accounts
Direct assignment gives one account a catalog without changing its group. A customer can receive catalogs through both direct and group relations. SoftwareSilo combines the effective product sets rather than forcing the administrator to choose only one route.
Document why the direct relation exists. Otherwise an assortment may look surprising months later when the customer's group appears to explain only part of it.
Use direct products for small exceptions
One product for one customer does not justify a new catalog. A direct customer-product relation is a better fit for a replacement part, private-label SKU, trial item, or legacy contract line.
If the exception list grows, promote it into a named catalog. The threshold is operational rather than technical: choose the model that another administrator can understand and update safely.
Global and store-view assignments
SoftwareSilo stores customer, group, and direct product relations with a store ID. Store ID zero is global. A store-specific relation takes precedence for the same context, while the global relation acts as fallback when no specific relation exists.
Use store scope for genuine differences such as country storefronts, brands, or legal ranges. Do not duplicate identical relations per store. That adds maintenance without changing the result.
A simple governance table
| Business rule | Assignment to use |
|---|---|
| Many accounts share one range | Customer group to catalog |
| One account has a full negotiated range | Customer to catalog |
| One account needs a few extra SKUs | Direct customer products |
| One storefront differs from all others | Store-view relation |
| Parent company and employees need separate limits | Sublogin Custom Catalog integration |
Before launch, export or document every rule owner, source identifier, store scope, and expected product count. That small inventory makes later ERP automation and support much easier.
Related product
Last reviewed: August 9, 2026.