Create permanent custody identities, optional package labels, destination-specific QR codes and fast scan workflows without losing the relationship between the physical asset and its operating record.
Storage-only clients can use identification selectively. Items routed to rental, sales or subscription workflows receive the required item-level identity and supporting catalogue or destination references.
The identification model follows the client’s storage and operating choices. Package QR can remain optional, while item-level custody identity becomes mandatory where the selected workflow requires individual control.
Create optional identities for cartons, trunks, crates, rails, bins and other receiving or storage units.
Create the stable item-level reference used through intake, location, movement, care and return.
Connect catalogue, SKU and destination-specific QR references to the same underlying custody record.
Each component remains visible so the team can distinguish generation, physical labelling, verification and later relabelling without losing the custody record.
Create the stable item record used across storage, movement, fulfilment, return and care workflows.
Add optional container identities and connected site-specific references where they improve control.
Use fast scanning with immediate confirmation, duplicate control and mismatch handling.
Replace damaged labels, recover missing identity and retain the original activity history.
Start with the complete identification architecture, then move through custody QR generation, package labels, readable code display, destination mapping, continuous scanning, validation, batch export, reprint and missing-label recovery.
The permanent custody identity connects the physical item to its client, intake history, location, movement, condition, care and return activity.
Relabelling should replace the physical label—not create a new custody record for the same item.
Create the permanent code after the required intake identity checks.
Show the readable QR value so users can visually verify or copy it when required.
Connect the item to its current storage or operational position.
Retain every generation, scan, relabel, movement and exception event.
Package QR remains optional and should be used where it improves receiving, storage or custody. Catalogue and site-specific references can be added without replacing the permanent item identity.
When the same item appears on more than one site, each destination reference should resolve back to the same custody record and its approved destination mapping.
Identify receiving and storage units only where the operating model requires them.
Connect the custody identity to the approved internal or destination reference.
Create a different destination QR where the item is approved for more than one site.
Show how every approved reference connects to one underlying item.
The scan interface should accept approved custody, storage, catalogue and SKU references and return the correct operational record immediately.
A successful scan should confirm the item and action—not send the user to an unexplained raw site path.
Use the device and workflow appropriate to the operating stage.
Process large queues without repeatedly returning to the input field.
Stop incorrect, duplicate or out-of-scope scans before they change the task.
Show the item, current state, action completed and next operational step.
Labels can be generated individually or in batches for internal or external printing. Reprints should be authorised, logged and linked to the original custody identity.
When a QR is missing or unreadable, the team can use controlled search, item details and approved image matching to recover the correct record before relabelling.
Create labels for one item or a large intake queue.
Replace a damaged or unsuitable physical label without changing the identity.
Find the correct item record before creating a replacement label.
Stop movement when the item cannot be identified with sufficient confidence.
The workflow keeps every label and scan connected to the physical item and its authoritative custody record.
Choose package, custody, catalogue, SKU or destination-specific identification.
Create the approved code and make the readable value available for verification.
Produce the label individually or in a batch and attach it to the correct asset.
Scan the physical label and confirm that it resolves to the intended record.
Use the identity across storage, movement, picking, return, care and destination workflows.
Replace damaged labels or resolve missing identity without creating duplicate custody.
It should be applied where the receiving or storage model benefits from package-level control.
Rental, sales, subscription and item-controlled workflows require permanent individual identification.
The client or seller approves the operating model. The Vault team generates and verifies the required identity. Destination owners define site-specific references and permissions.
The right combination of package, custody, catalogue and destination references depends on how the inventory will be stored, moved and used.
The final identification scope depends on storage ownership, item-level control, catalogue requirements, destinations, label volume and recovery needs.
No. Package QR is optional and should be used where it improves receiving, storage or custody. It may not be required for every client-managed storage model.
It is required where the operating model needs individual custody, including approved rental, sales, subscription or item-controlled workflows.
Yes. One permanent custody identity can be connected to catalogue, SKU and destination-specific QR references. The custody identity remains authoritative.
Each approved site can use its own reference or QR while resolving back to the same custody record and destination mapping.
Yes. The readable code should be shown beside the QR so users can visually verify, copy or paste it without needing the full raw URL.
The workflow can support phone camera, handheld scanner, scan gun, manual entry and clipboard paste according to the stage and device.
Yes. Approved label data can be exported in a batch format, including a spreadsheet where an external printer requires it.
The label can be reprinted under a recorded reason and approval. The item keeps the same permanent custody identity.
Images can support controlled recovery, but uncertain matches should move to hold and supervisor review before a new label is attached.
The operational scan should resolve to the relevant record and action. It should not leave users on an unexplained raw path instead of confirming the item and workflow result.
We will map package, custody, catalogue, SKU and destination identities together with printing, verification, recovery and activity-history requirements.
Login