On 20 July 2026, the European Commission launched the Digital Product Passport (DPP) Registry together with a testing environment. The Registry is an operational part of the developing EU system for digital product information. The Commission explains that DPPs will be introduced progressively across product groups, with aluminium and construction products among the areas relevant to future development.
For a window or door supplier, this is a reason to improve product-data control-not a reason to announce that every finished window or door already needs a DPP. The Commission's public timeline is indicative. The exact DPP requirements, timing, data fields, and products in scope depend on the applicable legal act and product group. A practical first step is to build a reliable internal product-data record that can support future buyer, project, and regulatory questions without making an unsupported compliance claim.
Important: This article does not confirm DPP applicability for any SGL product, component, or destination. It does not prove that a DPP is currently required for a window or door, and it does not replace legal, compliance, technical, or project-specific review.
What Changed on 20 July 2026-and What Did Not
The European Commission states that the DPP Registry is now operational and that the test environment, technical documentation, guidance, and support resources are available. A DPP can act as a digital identity record for products, components, and materials. Depending on the applicable product framework, it may contain information connected to origin, materials, safety, repairability, environmental performance, reuse, or recycling.
The change is an implementation milestone for the EU's data infrastructure. It is not evidence that one shared document template now applies to every aluminium profile, glass unit, hardware item, finished window, or door. The Commission's public DPP timeline identifies future work on construction materials and aluminium, but labels the schedule as indicative. Specific obligations arise from the relevant product-specific legal act, and economic operators need to verify whether and when their product is within scope.
For supplier teams, the sensible response is preparation: make product identity, evidence, changes, and document ownership easier to find and verify. That is useful in a customer RFQ today and avoids treating a future DPP request as a last-minute data-collection exercise.
Build a Controlled Product Identity Record Before an RFQ
Start with a record that identifies what is actually being quoted. Do not attach a generic system name to multiple configurations and assume that it represents every opening size, glazing build-up, hardware package, finish, or installation condition.
| Product-data field | Why it matters | Safe status label |
|---|---|---|
| Internal product or configuration ID | Distinguishes the exact proposal from a generic catalogue family | Configuration identifier to be confirmed for the quotation |
| Opening type and use | Separates sliding, casement, tilt-and-turn, entrance, folding, or other project configurations | Opening configuration to be confirmed from current drawings |
| Dimensions and key interfaces | Makes revision-sensitive details visible | Dimensions and interfaces subject to final drawing review |
| Glazing, hardware, finish, and accessories | Prevents evidence for one component set being used for another | Component selection to be confirmed for final configuration |
| Intended market and project route | Identifies the legal, document, and commercial questions that still need review | Destination and project requirements to be confirmed |
| Revision date and record owner | Creates a traceable point of reference for a buyer or internal team | Record owner and revision date to be assigned |
This internal record is not a DPP. It is a disciplined way to make sure that the information later discussed with a buyer belongs to the same product configuration that appears in the drawings and quotation.
Separate Configuration Data, Evidence, and Claims
Supplier files often mix product descriptions, performance claims, and marketing language. A DPP-style readiness process should separate them so that the customer can see what is confirmed, what is available as evidence, and what still requires a technical or compliance decision.
| Information layer | What it should contain | What it must not imply |
|---|---|---|
| Configuration data | The proposed opening type, dimensions, components, finish, and current revision | That every variant has identical evidence or approval |
| Available evidence | Approved document title, issue date, scope, configuration boundary, and document owner | That a document automatically applies to the buyer's final project |
| Project request | The buyer's stated document, performance, approval, or handover question | That the supplier has accepted or satisfied the request before review |
| Approved claim | Wording that a named owner has verified for the exact scope | A broader sustainability, certification, or compliance promise |
| Open item | A missing input, pending decision, or document gap | A reason to fill the gap with a generic statement |
This separation also prevents a data request from becoming a misleading claim. For example, an environmental document may be relevant to a project request, but it does not create a verified life-cycle result for an unconfirmed window or door configuration. Likewise, a component origin record does not by itself prove regulatory compliance or project acceptance.
Create a Traceability-Ready Document Register
The Commission describes DPP information as being stored by the economic operator or a DPP service provider, with the Registry holding identifiers and required registration data under the applicable legal act. Before any future registration question arises, a supplier can create a simple document register for each product family and final project configuration.
| Register field | Practical question |
|---|---|
| Record ID and product/configuration ID | Which exact quoted configuration does this record concern? |
| Document name and issue date | What is the document, and which version is current? |
| Source and document owner | Who issued it, who can update it, and where is the approved copy held? |
| Scope boundary | Which size, opening type, component combination, market, or intended use does it cover? |
| Buyer/project relevance | Was it requested for this project, or is it background information only? |
| Review status | Has the responsible technical, compliance, or project owner confirmed its use? |
| Change history | What changed, when, and which quotation or drawing revision is affected? |
Do not publish a document register as a public compliance statement without review. Its first purpose is internal control: it shows the team which records are available, which are project-specific, and which information still needs confirmation.
Control Substitutions, Revisions, and Data Ownership
Traceability is lost when the quotation changes but the supporting record does not. Establish a simple handover rule: if a material, glass build-up, hardware item, finish, opening type, dimension range, intended use, or project destination changes, the record owner reviews whether the product-data entry and supporting documents must be revised.
Assign named responsibilities before the RFQ becomes an order:
- Sales or project coordinator: records the buyer's drawings, destination, requested documents, and target revision.
- Product or engineering owner: confirms the configuration reference, component list, and technical-document scope.
- Compliance owner: checks whether any product, market, DPP, CE/DoPC, customs, or other legal statement is appropriate for the actual scope.
- Document controller: manages approved file versions, access rights, change history, and archive location.
- Buyer or project team: confirms the final project requirements, acceptance route, and local responsibilities.
This is a governance model, not evidence that the supplier has a DPP Registry account or a ready-to-register product. It simply makes the eventual evidence path easier to audit and explain.
Ask Buyers the Right Questions Before a European Project Inquiry
The supplier can only prepare useful information when the buyer's project route is clear. Ask for:
- the latest drawings and window/door schedule;
- opening types, quantities, dimensions, glazing, hardware, finish, and accessory choices;
- target country, buyer role, project stage, and intended market route;
- requested technical, environmental, product-information, maintenance, or handover documents;
- the named project or compliance contact who decides which documents apply;
- required file formats, language, data fields, and review dates; and
- open decisions that may change the final product configuration.
Use the answers to identify gaps rather than to promise DPP registration, CE marking, an EPD, product performance, local approval, customs clearance, or delivery. Those matters need separate confirmation based on the actual product and destination.
FAQ
Q: Does the July 2026 DPP Registry launch mean that every window or door needs a DPP now?
A: No. The Commission says DPPs are introduced progressively across product groups. The public timeline is indicative, and the applicable DPP obligation depends on the relevant product-specific legal framework. Confirm the exact product scope before stating that a DPP is required.
Q: Is a DPP the same as an EPD, CE marking, DoPC, or a test report?
A: No. A DPP is a digital product-information framework. Depending on the applicable law, it may reference information relevant to a product, but it does not create a valid EPD, CE marking, DoPC, test result, or project approval. Each document needs its own scope and verification review.
Q: What is the safest first step for a window or door supplier?
A: Create a version-controlled product identity record and document register for the exact configurations you quote. Record the source, owner, scope, issue date, and change history of available information. Then verify the legal and project requirements before making any DPP or compliance statement.
Q: Send Your Project Document Requirements for Preliminary Review
A: Send your available drawings or window/door schedule together with the target market, requested document list, and project review route. The SGL team can review the inquiry scope and identify the next technical and commercial questions. Product applicability, final documents, and any regulatory statement must be confirmed for the individual project.
Send Your Project Document Requirements for Preliminary Review
Send your available drawings or window/door schedule together with the target market, requested document list, and project review route. The SGL team can review the inquiry scope and identify the next technical and commercial questions. Product applicability, final documents, and any regulatory statement must be confirmed for the individual project.
