A supplier packet for a powered infant or cradle swing may contain product images, product specifications, electrical-component details, drawings, restraint descriptions, seat-angle records, test material, label artwork, registration-card content, certificates, factory records, and shipment documents. A clean folder can still contain mixed versions. A source map keeps every record tied to the product wording and configuration it actually shows.
This guide organizes China supplier infant and cradle swing evidence as factual buyer-side records. It explains how to preserve product, powered-mechanism, seat, restraint, angle, test, label, tracking, registration-card, certificate, factory, production, package, and shipment sources. It does not decide whether a product is an infant, cradle, combination, or travel swing; whether it has a powered mechanism; whether a standard applies; whether testing passed; or whether goods may be certified, imported, sold, or released.
CPSC business guidance describes several swing terms and source categories in the stated context. 1 CPSC’s voluntary-standard material discusses infant-swing product wording. 2 Current Part 1223 establishes a stated standard for infant and cradle swings and incorporates ASTM F2088-25. 3 These primary sources help organize records. They do not make a supplier file a product-scope, test, safety, label, certificate, import, sale, or release decision.
Start with the literal product record
Record what each source calls the product. Save the exact model, SKU, product title, drawing revision, frame description, seat position, mechanism wording, image, accessory, and supplier identity. Do not use a product title or photograph to select a product classification.
CPSC guidance uses terms including infant swing, cradle swing, combination swing, and travel swing in the stated context. 1 The buyer-side map should preserve a supplier’s words without applying those terms to the buyer item.
| Source question | Preserve | Keep separate |
|---|---|---|
| What item appears? | Literal model, image, and product text. | Product scope decision. |
| What motion source appears? | Exact powered-mechanism wording. | Mechanism assessment. |
| What seat appears? | Stated seat position and configuration. | Angle or use conclusion. |
| What report appears? | Full source, sample wording, issuer, dates. | Test result or adequacy. |
| What certificate appears? | Original document and product reference. | Certificate validity. |
Separate product configurations
Create a separate record whenever a source differs on model number, SKU, seat style, frame, powered mechanism, control panel, restraint, tray, armbar, toy, accessory, angle statement, drawing revision, packaging, or supplier entity. Similar photographs are not proof of the same production configuration.
A product video might show a removable tray. A report might describe a version without it. A carton may carry another code. Keep the original sources distinct and record the missing relationship.
| Identity field | Source-based entry | Do not add |
|---|---|---|
| Model or SKU | Exact source code and source path. | Assumed equivalence. |
| Product description | Literal supplier wording. | Scope finding. |
| Configuration | Stated frame, seat, restraint, accessory. | Performance conclusion. |
| Drawing revision | File name, date, revision text. | Current-status finding. |
| Supplier entity | Exact name and address shown. | Manufacturer or importer role. |
Preserve powered-mechanism records
CPSC’s business guidance describes a stated scope that involves swings using a powered mechanism for motion. 1 A buyer can preserve a supplier’s mechanism drawing, motor description, control-panel image, power source, wiring source, bill of materials, video, and correspondence. The source map should not decide whether an item has a powered mechanism or whether that feature places it within a category.
Record the product relationship only when a source states it. A motor part number in a general component catalog does not establish its use in a particular swing.
Keep seat, restraint, and angle sources separate
The CPSC guidance lists restraint, seat-angle, structural-integrity, stability, folding, and other source categories in the stated context. 1 Store drawings, instructions, photographs, component lists, videos, and supplier statements under their actual source labels. Do not rewrite them as proof that a seat has a certain angle, a restraint is sufficient, or a structure performs in a stated manner.
| Configuration source | Capture | Do not conclude |
|---|---|---|
| Seat drawing | Revision, model wording, callouts. | Seat angle or product use. |
| Restraint source | Exact part names and images. | Restraint performance. |
| Tray or armbar source | Product and component references. | Applicability to another version. |
| Mechanism record | Supplier wording and part code. | Function or safety. |
| Product video | Original link or file and receipt date. | Production configuration. |
Store full test sources
Part 1223 states a standard for infant and cradle swings in the cited context. 3 That does not determine what a supplier report means for a buyer product. Preserve the complete source, including the original report, sample description, configuration wording, dates, laboratory identity, images, pages, attachments, and stated results.
The source map should not decide sample equivalence, test conditions, method application, adequacy, or result. It should show the original source and any missing model or configuration link.
| Test-record field | Preserve | Open item if missing |
|---|---|---|
| Full report | Original file and attachments. | Original unavailable. |
| Sample description | Exact product and configuration words. | Buyer-product link absent. |
| Date fields | Visible issue, sample, or test dates. | Date meaning unclear. |
| Issuer details | Laboratory or supplier text as shown. | Issuer not identified. |
| Result wording | Exact text with page references. | No buyer result entered. |
| Source path | Email, portal, or attachment ID. | Origin not traceable. |
Treat label and tracking files as evidence objects
CPSC guidance describes permanent product information and tracking-label context for durable infant and toddler products. 1 Preserve label artwork, outer-package artwork, close-up label images, full product photographs, translations, revision numbers, and supplier messages. A close-up can show content; a full image shows location and product context.
Do not decide whether a label is permanent, complete, properly located, or associated with a particular production run. Keep the exact text and the source path.
Keep registration-card sources separate
CPSC’s cited guidance says product registration forms are required in the stated durable-infant-or-toddler-product context. 1 A supplier may send card artwork, a template, a package insert, a printed card photo, a data field list, or a message. Store each record without concluding that it applies to a particular item or is sufficient.
| Card-source field | Preserve | Keep separate |
|---|---|---|
| Artwork | Original file, revision, source date. | Requirement or sufficiency. |
| Package insert | Full image and visible product wording. | Inclusion in every unit. |
| Supplier message | Exact quoted statement. | Registration outcome. |
| Product link | Stated model or package connection. | Applicability to other models. |
Do not upgrade certificate sources
CPSC guidance discusses CPC material in a stated context. 1 A certificate file should remain a certificate source in the map. Preserve every page, product wording, cited material, date, issuer text, signature area, and source path. Do not label it valid, approved, applicable, complete, or sufficient.
A buyer-side source record does not decide that a product may be certified, or that a particular document supports an import, sale, or release action.
Map factory, production, package, and shipment sources
Factory profiles, production photographs, business documents, purchase orders, invoices, carton images, packing lists, and freight records identify a sourcing project. Join them to other evidence only when sources share a stated 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 text, quantity, date. | Source-document connection. |
| Package image | Item code, markings, configuration text. | Product-version identity. |
| Freight record | Shipment reference and visible dates. | Stated shipment relation. |
Build a source index before requesting more files
A simple source index reduces the chance that a team asks twice for the same document or loses the context behind an attachment. Give every received item a unique source ID. The ID can be a short sequence, such as SW-014, but the index should also retain the original file name and the channel through which it arrived. Record the date received rather than guessing a production or test date.
The index can identify a document as a drawing, product image, motor record, restraint source, test file, label artwork, card source, certificate source, commercial record, or supplier message. It should not use status labels such as compliant, approved, safe, or ready for shipment. Those labels imply a decision that the source index cannot make.
| Source-index field | Example of a factual entry |
|---|---|
| Source ID | SW-014 |
| Original file name | Model-S12-seat-drawing-rev-D6.pdf |
| Received through | Supplier email dated 27 August 2026 |
| Record type | Product drawing |
| Product wording | Model S-12, as printed in source |
| Configuration wording | Powered mechanism and removable tray, as stated |
| Related source IDs | Report R-24 relationship not stated |
| Open item | Request a source linking the drawing and report |
When a source has been replaced, preserve both the earlier and later files. Note the revision wording, date, and stated change if the source gives one. Do not delete the earlier record merely because a newer-looking file arrived. The earlier file may explain a mismatch elsewhere in the packet.
Ask for a source, not a conclusion
A request for “swing compliance proof” often produces a broad statement. Ask for the source that links a report to a model, a mechanism record to a drawing revision, a label file to a product photograph, or a card file to a package.
For example: “Please provide the original source that states the relationship between report R-24, model S-12, drawing D-6, and the powered-mechanism configuration shown in the product record.” The request traces evidence. It does not ask the supplier to decide safety, certification, import, sale, or release.
Maintain a contradiction queue
A contradiction queue lists visible differences without silently selecting a winner. The report model might differ from the purchase order. A drawing could omit an accessory shown in a video. A label may name a different entity.
| Difference | Preserve | Neutral follow-up |
|---|---|---|
| Model mismatch | Exact codes and product wording. | Request stated relationship. |
| Configuration mismatch | Images, drawings, component sources. | Keep versions separate. |
| Label mismatch | Original artwork and photographs. | Request revision source. |
| Certificate mismatch | Full document and product words. | Request original supporting source. |
| Entity mismatch | Names and addresses by source. | Request relationship documentation. |
Prepare China supplier infant and cradle swing evidence for review
A compact handoff packet helps product, safety, testing, certification, legal, or import reviewers find the originals. Include product identity, mechanisms, seat and restraint sources, test material, labels, tracking files, registration-card sources, certificate sources, factory records, commercial records, and open differences.
| Handoff section | Include | Leave to the assigned reviewer |
|---|---|---|
| Product record | Literal model, drawing, image, configuration. | Scope decision. |
| Mechanism record | Motor, control, power, and source files. | Mechanism determination. |
| Test record | Full source, sample words, date, issuer. | Test review or conclusion. |
| Label and card record | Artwork, photos, and package sources. | Label or registration decision. |
| Certificate record | Original file and stated associations. | 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 picture as proof that its powered mechanism or configuration matches a test source. Preserve both records and request a source-based connection.
The second is calling a certificate an approval. Retain it as a certificate source with its exact product wording.
The third is merging a label, a registration-card template, and a package image into one record. They are different evidence objects even when they arrive in the same email.
The fourth is treating a well-organized source folder as a product-safety or release decision. It is not. The packet makes review possible but does not perform the review.
Frequently asked questions
Does a product video establish that a swing uses a powered mechanism?
No. Preserve the video, source date, model text, and visible configuration. The buyer-side source map does not decide product scope or mechanism status.
Does a test report prove the report sample matches production?
No. Keep the complete report, sample description, model wording, configuration sources, dates, and source path. A source map does not establish sample equivalence unless a source states it.
Does a registration-card file show that the card applies to every model?
No. Preserve the card source and any stated model or package link. Do not extend that link to other products without a source.
What should a buyer do when the label artwork and carton use different model codes?
Retain both original sources, list the mismatch, and ask for a document that states the relationship. Do not edit codes or assume they identify the same product.
Preserve source relationships before anyone reaches a decision
A useful evidence packet keeps product files, mechanism records, configuration sources, reports, artwork, card material, certificates, factory records, and commercial documents traceable to their originals. It also records missing links and differences.
For China supplier infant and cradle swing evidence, create separate records for each stated configuration, retain the original source behind each 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 