A Baby Toy Warehouse Receiving Checklist by SKU: What to Count, Check, and Record Before You Post the Receipt

Key takeaways for baby toy receiving by SKU

• No PO number on screen or paper means no unload. A shipment you cannot match line by line is a shipment you cannot post, and posting it anyway creates phantom stock that only surfaces at the next cycle count.
• Count, condition, identity, and information completeness are four separate records. A short line and a damaged line can both be true on the same SKU, and merging them into one note makes the supplier dispute unwinnable.
• Damaged or wrong-item units go to a hold area, never into sellable stock. Post only counted good units, so on-hand inventory reflects what can actually be picked.
• Carton marks must carry SKU, quantity, destination, handling information, and a lot or shipment reference. If the marks are missing or wrong, the receiving team is guessing, and guessing at the dock is where wrong-item errors enter the building.
• Age grade and intended use come from SKU-level documents, not from the catalog category, the material name, or the product photo. If the record does not state it, the receiving line carries an open question, not an assumption.
• Every number in your receiving log is either a counted value or a target you set internally. Do not treat a tolerance, an accuracy percentage, or an inspection plan pulled from a blog as a contractual specification.

What should the count record contain for a baby toy SKU?

The count record reconciles expected units against received units per PO line, and it closes only when every line is marked matched, over, short, or wrong-item. Nothing is left blank and nothing is left as 'approximately correct.'

Count against the packing list first and the PO second. Carton counts and pallet counts are useful for a fast sanity check, but they are not the receiving count — a carton marked as one quantity that holds another is exactly the failure a line-by-line count catches. If unit-of-measure differs between the PO and the packing list, stop and resolve it before counting, because a case-versus-piece mismatch will show up as a large overage or shortage that is purely a paperwork error.

When a line is short, note it on the delivery document while the carrier is still on site and log it as a partial receipt. When a line is over, tag the extra units and hold them as an unplanned receipt rather than quietly absorbing them into stock. Both cases need photo evidence and a timestamp, because the supplier conversation happens days later and memory does not survive that long.

Lot isolation is the containment step, not the fix. A failed lot gets separated, the defect class is recorded, and release happens only after rework. Sorting alone does not correct a cause, and a receiving checklist is not the place to settle root cause — it is the place to make sure the bad units never get posted as good ones.

What condition checks apply at the dock for baby toys?

Inspect the trailer, the seal, and the cartons before you open anything: moisture, odors, shifted loads, and crushed cartons are all reasons to photograph and escalate before the shipment is accepted. Then inspect packaging integrity and closure condition at unit level, because a compressed carton can hide a damaged unit that passes a visual count.

For any SKU that uses a button-cell battery, the compartment is the condition check, not the toy function. Confirm the closure type, confirm what tool is required to open it, and confirm the warning is present and legible. A compartment that opens with fingernails is a receiving reject regardless of how well the toy works — the door design and the warning are the same conversation, and both belong on the dock checklist.

Drop testing is a design check for whether a packaged or unpackaged toy withstands a defined impact without creating unsafe broken parts or losing function. A receiving team does not improvise it at the dock. Use it as a document question: has this SKU been subjected to the defined impact test, and where is the record? If the answer is not documented, the line stays open.

Damage handling is mechanical: photograph the units, place them in a hold area, log them as damaged, and keep them out of available inventory. Do not mix them into good stock to hit a put-away target, and do not dispose of them before the supplier or carrier claim is resolved.

How do you verify SKU identity rather than assume it?

Identity verification means the SKU on the label matches the SKU on the PO line and the contents of the carton match the label. A pallet labeled with one SKU that contains another is the classic receiving failure, and it is caught at the dock or not at all.

Barcodes and scanners are the highest-leverage accuracy control because they remove hand-keyed counts and visual recognition from the process. A scanner that rejects a mismatched label is doing more for your margin than any training memo. If you scan, scan at receiving — not after put-away, when the carton is already buried in a pick location.

Age grade and intended use are identity attributes, not marketing attributes. They must come from SKU-specific documents; the catalog category, the material name, and the product photo are not evidence of infant suitability. If a SKU is listed as a baby toy but the record does not state an age grade and intended use, the receiving log should carry an unresolved check that blocks that SKU from being released as infant-appropriate.

Where the market is the EU, identity also includes the responsible manufacturer and, where applicable, the EU importer or authorised representative information being consistent across the product, the packaging, and the compliance records. Inconsistency between those three is an identity exception, and it is easier to raise it at the dock than to correct it after the goods are distributed.

What makes an information-completeness record complete enough to post?

A useful traceability record links the SKU, mold cavity, resin lot, component lots, production date, operator or process, and the carton or pallet identifier. If your receiving log cannot connect a carton to that chain, you have a count but not a record.

At minimum, capture the SKU, the expected versus received quantity, the condition status, and the assigned storage location. Add the fields that the SKU actually requires — lot or batch references, production dates, and any handling notes — rather than forcing every SKU into a heavy template it does not need. Over-collecting data at the dock slows receiving and encourages shortcuts, which is a worse outcome than a lean record that is actually completed.

Material documentation should be per SKU, not per family. A supplier that provides one material sheet for a product family is giving you a category claim, not a SKU record. The pattern worth copying is a kit where the material documentation travels with the SKU alongside the labeling and the packaging specification. If a supplier cannot point to the document for the exact SKU, log it as missing.

Tooling adds a record most receiving checklists forget. If a fee was paid, the fee, the ownership of the tool, the storage period, and what happens if the tool sits idle should all be written in the contract rather than agreed by handshake. A SKU whose tool ownership is undefined is a SKU whose future supply you cannot plan, and the receiving log is a reasonable place to flag that the document is missing.

Worked example (illustrative, not a real shipment)

A container arrives with two baby-toy SKUs. The first is a bath toy in ABS at a 144-unit MOQ, packed in a display configuration for one destination. The second is a table-based learning SKU in ABS at a 108-unit MOQ, packed in master cartons for a different destination. Two destinations means two carton-mark sets and two packing lists, and the first realistic failure is that only one set of marks was applied.

Pre-arrival: the PO and packing list are compared. The bath toy line shows the expected unit count for destination A; the learning-table line shows the expected unit count for destination B. Exit condition: both lines have a PO reference. If the learning-table line has no PO line on file, the pallet stays on the dock.

Dock inspection: the seal matches the delivery document, cartons are dry and square, and the display units for destination A are not crushed. The learning-table cartons for destination B show corner compression on two cartons. Those two cartons are photographed and moved to the hold area — they are not opened and mixed into the count as good units.

Counting: the bath toy count matches the line. The learning-table count is short by one carton against the packing list. The shortage is written on the delivery document before the carrier leaves, photographed, and logged as a partial receipt. Exit condition: both lines are marked matched or short; nothing is left unmarked.

Identity: the bath toy carton label matches the PO line, but the learning-table pallet carries a label for a different SKU in the same family. That is a wrong-item flag. The pallet is held and reconciled before any scanning, because scanning a mismatched label would post the wrong SKU into available stock. This is the step where the shipment gets held — not the count shortage, which is recoverable, but the identity mismatch, which corrupts inventory if it is posted.

Information completeness: the bath toy SKU has its material documentation and labeling on file. The learning-table SKU has a family-level material sheet with no SKU reference. That gap is logged as missing, and the receipt is posted only for counted good units with a recorded storage location. The receiving zone is cleared, the hold area carries the damaged cartons and the mismatched pallet, and the open questions go to the supplier the same day.

Receiving step | What to check | Red flag | Exit condition

What to ask suppliers before the next baby toy shipment

Send these as a written RFQ or inbound guide, not as dock questions. The answers belong on file before the goods move, because a receiving team cannot resolve a commercial or regulatory gap while a trailer is waiting.

What is the agreed inspection plan on the PO, and which document carries the sampling specification? Buyers who want a numeric sampling plan should get it from the agreed inspection plan, not from a catalog sentence.

For each button-cell SKU: what is the closure type, what tool is required to open the compartment, and where exactly is the warning placed on the product and the packaging?

For each SKU: what is the stated age grade and intended use, and which document records it? Confirm this per SKU, not per family.

For each SKU: what material documentation is provided, and does it reference the exact SKU? Confirm whether labeling and packaging specifications travel with the same document set.

What carton marks will be applied — SKU, quantity, destination, handling information, and lot or shipment reference — and can you provide the mark set in advance for each destination?

What barcode standard and label placement will be used, and will the ASN or packing list carry SKU, unit quantity, carton count, pallet count, and lot details before arrival?

If a tooling fee was paid: who owns the tool, how long is it stored, and what happens if the tool sits idle? Get this in the contract, not in a message thread.

When a lot fails: how is the defect class recorded, and what evidence is required before release after rework? Ask for the containment and release record format in advance.

Where the destination is the EU: how is the responsible manufacturer and, where applicable, the importer or authorised representative information kept consistent across the product, the packaging, and the compliance records?

What is your stated factory capacity for this SKU, and can it be supported by recent records covering the product type, machinery, shifts, and tooling? Treat a stated capacity as a planning input until those records are checked.

FAQ

Can I post a receipt before every PO line is resolved?

No. Post only when the physical count, the receiving documents, and the system record all match for that line. Lines marked short, over, or wrong-item should be logged and held rather than absorbed into available inventory, because posting them creates phantom stock that surfaces at the next cycle count.

What is a realistic receiving accuracy target for baby toy SKUs?

Set the target yourself and write it into your inbound guide; it is an internal service level, not a supplier specification. Accuracy percentages published in general warehouse guides are their authors' targets, and they should not be presented to a supplier as a contractual requirement or a regulatory threshold.

Do I need to inspect every unit of a baby toy shipment?

It depends on the agreed inspection plan on the PO and the risk of the SKU, so confirm that plan in writing before the shipment. At minimum, inspect trailer and seal condition, carton integrity, and the closure and warning on any button-cell SKU, and hold damaged units out of sellable stock.

How do I handle a carton that is labeled with the wrong SKU?

Flag it as a wrong-item exception, hold the pallet, and reconcile before scanning or posting. Scanning a mismatched label is what turns a dock problem into an inventory problem, because the wrong SKU enters available stock and the correct SKU shows as short.

What traceability fields should a baby toy receiving log capture?

At minimum the SKU, expected versus received quantity, condition status, and assigned storage location. Where the SKU requires it, add mold cavity, resin lot, component lots, production date, operator or process, and the carton or pallet identifier so a received carton can be linked back to its production chain.

Should the receiving log record age grade separately from the product description?

Yes. Age grade and intended use must be recorded from SKU-specific documents, and they cannot be inferred from the catalog category, the material name, or the product photo. If the document does not state it, log the item as an open check rather than releasing the SKU as infant-appropriate.

Does a button-cell warning check belong to receiving or to product design?

Both, but the dock check is the last line of defense. Confirm the compartment closure type, what tool is required to open it, and the presence and legibility of the warning before the toy function is even discussed, because a compartment that opens by fingernail is a reject.

Sources

• best practices for warehouse receiving processes
• fulfillment center receiving best practices
• receiving inventory process guide
• warehouse receiving

Turn this checklist into a supplier inbound guide

Copy the four records — count, condition, identity, information completeness — into a one-page inbound guide and send it with the PO. Add the carton-mark requirements, the barcode standard, and the ASN fields, and require the document set per SKU before the shipment leaves origin.

To compare how a baby toy program is quoted and documented against this checklist — MOQ bands, packaging configuration, labeling, and the records that travel with each SKU — send your SKU list and destination markets and a specification sheet can be returned rather than a catalog page.