EU product safety fields

GPSR Product Safety Field Audit

The EU General Product Safety Regulation requires manufacturer details, an EU responsible person, and warnings on product pages. Scan a product export locally and see which products still have empty GPSR fields.

Local browser scanSafe fixes onlyShopify-focused checks

Browser-side scan

Drop a product export with GPSR columns

-

No CSV selected

No CSV selectedUpload a product export carrying GPSR columns such as manufacturer, EU responsible person, and safety warnings to audit completeness per product. Files are read locally and nothing is uploaded.
Private by default. Your Shopify product or GPSR metafield CSV data stays in this browser session. The export applies only safe deterministic changes and leaves manual-review items in the findings list.

Use this GPSR field audit when your store sells physical products into the EU and the GPSR data lives in product metafields. Upload a product export that includes your GPSR columns — manufacturer name and address, EU responsible person, and safety or warning information; the audit groups rows by product and reports which products have no value in each field group, so gaps are visible before a marketplace, a competitor's lawyer, or a market surveillance authority finds them. The export is a per-product worksheet with a completeness status and review note. The tool checks field completeness in your browser — it does not judge whether the content itself satisfies GPSR, and it is not legal advice.

Import blockers

Common causes this scan checks

  • GPSR metafields were added for new products but never backfilled for the existing catalog.
  • A migration or app change dropped metafield columns without anyone noticing.
  • Products from non-EU manufacturers are missing the EU responsible person entry.
  • Warning texts exist for some categories but were never entered for others that need them.

Workflow

How to use the cleaned CSV

  1. Export products from Shopify including your GPSR metafield columns and upload the CSV.
  2. Review products missing manufacturer details or the EU responsible person first — both are required for most goods.
  3. Fill the missing metafield values in a spreadsheet or in Shopify admin.
  4. Re-import the completed data and re-run the audit until every product shows complete.

Auto-fix policy

What the export can safely change

  • Detects GPSR columns by name in English and German, including metafield export headers.
  • Groups variant rows by handle so each product is audited once.
  • Separates required gaps (manufacturer, EU responsible person) from category-dependent warnings.
  • Exports a per-product worksheet with a completeness status instead of changing any value.

CSV example

CSV example: GPSR safety field completeness

The audit shows the toy carrying all three GPSR field groups while the candle has none, so the worksheet flags exactly which product needs manufacturer and responsible-person data before the next EU sale.

Before
Handle,Title,GPSR Manufacturer,EU Responsible Person,Safety Warnings
wood-toy,Wood Toy,Toymaker GmbH,EU Rep Ltd,Choking hazard
candle,Scented Candle,,,
After
Handle,Title,Manufacturer info,EU responsible person,Safety and warnings,GPSR status,Review note,Source row
wood-toy,Wood Toy,Present,Present,Present,Complete,GPSR fields present for this product,2
candle,Scented Candle,Missing,Missing,Missing,Missing required info,Fill the missing manufacturer or EU responsible person metafields before selling into the EU,3

FAQ

Shopify CSV questions

Which columns does the audit look for?

Any column whose name mentions manufacturer, responsible person, safety, warning, or GPSR — including German names like Hersteller and the long metafield headers Shopify exports generate.

Does a complete status mean my store is GPSR compliant?

No. The audit proves the fields are filled, not that their content meets the regulation. Whether the named person qualifies and the warnings are sufficient remains a merchant and legal review.

My export has no GPSR columns at all - what now?

Store the data in product metafields first (manufacturer, EU responsible person, warnings), include those metafield columns in the export, and run the audit again.

Is my catalog data uploaded during the audit?

No. The CSV is read locally in your browser and nothing is stored or transmitted.

Related tools

Feedback

How is this tool working for you?

Found a bug, a false alarm, or a missing check? Tell me — a human reads every note.