Pandora Fitness / Commission reporting
A clearer monthly commission workflow
A Python system turns sales, attendance and staff data into branch-specific commission reports with visible checks and individual breakdowns.
The process
Sales, attendance and staff information arrived in separate spreadsheets. The two branches used different formats and rules. Preparing reports meant matching people and packages across sources, applying the relevant rates, checking exceptions and producing a usable result for managers and staff.
The workflow
A spreadsheet export supplies the system with sales, attendance and staff data. Shared Python functions handle common calculations, while branch settings preserve the rules that differ. The output is versioned and includes checks for price mismatches and packages that do not match reference data.
Designed for review
Exceptions stay visible. The system marks records that need attention, keeps previous output versions available and can produce an individual staff breakdown. Managers can review flagged rows before using the results.
Refined through use
The work grew from a single-branch script into a shared calculation library with branch-specific steps. Package checks, clearer highlighting, versioned output and staff reports were added as the workflow's needs became clearer. An operator guide records the monthly steps and common issues.
The useful lesson
A recurring calculation is only one part of the job. The inputs, branch rules, exceptions and report format all need to be clear enough for someone to review and run the process again.
Have a recurring process with spreadsheets in the middle? Tell me about it.