Short answer: Shopify metafields are a good way to show passport information, such as composition, care and origin, on your product pages. On their own, they are not a Digital Product Passport. A passport also needs a data carrier on the product, long-term availability, access rights and supplier evidence. Most Shopify brands use a hybrid: a DPP platform holds the passport, and Shopify displays it.

We make Portia, which pushes passport data to Shopify, so we have an interest here. Shopify facts on this page come from Shopify’s own Help Center, read on 28 October 2026. For other tools, see all our comparisons and buyer’s guides.

What Shopify metafields handle well

Shopify describes metafields as a way to “extend an existing platform data model, such as products, customers, and orders with your own custom data”, and its own example is adding care instructions to apparel products (Shopify Help Center: Metafields). For passport-style information, that gives you a lot:

• Structured product fields. Text, numbers, measurements, dates, URLs, files, JSON and references to other products or metaobjects (metafield content types).
• Basic rules per field. Text fields can have minimum and maximum lengths and regular-expression rules, single-line text can be limited to preset choices, and URL fields can be limited to specific domains.
• Files. A file metafield can hold, for example, a PDF up to 20 MB, such as a care guide.
• Display in your theme. Metafields can be connected to theme settings, so the information appears on the product page next to the price and the Add to cart button.

For a brand that wants to show composition, care and origin to shoppers, that is a solid start, and you may already be using it.

What a passport needs that Shopify alone doesn’t give you

The Ecodesign Regulation (ESPR) sets the rules that every passport will have to meet once the textile delegated act applies. Compared with metafields on a product page, five pieces are missing.

1. Validation across the whole passport

Metafield rules check one field at a time: a length, a pattern, a preset choice. A passport has to be “accurate, complete and up to date” (ESPR Article 9(1)). That means checking the passport as a whole: are all required fields filled in, do the fibre percentages add up, and is there a certificate behind every claim?

2. Version history

When you overwrite a metafield, your product page shows the new value. If you need to show what the passport said for an earlier batch, or when a material changed, you need to keep that history somewhere else.

3. A stable link from the label

A passport must be connected through a data carrier, such as a QR code, to “a persistent unique product identifier” (Article 10(1)(a)), and must stay available even after an insolvency or if the company stops trading (Article 11(e)). A QR code that points to a product page depends on that page: if a product is archived, its URL changes or the store closes, the code can break.

4. Access levels

ESPR lets the product-specific rules decide which actors see which data, and who may create or update it (Article 9(2)(f) and (g)). Customers, repairers, recyclers and authorities are to get access “based on their respective access rights” (Article 11(b)). Shopify is built to show product data to shoppers, not to give each of those groups its own level of access.

5. Supplier evidence

Most passport data, such as materials, origin and certificates, comes from your suppliers, not from your store. Metafields store the result. They don’t collect data from factories or keep their certificates with it.

Shopify metafields vs a DPP platform: side by side

	Shopify metafields alone	DPP platform with Shopify (e.g. Portia)
Best for	Showing extra product information in your store	Publishing passports and showing them in your store
Where the data lives	In your Shopify store	In the DPP platform; Shopify receives a copy for display
Field rules	Per field: length, pattern, preset choices, URL domains	Depends on the platform; ask how it checks a whole passport
Data carrier on the product	Not included; a QR code would point to your product page	Portia: passports reached via QR codes
Passport level	Usually one product page per product	Portia: you choose style, batch or individual item
Supplier data and certificates	Entered by your team	Portia: tier-1 suppliers log in, enter data and upload certificates
Languages	Depends on your store setup	Portia: English, Swedish, German and Dutch, with more languages coming
Connection to Shopify	Native	Portia: one-way integration that pushes passport data to Shopify
Pricing model	Included in your Shopify plan	Portia: pricing on request (book a demo)

The hybrid model: the platform is the source, Shopify displays it

For most Shopify fashion brands, the practical setup is a hybrid:

1. Create and maintain the passport data in a DPP platform. That is where product, material and supplier data, and the certificates behind it, are kept.
2. Publish the passport behind a QR code on the label or hangtag, so it works in a shop, at home or at a recycler, not only in your store.
3. Send the passport data to Shopify for display on the product page.
4. Update in one place. Changes are made in the platform and sent to Shopify again, so the two don’t drift apart.

This is how Portia works with Shopify. Portia’s integration is one-way: Portia pushes passport data to your Shopify store, and data is not synced back from Shopify into Portia. Portia is not a listed Shopify App Store app; it connects through its own integration, and custom integrations are available on request. The steps are on our Shopify Digital Product Passport page and in connecting Portia to your Shopify store.

Decision checklist: are metafields enough for you?

Answer yes or no:

1. Do you only need to show product information in your own store, with no passports planned for the next year?
2. Is one person responsible for entering the data, with no supplier input needed?
3. Can you prove every material, origin and certificate claim from files you already hold?
4. Are you fine with a QR code that depends on your product page staying online at the same address?
5. Is one current version of the data enough, with no need to show what earlier batches contained?

If you answered yes to all five, metafields are probably enough for now. If you answered no to two or more, look at a DPP platform that sends its data to Shopify. Our buyer’s guide to DPP software has 25 questions to ask vendors, and the textile DPP data checklist shows which fields a passport is expected to hold.

When Portia is not the right fit

• You need two-way sync, for example orders or inventory flowing from Shopify back into Portia. The integration is one-way.
• You want a one-click Shopify App Store install. Portia is not a listed App Store app.
• You need NFC or RFID tags. Portia passports are reached through QR codes.
• You need environmental impact calculated in-house. Impact data is imported from partners or uploaded into Portia, not calculated there.
• You only want to show care and composition in your store. Then metafields alone may be all you need.

Sources and further reading

Last verified: 28 October 2026.

• Shopify Help Center: Metafields
• Shopify Help Center: Metafield content types and values
• Regulation (EU) 2024/1781 (ESPR), EUR-Lex
• European Commission: Textile apparel and the Digital Product Passport

More from Portia:

• Compare DPP and PLM software
• Shopify Digital Product Passport: how to add DPPs to your store
• Digital Product Passport software for small fashion brands
• ESPR Textile DPP Tracker

Frequently asked questions

Can I create a Digital Product Passport with Shopify metafields?

You can display passport information with metafields, such as composition, care and origin. A passport also needs a data carrier on the product, long-term availability, access rights and supplier evidence, which Shopify alone is not built to provide. Most brands keep the passport in a DPP platform and send the data to Shopify.

What are Shopify metafields good for in a passport setup?

Showing structured product information on your product pages. Metafields support many content types, basic rules per field such as lengths, patterns and preset choices, and files such as PDFs up to 20 MB, and they can be connected to your theme.

Do I still need a QR code if the passport data is on my Shopify product page?

Yes, once textile passport rules apply. ESPR requires a data carrier connected to a persistent unique product identifier, and the Commission expects textile passports to be reachable through a data carrier on the product itself. Portia passports are reached through QR codes.

Does Portia replace Shopify?

No. Portia is where you create and maintain product, supplier and passport data, and Shopify stays your store. Portia’s one-way integration pushes passport data to Shopify for display.

Does Portia sync data back from Shopify?

No. The integration is one-way, from Portia to Shopify. Portia is not a listed Shopify App Store app; custom integrations are available on request.

When do Shopify fashion brands need Digital Product Passports?

There is no legal date for textiles yet. The Commission plans to adopt the textile delegated act in Q4 2027, and it can apply no earlier than 18 months after entering into force, so mid-to-late 2029 at the earliest. That is our estimate; see the ESPR Textile DPP Tracker.

See your passport data in your own Shopify store

Pricing is on request. Book a short demo and we’ll show you how passport data moves from Portia to Shopify.