dpp.cloud logo
HomeComplianceIntegrationPricing
Resources
BlogFAQ
Company
About usPartnerContact
Schedule a Call
EN
DE

Menu

  • Home
  • Compliance
  • how it works?
  • Pricing Plan
  • Partner
  • Blog
  • About
  • Faq
  • Contact
Schedule a call
GS1 solution partner - Sqanit

Digital Product Passport with inRiver: Entity Mapping, Machinery Rules, and the Industrial B2B Case

August 18, 2026
Sebastian Eberhardt
/
Implementation & Integration

inRiver's customer base looks different from most PIM vendors: B2B manufacturers, industrial products, deep variant structures. That changes the Digital Product Passport conversation. The relevant regulations are not only ESPR textiles rules but intermediate product categories like steel and aluminium, and the EU Machinery Regulation with its digital documentation rules from 2027. Here is how an inRiver-to-DPP integration works and what is specific to industrial manufacturers.

Which rules actually hit industrial manufacturers

Three regulatory threads matter for the typical inRiver user:

  • ESPR intermediate products. The Commission's first working plan under the ESPR (Regulation (EU) 2024/1781) includes iron, steel, and aluminium. If you buy these as inputs, your suppliers' passports become your data source. If you produce them, the obligation lands on you directly.
  • The Machinery Regulation (Regulation (EU) 2023/1230) applies from January 2027 and explicitly allows digital operating instructions and digital declarations of conformity. We covered the details in how digital documentation changes machinery compliance.
  • B2B customer pressure. Industrial buyers face CSRD reporting and increasingly push structured sustainability data requests down their supply chains, ahead of any product-specific mandate.

How the inRiver integration works

The connector uses inRiver's REST API and follows the same pattern as our other PIM integrations, documented in creating a DPP from PIM data: sync, mapping, validation, QR generation. Entities and fields in inRiver map to DPP fields through configuration, and the passport URL can flow back into an inRiver field for downstream systems.

The part that is genuinely inRiver-specific is the model. inRiver's entity structure separates products, items, and resources, and industrial catalogs use it for deep variant trees: one pump family, forty configurations, each with its own technical documentation. The mapping has to decide which entity level becomes a passport. Our default: the sellable item level gets the passport, inheriting shared data from the product level, with documents attached from resources. That decision takes one workshop, and it is the most important hour of the project.

Machinery documentation is the near-term win

For machine builders, the DPP conversation usually starts with compliance and ends with the documentation problem they have had for years. A machine ships with a binder. The binder dies in a cabinet. Three years later a technician needs the wiring diagram and calls your support line.

The Machinery Regulation makes digital instructions legal from 2027, with conditions: availability for the machine's expected lifetime, printable on request. A QR code on the type plate resolving to a maintained machine page satisfies the pattern, and once that page exists, it can carry more than PDFs: spare parts catalogs, service request forms, maintenance history per serial number. dpp.cloud passports support item-level identity, so each machine in the field has its own page, not the model's.

Typical data situation for inRiver users

Industrial manufacturers usually arrive with strong technical data (dimensions, materials, performance specs, certificates) because their catalogs and datasheets demanded it for decades. What is often missing for a passport:

  • Recyclability and end-of-life information per material group
  • Substance data in structured form rather than in supplier PDFs
  • A clean GTIN or identifier strategy at the item level, especially for configure-to-order products

The identifier question deserves early attention. ESPR passports need unique identifiers, and GS1 Digital Link is the emerging carrier standard. If your items already carry GTINs, this is solved. If your identifiers are internal article numbers, plan an identifier workshop before the mapping.

Timeline and cost

An inRiver integration runs two to four weeks depending on how settled your entity model is. Pricing is flat: 10,500 euros per year for Growth, 17,500 euros per year for Professional, no per-SKU fees. The full vendor comparison is in the DPP software buyer's guide, and category dates are in the DPP timeline.

Next step

If you run inRiver and want a concrete answer on entity mapping and identifier strategy for your catalog, book a 30-minute strategy session. Bring your entity model, and we will sketch the passport structure in the call.

Book your strategy session

FAQ

Which regulations matter for industrial manufacturers on inRiver?

Three areas are particularly relevant: the ESPR first working plan addresses iron, steel, and aluminium as intermediate products; the Machinery Regulation (EU) 2023/1230 allows digital operating instructions from January 2027 under defined conditions; and B2B customers increasingly request structured sustainability data as part of their own reporting and supply-chain requirements.

Which inRiver entity level becomes the Digital Product Passport?

A common approach is to use the sellable item level as the basis for the passport, while inheriting shared information from the product level and attaching relevant documents from resources. For manufacturers with deep variant trees, defining the correct entity level is an important design decision that should be clarified at the beginning of the integration.

Can machine documentation legally be provided digitally?

Yes. Under the Machinery Regulation (EU) 2023/1230, digital operating instructions can be provided from January 2027, subject to specific requirements. The documentation must remain accessible for the expected lifetime of the machinery and must be printable on request. A QR code on the machine type plate that links to a maintained digital machine page can support this approach.

What if our products do not have GTINs?

The identifier strategy should be clarified before the data mapping begins. Digital Product Passports require unique product identifiers, while standards such as GS1 Digital Link can provide a structured way to connect identifiers with digital information. Internal article numbers may therefore need to be complemented by stable identifiers, particularly for configure-to-order products and complex product variants.

What data do industrial manufacturers typically lack for a DPP?

Industrial manufacturers often have strong technical product data already. Typical gaps are structured recyclability and end-of-life information for individual material groups, structured substance and composition data instead of supplier PDFs, and stable identifiers at the item or product-variant level.

Sebastian Eberhardt

Business Development, sqanit

Related Posts

Circular Economy Revenue: How the Digital Product Passport Turns Returns into a Business
The EU circular material use rate is stuck near 12 percent, and regulation alone will not move it. What moves it is unit-level product data that makes second-life business profitable. Four models with numbers, from brand-owned resale to materials recovery.
Julian Sotek
Julian Sotek
August 31, 2026
Osapiens Alternatives 2026: 10 DPP Platforms When You Need a Passport, Not an ESG Suite
Osapiens makes sense when a corporation consolidates CSRD, supply chain due diligence, and DPP into one platform. When the actual job is compliant passports for your catalog, focused alternatives cost a fraction and go live in weeks. Ten options compared, with the three-year TCO math.
Julian Sotek
Julian Sotek
August 31, 2026
Battery Passport Access Rights: The Missing Implementing Act and What to Build Before February 2027
The Commission missed its own deadline for the battery passport access rules, but the passport deadline stays. Here we sort out what is already settled, what isn't, and how to build the restricted layer so it still works once the final rules arrive.
Sebastian Eberhardt
Sebastian Eberhardt
October 26, 2026
EU Green Claims Rules Since 27 September 2026: Why Structured Product Data Matters More Now
Since 27 September 2026, generic claims like “eco-friendly” need recognised excellent environmental performance, and sustainability labels need a certification scheme or a public authority behind them. We look at what changed and where the Digital Product Passport helps, and where it doesn’t.
Sebastian Eberhardt
Sebastian Eberhardt
October 14, 2026
Batteries Without a Passport Still Need a QR Code: Article 13(6) of the EU Batteries Regulation Explained
Most batteries will never get a battery passport, but from February 2027 they still need a QR code. We explain what it has to link to, who is affected and why it's a much smaller project than a full passport.
Benedikt Biallowons
Benedikt Biallowons
November 11, 2026

Browse by Category

Platform comparisons
Implementation & Integration
Business Case & ROI
Industry-Deep-Dives
Company News
ESPR & EU Regulations
DPP Fundamentals

Browse by Authors

Sebastian Eberhardt
Julian Sotek
Benedikt Biallowons
Christian Hieronimi
Dinesh Parmar
Lisa Fauland
Simon Manz
Leopold Holverscheid
dpp.cloudsqanit.com
Create your digital product passports in no time and with minimal effort.
Member of Digital Product Passport ProMEMBERDIGITAL-PRODUCT-PASSPORT.PRO
Google walletGoogle payFORRESTER
Contact us
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
    HomeComplianceBlogPricingIntegrationPartner
        About UsFAQVisit sqanitContact usLegal
          © 2025 sqanit GmbH – All rights reserved.
          ‍