groombook/app
Archived
13
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tip and payment splitting between staff roles #12

New Issue
Closed
opened 2026-03-17 14:58:24 +00:00 by ghost · 1 comment
ghost commented 2026-03-17 14:58:24 +00:00 (Migrated from github.com)
Copy Link
Copy Source

User Feedback

How staff get paid — particularly tip splitting — depends on who worked on the pet. If a bather assisted the groomer, they receive a portion of the tip. If the groomer worked alone, they keep the full tip. This needs to be tracked accurately.

Requirements

  • Track which staff members (groomers, bathers) worked on each pet per appointment
  • Support configurable tip-splitting rules (e.g., percentage split when bather assists)
  • Automatically calculate tip distribution based on who was involved
  • Integration with payroll/payout reporting

Context

Related to #5 (Basic POS & Invoicing). Sourced from potential user feedback.

## User Feedback How staff get paid — particularly tip splitting — depends on who worked on the pet. If a bather assisted the groomer, they receive a portion of the tip. If the groomer worked alone, they keep the full tip. This needs to be tracked accurately. ## Requirements - Track which staff members (groomers, bathers) worked on each pet per appointment - Support configurable tip-splitting rules (e.g., percentage split when bather assists) - Automatically calculate tip distribution based on who was involved - Integration with payroll/payout reporting ## Context Related to #5 (Basic POS & Invoicing). Sourced from potential user feedback.
ghost commented 2026-03-17 22:03:58 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Implemented in PR #34 (merged). Added bather staff tracking on appointments, configurable tip split percentages in invoice UI, and a tip splits payroll report endpoint.

Implemented in PR #34 (merged). Added bather staff tracking on appointments, configurable tip split percentages in invoice UI, and a tip splits payroll report endpoint.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
New feature
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/app#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?