How Should Buyers Prepare a Product Documentation Request List Before Import Review?

Answer first

Buyers should prepare a SKU-specific, destination-specific and version-controlled request before they ask a supplier for import evidence. Define the exact product, proposed destination market, intended importer and decision the documents must inform. Then request the records needed to identify that product, understand the route, connect declarations to evidence, and resolve gaps before a purchase or listing decision.

A practical documentation request index is not a demand for a large folder of unrelated files. Each line should say what is needed, why it matters, which SKU and version it covers, who supplied it, when it was issued, and what reviewer action remains. This reduces the risk of mistaking a report for a similar model or draft artwork for the current version.

For toys proposed for the EU, importers have specific duties before placing a toy on the market: they must ensure that the manufacturer completed the appropriate conformity assessment, prepared technical documentation, applied the required marking, and supplied required documents. They must keep a copy of the EC declaration of conformity for 10 years and ensure that technical documentation can be provided on request. [1] That is a useful reason to treat evidence collection as an importer-controlled review process, rather than as a one-time supplier email.

The file set will differ by market, product, route and retailer. No request list can itself establish compliance or replace the importer’s destination-market assessment. Product details must be checked against the exact SKU, approved sample, current instructions, packaging, supplier records, retailer rules, importer obligations and destination-market review.

Set the review boundary before contacting the supplier

The fastest way to receive unusable files is to ask, “Please send all certificates.” That wording does not identify a product version, market or regulatory question. It also encourages a supplier to send generic company documents alongside reports that cannot be matched to the item being considered.

Create a short review brief first. Give the SKU a unique internal identifier and record the supplier’s model identifier, proposed trading name, product category as currently understood, destination country or countries, and the intended importer or economic operator. Attach photographs or controlled images of the approved sample where available. Record the current packaging-artwork and instruction versions rather than relying on a descriptive file name.

Next, state the review boundary. Is the team deciding whether to continue sourcing, whether evidence is sufficiently organised for specialist review, whether current artwork matches the evidence, or whether a retailer’s onboarding request can be answered? These decisions need different levels of detail. A procurement gate may need a clear evidence inventory and open issues. A destination-market assessment may need deeper records and professional interpretation.

Keep the market paths separate. A file relevant to one jurisdiction is not proof for another. In Great Britain, for example, official guidance says that importers should make sure the manufacturer has completed the relevant declaration of conformity and technical documentation before the importer places a toy on the GB market, and that the importer keeps the declaration and makes technical documentation available to enforcement authorities for 10 years. [4] A buyer should therefore label every request row with its intended market rather than build a single undifferentiated “global” folder.

Identify the accountable people

Assign a request owner, an evidence reviewer, a commercial decision owner and an escalation contact. The request owner chases files and maintains the index. The reviewer checks identity, coverage and coherence; they do not simply mark an attachment “received.” The commercial owner decides whether an unresolved issue stops the next business step. The supplier should know the technical contact who can explain a drawing, bill of materials, artwork revision or report scope.

Build the request around evidence, not document names

Ask what a record has to demonstrate, then request the appropriate source. A declaration, a test report, a safety assessment and a label proof are connected but not interchangeable. Under the EU Toy Safety Directive, technical documentation can include a design-and-manufacture description, component and material list, relevant chemical safety data sheets, safety assessments, the conformity-assessment route, the declaration, manufacturing and storage addresses, and applicable test or notified-body material. [1]

The European Commission’s technical-documentation guidance also says that documentation is unique to an individual toy. It allows shared material across similar toys only when differences and product-specific documents are retained, and it stresses keeping records current with product history. [2] For a buyer, that means every attachment needs an explicit product-identity check. Similar appearance, a shared factory or a near-identical model number is not enough.

This evidence-first structure is more useful than a generic supplier document request because it exposes why a document is being sought. It also gives the supplier a fair, precise way to answer: “not applicable,” “available but not this version,” “under revision,” or “attached and mapped to SKU.” Those responses reveal what must happen next.

A documentation index can be a spreadsheet, controlled procurement workspace or product-information system. Record the request-line ID, SKU/version, market, document type, evidence question, supplied filename, issuer, issue date, product identity shown, reviewer, status, gap, follow-up owner and final decision date. Retain the source file alongside working notes.

Use an import product review checklist before files are accepted

The following checklist is a procurement control, not legal advice or a substitute for the importer’s own assessment. Work through it in order. Do not let a deadline silently turn an incomplete item into an approved one.

1. Lock the product identity

Confirm the exact SKU, variant, colour or configuration if relevant, supplier model code, product revision and proposed destination. Capture the approved-sample date or identifier when one exists. Ask whether the supplied records cover that exact configuration or a family of products. If they cover a family, request a written cross-reference that explains the common basis and identifies the differences.

2. Map market responsibilities

Record who is manufacturer, supplier, importer, distributor and private-label owner for the proposed route. The labels must reflect the actual arrangement, not simply the party that sent the file.

For EU toy placement, Article 6 identifies importer checks that include the manufacturer’s conformity assessment, technical documentation, required marking and accompanying documents; it also requires importers to ensure instructions and safety information are provided in the language or languages determined by the Member State. [1] Put these as separate rows in the index so a declaration does not close every question by itself.

3. Request the evidence set with a coverage statement

Ask the supplier to return a simple cover sheet for each SKU. It should list every submitted file, its document date and revision, the products it covers, the destination market claimed, the issuing organisation, and the supplier contact able to answer technical questions. Request full documents rather than screenshots, cropped certificates or unverifiable summaries whenever a reviewer needs the underlying scope.

For a U.S. children’s product that is subject to CPSC children’s product safety rules, CPSC guidance says the domestic manufacturer or importer issues a written Children’s Product Certificate based on testing from a CPSC-accepted third-party laboratory. The guidance also says the CPC and supporting test reports must be in English. [3] Its seven required CPC elements include product identification, cited rules, certifier, test-record custodian, manufacture, testing and laboratory information. [3] Use those fields as an identity check for the specific U.S. route, not as a universal toy-document template.

At this stage, call the assembled folder a toy product evidence pack only when it remains an indexable collection tied to the exact SKU and market. It should not be presented as a blanket approval, a substitute for import review, or proof that every future product version is covered.

Need help framing a SKU-level evidence index for a prospective B2B project? Email Toywink’s B2B team with the product category and intended market. The discussion should be scoped to the exact product and documentation available for review.

4. Compare evidence to the production-intent presentation

Review product description, drawings, packaging, labels and instructions side by side. Look for mismatches in model identifiers, components, warnings, language versions, dates and market names. A report with vague product identification needs clarification even if the supplier says it applies.

5. Check change control and traceability

Ask what changed after the latest report, declaration, safety assessment or artwork approval. Changes can include a component, material, supplier, manufacturing site, product construction, packaging copy, instructions or warning layout. The correct follow-up is not always a new document; it is a documented assessment by the responsible party of whether the change affects the evidence and what action follows.

EU Commission guidance says the product history should be retained and that documentation should be kept up to date to reflect changes to the toy, legislation or standards. [2] A buyer can operationalise that guidance by recording a change date, description, affected evidence IDs, supplier response, reviewer decision and the next review trigger.

6. Close or escalate each gap

A missing file is not the same as evidence that the item is unsuitable. It is an unresolved information condition. Describe the gap without guessing: “full report not supplied,” “report identity does not show the proposed variant,” “final instruction artwork not available,” or “market applicability not confirmed.” Then give the gap an owner, due date and decision effect.

Escalate when a file’s legal meaning, test scope, safety assessment, classification or destination-market relevance needs specialist interpretation. Procurement can coordinate evidence, but should not manufacture conclusions it is not qualified to make. If a supplier cannot establish the relationship between a document and the exact product, retain that limitation in the decision record.

Turn the request into an importer documentation workflow

A repeatable process has five gates: define, request, match, resolve and retain. At the define gate, the buyer creates the product and market brief. At request, the supplier returns a cover sheet and source files. At match, the designated reviewer checks each record against SKU, version and market. At resolve, open questions are assigned and decisions are captured. At retain, the importer preserves the final index, source files, correspondence that explains scope, and the approval or hold decision.

Set a status vocabulary that prevents accidental release: requested, received, under review, accepted for stated purpose, gap open, superseded, and closed. “Accepted for stated purpose” is particularly useful because it does not overstate what a document proves. The stated purpose might be “identity confirmed for internal procurement review,” not “all market obligations satisfied.”

Version control must apply to the request list itself. Freeze a dated review snapshot when the team makes a decision. When new packaging, instructions or supplier evidence arrives, create a new snapshot and link it to the previous one. Store an audit trail of who changed a status and why. The EU technical-documentation guidance recognises that information can sit in different formats and locations, but emphasises that the documentation must be current and the product history retained. [2] A controlled index is the practical bridge between dispersed files and a retrievable record.

Also distinguish supplier ownership from importer accountability. The supplier may hold source manufacturing records, but the importer should be able to locate the appropriate evidence, explain its connection to the product, and respond through the responsible process for its market. In GB, official guidance includes maintaining the declaration of conformity and making technical documentation available to enforcement authorities on request for 10 years. [4] This is why links to a supplier portal alone are a weak retention method unless access, versions and retrieval responsibility are controlled.

Make the request proportionate and repeatable

A strong product compliance information request is precise without becoming a catalogue of speculative paperwork. Use a core template for identity, market, declaration, assessment or report, product presentation, traceability and change history. Add modules only when the product, market or retailer rule makes them relevant. This improves response quality and makes gaps visible early.

Keep a “not applicable” column with a reason and reviewer name. A blank cell does not establish whether an item was missed, irrelevant or awaiting a response.

Frequently asked questions

Is a declaration enough to close an import review?

Usually, no single file closes every review question. A declaration may be a required part of a particular route, but a buyer still needs to establish the product it covers, its version, the destination market, and the relationship to accompanying records and current presentation. Under the EU Directive, the declaration is one element of the broader technical documentation, alongside materials such as design information, safety assessment and relevant reports. [1]

Should buyers ask for every document before evaluating a supplier?

Ask for evidence in stages. An initial request can verify identity, market intent and whether the supplier can map key documents to the exact SKU. Request deeper records when the project reaches a defined review gate.

What should happen if the report shows a different model number?

Do not rename the file or assume the difference is cosmetic. Log the mismatch, request an explanation and ask for a traceable mapping to the proposed SKU or revised evidence that identifies it. If the explanation cannot be supported, leave the coverage unresolved and escalate according to the importer’s destination-market process.

Can one document set cover several product variants?

It may contain shared records, but the buyer should confirm the relationship for each variant. European Commission guidance notes that technical documentation is unique to an individual toy while allowing generic files when the differences and toy-specific material are retained. [2] Record which files are shared, which are variant-specific, and the basis supplied for the mapping.

Who should keep the final evidence index?

The importer or accountable buyer function should keep a controlled copy, with source files and the decision record, while supplier-held source records remain accessible through agreed contacts. The appropriate retention period and contents depend on the market. For example, EU and GB materials cited here set 10-year requirements around declarations and technical documentation in the toy context. [1] [4]

Build an evidence trail before the decision point

The practical goal is a clear, retrievable trail from the SKU and destination market to the records reviewed, the gaps found and the decisions made. Build the request list before import review begins, then update it whenever the product, evidence or market route changes. That approach supports disciplined procurement without implying that a generic folder, a supplier statement or a single document guarantees an outcome.

For a B2B discussion about product-information handover for a specific proposed SKU, email Toywink at info@toywink.com. Please include the intended market and the documents or product version you want to discuss; any next step remains subject to the exact SKU, approved sample, current records and destination-market review.

References