Services and packages as sellable items
A treatment or a bundled package is set up and priced the same way a product is, so it sells through the same POS and sales flow without a workaround.
A salon or spa doesn't sell inventory in the usual sense - it sells time and treatments. Farexa lists services and packages the same way it lists products, connects booking inquiries from your own website straight into CRM, and keeps staff access matched to who's actually taking payments.
Updated
A salon or spa's real inventory problem is that its main product isn't a product at all - it's a service, and most ERPs were built around things you can count on a shelf. Packages get tracked in a notebook, follow-ups depend on someone remembering, and the person on reception often has the exact same system access as the owner.
Farexa treats a service or a package as a sellable item with its own pricing, so it moves through the same POS and sales flow as anything else - no separate spreadsheet for treatment bundles. Booking and service inquiries submitted on the salon's own public website land directly in CRM, so a follow-up is a task on a real customer record, not a sticky note.
Staff access follows the same role-based model the rest of the platform uses: a stylist, a front-desk booker, and a manager can each have exactly the access their job needs, without three people sharing one login to keep discounts and refunds under control.
A treatment or a bundled package is set up and priced the same way a product is, so it sells through the same POS and sales flow without a workaround.
Inquiries and booking requests captured from the tenant's own public website land directly in CRM, ready for follow-up, instead of arriving as a message someone has to copy in by hand.
Roles and permissions control who can take payments, apply discounts, or see customer history - access matches the job, not a shared login.
List treatments and packages with their own pricing, and assign staff the access level that matches what they actually do at the counter.
A visitor's booking or service inquiry on the public site becomes a CRM record automatically, not a message waiting to be re-typed.
Every sale, follow-up, and package redemption sits against the same customer record, so a repeat client's history is one lookup, not a memory test.
Services and packages sell through the same flow as products - no separate manual tracker for treatment bundles.
Booking inquiries and follow-ups land in CRM against the customer's real record, so nothing depends on someone remembering to call back.
Role-based access means a stylist and a manager see different things, without sharing one login to control who can discount or refund.
Yes. Packages are set up and priced the same way individual services and products are, so a bundled treatment sells through the same POS and sales flow.
Yes. Inquiries and booking requests captured on the tenant's public website land in CRM as records ready for follow-up, rather than arriving as a message that has to be copied in manually.
Yes. Roles and permissions scope what each user can see and do - taking payments, applying discounts, viewing customer history - so access matches the role, not a shared counter login.
The same branch-scoping the rest of the platform uses applies here too, so a multi-location salon group runs on one tenant with access scoped per branch.
Book a walkthrough with your real service list and packages, and see a booking inquiry land in CRM.