Managing service packages in a beauty care chain involves more than redemption. Trial vouchers support first visits, treatment courses and visit bundles shape subsequent service, and stored value or long-term benefits require ongoing usage records. One visit may combine a treatment, a promotional benefit and a product purchase.
Brands must design benefits, execute consistent rules and understand what was sold, where it was used, what remains and what exceptions occurred. Product purchases after treatment still require normal retail payment, inventory and member records. The companion system-selection guide covers appointments, scheduling, redemption, franchising and cutover; this article focuses on acquisition, upgrades, repeat visits and outstanding obligations.
1. Packages support three operating objectives
| Objective | Typical benefit | Records needed |
|---|---|---|
| Acquisition | Trial vouchers, introductory packages and first-visit benefits | Issue source, claims, first-visit identification and actual use |
| Upgrade | Move from a single treatment to a course, visit bundle or longer-term benefit | Upgrade context, treatment of original rights, additional payment or benefits, member and store |
| Repeat visits | Courses, visit bundles and stored value | Remaining benefits, usage dates, individual fulfilment, expiry and adjustments |
A feature labelled “packages” does not prove these relationships work. Validate the path from issue or sale to identification, use and reporting by member, store and benefit type. Software executes and records the rules; it does not itself create growth.
2. Track outstanding obligations separately from sales
Selling prepaid rights begins an ongoing fulfilment obligation. Management needs to know how much remains, how long it has been outstanding and where it is concentrated. Recently sold benefits and long-unused benefits have different operating implications.
| View | Required records | Question answered |
|---|---|---|
| Ageing | Sale date, last use, remaining visits and status | Which older packages have little or no use? |
| Store distribution | Packages sold and fulfilled or outstanding benefits by store | Where is future service demand accumulating? |
| Funds and fulfilment pressure | Volume and trend of obligations linked to advance payments | What service capacity and operating arrangements need attention? |
Distinguish remaining visits from remaining monetary value. Discounts, free visits and mixed services mean they are not interchangeable. Visit counts support fulfilment; monetary measures support operating and financial reconciliation.
If a store sells packages faster than it delivers services, headquarters should see outstanding rights and their age alongside sales. Retail systems provide sale, balance, usage and adjustment records. Revenue recognition and accounting follow contracts, fulfilment and the brand’s applicable accounting policies.
3. Product retail continues after the treatment
Beauty care chains often sell both treatments and take-home goods. Customers may buy products after care or buy first and book a later service. These remain distinct processes even when they occur during one visit.
Using a purchased treatment fulfils a service entitlement and creates redemption records. Selling a product creates a retail transaction, payment, promotion or return and inventory movement. Both concern the same member, but do not necessarily belong in one document.
Headquarters needs to see services received, benefits used, products purchased and the relevant stores. Preserve each process correctly while linking them through the member relationship.
4. Packages and coupons represent different relationships
| Type | Business relationship | Control focus |
|---|---|---|
| Purchased package | Service or stored-value rights awaiting later fulfilment | Ownership, remaining quantity or value, validity, current use and history |
| Promotional coupon | A marketing benefit | Conditions, expiry, applicability, stacking and redemption |
| Gift or trial benefit | Experience, gifting or specific member service | Identity, eligibility, claim or service and usage state |
All may appear in a member wallet, but creation, use and subsequent treatment differ. Refer to the beauty care system-selection guide for the wider appointment, redemption and franchise workflows.
5. More stores make consistent execution harder
A familiar employee can resolve many single-store questions manually. Across regions and teams, explicit rules become essential: where benefits work, how eligibility is checked, whether states remain consistent after use, expiry, refunds or adjustments, and how disputes or duplicate redemption are traced.
Cross-store benefits often fail because revenue and cost ownership remain unclear. If Store A sells a package and Store B delivers the treatment, sales attribution, service cost, commission and internal settlement must be agreed. A working redemption button does not give Store B an operating incentive or decide those allocations.
Define the business policy first, then configure execution. Each use should leave a record that can be reconciled across stores.
6. Divide responsibilities between CRM, POS and customer touchpoints
| System or touchpoint | Role | Typical actions |
|---|---|---|
| CRM | Member relationships and relevant benefit rules | Identity, tiers, points, coupons, tags, groups and member records |
| Mini-program | Customer access | Benefit enquiries, coupon claims and appointments |
| Store POS | Transactions and redemption | Identify members, sell goods, use coupons, redeem services and take payment |
| Adviser tools | Personal service and follow-up | Invitations, communication and product or campaign sharing |
| Store team | Actual delivery | Treatments, product sales and benefit confirmation |
Agree who maintains identities and rights, where customers query them, how stores identify and redeem them, and where retail and service records return. PEKON Omnichannel CRM & Loyalty Platform supports profiles, tiers, points, coupons, tags and groups; WeChat mini-programs can provide benefit, appointment and member-service access.
7. Test more than successful redemption
A demonstration of package creation and a redemption confirmation leaves much unproven. Use continuous scenarios:
- Trial-led first visit. Follow source, claim, customer identification and use. Check record completeness rather than assuming the system proves exclusive acquisition attribution.
- Upgrade after a trial. Show how new rights, original rights, additional payment and member/store attribution are recorded.
- Several benefits held by one member. Distinguish types, validity, balances and usage history, rather than judging the wallet’s appearance.
- Treatment and product purchase. Test service use separately from retail checkout and inventory, linking both to the same member.
- The same benefit across stores. Test applicability, visible state, post-use changes and discrepancy resolution against actual cross-store rules.
- Refund or adjustment. Check eligibility, permission, preserved usage history and links to the original transaction.
- Long-outstanding benefits. Query remaining rights and ageing by member, store or type, supporting operational and financial review.
The real requirement is the entire lifecycle from creation and ownership through use and exceptions, alongside merchandise retail.
8. PEKON’s role in combined service and retail operations
For medium and large beauty care brands selling both goods and services, PEKON addresses the combination of retail, membership and service entitlements. CRM manages member information and rules. The PEKON Smart Retail System and POS support identification, coupons, normal product sales, payments, service-product redemption after treatment and gift benefits. Mini-programs and adviser tools provide customer and staff entry points.
A complete treatment-course management centre, complex cross-store packages, transfers and freezes, complex refunds, therapist scheduling, room or bed allocation, sophisticated commissions and full package accounting require explicit project-by-project scope confirmation.
Frequently asked questions
How do packages differ from coupons?
Packages usually represent purchased rights awaiting fulfilment; coupons provide marketing discounts or benefits. Their creation and subsequent treatment differ.
How can trial-voucher acquisition be evaluated?
Record source, claim, first visit and actual use. Attribution of a new customer to a voucher depends on the brand’s own channel and measurement rules.
What happens when a trial becomes a course?
Define new rights, treatment of the trial, additional payment and member/store records. Test complex offsets or carryovers during selection.
How should money received for stored value or courses be recorded?
The retail or loyalty system records sales, remaining benefits, use and adjustments. Finance determines revenue recognition, contract liabilities and other accounting under applicable policies and contracts.
Must services and goods use one order?
That depends on system design. Both must link correctly to the member, store and actual consumption while preserving their distinct processes.
Can all stores share entitlements?
Only under agreed rules and configuration. Confirm eligibility, visible states, attribution, permissions and exceptions.
Is another system always needed for packages?
No. If existing processes reliably support benefits, service redemption, retail and multi-store traceability, an extra system may be unnecessary.
What matters most in selection?
Run the real lifecycle: issue or sale, ownership, first visit, service, product purchase, multi-store use, adjustment and outstanding-benefit review.
Connect benefits to actual fulfilment
Packages have both marketing and continuing service obligations. Trial benefits can introduce a customer; courses and visit bundles support later consumption. Each still depends on store execution and accurate member and fulfilment records.
Service use and merchandise sales need continuous member visibility without being forced into one process. Test real scenarios rather than count package features, and confirm complex industry requirements within the project scope.