TL;DR
Set up serial number tracking at six control points: receipt, transfer, pick, shipment, return, and replacement. Require one serial per unit, attach every scan to a transaction and location, quarantine mismatches, and link each replacement serial to the original unit. The SOP below gives warehouse and customer-service teams a repeatable process.
Set up serial number tracking at six control points: receipt, transfer, pick, shipment, return, and replacement. At each control point, scan or enter the unit’s serial number with its transaction, location, status, and operator.
A serial number identifies one physical unit. A SKU identifies a product type, and a lot identifies a group of units. In GS1 barcodes, AI (21) identifies a serial number, while AI (10) identifies a batch or lot.
Copy This Serial Number Tracking SOP
Use this SOP for high-value, warrantied, repairable, or regulated inventory. Assign a Receiving Lead, Warehouse Lead, Returns Lead, and Customer Service Lead before launch.
1. Set the Serial Rule Before Goods Arrive
Mark each applicable SKU as serial tracked in the system of record.
Use the manufacturer’s serial number when it is present and readable. Create an internal serial only when the product has no usable manufacturer serial or your operation requires an additional internal identifier.
Set these rules:
- One serial identifies one unit.
- A serial number is never reused.
- Every serial has one current location and one current status.
- Allowed statuses are: Receiving, Quarantine, Available, Allocated, Picked, Shipped, Returned, Repair, Refurbish, and Scrap.
- A quantity adjustment cannot change a serial’s location or status without a reason and named operator.
If suppliers use GS1 labels, keep GTIN, lot, expiry, and serial in separate fields. GS1 states that a trade-item serial appears with AI (21), while a lot uses AI (10); mixing both values into one note makes searches and recall work slower. See the GS1 label guidance.
2. Receive Each Unit Before It Becomes Available
The receiver matches each unit to the purchase order, SKU, supplier, and physical count.
For every unit, the receiver scans or enters:
- Serial number
- SKU or product ID
- Purchase order or receipt number
- Supplier
- Receipt date
- Receiving location
- Condition
- Receiver name
The receiver then checks for a duplicate serial. A duplicate, unreadable, damaged, or unmatched unit goes to Quarantine. The receiver records the reason before the end of the same shift.
Only make stock Available when the serial count equals the physical count and every unit is linked to its receipt. Barcode-based receiving and bin put-away keep that information close to the physical work. For more receiving controls, see our warehouse workflow guide.
3. Record Every Warehouse Transfer
A transfer changes the unit’s custody. It needs more than a new bin name.
The transfer operator scans:
- The serial number.
- The source location.
- The destination location.
- The transfer reference.
Set the status to In Transfer before the unit moves. The destination operator confirms receipt before the system marks the unit Available again.
Treat missing destination confirmations as an exception queue. The Warehouse Lead reviews that queue daily. A serial should never be simultaneously available in two locations.
4. Match the Serial to the Order at Pick and Shipment
The picker scans the order and unit serial before packing. The system should confirm that the serial belongs to the ordered SKU and remains eligible to ship.
The packer records the serial against:
- Sales order
- Customer
- Shipment reference
- Ship date
- Packing operator
If the wrong serial appears, stop the pack. The Warehouse Lead approves any override and records the reason, operator, and timestamp.
The shipment record is the point where the unit becomes Shipped. That record lets customer service identify which exact unit went to which customer.
5. Put Every Return into Inspection First
The Returns Lead creates or records the return authorization before receiving the physical unit. The team then scans the returned serial and compares it with the original shipment.
Record the return date, customer, return reason, condition, and receiving operator. Move every returned unit to Quarantine or Returned status first.
A matching serial can still be damaged or incomplete. It becomes Available only after an approved inspection. A mismatched serial stays quarantined and moves to an investigation queue.
6. Link, Never Replace, a Replacement Serial
A replacement unit needs its own serial history. Customer service creates a new replacement order or transaction and links it to the original order and return authorization.
Record:
- Original serial
- Replacement serial
- Original sale
- Return authorization
- Replacement reason
- Approval
- Replacement ship date
- Final disposition of the original unit
Never overwrite the original serial with the replacement serial. The original unit may go to Repair, Refurbish, supplier return, or Scrap. The replacement unit becomes Shipped only after its own shipment scan.
For a wider process view, see inventory replacement workflows.
Test Whether Your Serial Tracking System Is Working
A serial number tracking system is useful only if it can reconstruct a unit’s path without manual detective work.
Run this test before rollout and once each month:
- Receive one serialized unit against a purchase order.
- Move it to a second bin or warehouse.
- Pick and ship it against a sales order.
- Process a return for that serial.
- Ship a replacement with a new serial.
- Search both serials and export their histories.
The history should show the receipt, supplier, locations, transfers, order, customer, shipment, return, replacement, current status, users, and timestamps.
Ask your software provider to perform that exact test in a live environment. A serial field alone is not enough. The transaction history must survive each handoff.
Fix the Mistakes That Break Traceability
The most damaging serial tracking errors happen when teams separate the physical move from the system transaction.
Receiving by quantity first: If a team receives 20 units and adds serials later, the system cannot prove which units were present at receipt. Capture the serial during receipt.
Using free-text locations: “Back room” or “temporary shelf” cannot support a reliable search. Use the actual warehouse, zone, bin, or service location.
Returning stock directly to Available: A returned unit may be authentic but unsuitable for resale. Put it in Quarantine until inspection records its disposition.
Overwriting a replacement: Replacing one serial with another erases the customer and warranty chain. Link original and replacement serials instead.
Skipping the destination scan: A source-side transfer record proves only that a unit left. The destination confirmation proves where it arrived.
Treating a dashboard as an audit trail: A dashboard can show totals. A traceability investigation needs transaction-level records, including who performed each action and when. Use a traceability requirements checklist to test that evidence.
Choose the Right Setup for Your Operation
Start with the SKUs that create the most costly exceptions: high-value equipment, warrantied devices, repairable goods, or items prone to return fraud. Pilot the SOP with one receiving area and one fulfilment team before extending it to every warehouse.
Set one owner for exceptions. The owner should review duplicate serials, units stuck In Transfer, unmatched returns, and open replacement cases each day. Run the monthly traceability test with a serial selected at random.
At Arka, we support lot and serial tracking alongside barcode-based receiving, warehouse operations, inventory allocation, and multi-warehouse visibility. Our Enterprise plan includes Sales Orders, Lot/Serial Tracking, Landed Cost and BIN tracking with flexible pricing. Explore Arka’s lot and serial tracking when you want to map this SOP to a Salesforce-based inventory workflow.
FAQs
Can I Use a Manufacturer Serial Number Instead of Creating My Own?
Yes. Use the manufacturer serial when it is unique, readable, and printed on every unit. Create an internal serial only when the manufacturer serial is absent, unreliable, or insufficient for your internal process.
Keep the manufacturer serial even if you add an internal identifier. Customer service and suppliers often search by the serial printed on the unit.
Can a Barcode and a Serial Number Be Different?
Yes. A barcode is a machine-readable format, while a serial number is the unit identifier stored in the record. One barcode may encode a serial, GTIN, lot, and expiry data.
Keep the barcode value and serial value separate if your system captures both. That makes rescans and exception investigations easier.
Can One Product Have Both a Lot and a Serial Number?
Yes. Use the lot to identify the shared production or receipt group and the serial to identify one unit within it. This setup is useful when a unit-level warranty record must also retain batch provenance.
Store the lot relationship on each serialized unit. That relationship supports both unit investigations and lot-based recalls.
How Do I Import Existing Serials from a Spreadsheet?
Import serials only after cleaning duplicate values, missing SKUs, invalid locations, and unclear statuses. Map each serial to its SKU, opening location, available status, receipt reference where known, and current condition.
Run a physical count on a sample before making imported stock available. Then test a transfer and shipment before the first live order.
What Should a Serial History Report Show?
A useful report shows the serial, SKU, current status, current location, receipt, supplier, transfers, shipment, customer, returns, replacements, users, timestamps, and exception reasons. The report should let an operator search by serial and reach the linked transactions.
If a team cannot retrieve those records from one search, the workflow has a missing capture point.
