Loading

Product Instances

A Product Instance represents one physical item. The Product describes a model; the instance identifies an individual manufactured item with its issuer and serial number. Each instance can have its own measurements, component use, lifecycle history, and Digital Product Passport.

For example, Battery Module M1 is the model, release R2 is its approved definition, batch MAY-001 identifies production at Factory North, and serial 000042 identifies one battery. Serial 000043 identifies another item with its own history.

The physical-item chain

The guided manufacturing screen uses Published concrete company product and approved release/template → released batch and actual factory → issuer numbering policy and genuine instance number → physical Product Instance. An Item passport is a separate reviewed publication. Model or Batch passports identify their own subjects without requiring unnecessary instances.

The batch supplies manufacturing provenance. A warehouse is not selected as a replacement factory. Serial numbers are text; leading zeros and significant characters belong to the identity. An instance is not a product variant, seller SKU, stock quantity, or commercial multipack.

Instance and passport are different records

Product Instance Digital Product Passport
Identifies one physical item and its issuer-scoped serial. Publishes reviewed information for an exact Model, Batch or Item subject.
Keeps original release and known batch provenance. Uses an approved profile and category mapping to choose source information.
Can receive observations, component history and lifecycle events. Preserves immutable publication versions and a stable access link.
Can exist before or without a passport. Does not create an item, production quantity or stock balance.

For an Item passport, the selected instance supplies its identity, the linked batch supplies manufacturing facts, and the linked release supplies nominal specifications. The QR code opens the published passport page for that subject. It does not open an editable instance form or infer another item's data.

The numbering policy helps choose the issuer's scope or reserve numbers. A reserved allocation, when selected and assigned, links that policy to this instance. An existing manufacturer's serial can instead be registered directly; that is not a claim that the policy generated it.

Who creates and maintains instances

A Production Manager, Company Administrator, or properly delegated production user registers the items. Product Editors maintain working model information; Product Governance Managers approve releases and evidence. Passport preparation and publication require separate permissions.

Register one item

  1. Open Logistic → Production → Product Instance in the administering company. Search before choosing + Create new product instance.
  2. Select the exact release in 1. Product and approved release, then its released batch in 2. Production batch.
  3. Check Inherited manufacturing information: product, approved template, revision, batch, factory, and issuer.
  4. Select an active Numbering policy belonging to the batch issuer. Select a compatible reservation when available, or enter the genuine manufacturer serial in 3. Instance number.
  5. Add supported condition/expiry and create the instance. The batch's expiry supplies the default when no other expiry is entered.
  6. Open the saved item for Manufacturing traceability or + Create new product passport.

Release, batch, issuer, numbering scope, and serial cannot be reassigned through ordinary editing. Later configuration or state changes belong in accepted lifecycle events; measurements belong in observations.

Register several items quickly

Use Product Overview in preparation mode. Choose a product-level category associated with the current company as Manufacturer or Brand Owner, then filter the Published concrete company products and use Select items. Continue to preparation, reuse existing released definitions and batches, check the inherited factory, choose the issuer numbering policy and enter one genuine serial per line.

Preview row outcomes before applying. Inspect Created, Unchanged, Rejected and Conflict results. Repeated serial identities are reused; different manufacturing assignments cannot silently replace them. Continue from the resulting instance to passport preparation only when an Item passport is appropriate.

Missing provenance and conflicts

The guided screen requires a released batch. Supported integration records can retain genuinely unknown batch provenance. An Item profile evaluates the recorded provenance and reports any applicable readiness gaps; do not invent a batch. If a picker is empty, check release, state, company, permissions, and manufacturing prerequisites.

A duplicate issuer-scoped serial or incompatible allocation is rejected. Reload after a version conflict. Import replay resolves existing items and reports conflicting rows rather than creating duplicates.

Keep each item current

Preserve the original manufacturing release when an accepted rebuilding event links a later configuration. Record service, movement, and recycling as lifecycle events. An observation for this item does not alter the model or another item. Refresh affected passport drafts and review before republication; stable access links and earlier publications remain separate from draft updates.

Registering product instances · Production batches · Serial number policies · Instance observations · Digital product passports