WooCommerce merchants selling into the EU can prepare Digital Product Passports by importing their WordPress catalogue into a passport system, structuring the required data and evidence, and publishing a controlled public passport reached by a QR code or GS1 Digital Link. DPP Shield connects through imports and its API; it does not certify legal compliance.
Do WooCommerce sellers need a DPP?
Only where an EU act covers the product group, such as batteries now and further groups through the ESPR over time. Running a WooCommerce store does not create a passport duty by itself, but EU-facing sellers gain from structuring data before the category applies.
How does it connect to WooCommerce?
Export or import the product list and identifiers, map them to passport fields and category templates, attach supplier evidence, then publish a passport page per product. A QR or GS1 Digital Link on the product or listing resolves to that page.
Who stays responsible?
The economic operator placing the product on the EU market keeps the legal duty. DPP Shield structures, versions and publishes the data through imports and the API, while accuracy and legal scope remain with the merchant.
Frequently asked questions
Is there a WooCommerce plugin for this?
DPP Shield connects through catalogue imports and a scoped API rather than a specific WordPress plugin, so it works with different WooCommerce setups.
Does a WooCommerce store selling to the EU need a DPP?
Only for product groups an EU act covers. Early preparation helps, but the obligation follows the product category, not the platform.