How a B2B Distributor Managed Product Attribute Visibility

Product attributes in Magento are widely used to store important data about wholesale costs, suppliers, pack sizes, pallet quantities, margin classes, warehouse information, and internal notes.

However, not all of this information is necessarily intended for retail customers — or even for every B2B customer.

For stores serving several types of customers, this creates a practical problem: different customer groups may need access to different sets of product information.

A large industrial supplies distributor faced exactly this challenge and used the Customer Group Permissions module by Mageside to create more granular control over product attribute visibility for different customer groups.

Background

The distributor was working with over 12,000 SKUs and used product attributes extensively for logistics, pricing, and classification purposes.

The website targeted three different audiences:

• Public retail customers — small businesses and individuals buying at regular prices;
• Approved B2B customers — companies with negotiated pricing and additional purchasing requirements;
• Internal buyers & partners — distributors and procurement teams that needed access to additional operational data.

The challenge was that the Magento product catalog contained attributes intended for different purposes and audiences.

Some attributes were useful for every customer.

Others contained operational, wholesale, supplier, or internal information that the distributor did not want to make available to every customer group.

This created a risk of exposing internal information and could also cause unnecessary confusion for customers.

The distributor needed more granular customer-group-based control over product attribute visibility.

To address this, the company implemented Customer Group Permissions.

The Problem

Several practical problems had to be addressed.

1. Internal attributes were not intended for retail customers

   The Magento catalog contained attributes used internally for logistics, supplier management, pricing, and product classification.

   Retail customers did not need to see information such as internal cost-related fields, supplier codes, or margin-related metadata.

   Showing unnecessary internal information could make the product experience more confusing and potentially expose business information that was not intended for that audience.

2. B2B customers needed more information than retail customers

   The opposite problem existed for approved B2B customers.

   These customers could need operational information that was not relevant to a regular retail shopper.

   For example, pack sizes, minimum order quantities, or lead times may be useful when a business customer is planning a larger purchase.

   Simply showing the same set of attributes to every customer group therefore did not reflect the actual information needs of the store.

3. Internal users needed access to additional product data

   Internal buyers, partners, and procurement teams could require an even broader set of information.

   Supplier codes, internal logistics fields, warehouse information, and other operational attributes may be useful for these users while remaining unnecessary for external customers.

   The distributor therefore needed a way to define product attribute access according to customer group.

Solution: Restrict Sensitive Attributes for Specific Customer Groups

Using Customer Group Permissions, the store created an attribute visibility structure for its different customer groups.

The module allows an administrator to restrict product attributes for selected customer groups.

This made it possible to approach product information differently for retail customers, approved B2B customers, and internal users.

A simplified permission structure could look like this:

Retail Customers — Guest + Standard Group

Visible product information could include:

• product name;
• retail price;
• description;
• dimensions;
• customer-facing technical specifications.

Restricted attributes could include:

• internal cost information;
• wholesale pricing metadata;
• MOQ-related internal fields where not intended for retail users;
• supplier codes;
• internal warehouse information;
• internal logistics data;
• margin-related metadata.

This allows the retail product experience to remain focused on information relevant to a regular buyer.

Approved B2B Customers

B2B customers may need access to additional operational information.

Depending on the business model, visible attributes could include:

• pack sizes;
• MOQ information;
• relevant product classification information;
• lead times;
• additional technical or purchasing data.

At the same time, the store could continue restricting information such as:

• internal costs;
• supplier-specific internal data;
• margin classes;
• other internal business metadata.

This gives B2B customers access to more useful purchasing information without automatically exposing every attribute stored in the Magento catalog.

Internal Buyers & Partners — Private Group

Internal users may require a broader set of product information, including:

• cost-related information;
• supplier codes;
• internal logistics fields;
• warehouse information;
• other operational attributes.

The exact visibility structure depends on the individual business and the purpose of each customer group.

The important point is that the same product does not necessarily have to expose the same set of attributes to every group.

Configuration Without Custom Attribute-Permission Development

The restrictions can be configured through the module's product attribute permission functionality.

For basic configuration and management, an administrator does not need specific programming knowledge.

Instead of building separate product pages or maintaining different versions of the same catalog information for each audience, the merchant can define which product attributes should be restricted for particular customer groups.

This can be especially useful for B2B and hybrid stores where the same Magento catalog serves several types of customers.

Potential Impact

1. Better control over internal product information

   The most direct benefit is the ability to restrict selected product attributes for customer groups that should not have access to them.

   Retail customers do not need to see internal supplier or margin-related fields simply because those attributes are useful to the business internally.

   Customer Group Permissions gives the merchant a way to apply product attribute restrictions based on customer group.

2. Cleaner product information for retail customers

   A product catalog can contain significantly more information than a retail customer actually needs.

   Restricting internal or B2B-specific attributes can help keep the customer-facing product information focused on the details relevant to that audience.

   Instead of exposing every attribute used by the business, the store can create a more appropriate information set for regular shoppers.

3. More relevant information for B2B customers

   B2B customers often need more information than retail shoppers.

   Pack sizes, minimum order quantities, lead times, or other operational details can be important when planning business purchases.

   Customer-group-based attribute permissions allow the merchant to provide additional information to these customers while continuing to restrict internal business data.

4. Better separation between customer and internal information

   Magento product attributes can serve both customer-facing and operational purposes.

   A distributor may use the same product record to store technical specifications, purchasing information, supplier details, and internal logistics data.

   Attribute permissions help separate these different information layers according to the audience.

5. Easier catalog management for hybrid stores

   Without customer-group-based attribute restrictions, a merchant may be tempted to separate information manually or maintain different catalog experiences for different audiences.

   Being able to restrict selected product attributes by customer group provides another way to manage a shared product catalog.

Why Attribute Visibility Matters in B2B

In B2B commerce, product information is not always intended for one universal audience.

A retail shopper may need:

price + dimensions + technical specifications

A wholesale customer may additionally need:

MOQ + pack size + lead time

An internal buyer may need:

supplier information + internal logistics data + cost-related fields

All of this information can relate to the same product.

The difference is who needs to see it.

This is why attribute visibility can become an important part of product information management in a B2B or hybrid Magento store.

The goal is not simply to hide information.

It is to make the information available to each customer group more relevant to its role.

Product Attribute Permissions Are Only Part of the Module

Although this use case focuses specifically on product attributes, Customer Group Permissions provides broader customer-group restriction functionality.

The module can also be used to restrict:

• products;
• categories;
• payment methods;
• shipping methods;
• wishlist functionality;
• product attributes.

For example, a merchant may want to make a particular category unavailable to the "Not Logged In" group.

Another business may want to restrict a particular shipping or payment method for a specific customer group.

Product attribute permissions therefore fit into a broader approach to controlling which parts of the Magento store are available to different audiences.

For a B2B or hybrid merchant, this can be useful when retail customers, wholesale customers, and other groups all use the same storefront but have different purchasing requirements.

Attribute Permissions Should Reflect Business Requirements

Not every operational attribute needs to be hidden.

Likewise, not every B2B customer needs access to the same additional information.

The appropriate permission structure depends on the individual store.

Before configuring restrictions, a merchant can divide product attributes into several practical categories:

Public information

Information that should be available to every customer.

B2B information

Additional information required by approved business customers.

Internal information

Operational or commercial data intended only for internal users or selected partners.

This creates a clearer basis for configuring customer-group permissions.

Any information subject to regulatory, contractual, or other legal disclosure requirements should, of course, be handled according to the applicable requirements rather than hidden solely on the basis of customer-group configuration.

A More Relevant Product Experience for Each Audience

The value of attribute permissions is not limited to restricting sensitive business information.

It can also help merchants create a more relevant product experience.

Retail customers are not distracted by internal fields they do not need.

B2B customers can receive additional purchasing information relevant to larger or more structured orders.

Internal users can retain access to operational information required for their work.

The same catalog can therefore serve different audiences without treating every customer as though they have identical information needs.

Conclusion

For B2B and hybrid merchants, product attributes can contain business-critical metadata that is not necessarily intended for the general public or every customer group.

A Magento catalog may simultaneously contain customer-facing specifications, wholesale information, supplier data, logistics fields, and internal business metadata.

Customer Group Permissions gives merchants a way to restrict selected product attributes for specific customer groups.

This can help create:

• better control over internal product information;
• cleaner product information for retail customers;
• more relevant operational information for B2B customers;
• better separation between external and internal data;
• and a more manageable shared catalog for different audiences.

The module does not determine which attributes a particular business should consider sensitive or which information must be disclosed. Those decisions depend on the store's business, operational, and legal requirements.

What it provides is the permission mechanism needed to apply those decisions to different customer groups.

For B2B eCommerce, controlling what different customers do not need to see can be just as important as deciding what they do need to see.