GPSR CSV Template: All 17 Columns and Example Rows (2026)

The EUSellKit GPSR CSV template has 17 columns: one row per SKU, product facts in that row, and optional manufacturer/RP cells that inherit your saved profile when empty. Download the template from your catalogue, replace the examples with your own product data, and inspect missing/review results after import. The check evaluates what you enter; it does not inspect the live listing or certify a product.

Is this an official EU GPSR template?

No. It is EUSellKit's catalogue import format, not a form prescribed by the EU. The GPSR has applied since 13 December 2024; “2026” is this guide's year. Regulation (EU) 2023/988 sets the legal obligations, including online-offer information in Article 19. A populated CSV is not the same thing as fulfilling them.

The import header is fixed. Keep its English column names in every language version of your file.

What does each CSV column mean?

Use the exact names below and separate multiple values within a cell with |. Do not translate category or warning codes.

Column	What to enter
sku	Stable product identifier, such as TOTE-NAT-01; preserve leading zeros
title	Product name that lets you recognise the row
category	One supported category code, such as bag_wallet or candle
materials	Material names, such as cotton or soy wax|cotton wick|glass
markets	EU market codes, such as DE|FR; empty uses profile defaults
intended_use	Specific intended use, not just “general use”
warnings	Relevant standard warning codes separated by |; empty selects none
known_hazards	Known hazards separated by |; empty is not a safety finding
packaging_materials	Packaging materials, such as paper or cardboard
packaging_weight_g	Packaging weight in grams, as a number
source_url	Optional valid product URL for reference; it does not trigger a live-listing audit
manufacturer_name	Manufacturer's name; empty inherits the profile value
manufacturer_address	Manufacturer's postal address; empty inherits the profile value
manufacturer_email	Manufacturer's email; empty inherits the profile value
rp_name	Actual EU Responsible Person's name; empty inherits the profile value
rp_address	RP's postal address; empty inherits the profile value
rp_email	RP's email; empty inherits the profile value

Supported category codes are home_accessory, candle, stationery, bag_wallet, decor, pet_accessory, household, apparel_accessory, textile_home, hardware_fasteners, footwear, jewelry, furniture, garden, craft_supplies and sports_leisure.

Support is limited to low-risk, non-electrical products within those categories. Toys, electronics, batteries, cosmetics, food, food-contact products, children's products, PPE, medical products and machinery are excluded. A category code does not prove that your product belongs within the supported scope; do not use household for a food-contact utensil or sports_leisure for protective equipment.

What do valid example rows look like?

These two examples demonstrate syntax, not completed compliance assessments. Save your real manufacturer/RP profile first: the six contact cells are deliberately empty so they inherit it. Replace all product facts and review the risks before using the rows.

sku,title,category,materials,markets,intended_use,warnings,known_hazards,packaging_materials,packaging_weight_g,source_url,manufacturer_name,manufacturer_address,manufacturer_email,rp_name,rp_address,rp_email
TOTE-NAT-01,"Cotton tote bag, natural",bag_wallet,cotton,DE|FR|NL,Carrying everyday items such as groceries and books,,,paper,15,,,,,,,
CNDL-LAV-200,Lavender soy candle 200 g,candle,soy wax|cotton wick|glass,DE|AT,Decorative scented candle for indoor use,candle_unattended|candle_children_pets|candle_flammables,open flame|hot container,cardboard,85,,,,,,,

The comma in the tote title is inside double quotes. Keep that quoting when saving CSV. The tote has no selected warnings and no entered hazards; neither blank means the product has been assessed as safe. The candle contains three real warning codes: candle_unattended, candle_children_pets and candle_flammables. They are examples, not an exhaustive warning set for every candle.

How do shared profiles and row overrides work?

Each empty contact cell falls back to the corresponding saved profile field. Empty markets uses the profile's default markets. If one SKU has another manufacturer, supply all three manufacturer cells; otherwise a different company name could be combined with the default address or email. Use the same care with RP overrides.

The profile records an existing responsible person; it does not appoint one or verify their mandate. Confirm product coverage separately, using our EU Responsible Person guide. Changing the profile triggers a catalogue recheck, so inspect the records that inherit those values.

What happens when you import the CSV?

The importer reports new, updated, unchanged and rejected rows, then provides per-SKU results for stored records. Review these results instead of assuming every row succeeded. Use files no larger than 1 MB, retain stable SKUs for updates, and keep identifiers as text in your spreadsheet editor.

Missing SKUs and categories outside the supported set can cause rejection. Other invalid inputs can produce issues and a null score. An unknown warning code needs correction; it is not a free-text safety instruction. Empty warnings remain unselected, with relevant checks still requiring review or missing-data resolution.

What does the GPSR check prove, and what does it leave open?

It shows how the entered data performs against the current rules, not whether the actual product or offer complies. missing identifies absent information; review identifies matters you must examine. An ok result for an input-based check is not verification of the underlying real-world fact.

It does not inspect the physical product, verify the manufacturer's identity or RP authority, test safety, confirm labels, or prove that the risk assessment and technical file exist. Providing source_url does not change this. Live-offer visibility, actual warning languages and supporting documentation remain human review tasks. The score is not certification, legal approval or a promise that a marketplace will accept the listing.

Can you upload the exported CSV directly to a marketplace?

Treat it as prepared source data that needs mapping to the marketplace's current format. Seller Pro exports GPSR fields, warnings by available language, scores and gaps. Review missing language coverage and arrange any needed translations; a selected market does not guarantee all its required text is included.

Amazon documents its own safety-information spreadsheet workflow in official bulk-upload guidance. Its columns are not the 17 import columns above. Follow our Amazon bulk-upload guide for verified scope and our large-catalogue workflow for organising batches.

What do sellers ask about this CSV template?

How many SKUs can I check free?

The catalogue allows 5 SKUs free. Seller Pro is €19/month, with up to 2,000 SKUs and bulk CSV export.

Does leaving warnings blank select safe defaults?

No. No warnings are automatically selected. Assess the product and enter applicable codes deliberately.

Does importing a product URL check the live listing?

No. The catalogue check evaluates entered data. Review the actual published offer separately.

This guide is general information, not legal advice.