A China supplier may provide a crib product sheet, model reference, factory source, sample source, test report, Children’s Product Certificate (CPC) source, label artwork, registration-card source, date code, invoice, or shipment record. These files can identify what the supplier says about a product, model, factory, sample, report, label, or transaction. They do not establish that an item is a full-size crib, that a standard applies, that testing is sufficient, that a CPC may be issued, that a label is adequate, that a product is safe, or that it may be imported, sold, or released.
China supplier full-size crib evidence is buyer-side evidence that connects buyer product/SKU/version with supplier legal entity/site, supplier-stated model, factory, sample, report, CPC source, label/artwork, registration-card source, manufacture/import date source, shipment source, file/date, gap, and buyer owner. It does not establish product classification, standard applicability, testing, certification, CPC issuance, label outcome, product safety, importer status, sale permission, or release.
Keep supplier crib sources separate from product decisions
CPSC provides business guidance on full-size baby cribs that discusses product requirements, labeling, registration forms, and certification in the guidance’s stated scope.1 The current rule establishes a safety standard for full-size baby cribs and states its own scope and definitions.2 Supplier evidence can identify the product/model, report, CPC source, label, or date stated by the supplier. It does not decide that a buyer item is within scope or meets a particular rule or standard.
CPSC also explains that, in general, manufacturers and importers of children’s products must have products third-party tested and certified in a CPC to applicable rules and requirements.3 A China factory report or CPC source is not automatically the buyer’s CPC, an importer certification decision, evidence of testing sufficiency, or a product-safety result. Keep factual supplier collection distinct from responsible technical, certification, importer, legal, and release records.
Set the evidence boundary before collecting files
A buyer record should preserve original sources, dates, and stated relationships. It should not become a crib classification, standard-applicability, testing, certification, CPC, label, safety, importer, disposition, or release form.
| Review subject | A supplier record can identify | A supplier record cannot establish |
|---|---|---|
| Buyer product/version | Buyer-stated commercial product scope | Full-size crib classification |
| Supplier model source | Supplier-stated product/model | Match to buyer product or rule scope |
| Factory source | Supplier-stated entity and site | Manufacturer or importer conclusion |
| Sample/report source | Supplier-provided document | Test sufficiency, result, or compliance |
| CPC source | Supplier-provided file/reference | Buyer CPC issuance or certification outcome |
| Label/artwork source | Supplier-provided visual source | Label adequacy or product approval |
| Registration-card source | Supplier-provided form/source | Card requirement or outcome |
| Date/shipment source | Supplier-stated transaction link | Import, sale, disposition, or release |
Define product, model, factory, sample, report, certificate, label, and shipment scope
Begin with buyer SKU/version, buyer product description, buyer label/artwork source, supplier, and buyer transaction reference. A product family can have different dimensions, components, factories, samples, testing sources, label versions, manufacture dates, packaging, and shipments. Keep each version visible rather than relying on a product-family name.
Record supplier legal entity/site, product/model source, factory source, sample source, report source, CPC source, label/artwork source, registration-card source, manufacture/import date source, invoice/shipment source, file/date, and factual clarification contact. Preserve originals and file dates. A summary should not widen a document beyond the product, model, factory, sample, date, or shipment relation it states.
| Scope field | Buyer record purpose |
|---|---|
| Buyer product/SKU and version | Identifies buyer-stated product scope |
| Supplier entity/site | Identifies supplier-stated source entity/location |
| Product/model source | Identifies supplier-stated product wording |
| Factory/sample source | Identifies stated manufacturing/sample relation |
| Report source | Identifies a supplier-provided report file |
| CPC source | Identifies a supplier-provided CPC file/reference |
| Label/card source | Identifies supplied visual/form source |
| Date/shipment source | Identifies supplier-stated timing/transaction source |
| Open condition | Identifies a missing or conflicting relation |
Request factual sources, not safety or certification conclusions
A buyer can request product/model/version; supplier legal entity/site; factory and sample source; report source; CPC source; label/artwork source; registration-card source; manufacture/import date source; invoice/shipment source; file/date; stated relation to the buyer product; and a factual clarification contact.
Do not ask the supplier to classify the item, decide standard applicability, evaluate test sufficiency, issue a CPC, certify compliance, approve label content, determine safety, assign importer responsibility, approve sale, or authorize release. Those decisions should remain in controlled records owned by qualified functions.
| Supplier source | Buyer question | Review limit |
|---|---|---|
| Product/model source | What product/version does the supplier identify? | Does not classify the item |
| Factory/sample source | What site/sample relation is stated? | Does not establish responsible party status |
| Report source | What file/date/product scope is supplied? | Does not determine test result or sufficiency |
| CPC source | What document/source is supplied? | Does not issue a buyer CPC |
| Label/card source | What artwork/form version is supplied? | Does not determine label/card result |
| Date/shipment source | What item/transaction relation is stated? | Does not authorize import, sale, or release |
Keep related records separate
Supplier evidence can help product, technical, certification, label, importer, and shipment work. It cannot replace the controlled record for any decision.
| Record set | Question it may answer | What it must not replace |
|---|---|---|
| Supplier evidence map | What did the supplier provide? | Classification or standard decision |
| Product configuration record | What buyer product/version is under review? | Supplier model source |
| Technical/test record | What source needs controlled review? | Test sufficiency or compliance conclusion |
| CPC/certification record | What controlled certification work is recorded? | Supplier CPC source |
| Label/card record | What visual/form source needs review? | Label or registration-card outcome |
| Import/release record | What commercial decision is recorded? | Factory, report, CPC, or shipment source |
Map the stated relationships without inference
China supplier full-size crib evidence is most useful when every record is tied only to the product, model, factory, sample, report, certificate, label, date, or shipment it actually names. Link buyer SKU to supplier model. Link sample and report sources to the stated model or factory. Keep CPC, label, registration-card, date, and shipment sources separate.
CPSC’s guidance distinguishes its cited requirements and certification information within a stated full-size crib context.1 A buyer evidence map can preserve source scope for a qualified reviewer. It cannot decide that the buyer product belongs in that context or that a source satisfies a requirement.
| Association | Fact to preserve | Gap to surface |
|---|---|---|
| Buyer SKU to supplier model | Supplier-stated product/version relation | Buyer and supplier versions differ |
| Model to factory/sample | Supplier-stated relation | Factory or sample relation is unclear |
| Sample to report | Source-stated sample/report relation | Report does not identify sample/model |
| Model to CPC source | Supplier-stated document relation | Scope or date is unclear |
| Model to label/card | Source-stated version relation | Visual/form does not identify the model |
| Model to date/shipment | Supplier-stated transaction relation | Buyer and supplier references do not reconcile |
Use a restrained review sequence
Start with buyer SKU/version, product description, artwork, and shipment reference. Capture product/model, factory, sample, report, CPC, label, registration-card, date, and shipment sources separately. Map each source only to the relationship that it states. If a report names a factory but not a buyer model, or a CPC source names a different product version, record the gap without deciding what source should control.
| Review step | Buyer action | Boundary kept intact |
|---|---|---|
| Establish baseline | Identify buyer product/version and shipment | Does not classify the item |
| Capture sources | Preserve original files and dates | Does not establish testing or safety |
| Map association | Record stated model/factory/sample/report links | Does not decide standard applicability |
| Surface gap | Identify missing or conflicting relations | Does not cure a gap by assumption |
| Route work | Name responsible buyer function | Does not issue CPC or authorize release |
Reconcile sources before escalation
A supplier product sheet may use a family name, while a report names a model and the label artwork uses a third name. A factory may change between sample work and shipment production. A CPC source may identify a document date without naming the buyer SKU. These are evidence gaps. They do not prove that a product is unsafe, noncompliant, certified, approved, or releasable.
Keep each original source and write a precise gap statement. For example: “Report R-03 names supplier model M-11 and factory S-04; buyer SKU P-06 and shipment L-12 are not named.” This allows the next owner to locate the evidence without requiring a sourcing coordinator to determine product scope, testing, certification, safety, or release.
| Gap type | Factual source to retain | Follow-up question |
|---|---|---|
| Product mismatch | Buyer SKU and supplier model source | Which document states the product relationship? |
| Factory mismatch | Factory source, sample source, and report | Which site does each source name? |
| Sample mismatch | Sample reference and report scope | What sample/model does the report identify? |
| CPC mismatch | Document source, date, and product wording | What product/version does the source name? |
| Label mismatch | Artwork version and supplier product source | Does the visual source identify the buyer product? |
| Shipment mismatch | Invoice/shipment source and product source | What buyer product relation is stated? |
Keep supplier sources distinct from testing, certification, safety, and release conclusions
CPSC states that manufacturers and importers of children’s products generally must have products third-party tested and certified in a CPC to applicable rules and requirements.3 A buyer should not convert a China supplier report or certificate source into a statement that the buyer has met a testing or certification duty. Preserve source scope, then route it to the responsible technical and certification owners.
The same distinction applies to CPSC’s crib guidance and the current rule. The buyer evidence map documents files and their stated associations. It does not determine whether the item is a full-size crib, which version of a standard applies, whether a sample matches shipped product, whether testing is sufficient, whether a CPC is appropriate, or whether the product is safe, marketable, or ready for release.1
Build a compact crib evidence record sheet
| Field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU and controlled version reference |
| Supplier product/model | Supplier-provided product/model source |
| Supplier entity/site | Supplier-stated legal entity and factory site |
| Sample/report source | Supplier-provided sample and report references |
| CPC source | Supplier-provided document/reference and date |
| Label/card source | Supplier-provided artwork/form source |
| Manufacture/import date source | Source wording and document date |
| Shipment source | Supplier-provided transaction source |
| Open condition | Missing scope, mismatch, or unclear link |
| Buyer owner | Responsible review function |
Make owner handoffs readable
A useful handoff identifies the buyer product/version, supplier entity/site, file/date, stated relation, and exact gap. “Review crib compliance” is not a useful handoff. “Supplier report R-03 identifies model M-11 and factory S-04, but it does not identify buyer SKU P-06 or shipment L-12” gives the responsible function a factual starting point.
| Owner route | Question the buyer record can present |
|---|---|
| Product/configuration function | What buyer and supplier product/model sources are documented? |
| Technical/test function | What sample and report sources need controlled review? |
| Certification/CPC function | What source documents and product relations are available? |
| Label/card function | What artwork or registration-card source needs review? |
| Supplier-quality function | What entity/site and factory source apply? |
| Import/disposition authority | Is a separate controlled commercial decision recorded? |
Avoid predictable evidence-control failures
Do not call a supplier report “CPSC approved” or “crib compliant.” CPSC guidance and the rule provide stated context, but the evidence map does not decide product classification, standard scope, test sufficiency, certification, safety, or release.1
Do not treat a CPC source as the buyer’s CPC. Keep supplier document, product, factory, date, and stated relation distinct from the controlled certification record. Do not assume that a report applies because product names look similar. Preserve the mismatch instead.
Do not combine supplier, technical, CPC, label, importer, and release status in one field. A buyer may have received a complete-looking supplier packet while technical or commercial work remains open. Separate source records make that limit visible.
Frequently asked questions
Does a China supplier test report prove that a crib is compliant or safe?
No. A supplier report identifies a source file and any product/sample/factory relation it states. It does not determine product classification, standard applicability, test sufficiency, certification, safety, import eligibility, sale, or release.
Does a supplier CPC source become the buyer’s CPC?
No. CPSC describes CPC responsibilities in a manufacturer/importer context.3 A supplier source can be retained for qualified review. It does not issue or establish the buyer’s certification.
What can a buyer request from a China crib supplier?
Request product/model/version, supplier entity/site, factory and sample source, report source, CPC source, label/artwork source, registration-card source, date source, shipment source, file/date, stated relation to buyer product, and factual clarification. Do not request classification, test, certification, safety, importer, or release conclusions.
Does this evidence map authorize import, sale, or release?
No. It organizes supplier product, model, factory, sample, report, CPC, label, card, date, and shipment sources. It does not establish standard applicability, testing, certification, safety, import permission, sale permission, disposition, or release.
Preserve crib sources without making product decisions
A usable China supplier full-size crib evidence record connects buyer product/version with supplier entity/site, product/model, factory, sample, report, CPC, label, registration-card, date, shipment, file/date, gap, and buyer-owner sources. It makes a supplier packet retrievable without declaring a product classified, tested, certified, safe, importable, or released.
Supplier Ally can help buyers organize China supplier communications, factory references, product models, sample files, reports, label artwork, and shipment records. Product classification, standard applicability, testing, certification, CPC, labeling, safety, importer, legal, disposition, and release decisions should remain with the buyer’s qualified responsible functions.
ES 
EN 