What is unit-level product intelligence?
Unit-level product intelligence is analysis built from a persistent record for an individual physical item, usually identified by a product key plus serial. It preserves that item’s manufacture, movement, sale, interaction, return, repair, resale or recycling events instead of collapsing every event into a SKU total.
How is it different from SKU-level analytics?
A SKU describes a sellable variant; a serialized unit describes one physical instance. SKU analytics can show aggregate sell-through and stock. Unit history can show which item was scanned, sold, returned, repaired, authenticated or resold, when it happened and which evidence accompanied the event.
Both levels matter. Unit records do not replace product or SKU aggregates; they make them traceable and allow new post-sale questions.
What can a business learn only with persistent identity?
- Whether engagement concentrates in a small subset of physical items rather than evenly across the SKU.
- Which channels, locations, batches or individual units produce unusual return or repair patterns.
- Whether a specific item’s after-sale history supports warranty, authentication or resale decisions.
- How messages, services and ownership events evolve after purchase.
- Which evidence belongs to the exact item rather than a generic model record.
These conclusions require the relevant event to be captured against the persistent identity. Serialization alone does not manufacture lifecycle evidence.
Which aggregate blind spots does unit data remove?
| Aggregate view | Question it cannot resolve alone | Unit-level evidence |
|---|---|---|
| SKU return rate | Is one batch or channel causing the problem? | Identity joined to sale, batch and return event |
| Total scans | Are many units engaged once or a few units repeatedly? | Distinct units and event history |
| Resale volume | What provenance belongs to this exact item? | Serialized service and ownership record |
| Warranty cost | Has this unit already been repaired? | Dated repair and support events |
Does the EU require every textile DPP at unit level?
No final textile rule currently requires every garment to have a serialized item-level passport. ESPR states that the applicable delegated act will determine whether a DPP is established at model, batch or item level. A platform may support unit identity for operational or consumer use even where the legal minimum is less granular.
How does Cycle use the hierarchy?
Cycle separates master product, SKU, unit identity and Digital Twin experience. Business dashboards can aggregate upward, while a serialized Twin can preserve downstream activity and services. This granularity is the data foundation for product-specific agent actions and longitudinal memory.