Per-unit records
Each serialized unit has its own record with photos, condition, current location, and full history. The SKU rolls up the units.
Use case
Ten laptops are not '10 laptops'. They are SN-001 through SN-010, each with its own assignment, condition, hours-on-meter, and history. Serialized inventory software treats each unit as a record, not a quantity. Order3 keeps serial-level detail on items that need it without forcing it on items that don't.
Definition
Serialized inventory means each unit is unique and tracked individually. Aviation maintenance teams need it for FAA-traceable parts and lifed components. Automotive shops need it for serialized engines, transmissions, and ECUs. Antique dealers and collectibles sellers need it because every item is one-of-one. Government and education teams need it for asset audits. Medical device distributors need it for UDI compliance. Serialized inventory software gives each unit its own record with full history: manufacture date, hours-on-meter where applicable, condition over time, ownership chain. Order3 supports both serialized and quantity-tracked items in the same catalog. On or off per SKU, no forced choice.
Capabilities
Each serialized unit has its own record with photos, condition, current location, and full history. The SKU rolls up the units.
Scan a serial barcode or QR to pull up the specific unit. Useful for receiving, transfers, and audits where serials matter.
Each unit's history shows every owner, location, and condition change with timestamps and users. Audit-ready.
Some SKUs are serialized; others aren't. Order3 handles both in one catalog without forcing the wrong workflow on either.
Each condition update can attach photos. Useful for warranty claims, recall traces, and resale documentation.
When a manufacturer issues a recall by serial range or lot, pull the affected units and their current locations in seconds.
How it works
Mark the SKU as serialized
On the item record, enable serial tracking. Each new receipt requires capturing serials at the dock.
Receive with serials
At receiving, scan or enter the serial for each unit. Each unit becomes its own record under the SKU.
Assign and move
Assign serials to users, locations, or projects. Transfers carry the serial; history accumulates on the unit record.
Audit and trace
Audit by serial. When a recall or audit hits, pull affected serials with their full history and current location.
Workflow artifact
A useful serialized inventory workflow leaves an item, location, owner, next action, and approval trail behind it.
Order3 record
Trigger
Per-unit records
Each serialized unit has its own record with photos, condition, current location, and full history. The SKU rolls up the units.
Evidence
Mark the SKU as serialized
On the item record, enable serial tracking. Each new receipt requires capturing serials at the dock.
Next action
Receive with serials
At receiving, scan or enter the serial for each unit. Each unit becomes its own record under the SKU.
Control
Audit and trace
Audit by serial. When a recall or audit hits, pull affected serials with their full history and current location.
Who runs this
Aviation maintenance teams managing FAA-traceable parts and lifed components where each one needs full history including hours-on-meter. Automotive shops working on serialized engines, transmissions, ECUs, and high-value parts. Antique dealers and resellers where every item is unique and provenance matters. Government and education IT teams needing per-asset audit trails. Manufacturing teams managing finished serialized products with warranty obligations. Medical device distributors with UDI requirements. The pattern: each unit has its own story. Tracking it as part of a quantity loses the information that matters.
Fit checklist
Per-unit records
Each serialized unit has its own record with photos, condition, current location, and full history. The SKU rolls up the units.
Serial-level scanning
Scan a serial barcode or QR to pull up the specific unit. Useful for receiving, transfers, and audits where serials matter.
Ownership and assignment chain
Each unit's history shows every owner, location, and condition change with timestamps and users. Audit-ready.
Mixed serialized and quantity SKUs
Some SKUs are serialized; others aren't. Order3 handles both in one catalog without forcing the wrong workflow on either.
How it works in Order3
Mark a SKU as serialized and Order3 starts tracking each unit individually. Receiving captures the serial at the dock. Each serial gets its own record with condition, location, owner, and full history. Multi-location holds serialized units at the right level; transfers move the unit and update history. Barcode scanning works at the serial level: scan the unit's barcode and pull up its specific record. The activity log captures every change. Reports answer 'where is serial SN-0142', 'what's the history of SN-0142', 'which units of SKU XYZ haven't moved in 90 days'. Recall and trace queries return affected units and current locations.
Feature
Scan an item, confirm a quantity, and update the record from the floor. Order3 reads UPC, EAN, Code 128, Code 39, QR, and GS1 DataMatrix from an iOS or Android camera, plus Bluetooth handheld scanners that act as keyboards.
Feature
Multi-location tracking means you can answer 'where is it' without calling someone. One workspace holds stock across warehouses, retail shops, trucks, jobsites, stockrooms, zones, and bins. Each keeps its own balance. Transfers between locations are first-class events, not adjustments hidden inside a global total.
Feature
A stocker confirms a receipt at 9:47am. By 9:47am, the inventory value report reflects it. Reports in Order3 are queries against the live ledger. Every scan, transfer, count, and approval feeds the same data the leadership team reads. No nightly batch. No reconciliation lag. The number on the floor matches the number in the office.
Feature
Eight items are below reorder point. Two purchase orders are already inbound. The agent prepares a draft with quantities, supplier context, and the calculation behind each line. Nothing goes to a supplier until a person approves it.
How to choose
Confirm the system handles mixed serialized and non-serialized SKUs in one catalog. Forcing every SKU to be serialized adds friction. Forcing none to be ruins traceability. Check serial capture at receiving. Slow capture kills throughput and the dock team will skip it. Verify the audit and trace queries actually answer the recall scenarios you'd face. If you have FAA, FDA, or other regulatory traceability requirements, confirm the audit trail meets your specific standard. Order3 supports operational serialized tracking. Some heavily regulated workflows (full FAA 8130-3, FDA UDI) may need additional tooling on top. If you need full lot genealogy across a manufacturing process with bills of materials, look at a manufacturing platform with serial genealogy built in.
Related guides
Guide
Inventory management for a small business comes down to four things: knowing what you have, where it is, what changed, and what to reorder next. Most small teams do not need an ERP. They need clean item records, named locations, reorder rules where shortages hurt, and a weekly rhythm that survives a busy quarter.
Guide
Barcode inventory is the practice of identifying items, locations, and movements with machine-readable codes instead of typed entries. The point is not speed. It's removing the manual typing step from the moments where attention is lowest: receiving, counting, transferring, picking. Done well, barcoding is the cheapest accuracy investment a small business can make.
Serialized: each unit has its own unique serial number. Lot: groups of units share a lot number from production or receipt. Aviation parts are serialized; each part has unique history. A pallet of N95s is lot-tracked; the whole lot expires together. Order3 supports both, and a single SKU can use both. A serialized aviation part can also carry the lot it came from. Use serialized for one-of-one or per-unit traceability. Use lot for batch-level expiry and recall.
Yes. Each SKU has its own setting. A laptop SKU can be serialized while a mouse SKU is quantity-tracked. The catalog handles both without forcing a one-size-fits-all approach. Most operations have a small percentage of SKUs that warrant serialization and a larger percentage that don't. Order3 reflects that.
Order3 supports per-unit history, condition tracking, and audit trail: the operational backbone of traceability. Whether that meets your specific regulatory standard depends on the regulation. FAA 8130-3 and FDA UDI both have specific documentation requirements. Confirm with your compliance lead before relying on Order3 alone for regulated traceability. Specific compliance certifications have not been audited.
When a serialized SKU is received, the dock workflow prompts for each serial. You can scan from the unit's serial barcode, scan a vendor's packing list barcode, or type. Each captured serial becomes a unit record. Tedious for high-volume receipts; the alternative is bulk-import via CSV when the vendor provides a serial list ahead of delivery.
Yes. Each unit's record shows every change (assignment, transfer, condition update, photo addition) with timestamp and user. For audits, recalls, or warranty claims, pull the unit's full history. The activity log preserves it indefinitely; exports to CSV or PDF are available for external documentation.
Yes. Antique dealers often treat every item as a unique serialized record with photos, provenance notes, and condition. The serialized workflow fits naturally: each item is a single-unit SKU, and the record carries everything that matters about that piece. Many dealers use this pattern as both their inventory system and their pre-sale catalog.
Adjacent use cases
Start with the SKUs, locations, and counts behind the problem. Bring in expert help when the workflow needs integrations, approvals, or agent policy.