How to Capture and Sell Serialized Items
Serials entered after the sale are too late for stock and warranty
Receivers skip serials to “catch up later,” then stock and warranty history never match.
Cashiers sell by quantity and invent serials on the invoice printout.
Delivery notes ship reserved lots while the wrong serial leaves the dock.
Why this happens
- No mandatory capture on inbound for TrackSerial items.
- Outbound stock mutations that only take quantity.
- Sales orders that reserve batch lots but never serials.
- Returns that create new serials instead of restoring Sold units.
Biznsbook addresses this through mandatory serial capture on receipt, sale and POS serial picker, SO reserve and DN ship when the Inventory module is licensed — each sellable unit is an ItemSerial from receipt through sale, return, and warranty lookup.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Capture and Sell Serialized Items
Built for retailers and distributors who sell warranty-bearing units one serial at a time in Biznsbook — not company Tracked Assets.
- Receive with exact serial count. On GRN or Fast Receive, after quantity, capture serials (scan or type; comma or newline). Count must equal whole units.
- Post the receipt. Posting creates InStock ItemSerial rows at the receipt unit cost and writes ledger SerialNumber.
- Sell or ship with the picker. On Sale, POS, or Delivery Note, select available serials. Quantity-only outbound fails with a clear error.
- Confirm warranty on sale. Mark sold sets WarrantyExpiryDate from sale date plus warranty months when configured.
- Reserve on sales orders. Store reserved serials on the SO line; confirm reserves them; cancel releases them.
- Ship via delivery note. Posted DNs pass ReservedSerialNumbers into stock out so the same units leave inventory.
- Process returns carefully. Return restores the sold serial to InStock without resetting the warranty clock.
Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: No mandatory capture on inbound for TrackSerial items. Repeating this each month usually shows up first in warranty accuracy and unit-level stock identity.
- Mistake 2: Outbound stock mutations that only take quantity. Repeating this each month usually shows up first in warranty accuracy and unit-level stock identity.
- Mistake 3: Sales orders that reserve batch lots but never serials. Repeating this each month usually shows up first in warranty accuracy and unit-level stock identity.
- Mistake 4: Returns that create new serials instead of restoring Sold units. Repeating this each month usually shows up first in warranty accuracy and unit-level stock identity.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Receive with exact serial count — On GRN or Fast Receive, after quantity, capture serials (scan or type; comma or newline).
- Post the receipt — Posting creates InStock ItemSerial rows at the receipt unit cost and writes ledger SerialNumber.
- Sell or ship with the picker — On Sale, POS, or Delivery Note, select available serials.
- Confirm warranty on sale — Mark sold sets WarrantyExpiryDate from sale date plus warranty months when configured.
- Reserve on sales orders — Store reserved serials on the SO line; confirm reserves them; cancel releases them.
Teams that capture serials on every receipt, pick them on every sale, and use serial lookup for support keep warranty answers aligned with stock.
How Biznsbook supports this workflow
mandatory serial capture on receipt is documented in Biznsbook Inventory capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
sale and POS serial picker is documented in Biznsbook Inventory capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
SO reserve and DN ship is documented in Biznsbook Inventory capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Serial capture on GRN, sale pickers, and lookup are permission-separated so dock staff manage receipts while support only needs View Inventory.
Suggested implementation timeline
- Week 1: Document current process gaps and configure mandatory serial capture on receipt with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using ops tip and leadership dashboard.
Scan discipline on the dock
Prefer scan over type for IMEI and long serials. When typing is unavoidable, require a second operator to read the last four characters aloud before post. Duplicate serials for the same item and company are rejected at create time.
Fast Receive and GRN share the same integrity rule: serial count must equal whole-unit quantity. Partial serial lists are not allowed because they create orphan warehouse quantity without identity.
Sales order to delivery note continuity
When customers reserve specific units, store those serials on the sales order line and confirm the order so units move to Reserved. Delivery notes should ship the reserved list — picking a different InStock serial at ship time breaks the customer promise and warranty linkage.
Canceling an SO releases reserved serials back to InStock so other sales can pick them. Leaving cancelled orders reserved is a common cause of “serial available in warehouse but not in picker” tickets.
Returns and write-offs
A sale return restores the same serial to InStock and keeps WarrantyExpiryDate. Do not invent a new serial for a returned unit — that breaks recall and warranty history.
Stock adjustments that write off serial-tracked quantity should mark serials WrittenOff so they never reappear in available pickers or valuation of sellable stock.
Metrics to track monthly
- Serial-tracked items with TrackSerial enabled
- GRN lines posted with serial count matching quantity
- Sales and POS lines with serial picker selections
- Serial lookup searches by support staff
- Active warranty rows on the warranty expiry report
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook mandatory serial capture on receipt and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Inbound | ❌ Optional comments field | ✅ Mandatory serials = qty |
| Outbound | ❌ Quantity-only sale | ✅ Serial picker required |
| SO → DN | ❌ Hope warehouse remembers | ✅ Reserved serials on the line |
| POS | ❌ Manual after checkout | ✅ Validated before stock out |
| Return | ❌ New serial invented | ✅ Same serial → InStock |
| Write-off | ❌ Hide in adjustment notes | ✅ Status WrittenOff permanently |
Ops tip
After a busy receiving day, open the item serial register and spot-check that InStock count matches warehouse on-hand for that SKU. Sample ten posted sale lines weekly against the serial register until mismatch rate stays near zero, then widen serial SKU coverage.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
What if I typed the wrong serial on GRN?
Correct before post when still draft. After post, use controlled adjustment/write-off paths — do not invent a second identity for the same unit.
Can Fast Receive skip serials?
No. Once TrackSerial is on, Fast Receive requires the same one-per-unit capture as GRN.
Do kit sales need serials?
Only for components that are serial-tracked. Pass those serials when selling the kit.
Are recalled serials selectable?
No. Active recall blocks outbound sale and DN for those serials the same way as recalled batches.
What happens if POS omits serials?
Checkout stock posting fails for TrackSerial items. Capture serials on the POS line before completing payment.
How this differs by industry
Retail
POS associates pick scanned serials at checkout so warranty cards match the unit that left the shelf.
Wholesale & distribution
DC pickers reserve serials on sales orders and ship the same list on delivery notes.
Manufacturing
Spare-part counters capture serials on receipt and issue them on sales or DNs without a shop-floor serial MES in this phase.