Dosh Laravel Package

Product Decisions This Supports

• Multi-currency display without custom plumbing: Gives product teams a consistent way to render prices, totals, invoices, receipts, and transactional emails across currencies and locales, without inventing a formatting layer in every feature.
• Market expansion experiments: If roadmap includes launching or testing new geographies, this enables localized price presentation sooner. It supports the display decision, not the pricing/FX/tax decision.
• Build vs. buy for presentation logic: Treat this as a small “borrow/buy” formatting utility. Build the pricing engine, FX conversion, tax logic, and money arithmetic internally; avoid spending engineering time on symbol placement and separators.
• Roadmap prioritization: If currency display is a launch blocker, this is a low-effort enabler. If finance-grade money handling, rounding compliance, or conversion is required, this package is insufficient and should not drive the roadmap.
• Operational consistency: Supports admin dashboards, support tooling, exports, and partner-facing summaries where amounts must be displayed consistently.
• Representative use cases: SaaS pricing pages, travel/e-commerce catalogs, checkout summaries, invoices, refunds display, affiliate/payout summaries, and internal finance views.

When to Consider This Package

• Consider it when: You are on Laravel/PHP, need simple currency formatting only, and want a small MIT-licensed dependency rather than a full money library.
• Consider it when: Your amounts are already stored appropriately and you only need locale-aware symbols, separators, and decimal presentation.
• Consider it when: The blast radius is low and you can pin the version, wrap it behind an internal CurrencyFormatter interface, and fork if needed.
• Look elsewhere when: You need FX conversion, exchange-rate feeds, tax/VAT handling, rounding policies, cash rounding, allocation/splitting, arithmetic, or accounting-grade compliance.
• Look elsewhere when: You need a robust immutable Money value object and arithmetic; evaluate moneyphp/money, brick/money, or PHP’s intl NumberFormatter directly.
• Look elsewhere when: Low community signal is unacceptable for a critical path. With ~21 stars and a low adoption score, treat maintenance risk as real, even if the code surface is small.
• Look elsewhere when: Your team already standardizes on a Money pattern; adding a display-only formatter can create two competing conventions.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, MIT-licensed utility that can accelerate multi-currency price display and market experiments. It is not a strategic platform or a finance-grade money engine. The upside is speed and consistency; the downside is limited community adoption, which is manageable because the package is small and can be isolated behind an internal interface.

For engineering: Adopt it only as a thin presentation layer. Pin the version, wrap it in an internal adapter, add locale/rounding tests, and keep all arithmetic, FX, and tax logic outside it. If the package becomes unmaintained, replacing or forking it should be a contained effort. Do not let it become the source of truth for monetary values.