10 Questions to Ask When Evaluating a Connected Product Platform

This is the most consequential question in the evaluation. A connected product platform is not primarily a consumer engagement tool or a QR code generator, it is a product identity infrastructure. How that identity is structured determines whether every subsequent capability, grey market detection, DPP compliance, resale authentication, AI-powered analytics, can be built on a unified foundation or requires separate systems for each function.

The distinction to understand is between a unified identity model — where one item-level identifier per product is governed centrally and used across compliance, supply chain, after-sales, resale, and engagement, and a siloed model, where each function or regulation introduces its own identifier, creating fragmented records that cannot be reconciled. Platforms that lock you into siloed identity embed the most expensive technical debt in the industry.

Ask the vendor:

• Can one item-level identity support compliance, supply chain, consumer engagement, and resale without creating separate identifiers?
• Who owns and controls the primary identity database, the brand or the platform provider?
• If we move to a different platform in three years, can we export our complete product identity records with full scan history?

Most sophisticated brand protection programmes ultimately deploy more than one physical identifier,  NFC for luxury goods, secure QR for high-volume lines, RFID for supply chain checkpoint scanning. The critical question is whether these technologies all point to the same unified product identity, or whether each one generates its own product reference and data structure.

When NFC, QR, and RFID each create separate identifiers for the same product, a consumer authentication via NFC cannot be correlated with a supply chain scan via RFID. The scan intelligence that powers grey market detection becomes impossible to generate because the data lives in separate, irreconcilable records. The platform should treat NFC, QR, and RFID as access layers to the same identity, not as separate product tracking systems.

Security in connected product platforms is frequently discussed at the level of “encrypted NFC” without the specifics that determine whether that encryption is genuinely resistant to cloning or merely a marketing claim. The security of NFC-based authentication depends on two layers: the cryptographic implementation at the chip level, and the backend validation logic that processes each tap event.

At the chip level, the key question is whether the implementation uses a static identifier (which can be copied) or a cryptographic challenge-response protocol (where each tap generates a unique mathematically derived output using a private key that never leaves the chip). At the backend level, the question is whether duplicate scans, geographic anomalies, and velocity irregularities are detected in real time or reviewed manually in periodic reports.

Grey market diversion, genuine products sold outside authorised distribution channels, is one of the most commercially damaging and least visible threats facing premium brands. It is invisible to traditional brand protection methods because the product is authentic. Only item-level serialisation with geographic scan monitoring can detect it systematically.

The platform should not only flag individual anomalous scans, it should accumulate scan patterns across multiple events into diversion route maps that identify the source territory, transit path, and destination market. This requires the platform to store territory allocation data at the point of serialisation and correlate consumer scan locations against it in real time, not retrospectively in weekly reports.

Data ownership is the most frequently overlooked dimension of connected product platform evaluation, and the most commercially consequential. The scan intelligence generated by a connected product programme has compounding value: three years of behavioral data on where products are consumed, how often they are authenticated, and which geographies generate anomalous patterns is more valuable than one year. It is also irreplaceable, the data cannot be reconstructed after the fact if you switch platforms.

Platforms that control the primary identity database, restrict data export, or hold scan history under proprietary formats effectively hold the brand’s most valuable product intelligence as a vendor dependency. Brands must own their data fully, not as a contractual courtesy, but as a structural right enforced in the platform architecture.

EU Digital Product Passport requirements are expanding across luxury, fashion, cosmetics, and electronics on a regulatory timeline that has already begun. Brands that build connected product infrastructure for commercial reasons authentication, grey market detection, consumer engagement should be generating the data that populates a DPP as a by-product of that infrastructure, not building a separate compliance system in addition to it.

The question to ask is not “does your platform support DPP?”  every vendor will say yes. The question is whether DPP compliance is delivered through the same item-level identity and lifecycle data that drives the commercial use cases, or whether it requires a parallel data collection and reporting system that the brand must maintain separately.

The secondary luxury market is worth hundreds of billions globally and growing faster than primary luxury. A connected product platform that delivers authentication at first sale but cannot support verified ownership transfer, resale provenance records, or new owner onboarding in the secondary market is a first-generation solution being sold as comprehensive infrastructure.

Lifecycle identity means the product’s digital record persists and accumulates through every ownership event not just the first sale. When a bag or a bottle changes hands, the new owner should be able to tap the product and access its complete history: manufacture origin, previous owners, service events, and every authentication interaction. The platform must support this continuity without requiring a new identifier or manual reconciliation when ownership transfers.

A connected product platform that operates in isolation from the brand’s existing operational systems is a marketing tool, not an operational infrastructure investment. The commercial value of item-level product data, grey market alerts triggering distributor action, scan velocity informing replenishment decisions, ownership data enriching CRM profiles only materialises when the platform’s data flows into the systems where those decisions are actually made.

Integration quality is also a leading indicator of platform architecture quality. Platforms built on open, well-documented APIs that the brand controls are structurally different from platforms that require custom integrations negotiated case by case. The former scales; the latter accumulates technical debt.

Implementation complexity is consistently underestimated in connected product platform evaluations, particularly by vendors whose demonstrations involve pre-serialised samples and staging environments that bear no resemblance to a real production line. The questions that matter are: what changes at the packaging or manufacturing level, who is responsible for NFC chip embedding or QR code serialisation, and what is the realistic timeline from contract to first serialised products in market.

The distinction between a platform that integrates with existing packaging supplier workflows and one that requires new equipment, new suppliers, or significant production line changes is commercially significant particularly for brands managing multiple product lines across multiple manufacturing locations.

A connected product platform is not a one-time deployment it is an ongoing infrastructure relationship. The platform’s roadmap determines what capabilities will be available in two and five years: AI-powered anomaly detection, expanded DPP compliance categories, deeper resale ecosystem integrations, new geographic market support. The vendor’s business model determines whether their commercial interests are aligned with your brand’s control over its own product identity.

Vendors whose revenue model depends on the brand’s data remaining on their platform, rather than on the brand’s continued use of a platform that genuinely serves its interests, create misaligned incentives that manifest in data portability restrictions, proprietary formats, and contractual terms that make switching costly. Evaluate the vendor’s alignment as carefully as their feature set.

After completing vendor conversations using the questions above, use this scorecard to compare platforms across the dimensions that matter most for long-term control and commercial value.