Reconcile four things before a single carton leaves the warehouse: the SKU printed on the retail pack, the lot or batch code, the encoded barcode data, and the destination label. If any one of them disagrees with the approved product record for that exact SKU, stop the allocation — do not split the lot across stores and hope receiving sorts it out.
This is the working version of a baby toy wholesale SKU comparison checklist: what to verify pack by pack, which papers a port or customs examiner will actually ask for, where each document should physically sit, and what happens when it is missing. It covers retail-pack identity, lot traceability, barcode content versus barcode artwork, destination and carton marks, and the recall screen you run before committing shelf space.
Papers at the exam: what an officer asks for and where it should live
| Paper | Why the officer asks | Where it should be | If you do not have it | Commercial invoice and packing list | Ties the shipment to a buyer, a value and a carton count | In the document set you hand over, and a copy with the forwarder | Carton count and SKU list get reconciled by hand, which slows the exam and invites a deeper look |
|---|---|
| SKU-level product record | Confirms this pack is the product the invoice says it is | With your category buyer file, not only in the factory's system | SKU identity cannot be confirmed against the pack; the pack is treated as unidentified | |
| Lot or batch code plus manufacturer and date | Allows a trace from the pack back to a production run | Printed on the product or the pack, and recorded in your lot log | If a defect or recall question arises later, the whole shipment is in scope instead of one lot | |
| Barcode content sample (encoded data, not artwork) | Shows the pack can be scanned and resolved to a record | On the retail pack; the data assignment must match the retailer or GS1 owner record | Scanning fails or resolves to the wrong item at receiving, and store allocation cannot be automated | |
| Destination label and carton marks | Confirms the carton is routed to the right store or DC | On the master carton, agreeing with the SKU, lot and units-per-carton for that shipment | The carton can be misrouted or received against the wrong purchase order | |
| SKU-specific age and intended-use evidence | Establishes which age band this SKU is cleared for | In your product file, per SKU | Category, material name or product imagery is not a substitute; do not infer infant suitability from the catalog | |
| Recall screen record for the SKU | Shows the SKU was checked against current listings | In your pre-allocation checklist, dated | An unrecorded screen cannot be shown to a retail partner or an examiner after the fact |
Worked example (illustrative, not a real shipment)
A distributor allocates one container of baby toys — roughly 4,000 retail units across four ABS SKUs, with a reference MOQ band between 80 and 144 units per SKU in the catalog record — split between two destinations: one national DC and one regional retail group with its own label format.
At the pack check, three SKUs pass. The fourth — the Montessori Lock Activity Learning Table, recorded in the catalog snapshot at 16 units per carton in a color box — has a clean, well-printed barcode with no tracking label content behind it: no manufacturer, no date, no lot code on the product or pack. The destination labels for that SKU were generated from the purchase order rather than reconciled against the lot and units-per-carton actually produced.
That is the step where the shipment gets held. The other three SKUs can be allocated; the fourth cannot be split across the two destinations until the lot content is added and the destination label is regenerated against the produced lot. Everything else in the container was fine — which is the point. One SKU fails reconciliation and the whole allocation plan for that SKU stalls, not the whole container.
Note what this example does not claim: no AQL, no defect rate, no sampling plan, no lab result, and no certification status. The catalog snapshot establishes a catalog record only — not certification, infant suitability, licensing, stock or factory capacity. Sample, current quote, age evidence and destination documents all need reconfirming per order.
What to ask suppliers before you allocate
Send these as written questions with a required answer format, not as a conversation. A supplier who answers in prose rather than by SKU is telling you something about their records.
Identity and lot. What is the exact lot or batch code for this order, and where exactly does it appear on the product or the pack? Who is the named manufacturer, and what production date runs alongside the lot code? Can you send a barcode content sample — the encoded data, not a picture of the artwork?
Destination and carton. How is the destination label generated, and how is it reconciled against the SKU, the lot and the units-per-carton before shipment? What appears in the carton marks: SKU, quantity, destination, handling information, and the lot or shipment reference the warehouse needs?
Documents and age band. Which compliance document applies to which SKU, and is it matched to the SKU rather than to the factory? What SKU-specific age and intended-use evidence can you send for this exact item — not the category, not the material name, not the photo?
Nonconformance. If a pack fails the check, what does your nonconformance report contain? It should state the defect, the lot, the quantity, containment, disposition and the responsible decision — not only a pass/fail note. And if the fix is sorting, ask what the corrective action is: sorting is containment, not root-cause correction.
FAQ
What do I actually check on a baby toy retail pack before allocating it to stores?
Four reconciliations: the SKU on the pack against the approved product record for that exact SKU; the lot or batch code, manufacturer and date against your lot log; the encoded barcode data against the retailer or GS1 owner record; and the destination label against the SKU, lot and units-per-carton for that shipment. If any one disagrees, hold that SKU.
The barcode looks fine — isn't that enough?
No. A barcode can be cleanly printed and still carry no useful tracking content; a lot has shipped with a pretty barcode and no tracking label content behind it. You need the encoded data, not the artwork, and it must resolve to the right record at receiving.
Does the compliance document attach to the SKU or to the factory?
It must be matched to the SKU, not to the factory door. One document covering a factory's whole output cannot be shown to tie a specific retail pack to a specific product record, which is exactly what an examiner is testing for.
Can I infer the age band from the category or the material?
No. Infant suitability cannot be inferred from catalog category, material names or imagery — you need SKU-specific age and intended-use evidence on file. A catalog snapshot establishes a catalog record only, not certification or infant suitability.
Why run a recall screen before allocation rather than after?
Because allocation is the point of no return for shelf space. As historical external examples, two 2026 US recalls show the transferable lesson: a detachable small mirror on a busy board created a choking and laceration hazard, and a pool compression strap created a foothold with a drowning risk. Named recalled products only — no connection to any particular supplier, customer or SKU is established. The procurement question is still worth asking: if this SKU were listed, could I trace the affected lot from the pack?
What should a nonconformance report contain if a pack fails?
The defect, the lot, the quantity, containment, disposition and the responsible decision — not only a pass/fail note. And if the immediate fix is sorting, treat that as containment and ask separately for the corrective and preventive action that addresses the cause and verifies effectiveness.
Is there a 2026 regulatory change that affects this check?
Nothing in the supplied material confirms a new applicable date for this product category, so treat the workflow above as the classic sequence rather than a date-driven one. Where a regulation is relevant, keep the three states separate: entered into force, actually applies to this product category, and not confirmed from official text. Digital Product Passport, GPSR and toy safety rules are different regimes — do not merge them into one deadline.
Sources
- Baby Toy Product Assortment Strategy for Retailers
- Collectible Toy Release Calendar: What Lines Typically Launch Each Year
- How Many Baby Toy SKUs Should a New Brand Launch? A 5-10-20 Guide
- How to Manage Inventory for Plush Toys
Run the reconciliation before you commit the shelf
Reconciliation is cheap; a held SKU during allocation week is not. Build the four checks into your purchase order terms, require lot and manufacturer content on the product or pack as standard, and keep the compliance document matched to the SKU. If you want the pack, lot and label fields confirmed against a specific item before you place the order, ask for the current sample and the destination document set in the same request.