Table of Contents
Magento 2 shipping cost as percentage of order User Guide for Magento 2
Extension context
This is a Toweringmedia Magento 2 extension guide generated from the Magento Admin virtual product catalog.
Product page
Overview
Unlike default Magento shipping options, which don’t allow percentage-based rules, this module introduces a simple yet powerful way to align shipping costs with your business model. For example, if you set a 5% shipping rule, an order of $100 will generate a $5 shipping fee, while a $500 order will automatically calculate $25. Key Features: Set shipping costs as a percentage of the order subtotal Flexible configuration — define minimum and maximum shipping charges Apply to specific customer groups or store views Combine with free shipping rules for large orders Works seamlessly with discounts and tax-inclusive orders Compatible with Magento 2.4.x and PHP 8.2+ Why Use Percentage-Based Shipping? Flat rate.
What this extension does
- Define percentage shipping rules per website with optional minimum and maximum fees.
- Layer multiple tiers so high-value carts pay the exact percentage you expect.
- Automatically reduce charges when shoppers hit your free-shipping thresholds.
- Works alongside Magento flat-rate and table-rate methods without conflicts.
- Fully compatible with Magento 2.4.x Open Source and Adobe Commerce.
Installation
Install and validate in staging before production rollout.
cd /path/to/magento # Install from your licensed package source php bin/magento setup:upgrade php bin/magento setup:di:compile php bin/magento setup:static-content:deploy -f php bin/magento cache:flush
Configuration
Configure extension options in Magento Admin, then validate key storefront/admin flows tied to this extension.
Validation checklist
- Configuration saves without errors in Admin.
- Expected storefront/admin behavior is present.
- No critical PHP/JS errors occur during test flow.
- Caches and static assets are refreshed after changes.
Troubleshooting
- Feature missing: verify module status, cache flush, and static-content deploy.
- Unexpected behavior: retest with only required related modules enabled.
- Admin setting not applying: verify config scope and clear cache.
