Skip to content
Open Workspace

Your Shopify store is the starting point, not the finish line.

70%+solved before your input.

5 questions, not 22 fields  •  3 steps to live  •  1 product to start

Install on ShopifyTextiles is also on Shopify. Build your first passport free works for every product.See a live passport

In current textile testing, richer existing product records reached about 71% of scoped decisions settled before the merchant answered anything. How we measured it

How ActivateDigital passports work in Shopify

01 Connect

20+ ways to connect your data

Shopify is one button.

02 Build

You answer only what only you can know

Each value keeps its source.

03 {Activate}

1 product is enough to start

Live at its GS1 Digital Link.

From your store to a live passport, in three steps

Connect, Build, Activate. The same three steps create every ActivateDigital product identity. Your Shopify store is the quickest way in.

  1. 01 ConnectBring the store you already runProducts and variants over the Admin API, or a CSV export. Add a spec sheet, a certificate or a care label photo if you have one. Nothing is retyped.
  2. 02 BuildOur engine builds the passportEvidence is matched to the right product and resolved by the best approved method. You review, approve and add the finishing touches.
  3. 03 ActivateLive in one clickClick Print and the passport goes live on dppcode.org at its GS1 Digital Link, with the Product Pack for buyers, marketplaces and partners.
Put it to work

The passport may be all you need, and that's a finished job. If you want more from the same identity, it can also carry protection and measurement, both in beta.

The engine

A passport engine, not another compliance form.

The engine does the research. You confirm the facts. Every textile passport runs through the same machine, and this is what it brings to each one.

  • 22dedicated resolvers, one for every attribute in the textile model
  • 12governed calculation methods, Ecobalyse among them
  • 24official sources in its register, from EUR-Lex to HMRC and GS1
  • 9evidence routes tried in a fixed order, with your input near the end
  • 175plausibility rules checking its own answers
  • 4evidence states, so nothing has to be faked
  • 442decisions made across 10 test products before the merchant answered anything
  • 5,000+automated tests behind the engine

We resolve. We don't just autofill.

What a Shopify catalogue already answers

Shopify carries more of a passport than most merchants expect. These are the fields the engine reads first, and what it does with each one.

BarcodeA variant barcode is a candidate GTIN. We check whether it's a valid GTIN. A valid GTIN is the strongest starting point the engine can have.
SKUYour own product code. Useful for matching your records to each other, and never treated as a trade identifier.
VendorThe manufacturer, wholesaler or other vendor stored against the product. It may be the brand. We don't assume it is, and resolve it as a name.
Commodity codeShopify holds a harmonised system code on the inventory item. Many catalogues have it. Most merchants have forgotten it's there.
Country of originAlso on the inventory item. A useful declaration, and a declaration is what it stays until something supports it.
WeightA value with its unit beside it, which makes a Shopify weight usable without a further question.
MetafieldsWhere composition, care and supplier detail usually live once a store has grown past the default fields.
A denim jacket on a hanger with a hand holding a phone with a dark screen reading its white swing tag.
The scan is the end of the journeyBy the time anyone taps a tag, every value behind it has a source, a date and a reason it's there. That work starts in your Shopify catalogue. What happens when someone scans it

One tip before you connect. Get a GTIN.

A GTIN lets the engine resolve far more of the passport, and you'll need one soon anyway. A store without one still builds a passport. It just asks you more questions along the way.

  • With a GTINthe product's identity is settled first, and the attributes that hang off identity resolve from it rather than becoming questions.
  • The commonest faultan internal stock code sitting where a GTIN belongs. It's the first thing the engine checks. Check a GTIN
  • Questions are per product, not per varianta composition belongs to the product, so five sizes of one shirt are one question and five passports. Where a colour differs, it's asked for that colour. Model, variant and SKU facts

How the connection works

ActivateDigital reads the products and variants already in your store, over the Admin API. It's an integration with the store you have, not another place to keep product data.

  • Installed: add the app from the Shopify App Store and the store is read directly into the Workspace, where Connections shows when it was last read and lets you read it again, reconnect or disconnect.
  • Export: your products out of Shopify as a CSV or an Excel file, read the same way a connected catalogue would be.

The ActivateDigital DPP app is live on the Shopify App Store. Install it from the listing, approve what it asks to read, and the Workspace takes it from there. You can also start from an export today.

Textiles and batteries are in live beta. Other categories are in build and the Workspace says which.

Why this rather than a passport app you fill in

The difference is what happens to a value between your catalogue and the passport. Most tools move it. We keep asking where it came from.

  • Instead of import equals truthA catalogue field is evidenceEvery one of those fields was typed by somebody. That doesn't make it wrong. It makes it evidence with a source and a date, kept that way rather than promoted to fact on arrival.So the barcode box is checked rather than trusted, and a vendor name is resolved rather than assumed to be the brand.
  • Instead of last write winsWhen two sources disagree, both are keptA store label saying eighty per cent wool and a supplier declaration saying seventy-eight per cent recycled wool is the normal case. Neither is quietly overwritten.You decide, and the decision is recorded with what it was decided from.
  • Instead of a plausible numberWhat can't be proved is flaggedSome facts aren't in your catalogue, your documents or anything derivable from them. The engine flags those and asks you, rather than filling the gap.Better data later? Upload it and run the engine again. No filling gaps by hand.
  • Instead of one exportOne record, many destinationsWhat comes out is one governed record. The live passport and its GS1 Digital Link are one destination. The Product Pack for retailers and marketplaces is another.The record is also readable over the API with a key from your own account.

From Shopify data to a governed passport

You already have a starting point: the product information in your store and the evidence behind it. ActivateDigital uses that material to build the textile passport, then brings back the questions that need your knowledge.

In the current controlled textile test flow, initial product-specific questions averaged about five per product, with shared company identity handled separately. These are starting questions before answers, not a fixed limit; follow-ups can arise.

See how ActivateDigital builds a textile passport from existing data, including the supporting results and how they were counted.

The 22 fields are ActivateDigital's textile DPP readiness model, not a final statutory textile field list.

Start with the store you already have

One product is enough to see what your store already answers and what's left. Textiles and batteries are in live beta.

Install on ShopifyTextiles is also on Shopify. Build your first passport free works for every product.