Booking and check-in
Beauty, wellness, and in-home services do not sell a shelf SKU—they sell a technician’s time on a station. If the system is only checkout while bookings live in a WeChat group and the roster on a whiteboard, the front desk spends the day on collisions and empty slots. We first map where bookings come from: phone, Meituan, mini program, regulars walking in to a named technician. Those channels must land on one calendar. Bookable slots show by store, technician, and station; reschedule and cancel have rules; no-shows release the slot on a written clock. If customers can reschedule themselves, the desk stops being a switchboard.
Cards and balances
Course cards, visit packs, stored value, and gift items mixed together with balances in a notebook almost always means the customer and the store remember different numbers. Redemption must confirm item, count, operator, and time—signature or a check-in code when needed. Cross-store use, expiry extensions, transfers, and refunds live in the system, not a verbal manager exception with nowhere to look. If every balance change traces to a line, disputes can be handled and the desk can turn the screen to the customer.
Technician commission
Service commission, card-sale commission, named technicians, overtime add-ons, and referral bonuses—once the rules multiply, a month-end spreadsheet convinces nobody. Technicians keep clients off-book, the desk edits tickets, and actual service time never matches. We make commission configurable, with per-person and per-item detail technicians can check and finance can recompute. Rules are walked line by line before build; changing definitions after go-live is another round of broken trust.
Cross-store and add-ons
Cross-store redemption, named technicians, overtime add-ons, and gift items on a new card each change balance and commission. If those rules live only in a manager’s notes, two stores will execute them differently and you get complaints and internal disputes together. We configure which card types travel, which items do not, and how many expiry extensions are allowed, so the desk can reconcile on screen with the customer. Follow-up tasks trail the redemption instead of sitting in a pool nobody opens.
Client records
A client file is not a CRM slogan—it is so the next visit can continue: allergies, preferences, last service, when to follow up. Visit rate, card burn, and repurchase come from redemption history, not a weekly form the manager fills. Go-live usually connects the booking calendar and redemption first, then historical card balances, then commission. Training is front desk and technicians; the pilot is the store whose book is fullest—that is where collisions, reschedules, and empty slots actually show.