Agency resource
Shopify EU readiness field map for agencies
A practical field map for agencies auditing Shopify stores that sell physical products into the EU: GPSR product safety data, Responsible Person coverage, product identifiers, warnings, safety content, HS codes, country of origin, storefront display, and EU order review.
Download the neutral templates
Field map
Use this table to decide what to inspect, what evidence to collect, and what handoff note to leave for the client. It is not a legal opinion, customs classification, or certification checklist.
| Area | Field / operational question | Why agencies check it | Where to inspect in Shopify | Evidence or input to collect | Example value | Output / handoff note | Source note |
|---|---|---|---|---|---|---|---|
| Product reference | Product ID, handle, and SKU | Agencies need stable identifiers to match Shopify exports, supplier records, safety files, and client review notes. | Products export, product admin, variant admin, inventory systems. | Shopify product ID or handle, SKU, vendor, product type. | handle: trailbeacon-led-lantern-pro; SKU: NS-LED-058-01 | Keep one row per product or variant, depending on how the client stores compliance and customs data. | Operational mapping field. |
| Manufacturer | Manufacturer name, postal address, and electronic address | Online product offers may need manufacturer identity and contact information for EU product-safety review. | Supplier records, vendor data, product metafields, PIM, ERP, purchase records. | Legal name, postal address, email or other electronic address. | Evergreen Trail Goods, 500 Lake Union Ave N, Seattle, WA 98109, safety@example.com | Flag products where vendor names are not legal manufacturer records. | GPSR / online offer review. |
| Responsible Person | EU Responsible Person coverage | Non-EU manufacturers may require an EU-based Responsible Person workflow before products are offered to EU consumers. | Client compliance files, RP service contracts, product metafields, supplier onboarding records. | RP legal name, EU address, electronic contact, covered products/categories/markets, appointment evidence. | Rheinland Consumer Safety GmbH, Schanzenstrasse 36, 51063 Cologne, Germany | Mark whether coverage is present, missing, expired, category-limited, or market-limited. | GPSR / Responsible Person review. |
| Product grouping | Product category or risk grouping | Agencies need a practical way to prioritize products with similar warning, safety, RP, and document needs. | Product type, collection, tags, taxonomy category, supplier category. | Client-approved category label and any category-specific safety notes. | LED lanterns; camping cookware; children's accessories. | Use categories to group review work; do not treat category labels as legal classifications. | Operational prioritization field. |
| Product identifiers | Identifier type and value | The product page, warehouse item, supplier record, and safety documentation should be traceable to the same product. | Variant SKU, barcode, product metafields, supplier spec sheet, packaging artwork. | Model, type, batch, lot, serial number, SKU, or other traceable identifier. | Model: TBL-PRO-2026 | Document which identifier type the client uses and where it appears. | GPSR / traceability review. |
| Product markings | CE-marked flag where relevant | Some products require category-specific conformity evidence; agencies should not assume CE marking applies to every product. | Supplier declaration, technical file, product documentation, packaging images. | Client-provided CE status and supporting document reference. | CE-marked: yes; declaration file: DOC-LED-058 | Record status as client-provided evidence, not agency certification. | Category-specific conformity review. |
| Product restrictions | Age restriction where relevant | Age limits can affect warnings, storefront display, market review, and category-specific safety workflows. | Product specification, packaging, supplier compliance file, product metafields. | Age range or restriction statement approved by the client. | Not for children under 3 years. | Keep exact client-approved wording for storefront and support handoff. | Product safety review. |
| Safety content | Safety instructions | Instructions can be required for customers to understand safe product use and limitations. | Product manuals, packaging text, product metafields, supplier documentation. | Approved safety instruction text and source language. | Charge only with a certified USB-C power source. Keep dry during operation. | Flag placeholder text, supplier-only notes, or unreviewed AI translations. | GPSR / product-safety information review. |
| Safety content | Warnings | Warnings often need product/category-specific review before storefront publication. | Packaging artwork, manuals, product metafields, supplier safety sheets. | Approved warning text and source document. | Do not cover the lantern while operating. Stop use if the battery housing becomes hot. | Separate consumer-facing warnings from internal review notes. | GPSR / product-safety information review. |
| Language coverage | Market-language safety content | EU-facing safety content may need to be understandable to consumers in destination markets. | Shopify Markets, translations app, product metafields, localization workflow. | Language list, translated text, reviewer, approval date. | DE, FR, ES, NL reviewed; IT pending. | Track translation status separately from source-language completion. | Language and market-readiness review. |
| Storefront display | Product safety disclosure placement | Collecting data is not enough; agencies need to confirm what appears on the product page and in which markets. | Theme template, theme app blocks, product metafields, storefront preview by market/locale. | Screenshot or preview URL showing manufacturer, RP, identifier, instructions, and warnings where relevant. | Product safety accordion visible on EU product template. | Capture screenshots for client acceptance and future audit trail. | Online offer and storefront implementation review. |
| Customs readiness | HS code | Missing or inconsistent HS codes can delay downstream shipping, customs, and duty workflows. | Variant customs information, shipping app, ERP/PIM, broker classification records. | HS code and source of classification decision. | 851310 | Record broker/supplier source; do not invent classifications during a marketing-site audit. | Customs classification review. |
| Customs readiness | Country of origin | Origin data can affect customs documentation and import treatment. | Variant customs information, supplier declaration, ERP/PIM, broker records. | ISO country code or country name and supporting supplier/broker record. | CN | Flag unknown, mixed, or supplier-unverified origin values. | Customs origin review. |
| Order review | EU-bound order risk review | A catalog can look mostly ready while specific EU orders contain products with unresolved safety or customs gaps. | Orders, shipping country, line items, product readiness tracker, fulfillment workflow. | Order country, line items, missing fields, fulfillment decision, reviewer. | FR order blocked until missing RP coverage is resolved. | Define what should warn, hold, or block fulfillment in the client's operating process. | Operational enforcement field. |
| Audit handoff | Review status, owner, and evidence trail | Agencies need to hand clients a durable record of what was reviewed, fixed, deferred, or escalated. | Project tracker, product notes, audit exports, compliance files, client approval records. | Reviewer, date, status, evidence links, unresolved decisions. | Owner: client ops; status: pending RP contract; evidence: supplier email. | Use status values consistently across the client engagement. | Agency handoff field. |
How agencies can use this in a client engagement
- Start with a Shopify product export and a list of EU target markets.
- Map each product to its manufacturer, Responsible Person status, identifier status, and safety content status.
- Separate source-language completion from destination-market translation review.
- Confirm where customer-facing safety information appears on EU storefront product pages.
- Flag HS code, country-of-origin, and EU-bound order review gaps for the client's broker or operations team.
- Hand off unresolved items with owner, priority, evidence link, and next action.
Claim boundaries
This field map is an operational planning resource, not legal advice. Agencies should use it to structure discovery and handoff conversations with merchants, counsel, Responsible Person providers, customs brokers, and compliance experts where needed.
The field map does not guarantee compliance, certify products, replace a lawyer, replace a customs broker, replace a VAT filing service, calculate every EU customs duty, or act as a merchant's EU Responsible Person.
Official sources and references
Want to operationalize this inside Shopify?
This field map is published by SafeShelf. If a merchant wants to turn these checks into an ongoing Shopify workflow, SafeShelf can scan products, surface missing fields, support bulk review work, and monitor EU readiness gaps over time.