Shopify Product Metafields for Apparel Compliance: A Practical Guide
Metafields let you store material, supplier, origin and document references as structured data on each product, instead of burying them in the description. Structured fields can be filtered, exported, checked and reused in your theme.
Why metafields rather than description text
Text in a description is hard to validate and impossible to filter. A metafield has a defined type, can be required in your process, appears in exports, and can be shown in the theme wherever you choose.
Suggested structure
The table is a starting point. Rename and trim it to fit your products. Which fields you need depends on your markets and product types.
| Field (namespace.key) | Shopify type | Level | Example | Purpose |
|---|---|---|---|---|
| compliance.fiber_content | Multi-line text, or a list of metaobject references | Product | Cotton 95%, Elastane 5% | Label-consistent composition |
| compliance.country_of_origin | Single-line text | Product | Made in Portugal | Origin statement |
| compliance.company_identity | Single-line text | Product | Company name or RN | Who is responsible on the label |
| compliance.care_instructions | Multi-line text | Product | Machine wash cold | Matches the care label |
| compliance.supplier | Metaobject reference | Product | Supplier A | Link to supplier record |
| compliance.factory | Single-line text | Product | Factory name, city | Traceability |
| compliance.fabric_id | Single-line text | Product | FAB-0012 | Link to fabric master list |
| compliance.doc_ref | Single-line text or file | Product | TR-2026-114 | Reference to test or spec document |
| compliance.doc_expiry | Date | Product | 2027-03-31 | Triggers review |
| compliance.last_reviewed | Date | Product | 2026-09-14 | Audit trail |
| compliance.claim_evidence | Single-line text | Product | GOTS cert no. | Evidence for an environmental claim, if one is made |
Product level or variant level?
Fiber content and origin normally sit at product level, because they describe the garment. Use variant-level metafields only where something really differs between variants, for example different fabrics in different colourways. See auditing variants.
Setting them up
- In Shopify admin, go to Settings > Custom data > Products.
- Add a definition for each field, with a name, namespace and key, and the type.
- Pin the most important definitions so they show at the top of the product page.
- Fill the values by bulk edit, CSV import or an app, then reuse them in the theme.
Using metaobjects for suppliers and fabrics
Suppliers and fabrics are reused across many products. A metaobject definition for each lets you edit a supplier once and have every product reflect it. This is the data-model version of the fabric master list.
Showing data to customers
Only some fields should be public. Fiber content, origin and care normally belong on the product page. Supplier names, document numbers and internal review dates usually stay internal. Check what your theme exposes before you publish.
EU readiness (preliminary)
If you sell in the EU, similar fields may later feed a Digital Product Passport. The textile-specific requirements are not final, so treat extra fields as optional preparation. See DPP data preparation.
Frequently asked questions
Do metafields make a store compliant? No. They store data. The data still has to be correct and match the label.
Can I show metafields without a developer? Many themes allow dynamic sources in the theme editor. Otherwise a small Liquid edit is needed.
Are metafields included in product exports? Yes, metafields can be included in CSV exports and imports, depending on how you export.
Related guides
- Manage fabric composition at scale
- Compliance matrix in Excel
- Turn supplier PDFs into structured data
Sources: Shopify Help Center, Metafields and metaobjects ยท FTC, Threading Your Way Through the Labeling Requirements
Not legal advice. Check requirements for your products and markets.