Problem
Screenprinting account ranking needs tenant-facing sort controls that make it easy to review sales by order date and salesperson/owner, without relying on code or ad hoc exports.
Intended outcome
Add usable account-ranking sort/filter controls for the Screenprinting/FraterniTees account experience so a user can rank accounts by sales timing and salesperson.
Acceptance criteria
- Account ranking can be sorted by recent sales date.
- Account ranking can be sorted or filtered by salesperson/owner where runtime data has that attribution.
- Existing account ranking, score, search, and grade behavior remains available.
- The UI exposes the controls directly and works without mock data.
- Add focused regression coverage and run repo verification.
Non-goals
- No production data writes or historical backfill.
- No Printavo write-back.
- No broad account-ranking redesign beyond the requested sort controls.
Test expectations
- Add a RED test for the ranking behavior before implementation.
- Run the relevant targeted test, then
npm run verify.
Architecture impact
Keep the behavior in the existing Screenprinting/FraterniTees account-ranking surface and favor reusable ranking/filter helpers over tenant-only branching where practical.
Problem
Screenprinting account ranking needs tenant-facing sort controls that make it easy to review sales by order date and salesperson/owner, without relying on code or ad hoc exports.
Intended outcome
Add usable account-ranking sort/filter controls for the Screenprinting/FraterniTees account experience so a user can rank accounts by sales timing and salesperson.
Acceptance criteria
Non-goals
Test expectations
npm run verify.Architecture impact
Keep the behavior in the existing Screenprinting/FraterniTees account-ranking surface and favor reusable ranking/filter helpers over tenant-only branching where practical.