How to Choose a Designer Toy Retail System: IP Products, Blind Boxes and Fan Loyalty
A queue for a blind-box launch can expose weaknesses that an ordinary checkout demonstration misses. Stock may be recorded in full boxes when customers buy individual units. An online channel may show availability after a store has sold the last item. An associate may be unable to recognise a committed collector.
The Chinese source cites a Guangdong Toy Association estimate for 2025 of RMB 87.97 billion in market size and 21% growth. For brands managing that kind of expansion, system selection needs to address product complexity, stock accuracy, fan relationships and multiple retail formats together.
1. Can the product model represent the IP business?
A designer toy catalogue includes IP, collection, character, rarity, material, copyright year and size. These attributes need to support operations and analysis, rather than exist only in a product name.
Ask how the system connects a collection to its variants, applies prices and promotions, and reports results by IP or rarity. Product data also needs to remain consistent when a new series reaches multiple stores and franchise partners.
Check PDQ-to-unit conversion
Supply and display packaging may contain six, nine or twelve units, while checkout occurs by individual item. A defined conversion should flow through ordering, stock movement and ERP interfaces without forcing cashiers to calculate it manually.
PEKON Smart Retail System supports product and unit management, but the exact IP attributes, rare-edition SKU structure and conversion rules need to be established during requirements workshops.
2. Can inventory follow the way blind boxes are sold?
Cartons, full boxes, packs and individual items represent different stock levels. Splitting packaging or selling a combination must update the appropriate quantities. Demonstrate the complete movement rather than accepting a general claim of inventory support.
Rare designs may sell out while regular variants accumulate. Inventory should therefore be visible by variant, location, channel and relevant stock status. Reservations and logical warehouses also affect what each channel can sell.
Direct retail, online orders and unattended devices may share a stock pool or use separate allocations. Decide those rules explicitly. When assessing PEKON or another supplier, confirm which splitting steps are automatic, which require a store action, how rare stock is allocated, and the direction of any WMS interface.
3. Do loyalty and private-domain customer engagement recognise collectors?
Pop Mart's 2025 interim figures cited in the source reported 59.12 million registered members in mainland China at 30 June, with members contributing 91.2% of sales in the first half. These figures illustrate why membership is central to this category.
Occasional shoppers and collectors have different relationships with an IP. Alongside spending and frequency, useful segmentation can consider collection depth, preferred series, rarity preferences, purchase intervals and launch participation. Any additional touchpoint data depends on what the brand can actually obtain and connect.
A mini-program can provide IP information, limited-release pre-sales and stock enquiries. POS and PEKON Omnichannel CRM & Loyalty Platform records can help associates recognise preferences during service. The value comes from continuity across those interactions.
PEKON's One ID approach connects store POS, mini-programs, WeCom store associate engagement and device touchpoints. Confirm whether the proposed project includes the brand's required IP preference fields and the configuration needed for reservations or limited-release lotteries.
4. Can different store formats share data without losing their operating rules?
Direct stores, franchise outlets, pop-ups and unattended devices have different workflows. The source also notes work on drafting a national technical standard for designer dolls, reflecting the category's increasing formalisation.
A direct store may need a full POS and CRM workflow. Franchise partners need authorised product, price and promotion policies with clearly defined local discretion. Pop-ups may require mobile checkout and temporary permissions. Devices need product, stock and sales data, together with low-stock replenishment signals.
A shared data foundation does not require identical modules everywhere. Define which rules headquarters controls and which decisions each format can make.
Seven questions to use in supplier demonstrations
| Area | What to ask |
|---|---|
| IP product model | Can the platform manage collection, character and rarity as usable attributes? |
| Unpacking | How does splitting a carton or box update parent and child stock? |
| PDQ conversion | Are supply units and individual retail units reconciled across documents? |
| Fan segmentation | Can the brand distinguish collector interests and depth of engagement? |
| Retail formats | How do stores, pop-ups and devices handle their specific workflows and connectivity conditions? |
| New IP launches | How are products, promotion combinations and franchise updates configured and distributed? |
| Integration | Which system owns ERP, WMS, online order and membership data, and who handles exceptions? |
Frequently asked questions
How does this differ from selecting a basic POS?
The assessment includes IP product relationships, packaging conversions, fan loyalty and channel coordination, not just payment collection.
What inventory levels should be supported?
The levels used by the brand, potentially including cartons, boxes, packs and individual units, with traceable conversions between them.
Why does PDQ matter?
Ordering and display quantities can differ from the units sold to consumers. Inconsistent conversion creates discrepancies between systems.
What should fan loyalty capture?
IP and series preferences, collection depth and launch engagement alongside conventional purchase and membership information.
Can unattended retail devices be integrated?
Product, stock, sales and replenishment workflows can be connected, but device interfaces and project responsibilities must be confirmed.
Why can a new IP launch become a bottleneck?
Master-data preparation, bulk product setup and franchise synchronisation can delay a launch even when the promotion engine itself is adequate.
How long does implementation take?
It depends on organisational scope, data quality, interfaces and operating rules. A fixed timeline without these inputs is not a reliable basis for planning.
Define responsibilities before choosing the platform
A useful selection process establishes both what the retail system owns and what remains elsewhere. Test that division through real products, launch scenarios and store workflows before committing to implementation.