A buyer sourcing a frame child carrier from China may receive frame drawings, fabric specifications, shoulder-strap records, handle parts, retention-system sources, product photographs, test reports, labels, tracking information, registration-card files, certificates, factory documents, cartons, purchase orders, and shipment records. Similar catalog names can hide different frames, straps, or accessories. A source map keeps the original trail clear before a reviewer considers the documents.
This guide organizes China supplier frame child carrier evidence as factual buyer-side records. It explains how to preserve product, frame, fabric, strap, handle, retention, test, label, tracking, registration-card, certificate, factory, package, production, and shipment sources. It does not decide whether an item is a frame child carrier, whether a standard applies, whether components perform, whether a test passed, whether a label is sufficient, or whether goods may be certified, imported, sold, or released.
CPSC business guidance describes frame child carriers and stated topics that include frames, straps, handles, retention systems, labels, registration forms, dates, and CPC material. 1 CPSC’s FAQ identifies the cited product category and related questions. 2 Current Part 1230 establishes a stated standard for frame child carriers and incorporates ASTM F2549-22. 3 These sources assist document organization. They do not convert a supplier packet into a product-scope, test, safety, certificate, import, sale, or release decision.
Define the record boundary
The source map records what a supplier document, image, report, or message says. Keep literal product names, model codes, frame descriptions, fabric wording, strap part numbers, handle details, label text, drawing revisions, factory identity, source date, order number, and shipment reference. Retain originals behind every index row.
Do not use the map to decide product classification, child positioning, intended use, frame performance, strap retention, handle integrity, stability, testing, labeling, registration, certification, safety, legal matters, import, sale, or release. It is an evidence-control file, not a decision file.
| Evidence question | Preserve from the source | Keep separate |
|---|---|---|
| What product appears? | Literal model, description, drawing, image. | Product-scope decision. |
| What frame appears? | Frame wording, part reference, drawing. | Frame performance finding. |
| What strap appears? | Exact strap, buckle, or hardware source. | Retention conclusion. |
| What test exists? | Full source, sample wording, dates, issuer. | Test result or adequacy. |
| What certificate exists? | Original document and product text. | Certificate validity. |
Create separate records for each configuration
CPSC guidance describes a stated frame-child-carrier context and product wording. 1 Preserve supplier terms as they arrive. Separate records are appropriate whenever sources differ on model, SKU, tubular frame, fabric body, shoulder strap, waist belt, handle, buckle, restraint, accessory, drawing revision, carton, or supplier entity.
A test source may identify a version with one frame. An image can show a different buckle. A purchase order may use a shortened SKU. Store all sources and list the relationship as unconfirmed unless an original source states it.
| Identity field | Source-based entry | Do not add |
|---|---|---|
| Product name | Exact supplier wording. | Category conclusion. |
| Model or SKU | Literal code and source path. | Assumed equivalence. |
| Configuration | Stated frame, strap, handle, and accessory details. | Performance conclusion. |
| Drawing revision | File name, date, revision text. | Current-status finding. |
| Product image | Original image and receipt date. | Production confirmation. |
| Supplier entity | Exact name and address shown. | Manufacturer or importer role. |
Preserve frame, fabric, and strap sources
CPSC’s guidance lists general and performance topics for the stated product context. 1 Preserve a frame drawing, fabric sheet, buckle data sheet, shoulder-strap record, parts list, sewing instruction, product image, component photograph, and supplier message as their own source objects.
A fabric source can state material wording. A frame drawing can state dimensions or a part code. Neither source decides that the material or component occurs in every product version, that it performs in a stated manner, or that it is associated with a report without a stated link.
Keep handle and retention sources distinct
CPSC’s cited guidance includes handle integrity and retention systems among stated performance topics. 1 Record original drawings, component lists, instruction files, product photographs, videos, correspondence, and test sources. Do not turn a listed component into a conclusion about strength, use, retention, stability, or safety.
| Component source | Capture | Do not conclude |
|---|---|---|
| Frame drawing | Revision, model text, and callouts. | Frame performance. |
| Strap source | Part wording, image, and reference. | Strap retention. |
| Buckle sheet | Part number and supplier description. | Product fit or function. |
| Handle source | Original drawing or photo. | Handle integrity. |
| Product video | Original link or file and receipt date. | Production configuration. |
Preserve complete test sources
Part 1230 states a standard for frame child carriers in the cited context. 3 That does not settle the meaning of a supplier report for a buyer product. Preserve complete reports, including sample wording, model and configuration references, laboratory identity, visible dates, pages, images, method text, result statements, and attachments.
A buyer-side source map should not decide sample equivalence, report applicability, test adequacy, or result status. Record the source precisely and list any missing model, frame, strap, or configuration relationship.
| Test-record field | Preserve | Open item if missing |
|---|---|---|
| Original report | Complete file and attachments. | Original unavailable. |
| Sample description | Exact product and component words. | Buyer-product link absent. |
| Date fields | Printed issue, sample, test, or receipt date. | Date type unclear. |
| Issuer | Laboratory or supplier wording as shown. | Issuer unavailable. |
| Result text | Exact text and page reference. | No buyer conclusion entered. |
| Source path | Email, portal, or attachment ID. | Origin not traceable. |
Treat labels and tracking records as evidence objects
CPSC guidance discusses permanently affixed information and tracking-label context in the stated setting. 1 Store label artwork, outer-carton artwork, close-up label images, whole-product images, translation files, revision codes, print proofs, and supplier messages. A complete product image preserves location context. A close-up preserves visible wording.
Do not decide whether a label is permanent, complete, correctly located, or connected to a production run. Record what appears and keep the original source.
Keep registration-card records separate
CPSC’s guidance says registration forms are required in the stated durable-infant-or-toddler-product context. 1 A buyer may receive card artwork, a template, a package insert, a printed card photo, a data field list, or an email. Keep these sources separate from labels, reports, and certificates.
| Registration-card source | Preserve | Keep separate |
|---|---|---|
| Artwork or template | Original file, revision, source date. | Requirement or sufficiency. |
| Package insert | Full image and product wording. | Inclusion in every unit. |
| Supplier message | Exact source text. | Registration outcome. |
| Product reference | Stated model or package link. | Applicability to another item. |
Treat certificates as factual sources
CPSC discusses CPC material in the stated context. 1 Preserve every certificate page, issuer wording, product identification, cited material, visible dates, signature area, and source path. Call it a certificate source received. Do not label it valid, approved, applicable, complete, or sufficient.
A certificate source does not decide whether a product may be certified or whether goods may be imported, sold, or released.
Map factory, production, package, and shipment sources
Factory profiles, production photographs, business documents, quotations, purchase orders, invoices, cartons, packing lists, and freight records add commercial context. Link these sources to product, frame, component, test, label, or certificate records only when an original source states a shared model, drawing revision, order number, product description, lot, date, or shipment reference.
| Commercial source | Capture | Link only when source states |
|---|---|---|
| Factory record | Entity, address, stated activity, date. | Product or test relationship. |
| Production source | Product image, work order, model, date. | Sample association. |
| Purchase order | PO, item wording, quantity, date. | Evidence-document connection. |
| Carton image | Product code and visible marks. | Product-version identity. |
| Freight record | Shipment reference and visible dates. | Stated shipment relation. |
Build a controlled source index
Give each received source a unique ID while retaining its original file name. The index can record the record type, source channel, date received, literal product words, configuration words, related source IDs, and open items. Do not use status labels such as compliant, safe, approved, certified, or ready for shipment.
| Source-index field | Example factual entry |
|---|---|
| Source ID | FC-023 |
| Original file | FC9-frame-drawing-rev-B.pdf |
| Record type | Frame drawing |
| Source channel | Supplier email dated 27 August 2026 |
| Product wording | Model FC-9, as printed in source |
| Related record | Report R-28 relationship not stated |
| Open item | Request source linking drawing and report |
Preserve revision history
When a supplier sends a revised drawing, label file, product image, or component document, keep both the earlier and later sources. Record the original file name, stated revision, receipt date, and any stated change. Do not remove an earlier record merely because a newer file exists. The older source may explain why a report, carton, certificate source, or purchase-order description differs from current material.
If the supplier gives no stated relationship between versions, record that as an open item. A source map should show that the relationship is absent rather than filling the gap with an assumed model match. This keeps the reviewer focused on a concrete request for the missing source.
Request sources, not conclusions
A request for “carrier compliance proof” may produce an unsupported declaration. Ask for the original source that links a report to a model, a frame drawing to a product version, a strap source to an image, or label artwork to a carton.
For example: “Please provide the original source that states the relationship between report R-28, model FC-9, drawing D-8, and the frame, shoulder-strap, handle, and retention configuration.” The request traces evidence without asking the supplier to decide scope, safety, certification, import, sale, or release.
Maintain a contradiction queue
A contradiction queue records differences rather than hiding them. A report may show another model. A frame drawing may omit an accessory in a product photo. A carton can identify a different entity. Retain all originals and request a source that states the relationship.
| Difference | Preserve | Neutral follow-up |
|---|---|---|
| Model mismatch | Exact codes and product wording. | Request stated relationship. |
| Frame mismatch | Drawings, photos, parts lists. | Keep versions separate. |
| Strap mismatch | Component sources and images. | Request revision source. |
| Label mismatch | Original artwork and photographs. | Request product-link source. |
| Certificate mismatch | Full document and product wording. | Request original support. |
Prepare China supplier frame child carrier evidence for review
A compact handoff lets product, safety, testing, certification, legal, or import reviewers find original materials. Include product identity, frame and component records, reports, labels, tracking files, registration-card sources, certificates, commercial records, and unresolved differences.
| Handoff section | Include | Leave to assigned reviewer |
|---|---|---|
| Product record | Literal model, drawing, image, configuration. | Scope decision. |
| Component record | Frame, fabric, strap, handle, retention sources. | Performance review. |
| Test record | Full report, sample words, dates, issuer. | Test conclusion. |
| Label record | Artwork, photos, tracking and card material. | Label or registration decision. |
| Certificate record | Original document and stated links. | Certificate action or validity. |
| Commercial record | Factory, order, package, freight sources. | Import, sale, or release decision. |
Common record-control errors
The first error is treating a product image as proof that it is the same configuration shown in a test report. Keep the source relationship open until documentation states it.
The second is treating a strap or frame specification as proof of performance. Store the source and leave the conclusion to a qualified reviewer.
The third is calling a certificate an approval. Preserve its exact wording as a certificate source.
The fourth is treating an organized source folder as a decision to import, sell, or release goods. It makes review more traceable but does not replace review.
Frequently asked questions
Does a frame drawing prove a product falls into a particular category?
No. Preserve the drawing, product wording, revision, and source path. The buyer-side map does not make a product-scope decision.
Does a test report prove that a production carrier matches the sample?
No. Save the complete report, sample description, configuration wording, dates, issuer, and related sources. The map does not establish sample equivalence without a stated source link.
Does label artwork show that a label is sufficient?
No. Artwork is an evidence source. Preserve visible text, revision, product reference, placement image, and source path without evaluating it.
What should a buyer do when a frame drawing and carton use different model codes?
Keep both original records, list the difference, and request a source that states their relationship. Do not edit codes or assume the materials refer to the same version.
Preserve source relationships before decision work begins
A useful evidence packet keeps the source trail behind product drawings, frame records, component files, reports, artwork, certificate sources, and commercial documents. It also makes missing links visible.
For China supplier frame child carrier evidence, create a separate record for each stated model and configuration, retain the original source behind every summary field, and record only relationships that sources state. Supplier Ally can help buyers organize supplier communications, product documentation, and evidence packets so the assigned reviewer starts with a traceable source file.
EN 
ES 