Tierd pricing for barbers/salons

[Abertrandryan]

Hello - I would really love to see tiered pricing for my barbers. EX: Kristen charges $40 per cut & Jordan charges $50... but have both of them listed under "Haircut" ... instead of having to categorize their haircuts separately. 

As of now you have to seperate them if their prices are different - so youd list it as "Haircut with Kristen" or " Haircut with Jordan" ... but with a long service list that will make the booking page a mess. 

I just want the option to change each employees pricing separately essentially.

[Donnie-M]

@Abertrandryan If it could be fixed like this, would that work for you?

Add a staff_tier attribute on the TeamMember object and a required_tier_id attribute on CatalogItemVariation. Basically, your item would have variations that are tied to a tier.  Tiers are shop-defined (Level 1, Senior, Master, whatever the shop wants to call them), stored per-location, with configurable display labels for customer-facing surfaces.

You would have to do service-first booking and it would flow like this: customer selects the service, sees available stylists with tier and resolved price inline.  No per-staff override records, no service-by-service data entry. Promoting a stylist is a one-field change on their profile that cascades to every service they perform.

The ripple surfaces would line up cleanly:

• POS walk-in: staff assignment on the ticket triggers the same tier resolution, preventing undercharges on higher-tier work
• Square Online and embedded booking widgets: catalog API returns variations with tier metadata; consumers resolve at render
• Team commission: commission engine reads resolved price at transaction time so tier uplift flows to payroll correctly
• Packages and gift cards: tier is explicit in the package definition, making upcharge-or-honor logic a shop-configurable rule
• Reporting: You get clean item reporting and the shop can break down by tiers by parsing the stylists tier flag.

Opt-in per account, or gated to Appointments Plus. Shops without tiers defined see no change, existing flat-price services inherit as "no tier required," fully backward compatible.

I phrase this like this to see what you think.  Does it make sense to you, does it fit what you want from your point of sale?  Let me know, this will help.