Shipping & Payment per Customer Group

THE PROBLEM

What merchants struggle with

Restrict available shipping and payment methods based on customer groups, enabling B2B payment workflows and specialized shipping options.

THE SOLUTION

How Shipping & Payment per Customer Group helps

**Key features:**

PRODUCT DETAILS

What ships with Shipping & Payment per Customer Group

Source-derived package metadata, compatibility, and extension surfaces verified from the current MageRa codebase.

Composer package: magera/module-shipping-payment-customer-group
Magento module: MageRa_ShippingPaymentCustomerGroup
Current package version: 1.0.2
PHP support: PHP 8.3, 8.4, or 8.5
Magento version: 2.4.9
Source package: shipping-payment-customer-group
Detected surfaces: 1 config section(s), 1 REST endpoint(s)
Product preview images: 3 curated image(s)

BUYER INFORMATION

Know exactly what you get before purchase

License, package, compatibility, and implementation details are summarized here so your team can decide quickly.

Included

After purchase

Composer package

magera/module-shipping-payment-customer-group

Install and update through the private MageRa Composer repository.

Downloadable ZIP

Version 1.0.2

The downloadable package is kept in sync with the current product release.

Full source code

shipping-payment-customer-group

Readable Magento module code is included. No ionCube or encoded files.

License scope

1 production store

Use on one live Magento store plus development and staging environments.

Updates and support

3 months included

Access product updates and MageRa support during the included support window.

Purchase guarantee

30-day refund window

Evaluate the extension on your store and request a refund if it is not a fit.

Requirements

Compatibility

Magento platform

Magento 2.4.6 - 2.4.9

Compatible with Magento Open Source and Adobe Commerce, including the latest 2.4.9 release.

PHP versions

PHP 8.3, 8.4, or 8.5

Match this range in staging before installing on production.

Theme support

Hyva and Luma ready

Custom themes should validate templates, layout XML, and affected frontend routes.

Install method

Composer-first, ZIP available

Use Composer for repeatable deployments; keep the ZIP as a source reference or manual fallback.

Code access

Open Magento module source

Developers can inspect, extend, and audit the code before launch.

Dependencies

9 Magento dependency module(s) detected

Most stores already include the core Magento modules this extension depends on.

IMPLEMENTATION SCOPE

Where this extension appears in Magento

Source-detected admin pages, storefront routes, configuration areas, APIs, cron jobs, database usage, and dependencies.

Configuration 1

Stores > Configuration sections used to control the extension.

shipping_payment_customer_group

REST API 1

1 REST endpoint detected in source.

Dependencies 9

Magento modules that should be present and enabled in the target store.

MageRa_AdminUi
MageRa_Base
MageRa_FrontendUi
Magento_Backend
Magento_Customer
Magento_Payment
+3 more

RECOMMENDED ROLLOUT

Install, test, configure, launch

1

Purchase and download

Get version 1.0.2 from your MageRa account and keep the Composer package name handy.
2

Install on staging

Require magera/module-shipping-payment-customer-group through Composer, then enable MageRa_ShippingPaymentCustomerGroup.
3

Run Magento deployment

Run setup:upgrade, DI compile, static content deploy, and cache flush before browser testing.
4

Configure the module

Review these config section(s): shipping_payment_customer_group.
5

Validate affected areas

Test 1 config section(s), 1 REST endpoint(s) with realistic store data before launch.
6

Launch and monitor

Deploy through the same Composer flow, then monitor logs, cron, cache, and customer-facing flows.

DETAILED FEATURES

Everything Shipping & Payment per Customer Group can do

Key capabilities of Shipping & Payment per Customer Group. Composer install in under a minute, full Hyvä compatibility, and 3 months of updates included.

Shipping method restrictions per cu…

Shipping method restrictions per customer group

Payment method restrictions per cus…

Payment method restrictions per customer group

Custom flat rate shipping fees per …

Custom flat rate shipping fees per customer group

Free shipping override per customer…

Free shipping override per customer group

Custom table rates per customer group

Payment fee/discount for specific m…

Payment fee/discount for specific methods per group

Priority sorting of methods per cus…

Priority sorting of methods per customer group

Backend order support

LATEST RELEASE

Current version notes

The current release note focuses on active Magento compatibility, package metadata, and fixes included in the latest MageRa build.

1.0.22026-07-04
Compatibility
- Validated for Magento Open Source and Adobe Commerce 2.4.9.
- Compatible with Magento 2.4.6 - 2.4.9.
- Current package metadata targets PHP 8.3, 8.4, or 8.5.
Fixed and improved
- Rebuilt from the latest MageRa source tree with refreshed package metadata and product assets.
- Includes current bug fixes, dependency cleanup, and deployment-readiness fixes from the latest extension audit.
- Verified source-detected extension surfaces: 1 config section(s), 1 REST endpoint(s).
Technical details
- Composer package: magera/module-shipping-payment-customer-group.
- Magento module: MageRa_ShippingPaymentCustomerGroup.
- Configuration section(s): shipping_payment_customer_group.
- Magento dependency modules detected: MageRa_AdminUi, MageRa_Base, MageRa_FrontendUi, Magento_Backend, Magento_Customer, Magento_Payment, +3 more.

INSTALL IN 60 SECONDS

One `composer require` and you're done

magera/module-shipping-payment-customer-group

# 1. Configure the MageRa composer repository
composer config repositories.magera composer https://repo.magera.ca

# 2. Require the package
composer require magera/module-shipping-payment-customer-group

# 3. Enable the module
bin/magento module:enable MageRa_ShippingPaymentCustomerGroup

# 4. Run the Magento upgrade
bin/magento setup:upgrade

# 5. Compile DI
bin/magento setup:di:compile

# 6. Deploy static content + flush cache
bin/magento setup:static-content:deploy -f && bin/magento cache:flush

BEFORE YOU BUY

What to confirm for your store

Use this checklist before checkout, or send the details through the store fit form for a compatibility review.

Confirm platform fit

Use Magento 2.4.6+ and PHP 8.3, 8.4, or 8.5 in staging.

Check your theme stack

Hyva and Luma are supported; custom or headless storefronts should review affected templates and routes.

Review dependencies

Confirm these module dependencies exist: MageRa_AdminUi, MageRa_Base, MageRa_FrontendUi, Magento_Backend, Magento_Customer, +4 more.

Plan test coverage

Include these source-detected areas in UAT: 1 config section(s), 1 REST endpoint(s).

Share store details

Send version, theme, hosting, and deployment information if you want MageRa to review compatibility first.

STORE FIT CHECK

Confirm Shipping & Payment per Customer Group fits your store

Share your Magento version, theme, deployment flow, and rollout goal. MageRa support can review compatibility before you buy or install.

Magento edition and version
PHP, theme, Hyva, and hosting details
Current modules, store URL, and timeline

Name Email Store URL Phone Magento version PHP version Theme Deployment flow Hosting Target timeline Current modules or concerns Goal for this extension

Contact support

FREQUENTLY ASKED

Questions merchants ask before buying

Does this work with my current Magento version?

Every MageRa extension is tested on Magento 2.4.6 through 2.4.9 community edition. If you are on an older Magento version, contact us before purchase and we will confirm compatibility.

Do I need Hyvä?

No. Each extension ships with both a Luma-compatible template and a Hyvä-compatible template. The Hyvä template is provided as a fallback module under MageRa_<Extension>/view/frontend/templates/hyva/.

What if I am on Adobe Commerce (Enterprise)?

The same extension works on Adobe Commerce. The composer package, module activation, and templates are identical. Some EE-only features (e.g. B2B out of the box) get extended by the same code without an EE surcharge.

Can I install via composer?

Yes — every MageRa extension is published as a standard composer package. Add the MageRa Packagist repository, run `composer require magera/<module>`, then `bin/magento setup:upgrade`. The full install snippet is on the extension detail page.

What is the refund policy?

30-day money-back guarantee, no questions. Email support@magera.ca within 30 days of purchase and we issue a full refund.

What happens if the extension doesn't work for me?

We offer a 30-day money-back guarantee. If the extension doesn't meet your needs, email support@magera.ca within 30 days and we'll issue a full refund — no questions asked.

Will this work with my other MageRa extensions?

Yes. All MageRa extensions share the same base library (MageRa_Base) and are tested together. If you find an integration issue between two MageRa extensions, support@magera.ca is the right address.

How do I get support?

Email support@magera.ca. Every MageRa license includes 3 months of standard email support with a 24-hour weekday response SLA. Critical production issues are flagged and triaged within 4 hours.

Get Shipping & Payment per Customer Group today

Full source code. 30-day money-back guarantee. Composer install in under a minute.

Need help installing?