Start with the traceability question
Before adding tracking fields, write the question that a future colleague must answer. Which particular device was supplied to this customer? Which group of goods came from a particular delivery? Those questions need different records. A serial number distinguishes an individual unit. A lot number groups units. Neither label by itself proves regulatory compliance, product safety or the accuracy of a supplier’s claim. This guide helps prepare a software evaluation; regulated products or formal recall obligations require appropriate specialist advice.
Compare the work created at each handoff
A fictional tool reseller may need a serial identifier for warranty returns. A box of identical replacement washers may need only a product identifier and quantity. Recording every washer separately would create work without answering a useful business question. Conversely, one aggregate quantity cannot identify which device was returned. Map receiving, storage, picking, returns and counting before deciding. The required identity should remain understandable across those steps, rather than appearing on the purchase screen and disappearing when goods leave the building.
Verify the product and plan boundary
The merchant’s lot documentation describes lot-aware receiving and counts, but that does not mean every product edition or plan includes every capability. Confirm the exact tracking mode, barcode format, units and export fields for your use case. Ask the vendor to demonstrate one partial receipt and one return with the proposed identifiers. Inspect the exported result. Avoid treating a general feature tick as proof that your scanning device, existing labels or customer requirements will work without changes. Preserve unresolved compatibility questions in the buying brief.
Use a small case to decide whether the effort is justified
Create a fictional acceptance case before loading live data: two deliveries of the same product, one customer shipment and one return. Specify what should remain distinguishable after each event. If the team cannot say why that distinction matters, simplify the requirement. If the distinction is essential, do not accept a workaround that loses it. The right outcome is a repeatable record that answers the original question. More tracking fields are not automatically better inventory control, especially when people cannot consistently collect them at the point of work.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- inFlow lot numbers and expiry dates — Merchant documentation · inflowinventory.com · Merchant-controlled · checked 2026-09-24
- inFlow software product comparison — Merchant documentation · inflowinventory.com · Merchant-controlled · checked 2026-09-24