Home/Why HyperDPP

Three kinds of DPP software. One gap between them.

Enterprise platforms go deep but start with a sales call. Generic self-serve tools start fast but are not built for textiles. Here is how they differ.

Enterprise traceability platformsGeneric self-serve toolsHyperDPP
Built forLarge brands with supplier programmesAny sector, small cataloguesTextile and fashion: brands, manufacturers, label partners
How you startSales conversation and a projectSign up and type products inUpload the file you already export
Textile depthHighA general template with a few textile fieldsComposition per component, production stages, care, chemicals
EvidenceSupplier programmes and auditsMostly self-declaredEach field tied to a certificate, test report or declaration
SuppliersOnboarded onto the platformUsually not involvedAnswer through a link, without an account
Label partnerThrough selected partnersDownload a QRWhite label or API bridge to the label platform
Access layersVariesUsually a public pageConsumer, business, authority, recycler

A general description of each category, not a claim about any single product.

Before you choose

12 questions to ask any DPP vendor.

Use them with every option you look at, including us. The answers show quickly whether a tool fits textiles, your data and your suppliers.

  1. 01

    Can it read the files we already export?

    Excel, CSV, XML or JSON from your ERP or PLM, mapped once and reused. If every product has to be typed in again, the cost is in your team’s time, not in the licence.

  2. 02

    Does it model textile data properly?

    Fibre composition per component, production stages with their countries, care instructions and substances of concern. A general product template with a few extra fields will not carry this.

  3. 03

    Can every field be tied to evidence?

    A certificate, test report or supplier declaration attached to the value it supports, with validity dates and a warning before they expire.

  4. 04

    How do suppliers take part?

    Whether they need a licence, an account or training, or can answer through a link. Supplier effort decides how much data you actually receive.

  5. 05

    Can different audiences see different data?

    Consumers, business partners, market surveillance authorities and recyclers need different views. Ask how access is separated and who decides it.

  6. 06

    Does it follow open identifier standards?

    GTIN and GS1 Digital Link on the QR code mean the same code works in shops, in logistics and for the passport.

  7. 07

    How will it connect to the EU DPP registry?

    The registry and its technical rules are still being prepared. Ask what the vendor commits to deliver when they are final, and how.

  8. 08

    What happens to our passport links if we leave?

    Printed QR codes outlive software contracts. Ask who owns the domain and the resolver behind the link, and whether it can be redirected to a new provider.

  9. 09

    Can we export all our data at any time?

    Every product, field, document and version, in open formats such as JSON-LD and CSV, without a fee or a project.

  10. 10

    Is every publication versioned?

    When a value changes, the passport should keep the earlier version and show who changed what and when. Authorities may ask for it.

  11. 11

    How is the price calculated?

    Per product, per published passport, per user or per supplier. Model your own catalogue and supplier count over three years before you compare offers.

  12. 12

    Where is the data hosted, and who processes it?

    The hosting region, the sub-processors and the security measures, written in the contract and the data processing agreement.

Print it or share it with your team: this list belongs to you, not to a vendor.

See a live passport for your own product.

In a 30-minute session we take one of your products, build its passport from your own file, and map the missing fields and evidence status together.

Request a demo →