Limit fees to store views, localize their labels, and schedule active windows

Store view scoping

The Store Views multiselect on the fee form limits where a fee is evaluated. The default, All Store Views, applies the fee everywhere; selecting specific store views restricts it to those storefronts - a customs surcharge that only makes sense on one regional store, for example.

A fee can never end up scoped to nowhere: an empty selection, or any selection that includes All Store Views, resolves back to All Store Views on save. Fees created before store scoping existed (or through the REST API, which cannot set scope) default to All Store Views, so upgrades and API-created fees never silently stop applying.

Per-store labels

The collapsible Store View Labels fieldset overrides the fee’s display name per store view - the standard way to translate or localize a fee name without duplicating the fee. Add a row, pick a store view, enter the label. Store views without an override show the fee’s default Name/Label; a blank override also falls back to the default.

The resolved label is snapshotted into the order’s fee detail at the moment totals are collected, so renaming a fee or editing a store label later never changes what already-placed orders display.

Date-range scheduling

Active From and Active To restrict a fee to a window - a December-only holiday surcharge, a time-boxed promotion - without anyone having to remember to flip Is Active.

The semantics are deliberate and worth knowing:

• Both bounds are evaluated in the store view’s own timezone as wall-clock time, not the server’s or the admin’s timezone. “Active To Dec 31 23:59” ends at midnight local to each store.
• Both bounds are inclusive: the fee stays active through the entire minute of Active To.
• Either field may be blank for an open-ended window on that side; both blank (the default) means no schedule restriction at all.
• Saving is rejected if Active From is after Active To.

This follows the same pattern Magento core uses for scheduled catalog special prices, so behavior on multi-timezone installs matches merchant expectations from core pricing features.

How scoping and scheduling combine

At evaluation time the collector loads only fees scoped to the current store view, drops any whose schedule window does not cover “now” in that store’s timezone, then evaluates conditions on the remainder. Scope, schedule, and conditions are all AND-ed together - a fee has to pass all three to appear, plus the shopper’s opt-in if it is optional.