Cosmetics recalls are not completed simply by issuing a notice. A workable recall process must connect the affected batch, store inventory, sales suspension status, sales orders, returned products, and final handling results in one traceable record chain.
Whether a brand can trace products back to individual orders or physical items depends largely on the granularity of its daily inventory and transaction records.
Building Executable System Tasks from Recall Requirements
Under Article 44 of the Regulation on the Supervision and Administration of Cosmetics, the registrant or filing entity is responsible for implementing a recall, notifying operators and consumers to stop selling or using the affected products, keeping recall and notification records, and reporting the recall to the provincial drug administration. Operators are required to stop selling the affected products and cooperate with the recall.
To turn these requirements into executable work, the retail system should at least record:
- Product SKU and affected batch numbers;
- Stores, channels, operators, and other involved parties;
- Recall start time and sales suspension status;
- Product isolation, return, disposal, or other handling methods;
- Responsible employees, deadlines, completed tasks, and outstanding tasks.
The same SKU may correspond to multiple production batches. Batch numbers therefore need to be mapped to packaging information, receiving records, upstream documents, and any supplier or internal batch-number conversion rules.
The recall scope may also cover e-commerce channels, distributors, and other sales channels. The retail system should manage connected stores, inventory, and orders, while exchanging relevant results with ERP, WMS, and other channel systems.
Store Sales Suspension Must Apply to Both the System and Physical Products
If the system supports batch-level control, the affected batch can be blocked directly. If the system only supports SKU-level control, the entire SKU may need to be suspended before stores distinguish the affected batch through physical inspection.
A system block does not mean that physical handling has been completed. Store employees still need to check shelves, back rooms, reserved goods, and other non-sale areas, isolate recalled products, record actual quantities, and compare physical counts with system records.
Products in transit should also be included. The system should record whether goods are intercepted during transfer, rejected at receiving, or placed under a restricted status. Transfer records and final receiving results should remain available for review.
Order Traceability Depends on the Granularity of Sales Records
Inventory records alone do not prove which customer purchased an affected product. The key question is whether the actual batch or unique item was recorded in the sales transaction.
| Sales record type | What can be traced | Traceability level |
|---|---|---|
| Order lines store the actual batch number | Sales orders and quantities associated with the affected batch | Batch-level traceability, subject to checks for returns, exchanges, and backdated transactions |
| Unique item code is scanned and linked to the batch | The specific physical item and its related order | Item-level traceability, provided the outbound code is stored in the actual sale |
| Order stores only SKU, store, and transaction time | Candidate orders estimated through inventory and outbound rules | Rule-based estimation, not confirmed batch or item traceability |
Member and non-member orders should also be distinguished. For anonymous transactions, the system may not be able to reconstruct customer identity. Recall reports should therefore separate confirmed orders from pending or estimated orders.
Recall Returns Should Be Distinguished from Regular After-Sales Returns
A recall return is not simply an ordinary return. Its record should connect the original order, product line, batch or unique code, quantity, refund result, receiving store, operator, and recall reason.
If the original order cannot be found, the store should use an approved recall registration or exception process. The record should include the product, batch or unique code, quantity, store, customer-provided evidence, and final handling result. Refund rules should follow the brand’s approved policy.
Refund status and physical receipt status should be recorded separately. Recalled products should not return to saleable inventory. Where necessary, the retail system should pass the relevant information to ERP, WMS, finance, or other systems for follow-up.
Recall Results Should Be Reconciled by Status and Final Destination
At the beginning of a recall, the affected quantity should be fixed using upstream shipment records, store receiving records, transfers, and sales data.
During execution, each affected product should have a current status, such as:
- Isolated at store;
- Intercepted during transportation;
- Returned by customer;
- Sold but not yet returned;
- Returned and disposed of;
- Quantity difference pending verification.
Each product should occupy one current status at a time. The original source of the product and its current handling status should be recorded separately so that a product is not counted repeatedly across different stages.
The final review should check transfers, regular returns, exchanges, backdated transactions, inventory adjustments, write-offs, and customer returns. Orders identified through estimation rather than confirmed batch records should remain marked as pending verification.
PEKON Connects Batch Inventory, Store Transactions, and Recall Results
PEKON Smart Retail System covers receiving, transfers, stocktaking, sales, returns and exchanges, and batch or expiry-date management.
Depending on data availability, control rules, and project scope, PEKON can coordinate with ERP, WMS, and POS systems to support sales suspension, batch isolation, order traceability, recall returns, and result reporting.
Recall management should not be treated as an isolated process. It should be added to existing product, inventory, transaction, and after-sales records through dedicated recall tasks, statuses, and reconciliation results.
For beauty retailers, learn more about the PEKON beauty retail solution.
Conclusion
The level of cosmetics recall traceability depends on the batch, inventory, and transaction data retained in daily operations.
A complete record chain begins with the affected SKU and batch, continues through sales suspension, physical isolation, order review, and customer returns, and ends with a confirmed status and final destination.
During reporting, confirmed records should be separated from estimated records, and the product’s original source should be separated from its current status. This makes recall execution easier to verify and follow up.
Frequently Asked Questions
If the system has batch inventory, can it always identify who purchased the affected batch?
No. Batch inventory only shows where the batch may have entered or remained in the business. To identify related buyers, the actual batch or unique item must be recorded in the sales order.
Can the system suspend sales only for the affected batch?
It depends on the system’s control granularity. If batch-level control is supported, only the affected batch can be blocked. If the system only supports SKU-level control, the SKU may need to be suspended while stores complete batch-level checks.
Can a store register a recall return if the customer has no receipt or the original order cannot be found?
Yes, if the brand has an approved exception process. The store should record the product, batch or unique code, quantity, customer evidence, store information, and handling result, with the refund processed according to the approved policy.
Why should recalled products not be processed as regular returns?
Recall returns require batch information, recall reasons, product sources, customer return status, and final handling results. Treating them as ordinary returns may break the traceability chain and make final reconciliation more difficult.
Which records should be checked first when recall quantities do not reconcile?
First check the recall start time and batch scope. Then review goods in transit, returns, exchanges, backdated transactions, inventory adjustments, write-offs, customer returns, and any candidate orders identified through estimation.
If your brand is planning cosmetics batch traceability or recall management, the PEKON consulting team can help review batch records, store sales data, system responsibilities, and reconciliation requirements.