Choose the identity purpose
Decide whether the label represents an internal item, a unique unit, a returnable asset, a location or a logistic unit before selecting its code and carrier.
Workflow blueprint
An inventory tagging system that protects identity history
A label-lifecycle blueprint for stock teams that need every active, damaged, duplicated and retired tag linked to the right record.
Control what a tag identifies, who allocated it, where it belongs, which label it replaced and why it stopped being active before a scan can change stock.
TL;DR — Control what a tag identifies, who allocated it, where it belongs, which label it replaced and why it stopped being active before a scan can change stock.
Issue and attach under review
Create the identifier, verify that it is unused, record the object and placement, then activate the label only after a second check.
Replace without losing history
When a label becomes damaged, retire that physical instance and link the replacement event to the same approved record rather than reusing an unrelated old code.
Quarantine duplicates and retire cleanly
Stop conflicting scans, investigate which label is legitimate, preserve the evidence and close identifiers that must never return to circulation.
Page-specific decision aid
A tag issue, replacement and retirement register
The register follows one reusable pump from its first approved label through damage, controlled replacement, a duplicate-tag investigation, a repair movement and final disposal. The item identity stays stable while each physical tag instance gains its own dates, state, evidence and reviewer.
- ✓A printed pattern does not grant a global identifier.
- ✓Replacement preserves the retired label reference.
- ✓A duplicate scan triggers quarantine rather than an automatic merge.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Identifier types and allocation authority recorded
- ✓Uniqueness, activation, replacement and retirement rules approved
- ✓Label placement, durability and scan checks assigned
- ✓GS1 licensing, RFID hardware and verification excluded without separate proof
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow