General Product Safety: GPSR and Traceability Documentation

What the term actually covers

A general product-safety framework places duties on whoever places a product on the market, and those duties include traceability and a technical file. For a neck massager, with its shell, motor, controller, battery and skin-facing pad, the regime is not optional and it is not settled by the factory alone. The duties sit with the party that places the product on the market, which may be the manufacturer or an importer depending on how the sale is structured.

The buyer's task is to establish which document types exist, which party holds each one, and what the markings on the product have to carry. Applicability, current text and timing are confirmed with the authority or the compliance review, not with a clause number.

A related discipline is record keeping. Traceability is only useful if the record can be produced when an inquiry arrives, which means the buyer should know where the file lives and who can release it. A file that exists but cannot be produced is, for practical purposes, not in the file.

The four things to establish

First, the identity of the party placing the product on the market. Second, the technical file that documents the design and its risk assessment. Third, the markings and records that let a unit be traced to its supplier and its batch. Fourth, the process for updating the file when a component changes.

None of the four is a formality. A traceability mark that stops at the factory leaves the party on the market unable to answer a later inquiry. A technical file that is not updated after a motor or cell change stops describing the shipped product.

A fifth question belongs beside them: who answers the inquiry. When a complaint or a market request arrives, one named person should be able to reconstruct which unit, which batch and which revision was shipped. Ask for that name before the first container is booked.

Comparison table

Duty	What it covers	Who holds it	What to ask for
Placing on the market	Market entry	Manufacturer or importer	Named party on the file
Technical file	Design and risk record	Supplier or importer	File contents list
Traceability	Markings and batch records	Party on the market	Marking layout
Change control	Update on component change	Named owner	Trigger and approval
Inquiry response	Who reconstructs a shipment	Named contact	Contact and record path
Assembly batch	Parts fitted per unit	Assembly line	Batch and revision record

A framework is not the same as a compliance conclusion

Naming the framework ≠ proving conformity. Describing a general product-safety regime names the obligations a market expects. It does not state that a specific unit meets them, that the file is current, or that the marking is sufficient. The current text, the product categories and the timing all need confirmation with the authority or the compliance review.

The second boundary is between the factory and the party on the market. The factory supplies parts and records. The party on the market holds the traceability and file duties. A buyer who assumes the factory owns both will find the gap when an inquiry arrives.

A third boundary is between the file and the marking. The file describes the design; the marking tells a later party which units the file covers. A file that does not match the marking is two records that describe two different products, and neither can be relied on alone.

A second habit belongs beside the file: the marking layout. Ask for the marking plan as a drawing, with each mark placed on the shell or the battery bay, because a mark that is legible on a photograph can be illegible on the product. The party on the market will need to read that marking when an inquiry arrives, and the layout drawing is the difference between a mark that can be read and a mark that can be photographed.

The third habit is the review cadence. A file that is only opened at shipment is a file that will be stale at shipment. Ask when the file is reviewed and what event pulls it forward, whether that is a component change, a revision change or a schedule change. A file with a stated review cadence is a process; a file that is opened on demand is a document.

The traceability chain in practice

The traceability chain runs from the cell maker through the shell supplier, the driver board, the assembly line and the party placing the product on the market. Each link holds a record: the cell maker holds the cell identifier, the shell supplier holds the tool and material record, the assembly line holds the batch and revision record, and the party on the market holds the file. A chain that breaks at the shell supplier cannot be reconstructed at inquiry time. Ask which link the supplier owns and which record it keeps, so the gap is visible before the container is booked rather than after the request arrives.

Questions to ask a supplier

Which party places the product on the market, and is that stated on the file?
What does the technical file contain, and who signs the risk assessment?
What markings appear on the product, and how does a unit trace to its batch?
What change triggers a file update, and who approves it?
How is the file updated between shipments?

Common mistakes buyers make

Assuming the factory owns traceability. The duty sits with the party on the market.
Reading a supplier summary as the technical file. Request the file contents list.
Skipping the change-control question. A stale file describes an earlier revision.

Each is caught by naming the party, the file and the owner on the purchase order, and by re-reading the file at every shipment.

Next step

Request the traceability and file-owner answers with your RFQ, via contact.