A digital product passport (DPP) is a digital record that makes information about a product machine-readable and shareable through a data carrier such as a QR code, NFC tag or RFID tag: what it is made of, where and how it was produced, its environmental footprint, and how it can be repaired, reused and recycled. The European Union is making this record mandatory product group by product group through the Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) and the Batteries Regulation (Regulation (EU) 2023/1542). Batteries come first. For electric vehicle batteries, light means of transport (LMT) batteries such as e-bike and e-scooter packs, and industrial batteries above 2 kWh, the battery passport is required from 18 February 2027. Requirements for textiles, furniture, iron and steel, aluminium, tyres, mattresses, electronics and other groups will be set by product-specific delegated acts under ESPR over the coming years. 360 Soft designs, builds and runs digital product passport software for manufacturers and exporters: data model, supplier data collection, ERP integration, data carrier and access rights, delivered as a dedicated team from Istanbul.
What a digital product passport is and why it matters now
For an EU buyer, the passport is becoming part of the product itself: no passport, no market access for the product groups in scope. For manufacturers outside the EU, including exporters in Türkiye, the obligation reaches them through their EU importers and brand owners, who will ask for complete, verifiable passport data as a condition of purchase. Preparing early matters because most of the data does not yet sit in one place: it is spread across ERP, PLM, quality systems, supplier spreadsheets and test reports.
ESPR and the Batteries Regulation: key concepts
| Concept | What it means in practice |
|---|---|
| Unique identifier | Each product (or model or batch, depending on the delegated act) gets a persistent, unique ID linked to its passport. |
| Data carrier | A QR code, NFC or RFID tag on the product, packaging or documentation that resolves to the passport. |
| Access levels | Some data is public (consumers), some is restricted to repairers, recyclers, authorities or notified bodies. |
| Central registry | The European Commission is setting up a registry where passport identifiers are stored and linked to customs processes. |
| Economic operator | The party placing the product on the EU market is responsible for the passport, but needs data from the whole supply chain. |
Who needs to prepare
Battery manufacturers and their suppliers of cells, modules and cathode materials are the first wave. Textile and apparel, furniture, steel and aluminium, tyres, electronics and chemicals are among the next priorities named in the Commission working plan. Suppliers of components and materials to these sectors are affected indirectly, because the passport needs their data too.
Status by product group (general overview)
| Product group | Legal basis | Status |
|---|---|---|
| EV, LMT and industrial batteries above 2 kWh | Batteries Regulation 2023/1542 | Battery passport required from 18 February 2027 |
| Textiles and apparel | ESPR delegated act | Among the first priorities; requirements expected to apply in the following years |
| Iron, steel and aluminium | ESPR delegated acts | Prioritised in the working plan; details pending |
| Furniture, tyres, mattresses | ESPR delegated acts | Prioritised; timelines set by each delegated act |
| Electronics and ICT | ESPR and related acts | Expected in later waves |
Dates for groups other than batteries are indicative until the delegated act is published. We track the legislative process and design the data model so that new fields can be added without rebuilding the system.
What data goes into the passport
- Product identity: model, GTIN or other identifier, serial or batch number, manufacturer and facility
- Composition: materials, recycled content, substances of concern, critical raw materials
- Environmental performance: carbon footprint (mandatory for batteries), other footprint indicators where required
- Durability and repairability: spare parts, repair instructions, expected lifetime, state of health for batteries
- End of life: dismantling, reuse and recycling information, take-back schemes
- Compliance: declarations of conformity, test reports, due diligence information on supply chains
Scope of digital product passport software: modules
| Module | What it does |
|---|---|
| Product and data model | Configurable passport templates per product group and delegated act, with versioning |
| Supplier portal | Suppliers upload material, origin and footprint data with validation rules and reminders |
| ERP/PLM integration | Pulls bills of materials, production orders and batch data from SAP, Logo, Microsoft Dynamics or custom systems |
| Calculation engine | Carbon footprint and recycled content calculations with traceable sources |
| Identifier and carrier management | Generates IDs, QR codes and GS1 Digital Link URIs; encodes NFC/RFID tags |
| Passport viewer | Public and role-based views, multilingual, mobile-first |
| Access control and audit trail | Who saw or changed what, when; evidence for authorities and verifiers |
| API and registry connector | Exchange with customers, platforms and the EU registry once specifications are final |
Data carrier: QR, NFC or RFID
A QR code is the cheapest and most universal carrier and is readable by any smartphone. NFC adds tamper resistance and works well for premium consumer goods. RFID (UHF) enables bulk reading in warehouses and recycling facilities and can double as an inventory tool; see our RFID inventory systems. Many projects combine a printed QR code for consumers with RFID for logistics.
GS1 Digital Link and unique identifiers
We recommend GS1 Digital Link where possible: a single web URI carries the GTIN, serial or batch number and resolves to different views depending on who scans it. This keeps the carrier stable even if the passport platform changes later, and fits retail and logistics standards your customers already use.
Integration with existing systems
Passport data should not be typed in by hand. We connect to ERP (SAP S/4HANA, SAP Business One, Logo, Netsis, Microsoft Dynamics), PLM, MES, quality management and LIMS systems, and to supplier data sources. Where you already collect product carbon data, for example for CBAM emissions reporting, the same data foundation can feed the passport. For SAP-heavy landscapes our SAP consultants handle the extraction side.
Solution approaches: off-the-shelf platform or custom software
| Approach | Strengths | Limitations |
|---|---|---|
| SaaS DPP platform | Fast start, standard templates | Subscription per product, limited fit to your ERP and supplier reality, data held by a third party |
| Custom software | Fits your data model and processes, you own code and data | Needs a clear scope and a capable team |
| Hybrid | Platform for the viewer, custom integration and data layer | Two parties to coordinate |
Delivery models
- Project-based: fixed scope, milestones and acceptance criteria for a first product group
- Dedicated team: developers, a business analyst and a data engineer working only for you, from 1 to 200+ people, remote, on-site or hybrid
- Managed service: we run the platform, supplier onboarding and data quality checks after go-live
Project process step by step
- Scoping: product groups, applicable regulations, customers asking for data
- Data inventory: where each required field lives today and who owns it
- Data model and architecture design, including identifiers and access levels
- Pilot on one product family, with supplier portal and ERP connection
- Rollout to further products and suppliers, carrier printing or tagging on the line
- Operation: monitoring, regulatory updates, support
A team can typically start within 1 to 2 weeks of signing. The length of the pilot depends on data availability more than on development effort.
Governance and reporting
We set up a simple governance model: a product data owner on your side, defined data quality rules, completeness dashboards per product and supplier, and a change log for every passport version. Monthly reports show completeness, open supplier requests and upcoming regulatory changes.
Factors that determine cost
| Factor | Why it matters |
|---|---|
| Number of product groups and variants | Each group needs its own template and rules |
| Number of suppliers | Drives portal onboarding and data validation effort |
| Systems to integrate | Each ERP/PLM/MES connection adds work |
| Carrier type | NFC/RFID encoding and line integration cost more than QR |
| Hosting and security requirements | On-premise, private cloud or SaaS |
| Languages and markets | Multilingual viewer content |
We do not publish fixed prices; we prepare a written proposal after a short scoping call.
Risks and mitigations
| Risk | Mitigation |
|---|---|
| Delegated acts change | Configurable data model, versioned templates |
| Suppliers do not deliver data | Supplier portal with reminders, default values clearly flagged, escalation |
| Data quality | Validation rules at entry, completeness dashboards |
| Vendor lock-in | You own source code and data; open standards such as GS1 Digital Link |
| Confidential data exposure | Role-based access, only required data made public |
Security, GDPR, KVKK and intellectual property
Passports mostly contain product data rather than personal data, but supplier contacts, user accounts and scan logs can be personal data. We apply role-based access, encryption in transit and at rest, and audit logs.
Contract framework for international buyers: we work under a B2B service agreement with a full IP assignment clause, so source code, data models, configurations and documentation produced for you belong to you on payment. A mutual NDA is signed before any data is shared. Where personal data is processed, we sign a GDPR data processing agreement (DPA) with Standard Contractual Clauses (or the UK IDTA for UK controllers); on the Turkish side the team also complies with KVKK (Law No. 6698). Local rules in your own country apply in addition to these.
Your own team, a freelancer or outsourcing: comparison
| Criterion | In-house team | Freelancer | 360 Soft team |
|---|---|---|---|
| Start time | Months of hiring | Fast, but single person | Typically 1 to 2 weeks |
| Continuity | Depends on retention | High risk | Replacement process for staff |
| Breadth of skills | Limited to hires | Limited | Developers, analysts, data and SAP skills |
| Scalability | Slow | Very limited | 1 to 200+ people |
Illustrative scenario
Illustrative scenario: an e-bike battery pack assembler in Türkiye supplying an EU brand needs a battery passport for 2027. The project maps cell and module data from two suppliers, connects production batch data from the ERP, calculates the carbon footprint per battery model and prints a QR code linked to a GS1 Digital Link URI. The EU customer receives an API feed. This scenario describes an approach, not a completed client project.
Readiness checklist
- Which of your products fall under the Batteries Regulation or an ESPR delegated act
- Which EU customers have asked for passport data
- Where bill of materials, origin and footprint data live today
- Which suppliers must provide data
- Whether you use GTINs or other identifiers
- Which carrier fits your product and production line
- Who owns product data internally
Frequently asked questions
What is a digital product passport (DPP)?
A digital record linked to a product through a QR code, NFC or RFID tag that provides machine-readable information on composition, origin, environmental performance, repair and recycling, as required by EU rules such as ESPR and the Batteries Regulation.
Who does the battery passport apply to and when?
It applies to EV batteries, light means of transport batteries and industrial batteries above 2 kWh placed on the EU market, from 18 February 2027.
When will passports be required for textiles?
Textiles are among the first ESPR priorities. The exact date depends on the delegated act; requirements are expected to apply in the years after its adoption.
Are manufacturers outside the EU affected?
Yes. The EU economic operator is responsible, but it needs data from non-EU manufacturers and suppliers, so exporters in Türkiye and elsewhere will be asked to provide it.
Is a QR code enough as a data carrier?
For most products a QR code is sufficient and cheapest. NFC or RFID are useful where tamper resistance or bulk reading matters.
Can you integrate with our ERP?
Yes. We connect to SAP, Logo, Netsis, Microsoft Dynamics and custom ERP, PLM and MES systems so data is not entered manually.
Can the same system be used for CBAM and sustainability reporting?
Yes. Product carbon data collected for CBAM can feed the passport and sustainability reports from one data foundation.
Should we buy a SaaS platform or build custom software?
SaaS is fast for simple cases; custom or hybrid fits better when you have complex ERP data, many suppliers or want to own code and data. We help you compare both.
How long does a pilot take?
It depends mainly on data availability. The team itself can typically start within 1 to 2 weeks.
Who owns the source code and data?
You do. Our B2B agreement includes full IP assignment on payment, and passport data stays in your environment or your chosen hosting.
How is pricing determined?
By product groups, suppliers, integrations, carrier type and hosting. We send a written proposal after scoping; we do not publish fixed prices.
Related pages: carbon data management, CBAM emissions reporting software, textile and apparel outsourcing, automotive outsourcing, software outsourcing company in Türkiye.
Let us plan your digital product passport
Tell us which products and EU customers are involved and we will come back with a scoped proposal and a realistic plan. Call or WhatsApp us on +90 850 335 10 87, write to info@360-soft.com, message us directly on WhatsApp, or use the contact page. 360 Soft Marketing Yazılım ve Danışmanlık Ltd. Şti., Nidakule Ataşehir Batı, Barbaros Mah. Begonya Sk. No:1 D:2, 34746 Ataşehir/İstanbul.
Türkçe: Türkçe sürüm
