Should Headquarters Sync Temporary Store Bundles to ERP?
Handle Temporary Store Bundles Separately from ERP Product Master Data
A one-time temporary bundle usually does not require a new bundle SKU in ERP. However, component sales, inventory changes, and settlement results still need to be returned according to the agreed interface rules. Only when a bundle is sold over the long term, pre-assembled, purchased independently, or accounted for separately should it be added to the formal product master data.
PEKON records the temporary bundle, component relationships, and transaction results on the POS side. Which product lines, quantities, and amounts are sent back to ERP depends on the brand’s product master data policy and integration design.
Record Master Data, Inventory Changes, and Sales Results Separately
Product master data maintains product codes, costs, and purchasing rules. Component inventory reflects the physical goods held by stores, while sales results record the transaction amount. When a one-time bundle does not hold independent inventory, ERP does not need to create a new bundle SKU, but it still needs to verify the component quantities and sales results. A bundle that is sold continuously, pre-assembled, or accounted for independently should have a formal product record and defined component relationship.
Validate Interface Results with the Same Transaction
Take a RMB 129 gift set made up of products A, B, and C as an example. After two sets are sold, the POS records RMB 258 in sales, while the inventory of each component is reduced by two units:
| Business Condition | ERP Handling | Interface Validation Focus |
|---|---|---|
| One-time temporary bundle | Do not create a bundle SKU; the POS returns component and sales results. | Each component decreases by two units. ERP records the result according to the store warehouse, accounting time, and interface responsibilities. |
| Promotional bundle | ERP receives the sales results of the original products. | Components record sales and inventory separately, and the allocated amount totals RMB 258. |
| Formal bundle | ERP creates a bundle SKU and its component relationship. | Use consistent product codes and avoid duplicate accounting. |
The interface may use a bundle header line to record the RMB 258 transaction amount and component lines to record inventory changes. In this structure, the header line does not deduct inventory, and the component lines do not calculate the sales amount again. Alternatively, the system may return three component sales lines directly, with the allocated amounts adding up to RMB 258. Both methods are workable as long as the bundle line and component lines do not duplicate sales recognition or inventory deduction.
Each returned record should at least be associated with the original POS order number, temporary bundle identifier, component SKU, quantity, allocated amount, and processing status. Returns should follow the original sales structure to prevent the sale from entering ERP as a bundle while the return is processed only as individual components.
For related responsibilities, see How Should Trendy Toy Retail Systems Be Divided Among ERP, WMS, and OMS?.
PEKON Capabilities and Integration Conditions
Temporary bundle management and component inventory deduction are confirmed PEKON product capabilities. The ERP return fields, document structure, and processing status depend on the scope of the interface integration. After headquarters distinguishes one-time bundles, promotional bundles, and formal bundles, it can define what ERP should receive and at which point the result should be recorded.