Serial-number policies
A Serial Number Policy defines how an issuing company creates distinct numbers for individual physical products. It identifies the issuer, durable numbering scope, optional identifier namespace, prefix, digit width, number range, and policy revision.
A policy does not describe a model or batch. A Product Instance represents one physical item and receives an issuer-scoped serial identity. Its serial remains attached to that item throughout its history.
How a policy connects to other records
Issuing company + durable numbering scope
→ Serial Number Policy and format
→ Reserved serial allocation
→ Assigned allocation linked to one Product Instance
→ Item passport for that instance, when needed
The policy directly owns its allocations. An allocation records the policy, issuer, scope, exact serial and reservation request; when assigned, it also identifies the physical instance. The instance independently retains its issuer, scope, serial and optional allocation reference, as well as its release and optional batch.
The guided registration form selects a policy belonging to the batch issuer and uses its numbering scope. You can select a compatible reservation or register a genuine existing serial as text. Entering an existing serial does not mean Actualog generated or reserved that number. Without an allocation reference, issuer and scope identify the numbering boundary; they do not prove that a particular policy revision issued the serial.
One company policy can cover several products or batches if they intentionally use the same numbering scope. The policy is not attached to one product release or factory. Product/batch/factory history comes from the registered instance's manufacturing relationships.
What the policy's fields mean
| Field | Meaning | Example |
|---|---|---|
| Name | Readable title used to find the policy. | Demo sensor numbering. |
| Issuing Company | Company responsible for the numbering scope. | MIPEX. |
| Scope Key | Lasting boundary within which serials must be distinct for this issuer. | demo-sensors. |
| Prefix | Text placed before an automatically allocated number. | SENSOR-. |
| Digits | Number of digits, preserving leading zeros. | 6 produces SENSOR-000001. |
| Range Start / Range End | Permitted range for new reservations. | 1–999999. |
| Next Number | Starting value for the next reservation. | 3 after reserving the first two numbers. |
| Policy Revision | Revision of the numbering rules. | 1. |
| Active / Archived | Whether the policy can be used for new issuance and guided registration. | Active. |
An optional Identifier Namespace associates an existing issuer-owned identifier scheme. It is separate from the policy's display name and durable scope.
Example
A company defines scope BX-assembly, prefix BX-, and eight digits. Reserving the first two numbers can produce BX-00000001 and BX-00000002. The leading zeros are part of the serial. Changing the formatting policy later must not create another item with an already assigned serial in the same issuer's scope.
The MIPEX internal demo policy uses prefix MIPEX-QA-20261006- and four digits. Test items with suffixes 0001 and 0002 can belong to one batch, while suffixes 0003 and 0004 belong to another. Each serial contains the full prefix and suffix. Their common numbering scope does not combine the batches or their factories. These are test identities, not externally issued certificates.
Create a policy
Select the company and open Logistic → Definitions → Serial Number Policy. Search existing policies before selecting Create new serial number policy.
An authorized Production Manager or Company Administrator prepares the policy; an accepted production delegation can cover the corresponding work. The policy must belong to its issuing company.
Complete the form with the issuing company, meaningful Name, stable Scope Key, Prefix, Digits, Range Start, Range End, Policy Revision, and Is Active setting. Choose an Identifier Namespace only when an existing issuer-owned namespace applies. The digit width must fit the chosen range. Select Create new serial number policy.
The scope is a lasting numbering boundary, not a convenient description to change when the display name changes. Only one active policy revision may issue numbers within an issuer's scope.
Reserve, assign, or void numbers
- Open the policy record and locate Reserve serial numbers.
- Enter Number of serials, from 1 to 1,000 per request.
- Enter a Stable request key identifying this reservation operation, then select Reserve serial numbers.
- When registering a Product Instance, choose the policy and the reserved number for the intended item.
- If a reservation will never be used, select Void beside the reserved allocation and give a reason.
The stable request key protects a repeated request from accidentally issuing another set of numbers. Reuse it for a retry of the same reservation; use a new key for a different operation.
Allocation states have different meanings:
- Reserved: allocated for future assignment and not yet attached to an item.
- Assigned: permanently associated with a physical instance.
- Voided: intentionally unused and permanently excluded from reuse.
Assigned and voided numbers cannot be recycled. Reservation is coordinated so competing requests do not receive the same identity.
Maintenance and existing manufacturer numbers
Once a policy has allocations, its format is immutable. Archive the old policy and create the appropriate successor revision for future issuance, keeping the durable scope and existing uniqueness constraints. Archiving does not free its numbers for reuse.
When registering a genuine existing manufacturer serial, preserve its significant characters, issuer, and scope. Do not issue a replacement merely because the original number does not resemble your preferred format.
This policy is a numbering tool within Actualog. EU requirements govern identification of the applicable passport subject, without prescribing an Actualog Serial Number Policy entity. Model and Batch passports do not need individual serial issuance. A catalog offer also does not need a numbering policy merely because it represents the same model.
If reservation or assignment fails, check the active revision, available range, issuer, scope, allocation state, duplicate serials, and whether the page needs refreshing after another operation.
A directly registered existing serial does not advance the policy's Next Number. If the next requested range overlaps existing manufacturer numbers or earlier allocations, reservation is blocked; the current operation does not automatically skip occupied numbers. Plan an unused range for future issuance and preserve existing item identities.