To compare baby toy catalog cards side by side, strip every card down to four normalized fields — dimensions, contents, materials, care — and label each value as a confirmed fact, an assumption, or an unresolved check before you put two SKUs on the same grid. A catalog card is a marketing document until a sample, an approved record, or a process document backs the number printed on it, and the side-by-side view only becomes useful once those labels are attached.

This is a risk and compliance exercise as much as a merchandising one. Age grading drives whether third-party testing and a Children's Product Certificate are required in the US, dimensional thresholds decide small-parts outcomes, and material names without documentation tell you nothing about substrate or surface coating. Use this as a baby toy wholesale SKU comparison checklist: build the grid, mark the gaps, and ask the supplier the questions below before you commit a purchase order.

Key Takeaways

  • Compare only four fields across cards — dimensions, contents, materials, care — and mark every value as confirmed, assumed, or unresolved. A card that omits the unit basis or measurement point cannot be compared at all.
  • Age grading is a safety field, not a merchandising label. In the US, testing and certification requirements under 16 C.F.R. part 1250 apply to products primarily intended for children 12 or younger; toys for a 13+ audience may still fall under ASTM F963 but do not need third-party testing or a CPC.
  • Material names are not material documentation. ABS, PP, and mixed sensory-toy materials behave differently in molding, and moisture-sensitive resins can shift dimensions if drying and conditioning are not controlled — so record material against a document, not against a card headline.
  • Where two cards disagree, resolve it against the sealed golden sample on the QC shelf — colour, fit, flash, function — never against a photo, an email, or a trade-show booth unit.
  • Do not put an AQL number or defect rate on a catalog card comparison. The inspection plan lives on the PO; a failed lot is isolated, defect class recorded, and released only after rework.

What four fields should every baby toy catalog card be normalized to?

Normalize to dimensions, contents, materials, and care. Those four are the only columns you reconcile across SKUs; everything else on a card — price, marketing copy, hero imagery — is context. The reason is that these four are the fields where an unverified value turns into a compliance problem or a landed-cost surprise, not just a color disagreement.

Dimensions cover product size, packaging size, and any dimensional threshold that matters for safety, such as small parts, spherical ends, hemispheric openings, cords, and tether lengths. Contents covers what is actually in the pack: unit count, accessories, batteries, display or pack components. Materials covers substrate, surface coating, and finish. Care covers cleaning, inspection, and replacement instructions.

A card that fills three of four fields is not a slightly worse card. It is an incomplete record, and it should be flagged as such rather than filled in by inference from the category or the product photo.

How do you separate confirmed facts from assumptions on a catalog card?

Attach a status to every value: confirmed, assumed, or unresolved. Confirmed means an approved current-site product record, a physical sample, or a process document supports the printed value. Assumed means the value only appears in catalog wording or marketing language. Unresolved means the card is silent, or two sources conflict and nobody has resolved it yet.

This labeling is what makes a side-by-side comparison defensible. Two cards can show the same care instruction and one can still be an assumption, because the wording was copied from a category template rather than taken from the SKU's own documentation. When a buyer signs off on the grid without the labels, the assumption travels into the PO and surfaces on the second lot.

For any numerical example in your comparison, use an actual sourced value or an explicitly labeled hypothetical input. Never carry a price, MOQ, lead time, or test outcome into the grid because it looked plausible on another card.

How do you normalize dimensions across cards that use different units and measurement points?

Convert every card to one unit and one measurement convention before you compare anything. A card that lists a length without saying whether it is the assembled product, the retail pack, or the master carton is not comparable to a card that does — and mixing inches and millimetres across a grid is how a small-parts question gets missed.

Record the measurement point next to the number: assembled product, retail pack, or master carton. Then note the dimensional thresholds that actually matter for the category, because ASTM F963 contains specific dimensional requirements for small parts, spherical ends, hemispheric openings, cords, and tether lengths. A dimension field that ignores those thresholds is decorative.

Flag any card that omits unit basis or measurement point as unresolved rather than estimating. Nylon is moisture-sensitive compared with many non-hygroscopic resins, so conditioning and moisture control can affect dimensions and molding stability — which is exactly why the number on the card needs a documented basis, not a rounded one.

What belongs in the contents field — and what is just marketing language?

The contents field is a bill of materials for the pack: unit count, accessories, batteries and their type, and any display or pack components. If a card says a set is "complete" or "everything included" without a countable list, that is marketing language. Rewrite it as a list or mark it unresolved.

Battery-operated items deserve their own line. Note battery type, whether the compartment is accessible, and how it closes, because battery compartment security is a recurring theme in toy safety standards. For button-cell items specifically, check the closure type, whether a tool is required to open it, and what warning is applied — before you compare the toy's function at all. A compartment that opens with fingernails is a stop, not a note.

Display and pack components belong here too, not in a separate merchandising document. If a chain wants the SKU in a display box with localized stickers, that is a contents value, and it belongs on the same grid as the unit count.

How should materials be recorded — by name or by documentation?

By documentation, every time. "ABS", "PP", and "mixed sensory-toy materials" are names, not evidence. Record the substrate, the surface coating, and the finish separately, because ASTM F963 applies different requirements to paint and surface coatings, toy substrate materials, plastics, textiles, and expanding materials.

CPSC business guidance is explicit that firms must identify which sections of ASTM F963 apply to a given toy rather than assuming the whole standard covers everything. That logic maps directly onto a catalog card: a material field that says "non-toxic plastic" is not a controlled value and cannot be compared against a card that names a resin grade.

Processing matters here too. Processing melt temperature is resin-grade-specific, so a generic temperature applied across ABS, PP, PC, or nylon can degrade material or cause incomplete filling. Recycled resin is not automatic proof of toy suitability either — it can change contamination, color, odor, mechanical performance, and chemical compliance. Material documentation per SKU is the only thing that lets you compare two cards honestly.

What should the care field contain for a baby toy SKU?

Care covers cleaning instructions, inspection frequency, and replacement or disposal guidance. CPSC guidance has long recommended that caregivers inspect toys periodically, discard broken or unrepairable toys, and dispose of plastic wrappings immediately. Those are care-field values, not afterthoughts, and a card with no care field at all is unresolved.

Watch for care text that conflicts across the same SKU — a product record that says wipe-clean while the retail card says machine-washable is a documentation failure, not a formatting issue. Resolve it against the SKU record before the card enters the comparison grid.

Care also interacts with materials. A wooden item with a water-based finish and a soft item with a textile surface do not share cleaning instructions, so normalizing care without normalizing materials produces a grid that looks tidy and is wrong.

Catalog card normalization checklist: what to check and what stops a lot

Dimensions — unit basis stated?Check that the card states one unit and one measurement convention. Red flag: length given without saying whether it is assembled product, retail pack, or master carton.
Dimensions — measurement point stated?Check the point of measure and whether small-parts, spherical-end, hemispheric-opening, cord, or tether thresholds apply. Red flag: a bare number with no basis.
Contents — countable list?Check unit count, accessories, battery type, and display or pack components. Red flag: "everything included" with no itemized list.
Contents — button-cell compartmentCheck closure type, tool access, and the warning before comparing toy function. Red flag: a compartment that opens without a tool.
Materials — documentation per SKU?Check substrate, surface coating, and finish against material documentation. Red flag: "non-toxic plastic" as the only material value.
Materials — processing consistencyCheck that melt temperature and drying are resin-grade-specific and that conditioning is controlled. Red flag: one generic temperature applied across ABS, PP, PC, and nylon.
Care — instructions documented?Check cleaning, inspection, and disposal guidance against the SKU record. Red flag: no care field, or care text that conflicts across the same SKU.
Age grading — SKU-specific evidence?Check age and intended-use evidence for the specific SKU. Red flag: infant suitability inferred from catalog category, material name, or imagery.
Disputed value — physical standard?Compare bulk to the sealed golden sample on the QC shelf — colour, fit, flash, function. Red flag: a photo or email used as the production standard.
Tool and revision — labeled?Label tool number and revision where the card cites them. Red flag: a trade-show booth sample treated as the production standard.
Tracking label and certificate — matched to SKU?Check manufacturer, date, and lot on product or pack as required, and that the certificate is matched to the SKU. Red flag: a certificate matched to the factory door.
Defect handling — plan on the PO?Isolate a failed lot, record defect class, release only after rework. Red flag: an AQL number quoted from a catalog card instead of the agreed inspection plan on the PO.

Worked example (illustrative, not a real shipment)

This scenario is constructed to show where a comparison grid breaks. It is not a real order, and none of the figures below are sourced values.

Say a buyer is reviewing two baby-toy SKUs from the same supplier for a US destination and an EU destination, with a total lot of roughly 6,000 units split across the two. The cards look comparable at a glance: both list a length in inches, both say "batteries included", both say "wipe clean", both say "ABS".

Normalizing kills the match. The first card's length is the assembled product; the second card's length is the retail pack, so the units are the same but the measurement point is not. The first card lists the battery type and closure; the second lists "batteries included" with no type and no compartment description. The care text is identical on both cards but only one SKU record contains a care instruction, which makes the other an assumption. The material field says ABS on both, but only one card is backed by material documentation per SKU.

Where the lot gets held: the second SKU's battery compartment cannot be assessed from the card, and for a button-cell item that check has to happen before toy function is discussed. The destination split makes it worse — the US leg needs the age-grading and certification question answered, and the EU leg needs its own standard reference, and neither card carries the age and intended-use evidence for the specific SKU. The comparison does not fail on price. It fails on two unresolved fields and one missing document.

The fix is procedural, not commercial. Mark the second SKU's contents and care fields unresolved, request the material documentation per SKU, resolve the measurement point on both cards, confirm the compartment closure and warning, and only then re-run the grid. A card that cannot survive normalization should not survive to the PO.

What to ask suppliers before you finalize the comparison

Send these as written questions and require written answers. Verbal answers at a trade fair do not update a catalog card.

For dimensions: what is the unit basis and measurement point for the dimensions on this card, and does the number refer to the assembled product, the retail pack, or the master carton?

For contents: what exactly is in the pack for this SKU, including accessories, battery type, and display or pack components?

For materials: which material documentation covers this SKU, and does it match the card? Ask separately about substrate, surface coating, and finish.

For care: what are the care instructions for this SKU, and where are they documented?

For revision control: which tool number and revision does this card correspond to?

For button-cell items: what is the closure type, is a tool required to open it, and what warning is applied?

For traceability: where do manufacturer, date, and lot appear on the product or pack, and which SKU does the certificate cover?

For inspection: what is the agreed inspection plan on the PO for this lot?

For age grading: what SKU-specific age and intended-use evidence supports the rating on this card?

What changed in the US toy compliance picture, and what should buyers watch this year?

The structural requirement has not moved: Section 106 of the CPSIA made ASTM F963 a mandatory consumer product safety standard for children's toys, codified at 16 C.F.R. part 1250, and 16 C.F.R. § 1250.2 identifies the latest Commission-accepted version that is mandatory. What buyers should keep watching is which version is currently accepted, because the card has to reference the version that applies, not the version that was current when the tool was cut.

The second thing to watch is scope, not dates. Testing and certification requirements apply to products designed or intended primarily for children 12 years of age or younger. Toys aimed at a 13+ audience may still be subject to ASTM F963 requirements but do not need third-party testing at a CPSC-accepted laboratory or certification in a Children's Product Certificate. Cards that blur that line create a certification question that nobody can answer from the catalog.

One clarification worth repeating: CPSC does not approve, endorse, or certify toys, and a manufacturer's self-declaration is not a third-party test report. Treat any card that implies otherwise as an unresolved field.

If you sell into the EU as well, the applicable standard is a separate regime from the US one, and the two cannot be swapped on a single card. Confirm which framework applies to the specific SKU and destination, and record that as a field rather than a footnote.

FAQ

Can I compare two baby toy catalog cards if one omits the measurement point?

No — mark it unresolved and request the basis before comparing. A length without a stated measurement point (assembled product, retail pack, or master carton) cannot be reconciled against another card, and estimating it defeats the purpose of the grid.

Does a toy for children 13+ need third-party testing and a Children's Product Certificate?

No. Under the CPSC framework, testing and certification requirements apply to products designed or intended primarily for children 12 years of age or younger; toys aimed at a 13+ audience may still be subject to ASTM F963 requirements but do not need third-party testing at a CPSC-accepted laboratory or certification in a CPC.

How do I handle a button-cell toy in a catalog comparison?

Check the compartment before you compare the toy's function. Confirm the closure type, whether a tool is required to open it, and what warning is applied. If the compartment can be opened without a tool, that is a stop condition, not a note in the margin.

What should I do when two cards for the same product show different care instructions?

Treat it as a documentation failure and resolve it against the SKU record before the card enters the grid. Cleaning, inspection, and disposal guidance should be traceable to the SKU's own documentation rather than copied from a category template.

Should I put an AQL number on my catalog card comparison?

No. The inspection plan is agreed on the PO, not quoted from a catalog card. On the floor, a failed lot is isolated, the defect class is recorded, and the lot is released only after rework — sorting alone is containment, not root-cause correction.

Is a trade-show booth sample good enough as the production standard for a card comparison?

No. Booth samples are frequently hero units, so label the tool number and revision on the table and refuse to treat a fair photo as the production standard. Where a card value is disputed, compare bulk to the sealed golden sample — colour, fit, flash, function — not to a photo or an email.

Can I infer that a SKU is suitable for infants from its catalog category or material?

No. Infant suitability requires SKU-specific age and intended-use evidence. Do not infer it from the catalog category, material names, or product imagery, and do not carry an age rating across from a sibling SKU.

Sources

Build the grid before the PO

If you are normalizing a baby-toy range for a US or EU destination and want the four fields checked against product records before you commit, send over the SKUs you are comparing and we will work through the dimensions, contents, materials, and care fields with you.