What is a connected product platform?

A durable identity layer for physical products

A connected product starts with an identity that remains meaningful after manufacturing, distribution, purchase, service, resale, and end-of-life. That identity can represent a model, GTIN, batch, lot, asset, or serialized unit, depending on the business use case.

The identity should not be tied permanently to one marketing page. It should resolve to the information and service appropriate for the person, system, geography, lifecycle stage, and business rule involved.

Choose the right identity granularity

Not every use case requires the same level of identity. A model-level or GTIN-level identity may be sufficient for product information and general instructions. Batch and lot identities can support quality, expiration, recall, and traceability workflows. Serialized identities can support ownership, warranty, maintenance, authenticity, and asset history.

The platform should allow these identity levels to relate to one another. A serialized product still belongs to a model and may also belong to a production lot, packaging hierarchy, shipment, owner, and service history. Designing those relationships early prevents the QR code or NFC tag from becoming an isolated record with no reliable connection to enterprise data.

Beyond QR-code management

QR-code platforms are useful for generating codes and tracking scans, but connected-product infrastructure has a broader job. It must link identity to authoritative enterprise systems and support experiences that change as the product moves through its lifecycle.

• Product and master data from ERP and PIM systems
• Ownership, customer, and channel data from CRM and commerce systems
• Warranty, maintenance, recall, and service histories
• Traceability, materials, compliance, and sustainability disclosures
• Contextual experiences for consumers, retailers, technicians, and regulators

The core platform capabilities

Identity and resolution

Create durable product identities and resolve them to the correct destination, data source, or API response without reprinting the code.

Enterprise integration boundary

Keep ERP, PIM, PLM, CRM, service, commerce, quality, and supply-chain systems authoritative. OriginSpan exposes controlled product, identity, lifecycle, resolver, and export boundaries while broader connectors remain scoped to the needs and evidence of each pilot.

Experience and service delivery

Deliver product information, onboarding, manuals, warranty, service, recalls, parts, replenishment, and post-purchase experiences based on context.

Global localization and content governance

Keep portal interface language, tenant-supplied product content, and public Digital Product Passport language separate. The localization architecture is designed to support more than 70 languages and regional variants, while language coverage and review are matched to each engagement.

Operational visibility and command center

Present permission-scoped tenant summaries, attention categories, unfinished work, recent activity, and authorized quick actions without creating global or cross-tenant analytics.

What OriginSpan brings together

Capabilities buyers should expect

A connected product platform should provide more than a public page or QR code. Buyers should evaluate whether the underlying platform can support durable identity, controlled data, global delivery, and long term continuity.

A practical connected-product reference architecture

A durable implementation normally separates identity, enterprise data, experience delivery, and analytics so that each layer can evolve without forcing a packaging change.

1. Systems of record: ERP, PIM, PLM, quality, commerce, CRM, service, and supply-chain applications remain authoritative for their data.
2. Identity and resolution: a stable product URI maps the product to the correct resources and business rules.
3. Experience and API delivery: human-readable pages and machine-readable services are generated for each audience and context.
4. Events and analytics: scans, taps, service actions, registrations, and lifecycle events create measurable signals.
5. Governance and security: access control, audit history, privacy, data lineage, and operating ownership protect the system.

Where connected products create enterprise value

The strongest programs begin with one measurable use case and reuse the same identity foundation for additional outcomes. Common starting points include digital instructions, warranty registration, recall communications, service enablement, parts commerce, traceability, and Digital Product Passport preparation.

OriginSpan reuses one tenant scoped identity foundation across scanning, lifecycle, custody, evidence, export, and Digital Product Passport workflows. Integrations, operating controls, and expansion are shaped to the customer’s selected products and business requirements.

How to evaluate a connected product platform

When comparing solutions, evaluate the infrastructure behind the visible page or code:

• Can the company control its product identity domain and preserve identifiers if vendors change?
• Can one identity resolve to multiple resources rather than one fixed redirect?
• Can it represent models, GTINs, batches, lots, components, and serialized products?
• Does it integrate with existing systems instead of becoming another disconnected product database?
• Can it deliver both human-readable experiences and machine-readable APIs?
• Can interface and product-content localization scale beyond a handful of languages, including right-to-left scripts, regional formatting, provenance, and controlled fallback?
• Can customers add their own fields, validation rules, evidence requirements, approvals, and industry packs without a new custom application?
• Can suppliers and partners submit governed data and evidence without gaining broad tenant access?
• Does the platform address QR and label lifecycle, exceptions, targeted recall, analytics, and interoperable event exchange?
• Are availability, auditability, privacy, security, export, and lifecycle continuity designed into the platform?

A short-term campaign tool may be appropriate for a narrow engagement use case. A strategic connected-product program requires an identity and data foundation that can support new experiences long after the first campaign.