Installation notes

The standard composer require + setup:upgrade + setup:di:compile flow applies. The points below cover what's specific to this module.

composer require wimakeit/module-extra-fee
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush

Requires PHP 8.1+ (tested up to 8.4) and Magento 2.4.x / Mage-OS equivalent.

Companion modules

• For a Hyvä storefront, install wimakeit/module-extra-fee-hyva, which renders one fee row per rule in the cart, checkout summary, and mini-cart. The Luma checkout is supported out of the box.
• The admin menu attaches under the Wimakeit parent menu provided by wimakeit/module-core.

ACL resources

After installation, two new ACL resources are available under System → Permissions → User Roles, grouped under Wimakeit Extra Fee:

Assign them to your back-office roles as needed.

Configuration

The module ships with safe defaults. Go to Stores → Configuration → Wimakeit → Extra Fees only if you want to change them. All settings are available per store view.

General settings

Fee Tax Class is only shown when Apply Tax on Fees is set to Yes.

Fee rules

Fees themselves are managed as rules under Wimakeit → Extra Fees → Manage Rules. Three rule types are available:

• Fixed fee when cart subtotal is below a threshold — a flat surcharge applied while the subtotal stays under the configured amount.
• Caution / deposit (palette, big bag…) — a deposit computed from the wmi_caution and wmi_quantite_palette product attributes.
• Fixed fee per item matching a wmi_fraisconnexes option — a connex fee triggered by a product option.

Each matching rule adds its own labelled totals line. No rules exist after install — create the ones you need.

Each rule carries two scoping multiselects since 1.1.0:

• Store Views — select "All Store Views" (sentinel value 0) to apply everywhere, or pick specific stores. Empty selection is treated as "all" on save.
• Customer Groups — select "All Customer Groups" (sentinel 32000 = GroupManagement::CUST_GROUP_ALL) to apply to every group, or pick specific groups.

Product attributes (provisioned automatically)

A data patch creates three product attributes used by the caution and connex rules. The patch is idempotent: any attribute that already exists is left untouched.

All three are scope=global and created with is_filterable=0 to avoid breaking category pages via OpenSearch. They appear on products under a dedicated Wimakeit Extra Fees attribute group.

Storage layout

The legacy CSV columns wimakeit_extrafee_rule.store_ids and customer_group_ids are kept for rollback and will be dropped in a future release.

1.0.x → 1.1.0+ migration

Existing rules with CSV scope columns are migrated to the new junction tables by a data patch (MigrateRuleStoreAndGroupCsvToJunction) at setup:upgrade time. The patch is idempotent and transactional: it skips rules that already have junction rows and rolls back on error. Sentinel semantics are preserved — store_ids containing 0 and customer_group_ids containing 32000 produce empty junctions (= "applies to all"), which is the same semantics the runtime applied before.

To verify after the upgrade:

-- Each rule should be present with either matching junction rows
-- or an empty junction (= applies to all).
SELECT r.rule_id, r.label, r.store_ids AS legacy_csv,
       COALESCE(GROUP_CONCAT(rs.store_id ORDER BY rs.store_id), '— (all stores)') AS junction
FROM wimakeit_extrafee_rule r
LEFT JOIN wimakeit_extrafee_rule_store rs ON rs.rule_id = r.rule_id
GROUP BY r.rule_id, r.label, r.store_ids
ORDER BY r.rule_id;

Totals position

The fee totals line is positioned between subtotal and tax by default (sort order 25). Override under Stores → Configuration → Sales → Sales → Checkout Totals Sort Order.

REST extension attributes

Two extension attributes are exposed on Magento\Quote\Api\Data\TotalSegmentInterface and Magento\Sales\Api\Data\OrderInterface via DI preferences (since 1.0.1):

• wimakeit_extrafee_lines — per-rule fee breakdown attached to the totals API segment
• wimakeit_extrafee_sales_fees — per-order frozen breakdown attached to the Sales API responses

This makes the per-line detail consumable by REST / GraphQL clients (Hyvä checkout, custom front-ends, BI exports) without any extra plumbing.