Reporting - MUZE Architecture & Technical Documentation

Report types

MUZE generates three core reports, all served through the NestJS backend:

Report	Endpoint	Description
Store and regional spend	`GET /api/v1/reports/store-ops`	Per-store uniform spending with company/employee splits
Replacement due	`GET /api/v1/reports/replacement-due`	Employees approaching or past replacement boundaries
Production requirements	`GET /api/v1/reports/production`	Manufacturing requirements from active production orders

User-facing descriptions of each report live in the user guide. This page covers how reports are generated.

Report architecture

The replacement-due report reuses computeEntitlementPhase() from the entitlement engine, so report data and order-time eligibility always agree on phase and cycle boundaries.

Export

Format	Implementation	Notes
CSV	SheetJS client-side	Instant download, no server load; large datasets limited by browser memory
ZIP bundle	adm-zip server-side	CSV + PDF bundles for bulk downloads
PDF	pdf-lib server-side	Generated on request

Permission scoping

Role	Report visibility
STORE_MANAGER	Replacement-due for their store
HR	Spend and replacement-due across their client
MUZE_ADMIN / SUPER_ADMIN	All reports, all clients

The production requirements report is admin-only by permission (reports.production).