Beauty Retail System Selection: POS, CRM, Inventory and B2B Ordering
This guide is for brand leadership and retail, loyalty, merchandise, finance and digital teams. It provides an assessment framework covering POS, CRM, beauty advisors, department-store counters, inventory, distributor ordering, integration and implementation.
A shopper may discover a brand on Douyin or Xiaohongshu, try a product at a counter, consult an advisor through WeCom and later repurchase in a mini-program or store. Meanwhile, staff manage shades, batches, expiry dates, gifts, promotions, mall-collected payments and online orders.
Map five journeys before comparing software: how advisors sell, how customer relationships develop, how variant stock moves, how online orders are fulfilled and how distributors order. Evaluate whether the proposed systems can support those journeys continuously.
Four initial tests
- POS: demonstrate trials, samples, shades, gifts, combined promotions, member benefits and returns.
- CRM: go beyond points and broadcasts to identity, associate tools, data ownership and staff handover.
- Inventory: show how staff handle a missing shade, how an online order changes availability and how near-expiry stock is located.
- B2B: establish the source, frequency and completeness of downstream sales data before accepting claims of channel visibility.
1. Store POS and department-store counters
Payment is only the end of the sales interaction. Advisors may already have discussed skin needs, tested shades, issued samples, suggested sets, identified the member and calculated offers.
Test sales and promotions, authorised customer information, SKU-level availability, and consistent sample, gift and tester records. A useful scenario combines a returning member, a foundation trial, a shade-specific sample, a member coupon, a gift threshold and a later partial return.
Department-store sales need additional checks
| Scenario | What to establish |
|---|---|
| Mall-collected payment | Sales, payment method, mall transaction reference and trading date in the brand record |
| Combined campaigns | Compatibility and cost allocation for mall and brand offers |
| Later entry during busy periods | Permissions, historical dates, stock, benefits, advisor performance and logs |
| Returns | Original sale, mall refund evidence, stock and benefit reversals |
| Daily reconciliation | Sales, receipts, refunds, discounts, commissions and receivables |
The source states that PEKON has experience connecting to nearly ten mall systems, not every department store. Provide the actual mall list and classify each connection as existing, project-specific, batch/manual or unsupported. Confirm exception and reconciliation ownership.
2. CRM and advisor operations
One ID means matching identities across channels within a brand. A group can share CRM technology while individual brands retain separate clubs, tiers, points and benefits. Cross-brand sharing should not be assumed.
Assess three layers: identity and entitlements; tags and lifecycle operations; and advisor service, task assignment and customer handover for private-domain customer engagement. PEKON Omnichannel CRM & Loyalty Platform provides relevant capabilities, with scope determined by channels, rules and authorisation.
Agree ownership and export of profiles, points, coupons, interactions and service records during procurement. These terms affect the brand's ability to operate and migrate later.
3. Separate product detail, stock status and material purpose
A foundation shade is a specific SKU, while the same SKU can have different batches and expiry dates. Stores also hold sets, samples, gifts, testers, display units and damaged goods.
| Layer | Validation |
|---|---|
| Product detail | Consistent SKU, shade and barcode across sales, returns, stock and advisor results |
| Stock status | On-hand, available, allocated, in transit, reserved, damaged and non-saleable quantities |
| Batch and expiry | Consistent tracking through receipt, sale, movement, return and alerts |
| Non-sale materials | Separate setup, receipt, request, issue, redemption, follow-up and write-off records |
PEKON supports logical stock categories and store receiving, returns, dispatch, counts, transfers and batch management. Agree master data, the inventory system of record and update timing with ERP, WMS and OMS. Brands seeking action recommendations beyond dashboards can also assess inventory optimisation.
4. Distinguish distributor sell-in from consumer sell-out
A B2B platform manages authorised catalogues, regional prices, ordering policies, credit or terms, rebates and reconciliation. It does not automatically reveal sales at downstream stores that have not connected their data.
Direct-to-store supply, franchise distribution or agreed POS reporting can provide the basis for outlet analysis. Define the denominator whenever reporting distribution coverage: target distributors, target outlets or connected outlets are different groups.
PEKON B2B Ordering Platform supports channel workflows and integration with ERP, WMS or retail systems. Confirm the source of orders, shipments, channel inventory and consumer sales separately.
5. Assign system and group responsibilities
| Record | Typical owner and key question |
|---|---|
| Product master | ERP or product centre: how do SKUs, shades, codes and prices reach stores? |
| Store transactions | POS: how are sales, payments, returns and advisor results recorded? |
| Members and benefits | CRM: who calculates identity, tiers, points and coupons? |
| Omnichannel orders | OMS: how do routing, reservation, fulfilment and cancellations synchronise? |
| Warehouse stock | WMS: how do batches, expiry dates and movements connect to stores? |
| Distributor orders | B2B and ERP: who owns commercial policy and fulfilment? |
| Mall transactions | Brand and mall systems: how are payment and settlement reconciled? |
An API is only an entry point. Test data direction, timing, duplicate prevention, retries, exception logs and reconciliation.
Groups can standardise technology, data conventions, interfaces, security audits and reporting while brands retain separate products, pricing, promotions, loyalty, stock and permissions. Do not assume inventory or benefits move between brands.
6. Weight requirements by development stage
First store: prioritise a reliable opening, POS, products, stock, membership and payments, with room to expand.
Multi-store expansion: standardise workflows and definitions, and validate capacity, permissions, setup efficiency and franchise coordination.
System replacement: give greater weight to data scope, interfaces, pilots, rollback and phased rollout. Protect trading and member entitlements.
Use representative stores for a pilot. Mall, multi-brand, multi-country and large historical-data projects need appropriate design and testing time. Migration requires mappings, trial runs, balance reconciliation and cutover planning, not simply spreadsheet import.
7. Evaluate suppliers with real scenarios
After an initial review of products, references, qualifications and support, use anonymised brand data in a proof of concept.
- Can POS support advisor service and the actual department-store workflow?
- Can CRM preserve the brand's customer asset and support handover?
- Can stock be managed by shade, batch and sellable status?
- Are B2B data boundaries and credit policies clear?
- Are ERP, OMS and WMS responsibilities and failures defined?
- Is migration supported by mappings, validation and rollback?
- Are pilot, acceptance, training, rollout and support responsibilities realistic?
Classify each result as standard, configuration, integration, project adaptation or unsupported. Retain inputs, steps, expected and actual results, and exception evidence as acceptance criteria.
Common mistakes
Avoid comparing purchase price alone while omitting implementation and maintenance; leaving data ownership vague; underestimating cleansing and training; or deciding from a prepared demonstration without the brand's own promotions, shades, settlement and channel policies.
Further reading by topic
Detailed assessments can cover store operations, advisor efficiency, complex promotions, member service, automated journeys, samples and testers, batches and expiry dates, stock optimisation, distributor sell-through, group governance, first-store setup, migration and system return on investment.
Frequently asked questions
Which capabilities matter most?
POS, counters, CRM, advisors, shade and batch inventory, non-sale materials, B2B, omnichannel orders, migration and integration; groups also need brand isolation and reporting.
How does beauty POS differ from basic checkout?
It must support consultations, trials, gifts, complex promotions, benefits, batches and counter operations.
What is commonly missed at department-store counters?
Payment ownership, combined offers, delayed entry, returns and daily settlement reconciliation.
What should loyalty software include?
Brand-level One ID, profiles, tags, lifecycle activity, associate service, customer ownership and export, alongside points and tiers.
How should advisor departures be managed?
Reassign customers, tasks and authorised service history within the brand's systems and remove former access.
How are shades and shelf life managed?
Use SKU and batch records with explicit availability, expiry alerts, movements and separate material categories.
Why is B2B not automatically a sell-through platform?
Consumer sales require actual outlet data in addition to orders and shipments.
Is retail software needed alongside ERP, OMS and WMS?
Assess whether store transactions, service, promotions and counters are covered, then define complementary roles.
What matters during migration?
Scope, duplicates, code mappings, benefit and stock balances, trial migration, pilots and rollback planning.
Which brands should evaluate PEKON?
Brands needing coordination across stores, channels, counters, existing enterprise systems, membership, stock, ordering or multiple brands can assess the PEKON Smart Retail System, CRM, PEKON WeChat Mini-Program Suite, B2B, PEKON AI Inventory Optimization Engine and PEKON Jingang Low-Code PaaS capabilities against their own requirements.
Turn selection into an executable scope
Focus on usable store workflows, trustworthy operating records and room for growth. A supplier should document standard capabilities, configuration, interfaces, project adaptations and delivery responsibilities so the chosen solution can be implemented and accepted.