The six fields GPSR asks for, and where they live in Shopify

GPSR Product Compliance organises product-safety information into six working groups: responsible person, manufacturer, product identifiers, safety warnings, instructions, and traceability. These groups make the review task manageable inside Shopify. They are not a substitute for determining which legal duties apply to a particular product or market.

The practical question is where this information lives. A Shopify product has a title, description, variants, media, tags, and standard identifiers. It does not have six dedicated GPSR fields. The app therefore keeps the reviewed values in product metafields and lets a theme-app block read them on the storefront.

Generated compliance text is a draft. A merchant reviews the source, edits the value where needed, and decides what is ready to publish.

One product, six working groups

The six groups have different shapes. Contact details need structured lines. Warnings may need several entries. Traceability can refer to a model, batch, serial number, or another identifier already used by the business.

Working group	Typical source in the catalogue	Storefront treatment
Responsible person	Supplier or market-contact records	Contact details when applicable
Manufacturer	Vendor and supplier records	Name and contact details
Product identifiers	SKU, barcode, model, or product records	The identifiers selected for the product
Safety warnings	Existing safety copy and product documents	Reviewed warning text
Instructions	Product instructions and supporting documents	Text or document links
Traceability	Batch, model, serial, or internal references	The reference used for that product

This is an application mapping, not a legal checklist. Some products need information outside these groups. Some fields may not apply. The person responsible for the catalogue decides what the final record contains.

Keep related values together

A dedicated namespace gives the integration one predictable boundary. The exact stored keys are an implementation detail, but the operating rule is stable: compliance values do not compete with the product description, tags, or vendor field.

The resulting workflow is easier to inspect:

• The app reads the catalogue data already available for the product.
• Draft values remain separate from merchant-approved values.
• Saving writes the reviewed compliance record to product metafields.
• The storefront block reads the saved record without rewriting it.
• The merchant controls whether and where the block appears in the theme.

Code that consumes a namespace can stay deliberately narrow:

{% assign compliance = product.metafields.appavio_compliance %}

{% if compliance.manufacturer.value != blank %}
  <p>{{ compliance.manufacturer.value }}</p>
{% endif %}

The guard matters. It prevents a missing value from becoming an empty label or an empty section on the product page.

Empty output is not useful output

The theme block should render a meaningful record or render nothing. A heading followed by blank rows makes the page look unfinished and can suggest that an empty field carries meaning.

Use three checks before a section appears:

1. The merchant has enabled the theme-app block.
2. The product has a saved value for the section.
3. The value is suitable for storefront display.

The conditional can be small because the review workflow has already done the hard work. In pseudocode, the storefront rule is enabled && reviewed && present.

Review remains a separate state

Saving data and completing a review are different actions. A product can contain compliance data while still needing a merchant decision. Keeping those states separate avoids a common automation error: treating the existence of generated text as proof that the product is complete.

The app’s useful states describe work, not legal conclusions. A record can be not started, incomplete, ready for review, or marked complete by the merchant. The software can point to missing values and changed source data. It cannot decide that every applicable obligation has been met.

A maintainable boundary

Metafields make the compliance record part of the product data rather than part of the article body or a private note. That gives the merchant a stable place to inspect, export, and update it. The theme block remains a presentation layer over that record.

The boundary is simple: source data informs a draft, review controls the write, and the theme controls display. GPSR Product Compliance supports that workflow. It does not certify a product or replace product-specific legal review.