Skip to content

WooCommerce

Digital Product Passports for WooCommerce

Start with the products and variations you already hold in WooCommerce. ActivateDigital reads them as evidence, establishes what it legitimately can, and is specific about the facts WooCommerce has nowhere to put.

Open the Workspace How the engine decides
Direct answer

ActivateDigital can use WooCommerce product data as the starting point for a governed Digital Product Passport record. Product fields and metadata are observations rather than proof, and WooCommerce core has no field at all for several things a passport needs. The source stays attached to every value, conflicting evidence is kept rather than overwritten, and a value that cannot be established stays unresolved.

Start with the catalogue you already have

WooCommerce products and their variations are read over the store's own REST API, page by page, the way the store reports them. Attributes, categories and custom fields come with them. Nothing is retyped.

What WooCommerce has no field for

This is the part a generic integration page will not tell you, and it is the part that decides how much work is left. WooCommerce core is a shop, not a product master, and several passport facts have no home in it.

Commodity codeWooCommerce core has no dedicated commodity-code field. Stores may hold one in custom or meta fields, in attributes, or in plugin-managed data, so ActivateDigital maps the observation it finds rather than assuming one universal key.
Country of originWooCommerce core has no dedicated country-of-origin field either. Stores may hold origin in custom or meta fields, in attributes or through an extension, and the source stays attached to the value when it is read.
CompositionThree possible homes and none of them governed: a custom field, a product attribute such as Material, or the description, which is prose.
BarcodeWooCommerce added global_unique_id in 9.2 for identifiers such as GTIN, UPC, EAN and ISBN. Older stores may still hold an equivalent identifier in plugin or custom data.
BrandBrands became part of WooCommerce core in 9.6, and there is no vendor field. Older stores may still carry brand information through extensions or custom taxonomies.
Product typeSimple or variable, which describes the listing rather than the garment. Your categories are the nearest thing, under names you chose.
WeightA number with no unit beside it. The unit is a single store setting, so a weight read on its own cannot be used until the unit is stated.

None of that is a fault in WooCommerce. It is what a store is for. It does mean a WooCommerce catalogue starts a passport further back than a platform that carries origin and commodity codes natively, and it is better to know that at the start than at the end.

What a custom field can and cannot settle

A custom field whose key you chose is still evidence. It is read, and the key it came from is recorded with it. What it is not is a governed field that can be relied on across stores, because the next store calls it something else. So a value from a custom field carries its origin and is held to the same test as any other observation.

Which of your existing product data a passport can use

Variations and product identity

A variable product and its variations are read as what they are: one product and the versions of it you actually sell. Which of them a passport belongs to is a question about the product, not about the store, and Knowledge covers where that line falls.

Product, variant, batch or item

Evidence, conflict and what stays unresolved

Documents you already hold are read and matched to the product. Where two sources disagree, both are kept and the value is marked as conflicted rather than resolved to whichever arrived last. Where nothing supports a value, it stays unresolved and visible.

Publishing the passport back to the product page

The WordPress plugin renders a passport link on the product page from a single product field. Writing that field back into your store automatically is not something ActivateDigital does today, so the address is copied across. At a few hundred products that is a job. At three thousand it is not, and that is worth saying before you plan around it.

How you start today

The WooCommerce connector is implemented, and access to it is arranged account by account. It is not currently distributed as a public WordPress.org plugin, and it has not yet run against a live merchant store. You can also start from an export or a supported data import.

Textiles and batteries are the categories open today. The Workspace says which others are in build.

Where the underlying work is written down

Start with one product

Bring one product across and see how much of it your store already answers.

Open the Workspace