Where responsibility sits
The EU's general product safety regime asks that a product placed on the market be safe, and it distributes that duty across the parties who place it there. For a pet fan sold by a brand into the EU, the practical question is which party holds which part of the obligation: the manufacturer, the importer, the distributor, or the authorised representative. The answer is not a matter of goodwill; it decides whose name and address must appear on the product, the packaging and the listing.
A buyer's checklist begins by naming the parties. For each model and each sales route, record who is treated as the manufacturer, who as the importer, and who as the responsible person for the market in question. When a file set later changes hands, the responsibility map is the document that tells the next owner which obligations they inherited and which they did not.
What the technical file should carry
The technical file is the record of how the product was assessed. For a pet fan it typically includes the product description, the design and manufacturing information, the test reports that support the applicable requirements, and the risk assessment that connects the design to the identified hazards. The number of pages is not the point; the point is that each claim in the marketing copy has a line somewhere in the file that supports it.
Ask for the file as a set rather than as a summary, and ask for the version that matches the shipped revision. A file issued for the prototype and a file issued for the production article are different documents, and a buyer who keeps the prototype file has a file that does not describe the product they are shipping.
Labelling: what must be confirmed
Labelling on a pet fan carries several different pieces of information at once: the product identity, the power and charging details, the manufacturer or responsible party, the market markings, and the warnings or precautions that apply to use. Each has a different owner and a different update trigger.
The warnings are the part most often copied badly. A caution about water and the battery bay, a caution about the mount and the cable, and a caution about reachable openings all belong on the product or the packaging where the animal's owner will see them. Ask for the artwork version and confirm that the wording matches the file set.
GPSR checklist: documents and confirmations
GPSR table: items, evidence and owner
| Line | What to confirm | Document to request | Typical gap |
|---|---|---|---|
| Responsible party | Who is the manufacturer and who is the importer | Responsibility map | Party not named on the product |
| Market route | Which market each sales route serves | Route list | Route assumed without a record |
| Technical file | Version matching the shipped revision | Technical file | File issued for the prototype |
| Risk assessment | Hazards linked to the design | Risk assessment | Assessment without the test links |
| Test reports | Reports supporting each claim | Report set | Claim without a supporting report |
| Product labelling | Identity, power, party, markings | Artwork version | Artwork changed after the file |
| Warnings | Precautions for use and battery | Warning text sheet | Warning copied from another product |
| Packaging labelling | Markings on the box and carton | Pack specification | Carton label not confirmed |
| Listing wording | Claims match the file set | Final listing text | Claim added after the file |
Boundary: a checklist is not the file
A completed checklist records that a question was asked and answered. It does not prove the production article matches the approved sample, and it does not create the file it refers to.
Checklist ≠ technical file. The checklist tracks the files; the file holds the assessment.
Checklist ≠ label compliance. Confirming the checklist does not confirm the artwork on the shipped carton.
Checklist ≠ the product's safety case. The enclosure, the guard gap and the battery-bay seal carry the structural claims.
Checklist ≠ a one-time act. The parties, the route and the artwork all change, and the checklist should be re-issued.
Records that carry the claim
Ask for the responsibility map and the technical file version for the exact model and revision. Ask for the labelling and warning artwork version and the pack specification that goes with it. Ask who owns each document and what event triggers a review. Keep the checklist with the purchase order and reference it at sample approval and pre-shipment inspection, and record any line that cannot be answered as open with an owner and a date rather than leaving it blank.
Five questions to put to the supplier
- Which party is named as the manufacturer, and which as the importer or responsible person?
- Which market does each sales route serve, and is that recorded?
- Does the technical file version match the shipped revision?
- Which warnings appear on the product and packaging, and where are they stated?
- What triggers a review of the file and the artwork, and who approves it?
Where this sits next
The mandatory regimes that sit beside this checklist are in CE, FCC and UKCA: Documents to Request, Not Assumptions. The battery-specific files are in IEC 62133 and the EU Battery Law: What Buyers Ask. The channel-level preparation is in FBA and Offline Retail: A Channel Launch Checklist, and the listing-structure counterpart is in Amazon Pet Category: Listing Structure Buyers Amazon Pet Category: Listing Structure Buyers Should Knowugh [contact and we will show you which fields are missing.
Filed under the Pawluno pet-comfort programme. Illustrative specifications; confirm chew, clamp and battery-bay tests with the supplier.