How to fill in Etsy's GPSR fields, field by field

Etsy's GPSR fields are not hard. They are just unexplained. You open a listing, find a compliance section asking for an "economic operator" and a "responsible person", and Etsy's help text tells you to enter your economic operator, which is not an answer.

So here is each field, what it is actually asking, and where the answer comes from. If your listings are already live and you have skipped these, that matters: incomplete compliance information can get a listing hidden from EU buyers, or shown to them with a warning that the product is missing required safety information. Neither is good for conversion.

First, the two levels

Etsy splits this in a way that catches people out. There are account-level details and listing-level details, and you need both.

Account level is where you register the operators themselves: your business as manufacturer, and whoever is acting as your EU Responsible Person. You enter each one once, in your shop settings, and it becomes available to attach to listings.

Listing level is where you attach those operators to a specific product, and add the things that vary per product: identifiers, warnings, age grading.

The consequence: registering your responsible person once does not make your listings compliant. Every listing still has to have them attached. Sellers who did the settings step in December 2024 and assumed they were finished are often still non-compliant today.

The manufacturer field

What it wants: your name or registered trade name or trademark, your postal address, and an electronic address (email or a contact URL).

What to put: your own details. If you make it, you are the manufacturer, even if you are one person at a kitchen table. See the technical file guide for why that definition catches makers.

If you buy in finished goods and resell them under someone else's brand, the manufacturer is that brand, not you, and you need their details from your supplier. Get them in writing. "I could not find it" is not a defence, and a supplier who will not give you manufacturer details is a supplier with a problem.

Address, honestly: this becomes publicly visible on your listings, which sellers working from home hate. A registered business address, a virtual office, or an accountant's address that you are entitled to use are the usual answers. It has to be an address where you can actually be reached.

The EU Responsible Person field

What it wants: the name, postal address and electronic address of an economic operator established in the EU who is responsible for your product under Article 16.

What to put: the details of whoever holds that role for you, exactly as given to you by them. If you are a UK or US seller shipping direct to consumers, that is almost certainly an authorised representative you have appointed under a written mandate. Our guide to whether you need one walks the decision tree.

Three ways sellers get this wrong:

Entering their own address. If you are not established in the EU, your address does not satisfy Article 16, and putting it here is a declaration that it does.
Entering the buyer's country. The responsible person is one fixed operator, not a different one per destination. One appointment covers the whole EU.
Entering a shipping agent or a courier. A carrier moving your parcel is not your economic operator.

If you genuinely do not ship to the EU and never will, the correct move is not to invent an answer here. It is to exclude EU destinations in your shipping profiles, and Northern Ireland with them, since NI follows EU product rules.

The product identifier

What it wants: something that identifies this specific product and, ideally, the batch it came from. Type or model number, plus a batch, lot or serial number where relevant.

What to put: whatever scheme you use, as long as you actually use it. Small makers often have none, so invent one now and keep it simple:

SS-CH45-2026-03 = sterling silver, 45cm chain, made March 2026.

The point of the identifier is a recall you will hopefully never have. If a clasp supplier turns out to have shipped you a bad batch, the difference between "I need to contact everyone who ever bought this necklace" and "I need to contact the eleven people who bought the March batch" is that code.

Whatever you enter here should match what is on your labelling and in your technical file. Three different identifiers for one product is worse than none.

Safety information and warnings

What it wants: any warnings or safety instructions the product needs.

What to put: the warnings that came out of your risk assessment. This is the field that reveals whether you have actually done one, because if you have, the answer is already written down. From the necklace example in the technical file guide, the risk rows produce a warning like:

Small parts. Keep away from children under 3. Not suitable for children under 14. Remove before sleeping or swimming.

Two rules. Do not invent warnings to look thorough: a warning that does not match a real hazard makes your documentation inconsistent. And do not copy a competitor's: their product is not yours, and their risk assessment, if it exists, was done on different materials.

Language matters here. Article 19 requires warnings in a language easily understood by consumers in the market you are selling to. English only, on a listing selling into Italy, is a weak position. Keep warnings short enough that translating them into your top few EU markets is trivial.

Age grading and category questions

Etsy asks whether the item is intended for children, and this is not a formality. Saying a product is for children moves it into a different regulatory world: the Toy Safety Directive, CE marking, EN 71 standards, a Declaration of Conformity. Saying it is not, and then marketing it with photographs of children wearing it, is the kind of inconsistency that market surveillance notices.

Pick the honest answer, then make your listing photos, title and tags agree with it.

Where all these answers come from

Notice what the fields have in common. Manufacturer details, responsible person, identifier, warnings: all four already exist in your technical file and labelling sheet, if you have them. Filling in Etsy's form is meant to be a transcription job, not a research job.

That is the actual reason sellers find this section painful. They are being asked to output documentation they never created, one listing at a time, inventing it as they go and inevitably contradicting themselves across products.

Do the documents once and the fields fill themselves. That is what GPSRHub generates: the technical file, the risk assessment, the labelling sheet with your identifiers and warnings, and a Declaration of Conformity where the product needs one. The compliance checker is ten questions, about two minutes, and it tells you which of those you are missing. Free.

A sensible order of work

Sort your responsible person first. Every listing needs it and you cannot enter it until you have appointed someone.
Register both operators at account level, once.
Write your identifiers and warnings per product line, not per listing. Most shops have far fewer distinct products than listings.
Work through listings by product line, so you are copying the same block repeatedly rather than thinking afresh each time.
Spot-check from a buyer's view in an EU country afterwards, to confirm the information actually renders on the live listing.

Quick FAQ

Do I have to fill these in if I do not sell to the EU? No, but you should exclude EU and Northern Ireland destinations in your shipping settings so the question does not arise.

What happens if I leave them blank? Etsy can hide the listing from EU buyers or display a notice to them that required safety information is missing.

Can I bulk edit these across listings? Account-level operators are entered once and reused. Per-listing information still has to be applied to each listing, though working by product line makes it fast.

Is Etsy my responsible person? No. Etsy provides the fields. The economic operator has to be someone you have appointed.

Does filling in the fields make me compliant? No. The fields are a declaration about documents that are supposed to exist. Article 9(2) still requires the risk analysis and technical documentation behind them.