Pick up a bag of diapers and find its production code. Now ask a harder question: which records would your team retrieve if a distributor sent that code tomorrow?
Effective hygiene product batch traceability connects physical stock with a usable history. Printing a number is straightforward. Keeping the relationship intact as goods are packed, shipped, split and sold requires deliberate record design. For an importer, that relationship can determine whether a product query stays focused or spreads across unrelated inventory.
Start with one SKU, one finished-goods lot and one delivery. The exercise below is a proposed operating method for buyers and suppliers, not a description of a specific ERA shipment or a legal recall procedure.
A code needs somewhere to lead
A retail product identifier and a lot code answer different questions. The product identifier distinguishes the trade item; the lot code separates production groupings of that item. GS1 US explains that GS1-128 can carry attributes including batch or lot information. Choosing that symbol does not, by itself, create the underlying history.
ManufacturingProduction order, approved revision and material references
ReleaseInspection records and authorized disposition
DistributionCarton allocation, shipment reference and receiving customer
Agree what creates a new lot before deciding how the code looks. A date alone may be insufficient if different constructions or production runs share that date. Conversely, an extremely detailed printed code is not useful if nobody can interpret it after the employee who created it leaves.
The visible code can be short while the internal record is detailed. Buyers do not necessarily need confidential formulations or every supplier identity. They do need an agreed route for retrieving relevant evidence, with clear responsibility for maintaining it.
The relationship most easily lost
Consider a hypothetical distributor that opens master cartons and sends smaller quantities to several stores. The factory dispatch record may be complete, but the next movement can break traceability if the distributor records only the SKU and total quantity. A later question then reaches the warehouse without a reliable store-level allocation.
Ask receiving and dispatch teams to retain the lot reference at the level where stock is actually managed. Where a carton contains more than one lot, the record should describe that mixture. Where goods are repacked, preserve the original identity and link the new handling unit to it. Do not silently assign a fresh code that hides the original production history.
Returns deserve a separate route. Returned goods should not disappear into available stock simply because the outer bag looks similar. Record their origin, condition, lot and disposition so they remain distinguishable from untouched inventory.
Can the same lot be followed backward to its release evidence and forward to every recorded recipient?
Try the retrieval before you need it
Choose a real pack from an ordinary shipment, not a specially prepared sample. Ask the responsible teams to retrieve its production grouping, specification revision, release status, shipment quantity and destination record. Record how long retrieval takes, which fields are missing and where someone has to guess.
Then reconcile quantities. The starting quantity should be explainable through dispatched stock, remaining stock and documented exceptions such as samples, rejects or returns. The exercise is not improved by forcing the numbers to match; an unexplained difference is precisely what the drill should reveal.
- Photograph the readable code and preserve the pack reference.
- Retrieve the connected records without rewriting them.
- Reconcile quantities and mark gaps explicitly.
- Assign corrective work and repeat the failed part of the drill.
Agree a retrieval objective that fits the business. There is no universal number of minutes that makes every system adequate. The useful outcome is evidence that information remains available across departments, working hours and personnel changes.
Questions about lot identification
Is a product barcode the same as a lot number?
No. A product identifier describes the trade item, while a lot number identifies a production grouping. A suitable barcode can carry additional lot information, but the data still needs linked records.
Does each retail pack need an individual serial number?
Not necessarily. Choose the identification level around product risk, customer requirements and operational needs. Batch-level records can be useful without serializing every piece.
Keep the request small enough to be usable
A practical customer query starts with the SKU, size, lot code, purchase or shipment reference, quantity affected and a clear description. Photographs of the pack and the observed issue help the supplier locate the right records. Avoid collecting personal details that do not help identify the product.
Separate the investigation from its conclusion. Several reports sharing a lot number are a reason to investigate; they do not automatically establish the cause. Likewise, finding an inspection record is not sufficient to dismiss a documented field issue. Retain evidence and record what remains uncertain.
Quanzhou ERA supplies private-label hygiene products and operates brands including My A+. For either an OEM program or a branded order, agree the identification and record handoff before dispatch. Product scope can be discussed through the ERA contact page; the factory news section provides further sourcing context.
For your next order: bring one example retail pack, your warehouse receiving fields and a sample delivery record. Ask Quanzhou ERA to review how the lot reference should move between them.