Distribution
ERP
Field Service Management
Inventory Management
Warehouse Management
Serial Number Tracking: How to Track Serialized Inventory From Receipt to Service
Last updated: October 9, 2026 · Independent guide · We do not sell rankings or coverage.
Serial number tracking means recording the unique serial of every unit you handle at each point where it changes hands or status: when it arrives from the supplier, when it is picked and shipped, when the customer registers or claims warranty, when it comes back on an RMA, and when a technician services it. Done well, it tells you in seconds where a unit is, who has it and whether it is covered. For distributors and service companies, most of the work is making sure every ERP, warehouse and service transaction refers to the same serial record.
The serial number tracking process at a glance
- Set up the item master. Decide which items are serialized, which serial you record (manufacturer or your own), and when the system requires it.
- Capture serials at receipt. Scan every serial against the purchase order before the goods become available stock.
- Store and count by serial. Keep each serial tied to a bin and confirm it during cycle counts.
- Pick, pack and ship by serial. Scan the serial that physically leaves, and record it on the shipment and invoice.
- Start the warranty and record the installed base. Link the serial to the end customer, the ship or install date and the warranty terms.
- Handle returns by serial. Validate the serial on the RMA, confirm it at the dock and decide disposition.
- Service, repair and retire. Record every repair, part replacement, swap and scrap against the serial.
Who owns each stage
Serial data breaks down at handoffs, so name an owner for every stage. Adjust these roles to your organization.
| Stage | Responsible | Accountable / consulted | Record created |
|---|---|---|---|
| Item master setup | Inventory or ERP administrator | Operations manager; service manager consulted | Tracking code or serial class on the item |
| Receipt | Receiving clerk | Warehouse manager; purchasing informed of exceptions | Serial lines on the item receipt |
| Storage and counts | Warehouse staff | Inventory control lead | Serial by bin; count results |
| Pick, pack and ship | Pickers and packers | Warehouse manager; customer service informed | Serials on shipment, invoice and ASN |
| Warranty and installed base | Service coordinator | Service manager; sales consulted on end-customer details | Customer asset or service item with warranty dates |
| Returns | Customer service and receiving | Returns or quality manager; finance informed | RMA line with serial, inspection result, disposition |
| Service and retirement | Technicians | Service manager | Work order history, part swaps, scrap record |
Stage 1: Set up serialized items before the first receipt
Owner: your ERP or inventory administrator, with input from the service team. Inputs: the item list, supplier labeling practices and warranty terms. Output: items flagged as serialized with clear rules for when a serial is required.
Serialize items that are high-value, carry a unit-level warranty, get serviced in the field or fall under a regulation; handle low-value consumables by quantity or lot. Equipment distributors should usually record the manufacturer’s serial, because it is on the nameplate and the manufacturer’s warranty desk asks for it.
If your suppliers label with GS1 barcodes, the serial is carried in Application Identifier (21), which allows up to 20 characters (letters, digits and some symbols) and must be paired with a GTIN in AI (01) or (03), or with AI (8006) (GS1 Application Identifiers, no date shown). Two different manufacturers can use the same serial string, so your system should treat the item number plus the serial as the unique key.
Controls: settle the costing method at the same time. In Business Central, the Specific costing method gives each unit the exact cost at which it was received and “requires item tracking on both inbound and outbound transaction”; you can also use item tracking without the Specific method, in which case cost follows the costing method you select (Microsoft Learn, March 17, 2026). What goes wrong: turning serial tracking on after stock exists. Acumatica, for example, does not let you change the assignment method once there is stock, history or unreleased documents for items in the class (MYOB Acumatica Help, no date shown).
Stage 2: Capture serials at receipt
Owner: receiving. Inputs: the purchase order, the supplier’s packing list or advance ship notice, and the physical units. Output: a posted receipt with one serial per unit.
Receipt is the cheapest point to capture a serial, because the units are together and still boxed. NetSuite requires one serial per unit: “if you enter a quantity of 2, then you must enter two serial numbers” (NetSuite Help, no date shown). Acumatica’s Scan and Receive form prompts for the serial when the class uses the When Received method and the number is not generated automatically, and you can scan the serials one by one (MYOB Acumatica Help, no date shown).
Controls: scan rather than key serials; reject duplicates of an item-serial pair already in stock; compare scanned serials to the supplier’s ASN when one is sent; and hold units with missing or unreadable labels in a quarantine bin until someone reads the nameplate. What goes wrong: clerks receive the quantity and promise to “add serials later,” or scan the carton barcode instead of the unit serial. Acumatica’s When Used method defers capture to issue or shipment (same source as Stage 1), which is faster at the dock but gives up traceability back to the supplier.
Stage 3: Store and count by serial
Owner: warehouse staff, with an inventory control lead accountable for accuracy. Inputs: received serials and putaway locations. Output: every serial tied to a bin.
Moving a unit between bins should move its serial record with it. In Business Central, the SN Warehouse Tracking setting on the item tracking code must be on to assign serials in warehouse activities (Microsoft Learn, August 21, 2025).
Controls: count serialized items by serial, not by quantity, and resolve variances by finding the specific missing or extra serial. What goes wrong: quantities match but serials do not, because a picker grabbed the unit next to the one the system allocated.
Stage 4: Pick, pack and ship by serial
Owner: pickers and packers. Inputs: the sales order or transfer order. Output: a shipment, invoice and, where your customer requires it, an EDI 856 advance ship notice that list the serials that actually left.
You can let the system allocate a specific serial, or allocate only the quantity and scan the serial at pick or pack. NetSuite describes both: entering a specific serial designates that unit, while leaving it blank allocates quantity and lets you name the serial later (NetSuite Help, no date shown). Scan-at-pack is the safer default, because it records the unit actually in the box.
Controls: block shipment of a serial that is not in stock at that location, already shipped, or on quality hold; print serials on the packing slip and invoice so the customer has them. What goes wrong: serial swaps at pack-out, and serials recorded on the shipment but never copied to the invoice, which is the document your customer files.
Stage 5: Start the warranty and record the installed base
Owner: a service coordinator, with sales supplying end-customer details for dealer or contractor sales. Inputs: the shipment or installation record. Output: a customer asset (often called a service item or installed base record) holding the serial, the owner, the site, and warranty start and end dates.
Business Central can create service items automatically when you post a shipment, provided the item belongs to a service item group with Create Service Item selected, and it copies the serial from the item tracking lines to the service item card (Microsoft Learn, October 22, 2025). Its item tracking codes also include a Warranty Date Formula that sets the last day of warranty (Microsoft Learn, August 21, 2025).
Controls: decide which date starts the warranty (ship date, install date or the end customer’s purchase date) and apply it consistently. If you or your manufacturer offer a full warranty on consumer products, federal rules limit what registration can do: under 16 CFR 700.7, requiring the return of a registration card as a condition of a full warranty is an “unreasonable duty,” though you may suggest the card as one way to prove the purchase date (eCFR, 16 CFR 700.7, up to date as of October 5, 2026). What goes wrong: the serial stops at the distributor’s invoice and never reaches the end customer’s site, so a warranty call six months later starts with “who bought this?” Our guide to HVAC inventory management covers the contractor side of serialized equipment.
Medical device distributors face stricter rules. For devices under FDA tracking orders, distributors must promptly give the manufacturer the device identifier (the UDI, lot, batch, model or serial number), the date received and the source, and multiple distributors must produce records within 5 working days of a manufacturer request or 10 working days of an FDA request (eCFR, 21 CFR 821.30, up to date as of October 2, 2026).
Stage 6: Handle returns by serial
Owner: customer service issues the authorization; receiving and quality confirm and inspect. Inputs: the customer’s request with a serial. Output: an RMA line with the serial, an inspection result and a disposition.
The serial is your strongest control against bad returns. Before you approve, check that the serial was shipped by you, to this customer, and is inside the return or warranty window. At the dock, confirm the serial in the box matches the serial on the RMA. Our guide to RMA software covers credit memos, restocking fees and vendor returns in detail.
Illustration only: a customer returns a “failed” controller under warranty. The serial on the RMA matches your shipment, but the unit that arrives carries a different serial, one your records show you never sold. A dock check stops the receipt before any credit is issued.
Controls: no RMA without a serial for serialized items; receipt blocked if the serial does not match; disposition (restock, repair, return to vendor, scrap) recorded against the serial so its status is never ambiguous. What goes wrong: returned units are restocked under a new receipt with no link to their history, so the next customer receives a unit that has already failed once.
Stage 7: Service, repair and retirement
Owner: technicians, with the service manager accountable. Inputs: the customer asset record and work orders. Output: a complete service history per serial, including parts swapped and the final scrap or retirement.
Dynamics 365 Field Service keeps the service history of past and present work orders on each customer asset and supports parent-child assets, so a serialized component can sit under the unit it is installed in. It can also create an asset from a work order product marked Used when the work order is completed, but it creates only one customer asset regardless of the quantity on the line (Microsoft Learn, November 13, 2025). If a technician installs three serialized units on one line, you need to split the line or create the other assets yourself.
Controls: record both serials on every swap (the unit removed and the unit installed), and close the old serial with a status such as returned, repaired or scrapped. What goes wrong: advance replacements. You ship a new unit before the failed one comes back, the failed unit never arrives, and both serials sit open. The stakes are large: US-based manufacturers paid $30.37 billion in warranty claims in 2025, up 4% from 2024 (Warranty Week, April 16, 2026).
Metrics to track
| Metric | How to calculate | What it tells you |
|---|---|---|
| Serial capture rate at receipt | Serialized units received with a serial ÷ serialized units received | Whether receiving is deferring capture |
| Serial-level count accuracy | Serials found in the expected bin ÷ serials counted | Swaps that quantity counts hide |
| Installed base completeness | Shipped serials with an end customer and warranty start ÷ shipped serials | Readiness for warranty and service calls |
| RMA serial match rate | Returned units whose serial matches the RMA and your shipment history ÷ returned units | Return fraud and data errors |
| Open advance replacements | Count and value of replacement units shipped with no failed unit received after your set number of days | Cash and inventory at risk |
How software supports each stage
Microsoft Dynamics 365 Business Central covers stages 1 to 5 natively: item tracking codes, Specific costing, a warranty date formula and service items created on shipment. Test how your return orders validate serials before go-live.
Oracle NetSuite requires a serial per unit, supports specific or deferred serial allocation, and adds an Inventory Detail selector with Advanced Bin / Numbered Inventory Management. The serialized items page we reviewed does not cover installed base or field service, so plan for a connected service system.
Acumatica offers When Received and When Used assignment, issue methods such as FIFO and Sequential, scan-and-receive, and serial assignment for When Used items in field service appointments since its 2025 R1 release (MYOB Acumatica Help, no date shown). Decide the assignment method early, because it is locked once stock or history exists.
Zoho Inventory records serials on bills, invoices, transfer orders and adjustments once you enable it under Settings, Preferences, Items; Zoho says it is available only on selected plans (Zoho Inventory Help, no date shown). Its help page does not describe installed base or service history records.
Dynamics 365 Field Service handles stage 7, with the one-asset-per-line limitation noted above. For the broader ERP view of lot and serial controls in regulated manufacturing, see our article on lot and serial tracking in ERP.
How we researched this
We read the pages ranking for “serial number tracking” on October 9, 2026, from MRPeasy, Infios, Shipedge and Cleverence. All four are software vendors. They define serials and list benefits but say little about returns validation, warranty start rules, advance replacements or product limitations. We then reviewed vendor documentation from Microsoft, Oracle NetSuite, Acumatica (MYOB edition) and Zoho, GS1’s Application Identifier reference, the eCFR texts of 16 CFR 700.7 and 21 CFR 821.30, and Warranty Week’s 2025 claims data. No vendor paid for inclusion or reviewed this article.
Related guides
- Lot Tracking Software: How It Works and How to Choose
- Cycle Counting Software: Methods, Frequency and Tools
- Inventory Reconciliation: Count, Records and GL Tie-Out
Frequently asked questions
What is the difference between serial number tracking and lot tracking?
A serial number identifies one unit, while a lot number identifies a group of units made or received together. Serial tracking suits equipment with unit-level warranties and service histories. Lot tracking suits consumables where a recall covers a whole batch.
When should serial numbers be captured: at receiving or at shipping?
Capture at receiving whenever you can, because it links each unit to its supplier and purchase order and makes counts accurate. Some systems, such as Acumatica with its When Used method, let you capture at shipment instead. That is faster at the dock but loses traceability back to the supplier.
Do I need a warehouse management system to track serial numbers?
Not always. Business Central, NetSuite, Acumatica and Zoho Inventory all document serial capture on purchase and sales transactions within their inventory modules. A WMS or mobile scanning app becomes worthwhile when volume makes keying serials slow, or when you need serial checks enforced at every pick and pack scan.
How do serial numbers help with warranty claims?
The serial links a claim to the ship or install date, the customer and the unit’s repair history, so you can confirm coverage quickly and decline claims for units you never sold. For consumer full warranties, federal rules bar making a returned registration card a condition of coverage, so your own shipment record is often the proof of the start date.
What should happen to the serial when a unit is replaced in the field?
Record both serials on the work order: the one removed and the one installed. Update the customer asset to the new serial and give the old serial a status such as returned for repair or scrapped. Track advance replacements until the failed unit arrives.
Sources
- Microsoft Learn, Set up lots, serial numbers and package numbers for item tracking (Business Central), August 21, 2025. learn.microsoft.com
- Microsoft Learn, Design details: costing methods (Business Central), March 17, 2026. learn.microsoft.com
- Microsoft Learn, Create service items (Business Central), October 22, 2025. learn.microsoft.com
- Microsoft Learn, Assets in Dynamics 365 Field Service, November 13, 2025. learn.microsoft.com
- Oracle NetSuite Help, Serial Numbered Items, no date shown. docs.oracle.com
- MYOB Acumatica Help (Acumatica platform), Items with Lot and Serial Numbers: Tracking Settings, no date shown. help.myob.com.au
- MYOB Acumatica Help, Automated Operations with Lot- and Serial-Tracked Items: Receiving Items, no date shown. help.myob.com.au
- MYOB Acumatica Help, 2025 R1 release notes: support of stock items with lot or serial numbers assigned in appointments, no date shown. help.myob.com.au
- Zoho Inventory Help, Serial Number Tracking, no date shown (vendor). zoho.com
- GS1, Application Identifier (21) Serial number, no date shown. ref.gs1.org
- eCFR, 16 CFR 700.7, Use of warranty registration cards, up to date as of October 5, 2026. ecfr.gov
- eCFR, 21 CFR 821.30, medical device tracking requirements for distributors, up to date as of October 2, 2026. ecfr.gov
- Warranty Week, US warranty claims and accruals for 2025, April 16, 2026. warrantyweek.com
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
