Filament Currency Laravel Package

Product Decisions This Supports

• Admin/back-office money handling: Filament Currency supplies currency input fields and formatted table columns for Filament admin panels, so pricing, catalog, billing, and payout screens can be built without hand-rolling money parsing, rounding, and locale formatting.
• Build vs. buy: Replaces a recurring "we'll just format currency ourselves" decision. Custom money formatting is deceptively expensive (separators, symbol placement, minor-unit precision, negative/zero handling); this package makes that a small dependency instead of an owned code path.
• Upgrade roadmap (Laravel + Filament + this package): The maintained line has moved from v2 to v3 (we last assessed 2.1.0; current release is 3.0.2). This is now a two-part decision: (a) confirm our Laravel/Filament versions are inside v3's supported matrix, and (b) if we are still on the v2 line, budget a deliberate v2 → v3 step rather than assuming the v2 branch stays supported indefinitely. Treat v3 as the target line for any new admin work.
• Form-state integrity in admin screens: 3.0.2 fixes a currency mask that was "echoing programmatic updates back to Livewire" — i.e. forms where values are set by code (prefilled price records, recalculation, copy-from-catalog, bulk edit) could trigger spurious Livewire updates and dirty the field/model unexpectedly. That is a real data-quality risk in pricing and billing screens, not cosmetic. It is now fixed; this is a concrete argument for adopting ^3.0.2 specifically rather than an earlier pin.
• Scope decisions for commerce features: Useful signal on where to draw the line — this package handles presentation and input of money, not FX conversion, tax calculation, or ledger accounting. That clarifies whether a commerce initiative needs a payments/pricing platform versus just better admin UI.
• Multi-currency and localization use cases: Supports decisions about whether to expose per-market pricing, localized price display, or currency-aware reporting in internal tooling before committing to a larger localization effort.
• Vendor concentration review: Still a small, single-maintainer package. Two consecutive releases with first-time contributors (@pabbec on 3.0.2) plus a steady cadence through a major version is a positive maintenance signal, but it remains a low-criticality dependency with an exit path (swap to native Filament fields) if maintenance stalls.

When to Consider This Package

Adopt when:

• The product's admin or internal tooling is built on Filament; the package is Filament-specific and offers little value outside that stack.
• You need currency input fields and formatted display columns in forms and tables, especially across more than one currency or locale.
• You have programmatically populated money fields (prefill from a record, recalculate on change, copy-between-fields) — take ^3.0.2, which contains the fix for the mask writing programmatic values back into Livewire state. Earlier versions carry that bug.
• You want to avoid owning money-formatting logic in-house, particularly where rounding and minor-unit bugs have real financial or customer-trust consequences.
• You are planning a Laravel/Filament upgrade — the project's willingness to ship a major line (v3) and then patch it promptly indicates active stewardship, but you must verify v3's Laravel/Filament compatibility rather than extrapolating from the v2-era Laravel 13 note.
• You need a fast path to a working prototype for pricing or billing screens, where a small dependency beats a bespoke implementation.

Look elsewhere when:

• You are not using Filament — use a general money library (e.g. moneyphp/money) directly at the domain layer instead.
• You need currency conversion rates, tax/VAT calculation, invoicing, or accounting — this is a UI/formatting package, not a financial engine. Pair it with a domain money library rather than treating it as the source of truth for monetary values.
• You require strict correctness guarantees in the persistence layer — formatting belongs at the edge; storing formatted strings as the record of truth is an anti-pattern regardless of package.
• You are locked to the v2 line and cannot absorb a major upgrade this cycle — verify whether v2 still receives fixes; the 3.0.2 patch landed on v3 only, so v2 is best treated as legacy.
• You need a commercially supported or SLA-backed dependency; this is a community package with a small maintainer base.
• Your Filament/Laravel versions fall outside v3's supported matrix — check the compatibility table before adopting; the v2-era Laravel 13 support does not carry over automatically.

How to Pitch It (Stakeholders)

For executives: This is a small, low-risk open-source add-on that gives our admin tools correct currency input and display without us building and maintaining that logic ourselves. It has advanced to a new major version (3.x) and is being actively patched — the latest release fixes a bug where currency fields could push programmatic value changes back into the form, which is exactly the kind of quiet state bug that corrupts pricing data. Cost is effectively zero; the main consideration is that it is community-maintained, so we treat it as replaceable and keep the scope narrow.

For engineering: Filament Currency provides currency form fields and table columns for Filament panels. We assessed 2.1.0; the current line is 3.0.2, so the key follow-ups are (1) confirm v3's Laravel/Filament compatibility against our stack, and (2) if we're on v2, plan the major upgrade. Adopt ^3.0.2 — 3.0.2 (PR #58) fixes the currency mask echoing programmatic updates back to Livewire, which caused spurious field updates and dirty state in prefilled or recomputed money fields. Adopt it strictly as a presentation-layer dependency: keep monetary values as integer minor units or a money value object in the domain, and let this package handle formatting and input at the Filament boundary. Do not let it become the source of truth for stored amounts, and do not expect FX, tax, or ledger behavior from it. Pin the version, note the single-maintainer risk, and keep a fallback plan of native Filament fields if the package goes dormant.