Skip to main content

Reports and audit exports

Use reporting routes, audit exports, and traceability views to move from operational monitoring into launch and compliance review.

Updated March 22, 2026
2 min read

Overview

/reports is the operational command center for finance, production, compliance, inventory, and traceability review. Treat it as the place where launch teams confirm that the numbers and release records agree before product goes out the door.

Core report surfaces

  • /reports/profit-loss for revenue and margin direction
  • /reports/cost-analysis and /reports/margin for formulation economics
  • /reports/inventory and /reports/inventory-movements for stock position and movement review
  • /reports/production for batch activity
  • /reports/compliance for release-oriented compliance review
  • /reports/traceability/batch and /reports/traceability/ingredient for audit trails
  • /reports/audit-export when you need a packaged export for downstream review
  1. Review inventory and inventory movements.
  2. Check production and traceability views for the batches going out.
  3. Confirm cost analysis and margins still match the expected formula economics.
  4. Generate any audit export needed for QA, finance, or manufacturer review.

What this should reconcile

Before launch, the reporting layer should agree with:

  • ingredient and lot balances
  • batch deductions
  • cost snapshots
  • label and compliance outputs
  • sales and profitability records

If these surfaces disagree, treat that as a release issue, not just a reporting issue.

  • /reports
  • /reports/audit-export
  • /reports/traceability/batch
  • /reports/traceability/ingredient
  • /reports/inventory
  • /reports/production

Next docs

Related Docs

Need support instead?

Use the Help Center for troubleshooting, billing questions, account issues, and product guidance once your setup is already in motion.