Serials fail when they live in side systems. Clarus brings them into the handheld workflow and the live ledger. Choose where you capture… goods in, pick, or both. Enforce when serials are mandatory. Then surface everything in transactions and reports, so operations, customers, and auditors share the same truth.
Serial numbers are written to the WMS at source, linked to the receipt, task, user, time, and location. Search a serial to see every touch (from unload to despatch) without chasing files.
Pick your mode per SKU. No tracking for low-risk lines. Track during pick if inbound is fast but outbound needs proof. Full tracking to capture at goods in and pick for high-value or regulated items. Switch by customer, site, or product without re-engineering.
Scanner workflows prompt for serials only when needed, validate format and duplicates, and block out-of-policy moves. Mis-keys drop. Confidence rises.
Type or scan a serial and jump to its receipt photo, putaway, moves, pick, and shipment. Returns and recalls move from guesswork to a clear, timestamped trail.
Serial tracking only works when everyone sees the same truth. Audits become routine, not a fire drill.
Protect SLAs and compliance with a live view of serial status and exceptions. Direct effort based on fact, not hunches.
Capture once, capture right. The gun enforces what’s needed and blocks duplicates, keeping bays moving and data clean.
End escalations fast. Share proof of receipt and shipment with a click, backed by an audit trail customers trust.
Before Clarus, the RTS team logged serials in spreadsheets… even installing Excel on scanners to cope. Now serial capture happens on the handheld at the right step, with duplicates blocked and full click-through history in Transactions. Receipting and picking sped up because the gun asks for serials only when required. Returns, claims, and customer queries are resolved in minutes with proof, not manual hunts.
Where should we capture serials, goods in or pick?
It depends on risk and speed. Many sites use Full tracking for high-value items and Track during pick for fast-moving lines where inbound must fly. You can mix modes by SKU, customer, or site.
How do you prevent duplicate or invalid serials?
Handhelds validate format, check for duplicates, and enforce “serial required” where configured. If a number is wrong or already used, the gun blocks the step and prompts for a fix.
Can customers see their serial numbers?
Yes. With Client Access enabled, you can expose serials per account so customers self-serve receipts, shipments, and current stock (reducing tickets and emails).
What about returns and recalls?
Search the serial to view receipt photos, movements, picks, and shipments. Create a return against the same record to keep the history complete and auditable.
Will this slow down the floor?
No. Prompts appear only when needed. For non-tracked SKUs the step is skipped. For tracked SKUs, scan-to-confirm keeps flow steady and removes rework later.
How does this integrate with other systems?
Expose serials via API or include them on paperwork where required. Events can trigger webhooks so ERP, TMS, or service platforms stay in sync automatically.
