A China supplier may send a sling carrier drawing, fabric specification, seam detail, strap record, product image, warning artwork, test report, certificate, registration-card file, package image, factory record, purchase order, and shipment document. The documents can refer to different product versions even if the product name looks the same. A source map keeps each record tied to the wording and configuration it actually shows.
This guide organizes China supplier sling carrier evidence as factual buyer-side records. It explains how to preserve product, fabric, seam, strap, label, warning, restraint, test, tracking, registration-card, certificate, factory, package, production, and shipment sources. It does not decide whether an item is a sling carrier, whether a standard applies, whether a position or weight statement is suitable, whether a test passed, whether a warning is sufficient, or whether goods may be certified, imported, sold, or released.
CPSC business guidance describes sling carriers, fabric and label topics, performance subjects, registration forms, dates, and CPC materials in a stated context. 1 CPSC’s soft-carrier guidance supplies related source terminology while distinguishing another stated carrier category. 2 Current Part 1228 establishes a stated standard for sling carriers and incorporates ASTM F2907-22. 3 These primary sources help a buyer organize records. They do not turn a supplier source into a product-scope, test, safety, certificate, import, sale, or release decision.
Begin with a factual source boundary
Record what a source says, not what it might imply. Preserve the supplier’s literal product name, SKU, fabric wording, drawing revision, strap part number, image, label text, source date, sender, order code, and shipment reference. Keep the original file behind every index entry.
Product classification, position or age assessment, fabric and seam review, restraint evaluation, test assessment, warning review, certification, safety, legal, importer, import, sale, and release questions belong to the assigned reviewer. The buyer-side source map makes those questions easier to trace without answering them.
| Evidence question | Preserve from the source | Keep separate |
|---|---|---|
| What product appears? | Literal product wording, model, and image. | Sling-carrier classification. |
| What material appears? | Fabric, thread, strap, or hardware source text. | Material or seam conclusion. |
| What warning appears? | Original artwork, photo, revision, and location. | Warning sufficiency. |
| What test exists? | Full report, sample wording, date, issuer. | Test result or adequacy. |
| What certificate exists? | Original file and cited product text. | Certificate validity or issue decision. |
Create a separate product record for each configuration
CPSC’s business guidance provides stated sling-carrier wording and notes that designs can vary. 1 Preserve a supplier’s product terms as supplied. Create a new record when sources differ on model, fabric, carrier construction, position description, strap design, buckle, label, warning, accessory, drawing revision, package, or supplier entity.
A product photo might show one strap configuration while the test report identifies another. A generic fabric sheet may be sent with several models. Do not make a connection unless an original source states it.
| Identity field | Source-based entry | Do not add |
|---|---|---|
| Product name | Exact supplier wording. | Product category finding. |
| Model or SKU | Literal code and file path. | Assumed equivalence. |
| Fabric source | Material wording, color, construction text. | Use in every product. |
| Drawing revision | File name, date, and revision. | Current-status finding. |
| Product image | Original image and receipt date. | Production confirmation. |
| Supplier entity | Exact name and address in source. | Manufacturer or importer role. |
Preserve fabric and seam records
CPSC guidance refers to sling products of fabric or sewn fabric construction in its stated context. 1 Keep fabric sheets, swatches, photos, bills of materials, sewing instructions, seam diagrams, thread information, wash-care sources, and supplier correspondence. Use source labels such as fabric specification received or seam drawing source rather than performance labels.
A fabric source can identify a material description. It does not establish that the material was used in a named product, that a seam is suitable, or that a product meets a stated condition.
Keep strap, restraint, and hardware sources separate
CPSC’s sling-carrier guidance lists structural integrity, restraint system, and occupant retention as stated performance topics. 1 A buyer can hold a strap drawing, buckle data sheet, hardware part list, product photo, instruction sheet, supplier statement, and test source in the record set. The source map should not decide whether a strap retains, a buckle performs, or a component is appropriate.
| Component source | Capture | Do not conclude |
|---|---|---|
| Strap drawing | Revision, callout, and model text. | Strap performance. |
| Hardware sheet | Supplier wording and part number. | Applicability to a product. |
| Parts list | Component name and stated quantity. | Product configuration. |
| Product image | Full image and close-up. | Production configuration. |
| Instruction source | Original file and source date. | Correct use or operation. |
Preserve full test sources
Part 1228 establishes a stated standard in the cited context. 3 That does not determine what a supplier’s report means for a buyer item. Save the full report, not a cropped result page. Retain the sample description, model, configuration text, dates, laboratory identity, source pages, images, test-method text, result wording, and attachments.
The record map does not decide that a sample matches production, that testing is adequate, or that a stated result is passing. It records the source and any missing link between the source and a buyer product.
| Test-source field | Preserve | Open item if missing |
|---|---|---|
| Original report | Complete file and attachments. | Original unavailable. |
| Sample description | Exact product and fabric wording. | Buyer-product link missing. |
| Date fields | Issue, test, sample, or receipt date. | Date type unclear. |
| Issuer | Laboratory or supplier wording as shown. | Issuer unavailable. |
| Result statement | Exact source text and page reference. | No buyer conclusion entered. |
| Source path | Email, portal, or attachment ID. | Origin not traceable. |
Treat label and warning artwork as source files
CPSC’s sling-carrier guidance discusses labels and includes warning-label source details in the stated context. 1 Preserve artwork, full product photos, close-ups, placement images, translations, revision codes, print proofs, and related supplier messages. Store the complete image with the close-up because each answers a different source question.
Do not decide whether a warning applies, is complete, remains attached, is durable, is correctly located, or is sufficient. A source record should describe visible text and placement only.
Keep tracking and registration-card sources distinct
CPSC’s guidance discusses tracking-label and registration-form context for the stated product class. 1 Record any tracking-label artwork, code illustration, package source, registration-card artwork, card template, insert photograph, product reference, and supplier statement as separate evidence objects.
| Source type | Preserve | Keep separate |
|---|---|---|
| Tracking source | Original code, artwork, image, file revision. | Requirement or sufficiency. |
| Card artwork | Original file, product wording, date. | Registration outcome. |
| Package insert | Full image and visible model text. | Inclusion in every unit. |
| Supplier statement | Exact quoted wording. | Category or certificate decision. |
Do not upgrade a certificate source
CPSC discusses CPC material in a stated context. 1 Preserve a certificate source with all pages, issuer words, product identification, cited material, dates, signature area, and source path. Call it a certificate source received. Do not call it approved, valid, applicable, complete, or sufficient.
A supplier document does not decide whether a buyer product may be certified or whether goods may move forward for import, sale, or release.
Map factory, package, and shipment records
Factory profiles, production images, purchase orders, invoices, carton photographs, packing lists, and freight records provide commercial context. Link these files to product, fabric, label, warning, test, or certificate sources only where a source states a shared model, revision, order number, product description, date, lot, or shipment reference.
| Commercial source | Capture | Link only when source states |
|---|---|---|
| Factory record | Entity, address, stated activity, date. | Product or test connection. |
| Production source | Product image, model, work order, date. | Sample or shipment association. |
| Purchase order | PO, item wording, quantity, date. | Evidence-document relationship. |
| Package image | Product code and visible markings. | Product-version identity. |
| Freight record | Shipment reference and visible dates. | Stated shipment connection. |
Build a controlled source index
Before requesting additional files, assign each received source a unique identifier and retain the original file name. The index should state the record type, sender or source channel, date received, literal product wording, configuration wording, related source IDs, and open items. It should never use a source index to state that a product is compliant, safe, approved, certified, or ready for shipment.
| Source-index field | Example factual entry |
|---|---|
| Source ID | SC-017 |
| Original file | SC11-strap-drawing-rev-D4.pdf |
| Record type | Strap drawing |
| Source channel | Supplier email dated 27 August 2026 |
| Product wording | Model SC-11, as printed in source |
| Related record | Report R-25 relationship not stated |
| Open item | Request source linking drawing and report |
Retain an earlier file after a supplier sends a newer-looking version. Record the revision wording and stated change if the source contains one. The older source may explain why a report, product image, or label file differs from later material.
Request a record instead of a conclusion
A request for “sling compliance proof” can produce a broad statement without supporting files. Ask for the specific missing source. Request the drawing that connects a strap to a model, the original report that identifies a fabric and configuration, the artwork revision that matches a product photo, or the record linking a card template to a package.
For example: “Please provide the original source that states the relationship between report R-25, model SC-11, the fabric specification FS-8, and drawing D-4, including the strap configuration.” The request follows documents. It does not ask the supplier to decide scope, safety, certification, import, sale, or release.
Maintain a contradiction queue
A contradiction queue records visible differences. It prevents a team from treating sources as consistent because they arrived together. A report can name another model. A warning artwork file may show another entity. A product photo may use a different buckle.
| Difference | Preserve | Neutral follow-up |
|---|---|---|
| Model mismatch | Exact codes and product text. | Request stated relationship. |
| Fabric mismatch | Source sheets, photos, and parts lists. | Keep configurations separate. |
| Strap mismatch | Drawings, component source, product images. | Request revision history source. |
| Warning mismatch | Original artwork and photographs. | Request source-based product link. |
| Certificate mismatch | Full document and product wording. | Request original supporting source. |
Prepare China supplier sling carrier evidence for review
A compact handoff sheet lets product, safety, testing, certification, legal, or import reviewers locate original material. Include product identity, fabric and seam sources, straps and hardware records, reports, labels, tracking sources, registration-card material, certificates, commercial records, and open differences.
| Handoff section | Include | Leave to the assigned reviewer |
|---|---|---|
| Product record | Literal model, drawing, image, configuration. | Scope decision. |
| Material record | Fabric, seam, strap, and hardware sources. | Material or performance review. |
| Test record | Original report, sample wording, date, issuer. | Test conclusion. |
| Label record | Artwork, photos, tracking and card sources. | Label or registration decision. |
| Certificate record | Original document and stated connections. | 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 fabric data sheet as proof that it belongs to every product in a supplier catalog. Keep the material source and request a stated product connection.
The second is calling a certificate an approval. Preserve the document as a certificate source with its exact product words.
The third is merging warning artwork, a tracking image, and a registration-card file into one record. These are separate sources even when attached to the same email.
The fourth is treating an organized folder as a release decision. Source organization does not decide product scope, testing, safety, certification, import, sale, or release.
Frequently asked questions
Does a fabric specification prove it was used in a specific sling carrier?
No. Keep the original fabric source and record any stated product relationship. A buyer-side evidence map does not infer use across models or production versions.
Does a test report prove that a current production version meets a standard?
No. Preserve the complete report, sample description, product and fabric wording, date, issuer, and source path. The map does not decide sample equivalence, test result, or safety.
Does warning artwork show that the warning is sufficient?
No. Artwork is a source file. Preserve its text, revision, placement image, product reference, and original path without evaluating it.
What should a buyer do when a strap drawing and product photo differ?
Retain both records, describe the difference, and request an original source that states their relationship. Do not edit either source or assume the products match.
Preserve original source relationships before decision work starts
A useful packet keeps the trail behind product files, fabric records, component documents, reports, artwork, certificate sources, and commercial records. It also keeps gaps visible instead of filling them with assumptions.
For China supplier sling carrier evidence, create a separate record for every stated model and configuration, preserve the original file behind each summary field, and record only links 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 