Restrict Shipping & Payment by Customer Group in Magento 2

When One-Size-Fits-All Checkout Costs You Sales

Picture this scenario: a wholesale buyer who spends $50,000 a month on your Magento 2 store reaches checkout and sees PayPal Express, Stripe, and Apple Pay — but not the Net 30 invoice terms their procurement department requires. They abandon the cart, email your sales team, and wait three days for a manual workaround. Meanwhile, a retail customer sees "Purchase Order" as a payment option and gets confused. Your support inbox fills with questions about payment methods that do not apply to them.

This is not a hypothetical problem. A McKinsey B2B commerce report found that 70% of B2B buyers find the purchasing experience too complicated, and unclear payment terms are a leading cause of cart abandonment in wholesale channels. When your checkout treats every customer identically, you create friction for every segment simultaneously.

Magento 2 does not natively support filtering shipping or payment methods by customer group. Out of the box, every shopper — from first-time guests to enterprise wholesalers — sees the same list of options. For stores that serve both B2B and B2C audiences, this gap is not just inconvenient; it actively costs revenue.

The solution is to restrict shipping and payment methods per customer group, so wholesale buyers see Net 30 and freight shipping while retail customers see credit cards and standard delivery. For the complete B2B solution with all 7 extensions, see MageRa B2B Extensions Package.

What Is Shipping & Payment per Customer Group (and Why Your Magento 2 Store Needs It)

Shipping & Payment per Customer Group is a Magento 2 extension that lets you control which shipping carriers and payment methods appear during checkout based on the customer group assigned to the logged-in user. Instead of showing every available option to every visitor, the extension filters the list in real time so each segment sees only what is relevant to them.

This goes far beyond what Magento 2 offers natively. The core platform allows you to enable or disable payment methods globally, and you can set basic shipping restrictions by country or region. But there is no built-in mechanism to say "Wholesale customers should only see Invoice and Purchase Order" while "Retail customers should only see Credit Card and PayPal."

The principle behind this is straightforward: checkout clarity drives conversion. When customers see options that match their expectations and purchasing workflow, they complete orders faster and with fewer support tickets. When they see irrelevant options — or worse, are missing the one method they need — conversion drops.

This extension is the right fit if your Magento 2 store serves multiple customer segments with different purchasing behaviors: wholesale and retail, domestic and international, VIP and general. It is not necessary if you run a single-segment store where every buyer uses the same payment and shipping methods.

Key Features of MageRa Shipping & Payment per Customer Group

Shipping Method Restrictions by Group — Enable or disable individual shipping carriers (Flat Rate, Table Rate, FedEx, UPS, Freight) for each customer group. Wholesale accounts can see freight and table rates while retail shoppers see standard and express options only.

Payment Method Restrictions by Group — Control which payment methods appear at checkout per customer group. Assign Net 30 invoice terms to wholesale, credit cards to retail, and purchase orders to government buyers, all without writing custom code.

Screenshot of the Shipping & Payment per Customer Group admin configuration panel in Magento 2 showing method restriction rules for Wholesale, Retail, VIP, and Guest groups.

Per-Group Mapping Interface — Both restrictions are configured through a dedicated mapping interface in the admin, where you pick the allowed methods for each customer group. The customer group list, available shipping methods, and available payment methods are pulled from your live Magento configuration, so the options you see are the real methods on your store.

Allow-All by Default — Leaving a group's mapping empty allows every method for that group. This means you only have to configure the groups that actually need to be restricted, and any new group you create keeps full access until you decide to limit it.

Real-Time Checkout Filtering — The restrictions are enforced through plugins on Magento's quote shipping method management and payment method list, so the allowed methods are filtered as the customer reaches checkout — no separate rate tables or duplicate method definitions to maintain.

Screenshot showing filtered payment methods at checkout for a Wholesale customer — only Invoice/Net 30, Purchase Order, and Check/Money Order are displayed.

Real-World Use Cases for Method Restrictions

The power of this extension lies in how many operational problems it solves with a single configuration screen. Here are the most common scenarios where per-group restrictions make a measurable difference.

Wholesale with Net 30 Terms — Your wholesale buyers operate on purchase orders and invoice payment cycles. They do not pay by credit card at checkout. By restricting their payment options to Invoice/Net 30 and Purchase Order, you eliminate confusion and match their procurement workflow exactly. Combine this with MageRa Wholesale Fast Order for a seamless B2B ordering experience.

Retail Credit Cards Only — Consumer shoppers expect to pay with Visa, Mastercard, PayPal, or Apple Pay. They should never see "Purchase Order" or "Check/Money Order" in their checkout. Restricting retail groups to card and digital wallet payments reduces support tickets and prevents accidental order submissions via unsupported methods.

VIP Free Shipping — Your highest-value customers deserve perks that reinforce their loyalty. Configure Magento's Free Shipping method the way you want it, then map it so only the VIP group sees it at checkout while other groups see your standard carriers. This targeted benefit is easier to manage than a blanket free shipping promotion.

Government and Institutional Buyers — Organizations that purchase via purchase orders or government payment cards often have strict procurement rules. Create a dedicated customer group with only the payment methods their procurement department accepts, eliminating back-and-forth negotiation after order placement.

International Customer Groups — Buyers in different regions may need different payment options. European wholesale accounts might prefer bank transfer, while North American wholesale buyers use Net 30. Group-based restrictions let you tailor the experience by geography without setting up separate store views.

How to Set Up Shipping & Payment per Customer Group in Magento 2

Step 1: Verify Prerequisites

Before installing, confirm your environment meets the requirements: PHP 8.3 or higher, Magento 2.4.6 or later, and the MageRa Base module installed. The extension depends on Magento's Customer, Sales, Quote, Shipping, and Payment modules — all included in a standard Magento 2 installation.

Step 2: Install the Extension

Run the following Composer commands from your Magento root directory:

composer require magera/module-shipping-payment-customer-group
php bin/magento module:enable MageRa_ShippingPaymentCustomerGroup
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:flush

After installation, the new configuration section appears under Stores > Configuration > MageRa Extensions > Shipping & Payment Restrictions.

Step 3: Enable the Extension

In the General Settings group, set Enable Restrictions to Yes. Leave it set to No while you build out your mappings if you want to configure rules before they go live on the storefront.

Step 4: Configure Shipping Method Restrictions

Open the Shipping Method Restrictions group. Using the per-group mapping interface, choose the allowed shipping methods for each customer group. The methods listed are pulled from your live store configuration. A typical setup might look like:

• Wholesale: Allow Flat Rate, Table Rate, and Freight; leave FedEx and UPS express options out.
• Retail: Allow Flat Rate, FedEx, and UPS; leave Freight out.
• VIP: Allow all methods.
• Guest (Not Logged In): Allow Flat Rate and standard carrier options only.

Remember that leaving a group's mapping empty allows every shipping method for that group, so only restrict the groups that need it.

Step 5: Configure Payment Method Restrictions

Open the Payment Method Restrictions group. The same mapping interface lets you choose the allowed payment methods per group:

• Wholesale: Allow Invoice/Net 30, Purchase Order, and Check/Money Order; leave credit cards and PayPal out.
• Retail: Allow Credit Card (Stripe/Braintree), PayPal, and Apple Pay; leave Invoice and Purchase Order out.
• VIP: Allow all preferred methods.
• Guest: Allow Credit Card and PayPal only.

As with shipping, an empty mapping for a group allows all payment methods. Click Save Config and flush the Magento cache.

Each mapping is saved as a serialized rule keyed by customer group, so the table you build in the Shipping Restrictions by Customer Group and Payment Restrictions by Customer Group fields is stored as a single configuration value per group rather than as separate database records. The extension then filters the available methods at quote/checkout time based on the logged-in customer's group.

Step 6: Test with Different Customer Accounts

Create test accounts in each customer group and walk through the checkout process. Verify that the methods you mapped appear and the ones you left out do not. Test guest checkout to confirm the default group restrictions apply to unregistered visitors. If you are using MageRa One Step Checkout, verify that the filtered methods render correctly in the streamlined checkout layout. For programmatic management — for example, syncing rules from an ERP — the extension exposes admin REST endpoints to list and save restrictions: GET /V1/magera/spcg/restrictions and POST /V1/magera/spcg/restrictions.

MageRa Shipping & Payment per Customer Group for Magento 2

Built for flexibility: the extension works with all native Magento 2 shipping carriers and payment gateways, plus any third-party methods that register through Magento's standard shipping and payment interfaces. No carrier-specific or gateway-specific configuration is required.

Key differentiators include a per-group mapping interface that reads your live shipping and payment methods, an allow-all-by-default model so you only configure the groups you need to restrict, and real-time checkout filtering through Magento's native quote and payment plugins rather than duplicate rate tables.

Compatibility: Magento 2.4.6, 2.4.7, 2.4.8, and 2.4.9 on both Open Source and Commerce editions. PHP 8.3, 8.4, and 8.5 are supported.

https://magera.ca/magento-2-shipping-payment-customer-group.html →

Best Practices for Restricting Checkout Methods

Getting the technical configuration right is only half the work. How you design your restriction strategy determines whether the extension helps or hinders your customers. Follow these guidelines to maximize the impact.

Map your customer groups to payment workflows before configuring — Sit down with your sales and finance teams and document which payment methods each segment actually uses. Do not guess. Your wholesale buyers might prefer bank transfer over Net 30, or your retail customers might use PayPal more than credit cards. Build your restriction matrix on real purchasing data, not assumptions.

Always provide at least two payment options per group — Restricting a customer group to a single payment method is risky. If that method experiences downtime or is temporarily unavailable, customers in that group have no fallback and cannot complete their purchase. Always leave a secondary option enabled.

Confirm methods are enabled globally first — The extension controls which of your existing methods each group can see; it does not create new carriers or gateways. Before mapping a method to a group, make sure it is enabled at the global Magento level and configured correctly, otherwise it will not be available to map.

Pair restrictions with Magento's native rate tools — Because this extension handles visibility rather than rate calculation, use Magento's built-in shipping settings (flat rate amounts, table rates, free shipping thresholds, and cart price rules) to set the actual rates, then use the extension to decide which groups see each method. The two work together: native settings define what a method costs, the extension defines who can use it.

Review restrictions quarterly — As your business evolves, you may add new customer groups, new payment gateways, or new shipping carriers. Set a quarterly reminder to audit your restriction matrix and ensure it still reflects your actual business operations. Outdated restrictions can silently block customers from using methods they expect.

Common Mistakes When Implementing Payment Restrictions

Even with the right extension, missteps in configuration can frustrate customers instead of helping them. Here are the pitfalls to watch for.

Restricting methods without informing customers — If a customer is used to seeing PayPal at checkout and it suddenly disappears because you assigned them to a different group, they may think something is broken. Use Magento's customer group notification features or a brief message at checkout to explain why certain options are filtered.

Forgetting about guest checkout — Guest customers are assigned to the default "Not Logged In" group. If you configure restrictions for all named groups but leave the guest group unconfigured, guest checkouts will show every available method, undermining your segmentation strategy.

Overlapping restrictions with Magento's native settings — Magento 2 already lets you enable or disable payment methods globally and set shipping restrictions by country. If you disable a method globally, it will not appear even if you enable it in the extension for a specific group. Always check that the method is enabled at the global level first, then use the extension to control group-level visibility.

Confusing visibility with rates — The extension decides which methods a group can see, not what those methods cost. If a wholesale group should pay a different shipping rate, set that rate up in Magento's native shipping configuration first, then map the method to the group. Expecting the extension to change prices is the most common configuration mistake.

Conclusion

Restricting shipping and payment methods per customer group transforms your Magento 2 checkout from a generic one-size-fits-all experience into a segmented, conversion-optimized workflow. Wholesale buyers see Net 30 invoice terms and freight shipping. Retail customers see credit cards and standard delivery. VIP shoppers get free shipping as a loyalty reward. Each segment gets a checkout experience that matches how they actually buy.

MageRa Shipping & Payment per Customer Group for Magento 2 gives you complete control over which shipping and payment methods each customer group sees at checkout — all configured through the Magento admin panel with zero code changes. Stop losing wholesale orders to missing Net 30 terms and confusing retail customers with irrelevant purchase order options. Explore the extension today.

FAQ

Q1: Does this extension work with third-party payment gateways like Stripe, Braintree, or Authorize.net? Yes. The extension filters payment and shipping methods through Magento's standard method registry. Any payment gateway or shipping carrier that registers properly with Magento 2's native payment and shipping interfaces will appear in the restriction matrix. This includes Stripe, Braintree, Authorize.net, PayPal, and custom gateways you may have developed. The extension does not modify the gateway itself — it controls whether the method is visible to each customer group during checkout.

Q2: What happens if a customer is moved to a different group after placing an order? Orders that have already been placed retain the payment and shipping methods selected at the time of checkout. Changing a customer's group assignment does not retroactively modify existing orders. The new group restrictions take effect on the customer's next checkout session. This ensures order integrity and prevents accounting discrepancies from mid-cycle group changes.

Q3: Can I charge different shipping rates to different customer groups? The extension controls which shipping and payment methods each customer group can see, not the rates those methods charge. To vary rates by segment, configure them with Magento's native tools — for example, set up multiple Flat Rate or Table Rate methods, or use the built-in Free Shipping method and cart price rules — and then use the extension's mapping interface to decide which groups see each method. This separation keeps rate calculation in Magento's standard engine while giving you per-group control over method visibility.

Internal Links

• /blog/complete-b2b-extension-package-magento-2 (B2B Extensions Package — the full B2B toolkit including this extension)
• /blog/magento-2-wholesale-fast-order-bulk (Wholesale Fast Order — bulk ordering for wholesale customer groups)
• /blog/one-step-checkout-magento-2-conversion-rates (One Step Checkout — streamlined checkout that integrates with filtered payment methods)