- What is goldnead/statamic-invoices used for?
- It is a Statamic addon for creating and managing invoices directly inside the control panel. You define customers, add line items, and generate clean, branded invoice documents without leaving Statamic. It also handles automatic numbering and totals/tax calculations, and it is aimed at Laravel and Statamic sites that need simple invoicing without an external billing platform.
- How do I install Statamic Invoices in my Laravel project?
- Install it with Composer as goldnead/statamic-invoices, then publish the package config and views so they match your brand. Because it is a Statamic addon, check the composer.json constraints of the release you pick against your installed Statamic and PHP versions before upgrading. Set up your customers and brand settings before generating live documents.
- Does it work with Antlers and Blade templates?
- Yes, the addon is explicitly Antlers and Blade friendly. It ships fieldtypes so you can integrate invoice data into your own templates and blueprints. Views are publishable, so you can override the shipped markup and style it alongside the rest of your site.
- Can I customize the PDF invoice template and branding?
- Yes, PDF generation uses templates you can customize, and the package supports simple publishing of config and views to match your brand. On multi-brand installs, branding and tax/text behavior are stored per brand on the settings page, so each brand renders with its own configuration. Keep your published views in version control so template changes are reviewable.
- How are invoice numbers, totals and tax calculated?
- The addon handles automatic numbering and totals/tax calculations for you, based on the invoice line items you enter. From v2.8.0, the relevant tax and text behavior for CLI and scheduled runs comes from the saved settings page rather than the package's bundled defaults. On multi-brand hosts this means a settings edit can change calculation behavior without a deployment.
- How much work is the v2.8.0 upgrade?
- For a single-brand install, v2.8.0 is effectively a bug fix and roughly half a dev-day to verify. For multi-brand hosts, plan it as a behavior-change release of about 1.5 to 2 dev-days, dominated by inventorying export consumers, auditing historical invoices:pending records, and per-brand smoke tests. The release notes describe no migration, so confirm that before rollout, and treat the minor version bump as misleading for multi-brand setups.
- Why did the invoices:export filenames and CSV output change?
- On multi-brand hosts, export now produces one file per brand, so belege.csv becomes files such as belege_marke-2.csv. Writing CSV to stdout also requires the --brand option. Any automated ingestion that globs the old single filename will silently ingest one brand or none, so update consumers before upgrading.
- Does the INVOICES_RETRY_SCHEDULE environment kill switch still disable retries?
- That is the key risk to verify before relying on config-based rollback. Since retry timing now follows per-brand saved settings, the v2.7.0 kill switch may no longer disable retries as it did. Confirm precedence between env/config and database settings on a staging copy first, and use --brand to target or shard runs per brand.
- What production risks should I watch after upgrading?
- Drain queues before rollout, because jobs queued before the deploy lack brand context and will run with default-brand settings. send() on a failed row still bypasses the atomic claim, so duplicate sends remain possible regardless of this release. Exit codes only reflect the first failing brand, so cron alerting needs another way to identify which brand failed, and per-brand loops multiply runtime, which can collide with withoutOverlapping on long exports.
- When should I use this instead of Stripe, Cashier or a full billing platform?
- Choose Statamic Invoices when you need simple, branded invoice documents and totals kept alongside your content, and you do not need subscriptions, payment processing or dunning. If you need recurring billing, payment collection or tax filing integrations, an external billing platform or Laravel Cashier is a better fit. The addon is a lightweight option, not a replacement for a payments provider.