In-Store Gift Set Assembly for Trendy Toy Retail: Flexible Bundling Without Losing Product Control
A customer chooses an IP collectible and wants to add a charm and other accessories to create a gift within a specific budget. The store has all the individual items, but no pre-made gift set. The customer may also already own one of the items and want to replace it, or may need to keep the total price within a clearly defined range. In-store bundling can respond to these needs, but it also creates new requirements for store operations: which products can be combined, how replacements should be priced, and how inventory and sales should be recorded after the transaction.
A gift set assembled in the store is first and foremost a sales combination. If it has not been pre-assembled or separately stocked, it should not create an independent bundle inventory balance. The transaction should retain both the combination selected by the customer and every product actually delivered, so the payment amount, component inventory, and subsequent returns can all be checked against the same sales order.
PEKON supports stores in creating temporary bundles through POS, deducting component inventory during the sale, and sending component sales and settlement data back to ERP according to the integration plan. Stores can offer flexible combinations while headquarters still retains visibility into the products actually sold and the related transaction records.
Flexible Bundling Requires Clear Product and Pricing Rules
Figures, charms, and accessories from the same IP can be combined around a gift-giving theme. When a customer already owns one item, they may want to replace it with another. The brand should first define which products can participate in a bundle, such as products selected by IP, series, category, or product status. It should also specify the number of components in each gift set and the permitted replacement range. Whether new products, limited-edition products, or low-stock items can participate should also be clearly defined, so individual stores do not make different judgments.
The pricing basis must be equally clear. A brand may set a fixed gift-set price or calculate the price according to individual product prices and configured promotion rules. Whether a replacement changes the price, how price differences are handled, whether member discounts can be combined, and which adjustments require authorization should all be reflected in store operations. When a salesperson selects the actual components in POS, the system creates the transaction based on configured prices and promotion rules. Replacements or price changes outside the permitted range must follow the brand’s authorization rules.
For example, a store may launch a themed gift set priced at RMB 129, containing products A, B, and C by default. If the customer replaces C with D, the salesperson must first confirm whether D is within the permitted replacement range. The store must then determine whether the RMB 129 set price still applies or whether the price should be recalculated based on the difference. This preserves room for in-store service while preventing staff from relying on memory to decide prices.
With clear rules, stores can complete bundling and sales within an approved range, while headquarters can trace the products and prices included in every combination.
When a Gift Set Is Sold, the Actual Products Must Remain Clear
Store-level bundle sales generally involve three types of objects. A physical set that has been pre-assembled and stocked as an independent SKU deducts the set inventory when sold. A temporary or virtual bundle created in POS without holding separate inventory deducts the inventory of its components according to the bundle relationship. If each product remains an independent line item and receives a bundle price only after the required conditions are met, it is a promotional combination. It also deducts each component’s inventory and does not require temporary bundle inventory.
PEKON Smart Retail System can record the relationship between temporary bundles and their components, allowing stores to create inventory changes based on the individual components sold. The users who can create temporary bundles, the eligible products, and the authority to change prices can be configured according to the brand’s store management rules.
For example, one unit each of products A, B, and C forms a temporary gift set priced at RMB 129, and two sets are sold in one transaction:
| Record Object | Sales Record for This Transaction |
|---|---|
| Temporary bundle | Two sets sold, with a total transaction amount of RMB 258; no independent bundle inventory balance is created. |
| Products A, B, and C | Two units of each product sold, with the corresponding inventory deducted separately. |
Headquarters can see how many gift sets were sold and which products were included. The bundle and its components represent two reporting perspectives of the same transaction. The sales amount should be calculated under one consistent rule to avoid double counting.
If the customer replaces C with D in one of the two sets, the actual inventory change should be a reduction of two units each for A and B, and one unit each for C and D. The records for two gift-set combinations should remain, while the transaction amount should be calculated according to the applicable price after the replacement. This allows the store to answer how many gift sets were sold and accurately reflects the inventory change for each product.
When a return occurs, inventory quantity and refund amount must be handled separately. The store should first use the original sales order to confirm which components the customer has returned, then restore the inventory of those specific products. The refund amount should be calculated according to the allocation of the original bundle price and the brand’s after-sales rules. If split returns are allowed and the customer returns only A, the system should restore only A’s inventory rather than adding back a complete gift set. Retaining the relationship between the original bundle, components, and transaction price allows sales, inventory, and after-sales processing to refer to the same delivery.
For more information about the differences between product management objects such as bundles and individual products, see Basic Concepts of Trendy Toy Retail Digitalization.
Headquarters Should See Both Bundle and Individual Product Performance
If the transaction only records “one gift set,” headquarters cannot easily determine which products were purchased together or compare bundling performance across stores. When component records are retained, the same product’s individual sales and bundle sales can be analyzed separately. The sales volume, component contribution, and replacement patterns of temporary bundles also become traceable, preventing the performance of individual products from being hidden behind the name of a gift set.
For example, if the combination of A, B, and C repeatedly sells across multiple stores while C is frequently replaced by D, headquarters can compare the individual sales performance, price differences, and supply conditions of the two products before deciding whether to adjust the default combination. If a combination has been validated over time and needs to be sold continuously, pre-assembled, or accounted for separately, the brand can convert it into a formal bundle SKU. Until then, the temporary bundle can continue to manage inventory by component, avoiding the creation of a new headquarters product master record based solely on a one-time store-level combination.
These records reflect sales and replacement facts. Bundle frequency alone should not be used to determine customer preferences or campaign performance. Headquarters should also consider store coverage, sales period, product availability, and promotional prices. The reporting dimensions and the method for allocating bundle amounts should remain consistent with the brand’s accounting and reporting standards.
PEKON Connects Store-Level Bundling with Headquarters Product Management
PEKON Trendy Toy Retail System supports single-box, full-box, and combination sales, linking sales units, prices, and inventory deductions. Its POS temporary bundling capability supports in-store gift-set assembly while retaining component sales and settlement data, connecting store transactions with headquarters product management.
A temporary combination created in a store usually does not need to immediately create a new bundle SKU in ERP. However, component sales, inventory changes, and settlement results still need to be sent back according to the agreed interface rules. Whether the temporary bundle itself should be synchronized to ERP, and whether ERP receives a bundle identifier or detailed component data, depends on the brand’s product master data management model and integration plan. The specific support for component replacement, price-change authorization, split returns, and bundle analysis reports should be confirmed according to the brand’s rules and product configuration. For more information, see Retail System Selection FAQ.