Product Decisions This Supports

Feature delivery: Enables self-service Excel/CSV import and export for admin users directly inside the Voyager admin panel, avoiding bespoke "download CSV" endpoints per model.
Roadmap: Unlocks data-portability and reporting workstreams — bulk export for BI feeds, migration, compliance extracts, and QA seed data — with lower build effort than a custom export service.
Build vs buy: Strong "buy" case when the app already runs Voyager; the new custom export format capability (v2.2.0) tips the calculus further, letting teams define partner/tenant/regulatory formats declaratively instead of forking the package.
Use cases: Ops/analytics self-serve reporting, per-tenant export templates, regulatory filings with fixed column schemas, localized spreadsheet formats (e.g., delimiter/decimal conventions), and bulk import for data onboarding.
Prioritization signal: If export formatting requests are recurring support tickets, this release converts a recurring engineering task into configuration.

When to Consider This Package

Adopt when:

The project is already on Voyager (Laravel) and admin-driven import/export is a near-term need.
Stakeholders want configurable export schemas (partner formats, tenant-specific layouts) without custom code — now materially easier with custom export formats.
The datasets are moderate and admin-triggered rather than high-volume, streaming, or scheduled.

Look elsewhere when:

You are not using Voyager — integrate Laravel Excel (Maatwebsite) directly for less coupling.
You need scheduled/orchestrated exports, very large datasets, streaming, or advanced formatting (charts, pivots, templated reports) — consider a dedicated reporting/ETL tool.
You require a vendor SLA or long-term commercial support; weigh community-package maintenance risk and exit cost (abstract the export layer behind an interface to keep optionality).

Executives: Low-risk, low-cost capability that lets ops/analytics teams pull the data they need from the admin panel without filing engineering tickets — faster reporting and fewer internal bottlenecks. It builds on tooling we already operate.
Engineering: Thin integration between Voyager's BREAD and Laravel Excel. v2.2.0 adds pluggable custom export formats, so non-standard outputs (tenant schemas, partner contracts, regulatory layouts) become configuration rather than forks or one-off endpoints. Small maintenance surface; recommend wrapping the integration behind an internal export service/interface to control lock-in.
Product/Stakeholder takeaway: Ship reporting and data-portability features sooner, standardize export formats across tenants, and reduce ad-hoc engineering work — while keeping a clear fallback to Laravel Excel or a dedicated reporting stack if scale or support needs grow.