Subscriptions Filament Laravel Package

Product Decisions This Supports

• Subscription & billing admin UX is a first-class surface, not a side project. PlansTable, MoneyField, and CurrencyField indicate a ready-made plan management UI (table + form fields) layered on crumbls/subscriptions. This lets you ship pricing/plan CRUD without designing it from scratch — a build-vs-buy decision that clearly favors buy/reuse here.
• Roadmap sequencing around the billing stack. Because v2.1.1 explicitly tracks crumbls/subscriptions 2.x compatibility, this package should be versioned alongside your subscriptions dependency in the roadmap. Plan upgrades to the billing core now have a known, low-friction companion upgrade path.
• De-risks a specific dependency decision. The removal of the hard dependency on an unreleased currency service is a signal: the package maintainers are deliberately decoupling from pre-release infrastructure. That supports a "adopt now, don't wait for the currency service" decision.
• Reduces need for custom Plan model work. Host apps no longer must implement formattedPrice(); the package formats decimals itself while still honoring custom implementations. This lowers the integration cost for teams whose Plan model is simple, and preserves flexibility for teams with bespoke formatting — a both-ways decision rather than a forced migration.
• Supports multi-currency/pricing display use cases in admin and plan-editing flows, which underpins pricing experiments, tiered plan config, and regional pricing iterations.

When to Consider This Package

Consider it when:

• You are already on (or moving to) crumbls/subscriptions 2.x and want plan management UI without building tables and money/currency form fields yourself.
• Your Plan models are conventional decimal-price models and you don't want to bolt on a formattedPrice() method just to render a table.
• You have (or plan) custom price formatting and need the package to defer to your model's formattedPrice() when present.
• You want compatibility with released 2.x versions rather than tracking unreleased services.

Look elsewhere or wait when:

• You need the currency service functionality that this release deliberately does not depend on — you'll need to source that separately or wait for its release.
• You are pinned to crumbls/subscriptions 1.x or a fork; the compatibility work here is explicitly aimed at 2.x.
• You require the package to own your pricing/formatting logic end-to-end (it now defers to your model, by design).
• You need guarantees beyond patch-level signals — this is a v2.1.1 patch, so treat it as incremental hardening rather than a feature-complete platform bet.

How to Pitch It (Stakeholders)

For executives: This is a small, low-risk patch to our plan-management UI layer. It removes a dependency on an unreleased internal currency service and makes the package work cleanly with the released 2.x subscription core. Net effect: fewer moving parts, less upgrade risk, and no requirement to modify our Plan model. It is a maintenance-class release, not a strategic shift — but it makes the subscriptions stack safer to build on.

For engineering: v2.1.1 is a compatibility and decoupling release. PlansTable no longer requires formattedPrice() on the host Plan model — the package formats decimal prices itself and still honors custom implementations where they exist. MoneyField and CurrencyField no longer reach into an unreleased currency service, so plan create/edit forms are compatible with crumbls/subscriptions 2.x. Practical implications: existing integrations keep working; integrations that implemented formattedPrice() still get their custom output; anyone who was blocked by the unreleased dependency is now unblocked. Recommend pinning to v2.1.1 and aligning the crumbls/subscriptions constraint to 2.x in the same change.