- Does noxoua/filament-coupons calculate discounts or only manage coupon codes?
- The package clearly provides coupon administration in Filament: a CRUD resource, form and table schemas, expiry and usage limits, and redemption tracking. The technical evaluation flags that discount calculation may live inside Filament actions rather than a separate service, so verify the source before assuming headless reuse. If the calculation is UI-bound, treat the package as admin-only tooling and implement your own pricing logic.
- How do I install and register filament-coupons in a Filament v3 panel?
- Run composer require noxoua/filament-coupons, publish the config and migrations, then register the plugin in your target Filament panel provider. Before installing, confirm the Composer constraints resolve against your existing Filament and Livewire pins. The main effort is not installation but reconciling coupon semantics with your cart, order, refund, and reporting flows.
- Which Laravel, PHP, and Filament versions does this package support?
- The evaluation targets Laravel 10 and 11, PHP 8.1+, Filament v3, and MySQL or Postgres. It is a poor fit for Filament v2 or Livewire 2 projects and for non-Filament admin panels. Check composer.json for the exact version constraints before adding it to a production lockfile.
- Is it safe to use filament-coupons for checkout discount calculations in production?
- Treat it cautiously on the money path. Start with admin-only coupon creation and listing, then integrate evaluation behind a feature flag and a service interface you control. Review the 1.0.2 to 1.0.3 diff because the release notes contain only an auto-generated compare link, and test edge cases such as expired coupons, concurrent redemption, currency mismatch, and negative totals.
- How are coupon expiry and usage limits handled by this package?
- The package advertises coupon creation and editing with expiry and usage limits plus usage tracking through redemption tables. The exact enforcement behavior is not documented in the provided evaluation, so confirm whether limits are checked in the model, a service, or only in Filament actions. Treat the coupon and redemption tables as internal and expose reads through your own repository layer.
- Can I use filament-coupons headlessly without the Filament admin UI?
- That is the key question to validate. If the coupon model, migrations, and discount logic are separable from Filament, headless use in API checkout, queue jobs, or POS is possible. If evaluation exists only inside Filament actions, the package is admin-only tooling and you should not rely on it for headless redemption.
- How do I publish and customize the package migrations and config?
- Use Laravel's vendor:publish command for the package's config and migrations, then run migrations against a copy of your production schema to catch index or collation conflicts. Published migrations become yours to maintain, so plan for upstream column changes in later releases. A rollback strategy matters because coupons and redemptions touch order history.
- What are the risks of installing version 1.0.3 with no changelog body?
- Release opacity is a medium risk because a patch bump on a money-related dependency could still ship a silent behavioral fix, including discount rounding. The 1.0.2 to 1.0.3 diff review is mandatory before rollout, not optional. Pin the version and inspect the commit history and CI status before updating production.
- Does filament-coupons support stacking multiple coupons, tax, and rounding rules?
- The provided evaluation does not confirm stacking, rounding, or tax interaction support. Coupons are a cross-cutting concern, and even a clean plugin install implies reconciliation with your existing order lifecycle. Define stacking and rounding rules in your own service wrapper and use the package only for storage and admin UX if necessary.
- What should I consider instead if I need a full Laravel discount engine?
- If you are not on Filament v3, stop and evaluate the underlying coupon model as a fork candidate rather than adopting the admin plugin. For teams on Filament, use it for coupon administration and build a separate discount-evaluation service behind an interface so implementations can be swapped without touching call sites. Also check test coverage, maintenance bus factor, license terms, and private security reporting before committing.