イメージプレビューA build-to-order Magento 2 / Adobe Commerce extension that adds configurable extra fees and surcharges
(gift-wrap, handling, insurance, COD/payment surcharge) to the cart and checkout totals. Built, installed, and supported by
ECOSIRE on your store.
Checkout Extra Fee & Surcharge for Magento 2とは？
A build-to-order Magento 2 / Adobe Commerce extension that adds configurable extra fees and surcharges (gift-wrap, handling, insurance, COD/payment surcharge) to the cart and checkout totals. Built, installed, and supported by ECOSIRE on your store. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
この製品について
Magento 2 lets merchants charge for products, shipping, and tax — but there is no native way to add a separate line-item fee at checkout. If you need to recover payment processing costs, COD handling, gift-wrap, packing materials, or shipment insurance, you either eat the cost or hack it into shipping/tax. This extension closes that gap cleanly.
ECOSIRE builds a dedicated module under app/code/Ecosire/CheckoutExtraFee that registers one or more custom total collectors in etc/sales.xml and etc/quote_totals.xml, so each fee appears as its own row in the cart summary, order, invoice, and credit memo — not buried inside shipping. Fees are applied through the quote total-collector pipeline and persisted to quote, order, and their address tables, so reporting, refunds, and PDF documents all stay consistent.
Rules are admin-configurable: fixed or percentage amounts, per payment-method surcharges (for example a COD or card surcharge keyed off quote->getPayment()->getMethod()), and conditional logic by cart subtotal, customer group, website/store-view scope, or shipping country. Fees can be flagged taxable, integrating with Magento's tax module and your configured tax class so VAT/GST is calculated correctly.
The fee surfaces in the Luma checkout, Hyvä, and the GraphQL/REST cart APIs, so headless and PWA Studio storefronts display it too. All admin screens are gated behind a proper ACL resource in acl.xml, and configuration lives in system.xml under Stores → Configuration.
Because this is build-to-order, ECOSIRE scopes the exact fee rules you need, builds the module against your Magento version (Open Source or Adobe Commerce), installs it on your environment, and supports it afterward. This is not an instant Adobe Commerce Marketplace download — it is a tailored extension delivered with a clear lead time.
得られるもの
- A custom Magento 2 module (Ecosire/CheckoutExtraFee) delivered under app/code or as a Composer package, namespaced to avoid core conflicts
- Installation on your Magento environment — setup:upgrade, di:compile, and static-content deploy verified on staging then production
- Admin configuration of your specific fee rules (fixed/percent, payment-method surcharges, conditions, tax class) under Stores → Configuration
- Frontend integration tested in your active theme (Luma or Hyvä) plus GraphQL/REST totals if you run headless
- README / handover doc covering each setting, the ACL resource, and how to add or adjust fee rules
- A short post-install validation pass: cart, order, invoice, and credit memo all show the fee correctly
- Source code ownership and a defined post-launch support window for fixes and small adjustments
これは誰のためのものですか
Cost-recovery store owner
A merchant losing margin to card/COD processing fees and packing costs who needs to pass a transparent, itemized surcharge to the customer at checkout instead of absorbing it.
Adobe Commerce operations manager
Runs a multi-website Adobe Commerce install and needs scoped, taxable fee rules that behave correctly across store views, payment methods, and the existing tax setup without forking core.
Headless / PWA storefront lead
Operates a GraphQL-driven Hyvä or PWA Studio frontend and needs extra fees exposed through the cart API and totals, not just on the legacy Luma checkout.
Checkout Extra Fee & Surcharge for Magento 2 の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Magento 2 標準機能 |
|---|---|---|---|---|
| Separate, labeled fee line in cart, order, invoice & credit memo | 付属 | 部分的なサポート | 付属 | 含まれていない |
| Per payment-method surcharge (COD/card) | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Tailored to your exact fee rules and conditions | 付属 | 付属 | 含まれていない | 含まれていない |
| Installed & verified on your environment by the builder | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Taxable fee handling integrated with Magento tax module | 付属 | 部分的なサポート | 付属 | 含まれていない |
| GraphQL / REST cart totals for headless & Hyvä | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Instant self-service download | 含まれていない | 含まれていない | 付属 | 部分的なサポート |
| Upgrade-safe (no core edits) | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
Checkout Extra Fee & Surcharge に関するよくある質問
How long until the extension is delivered and live on my store?
Because this is build-to-order, ECOSIRE first confirms your exact fee rules, Magento edition, and version. A standard fixed/percentage and payment-method surcharge build is typically delivered, installed on staging, and promoted to production within about one working week. More complex conditional logic or headless GraphQL work can extend that — you get a firm timeline before any work starts. This is not an instant Marketplace download; it is a tailored module installed and verified on your environment.
What ongoing support and updates do I get after launch?
Every build includes a defined post-launch support window for bug fixes and minor configuration adjustments. Because the module uses plugins, observers, and total collectors rather than core edits, it is upgrade-safe across Magento patch releases. For major version upgrades (for example a jump across Magento minor versions) or new fee rules, ECOSIRE offers continued paid maintenance. You own the source code either way.
Does the fee work with payment-method surcharges like COD?
Yes. A common configuration is a COD or card surcharge applied only when the customer selects that payment method. The fee is evaluated against the quote's selected payment method during total collection, so it appears (or disappears) dynamically as the shopper switches methods at checkout.
Will the fee be taxed correctly?
Each fee rule can be flagged taxable and assigned a tax class. When taxable, the fee integrates with Magento's tax module so VAT/GST is calculated against your configured tax rules and displayed on the order, invoice, and credit memo. Non-taxable fees are added as a clean pass-through line.
Does this work on Adobe Commerce and headless/Hyvä storefronts?
Yes. The module is built for both Magento Open Source and Adobe Commerce, and respects website/store-view scope. The fee is exposed through the standard quote totals plus the GraphQL and REST cart APIs, so Hyvä, PWA Studio, and other headless frontends can render it. ECOSIRE tests it in your specific theme as part of installation.
関連モジュール
Cash on Delivery Suite (Multi-COD) for Magento 2
A build-to-order Magento 2 / Adobe Commerce extension that extends Cash on Delivery with geo restrictions, extra fees, multiple COD methods, and per-product/category rules. ECOSIRE builds, installs, and supports it on your store.
CCAvenue Gateway for Magento 2
A CCAvenue payment gateway integration for Magento 2 / Adobe Commerce, built to order for Indian merchants who need maximum local method breadth — 200+ payment options, UPI, net banking, wallets, EMI and 27+ currencies. ECOSIRE builds, installs and supports it on your store.
Checkout Extra Fee & Surcharge
A build-to-order Magento 2 / Adobe Commerce extension that adds configurable extra fees and surcharges (gift-wrap, handling, insurance, COD/payment surcharge) to the cart and checkout totals. Built, installed, and supported by ECOSIRE on your store.
- Fixed-amount and percentage-based fee rules, configurable per website and store view via system.xml scoped settings
- Per payment-method surcharge — e.g. COD or card surcharge keyed off the selected payment method at checkout
- Gift-wrap, packing/handling, and shipment-insurance fees as distinct, separately labeled total lines
- Custom quote total collector registered in sales.xml / quote_totals.xml so each fee renders in cart, order, invoice, and credit memo