Warehouse identification
LPN Barcodes: What a License Plate Number Is and How to Use One
An LPN barcode is a unique identifier for a physical handling unit — a pallet, tote, carton or cage — rather than for the products inside it. Scanning the label returns whatever your system currently says is on that unit, so one scan moves everything on it at once instead of counting each item again.
That single idea is what separates a warehouse that scans once at receiving from one that recounts the same pallet at putaway, at replenishment and again at the pick face. This guide covers what goes on the label, how LPNs differ from SKU barcodes, where they earn their keep, and when a smaller operation genuinely does not need them yet.
What does LPN stand for?
LPN stands for License Plate Number. The name is borrowed from vehicles on purpose: a car's plate does not describe the car, it points at a record that does. An LPN works the same way. The barcode carries an identifier and nothing else, and every fact about the unit — what is on it, how much, which lot, where it sits — lives in the warehouse system against that number.
This is why an LPN survives change. Repack the pallet, move it to another aisle, allocate half of it to an order, and the label never has to be reprinted. Only the record behind it changes.
What is actually encoded in an LPN barcode?
Less than most people expect. A well-formed LPN encodes a single unique number, usually rendered in Code 128 or GS1-128 symbology because both handle long numeric strings densely and are read reliably by inexpensive scanners.
The formal version of this is the Serial Shipping Container Code, an 18-digit GS1 key designed to identify a logistics unit uniquely worldwide. If your pallets leave your building and enter someone else's network, an SSCC is the identifier they will expect. If they only ever move inside your own four walls, an internal sequence works and costs nothing to issue.
LPN barcode vs SKU barcode: what is the difference?
A SKU barcode answers what is this. An LPN barcode answers which one is this. They operate at different levels and a working warehouse uses both.
Scanning a SKU on a loose carton tells the system the item is a size-9 boot. It cannot tell you which of the four hundred boot cartons in the building you are holding, where it came from, or which lot it belongs to. An LPN makes the physical unit itself addressable, which is what allows a system to reserve, move or count it without ambiguity.
| SKU barcode | LPN barcode | |
|---|---|---|
| Identifies | A product type | One physical unit |
| Uniqueness | Shared by every unit of that product | Never reused |
| Changes when repacked | No | No, the record changes instead |
| Answers | What is it | Which one is it, and what is on it now |
Where does an LPN earn its keep?
The value shows up at every point where a unit changes hands or location. One scan replaces a count.
Receiving
A pallet arrives, you confirm what is on it once, and the system issues an LPN. From that moment the pallet is a known quantity. If the supplier sent an advance ship notice, the LPN can be matched to it and the receipt becomes a confirmation rather than a data-entry exercise. Our guide to what an ASN is in a warehouse management system covers that handshake in detail.
Putaway
The operator scans the LPN, then scans the location. Two scans record that an entire pallet of mixed lots now lives in aisle 4, bay 12. Without a license plate, that same move is one scan per SKU and a mental note about quantities, which is where discrepancies enter the record.
Picking and replenishment
When a full unit moves to the pick face, the LPN moves with it and the system knows the contents travelled too. For anything less than a full unit, the system decrements against the plate. This is the difference between pick and pack that reconciles at the end of the day and pick and pack that reconciles continuously.
Cycle counting
Counting by license plate turns an audit into a verification. Instead of counting every item in a bay, an operator confirms the plates present and the system compares that against what it expected. Discrepancies narrow to a specific unit rather than a whole location.
What should be printed on the label?
The barcode is the functional part, but the human-readable block beside it is what stops errors when a scanner fails or a label is damaged. A usable LPN label carries the number in both machine and human form.
- The barcode itself, in Code 128 or GS1-128, sized so it can be read from the distance an operator actually stands at rather than the distance a designer imagined.
- The number in plain digits underneath, so it can be typed when a scanner will not read it.
- Received date and supplier, which turn a mystery pallet into a traceable one without a lookup.
- A short contents summary for the common case where the unit holds one SKU. Resist printing quantities that will change.
Anything that goes stale should stay off the label. A printed quantity that no longer matches the record is worse than no quantity at all, because people believe labels.
Do you need LPNs if you run a small warehouse?
Often not yet, and it is worth being honest about the threshold. LPNs pay for themselves when units move more than once. If stock arrives, gets put in one place, and is picked from that same place until it is gone, a license plate adds a printing step and removes very little work.
The signals that you have crossed the line are specific: you hold the same SKU in more than one location, you replenish a pick face from bulk storage, you receive mixed pallets, or you need lot traceability. Any one of those means somebody is currently keeping track in their head, and that is the cost an LPN removes. Until then, a well-run warehouse stock management system with location-level accuracy is usually the better next step.
How should you structure the number itself?
The best LPN scheme carries no meaning at all. That instinct feels wrong the first time, because a number that encodes the year, the dock door and the supplier looks more useful on a label. It stops being useful the moment any of those facts changes, and the number then actively misleads whoever reads it.
A meaningless sequence has one job: to be unique forever. Everything else belongs in the record, where it can be corrected. If you want the label to be readable at a glance, put the human-readable facts in the text block beside the barcode rather than inside the number.
Internal sequences
For units that never leave your building, a simple incrementing number with a short prefix is enough. The prefix is worth having only to distinguish an LPN from a SKU or order number at a glance, so that a mis-scan is obvious rather than silent.
GS1 SSCC
For units that enter someone else's network, the SSCC exists precisely so that two companies never issue the same identifier. It is built from your GS1 company prefix plus a serial reference and a check digit, which is what makes it globally unique without any coordination between trading partners.
What hardware do you actually need?
Less than vendors suggest. The scanner matters less than the label. A poorly printed barcode defeats an expensive imager; a clean one is read by a cheap handheld first time, every time.
The practical constraints are print quality, label adhesive suited to the surface and temperature, and enough quiet zone around the barcode for the scanner to find its edges. Thermal transfer printing survives cold storage and abrasion better than direct thermal, which fades. If pallets pass through a freezer or sit outside, that choice matters more than anything on the scanner spec sheet.
Beyond that, the question is ergonomic rather than technical: can an operator scan a plate on a pallet at floor level, and at the top of a rack, without putting anything down. Answering that honestly usually decides between a handheld, a ring scanner and a truck-mounted unit faster than any comparison table.
How do LPNs support lot and serial traceability?
This is where license plates stop being a convenience and start being a compliance mechanism. An LPN is the join between a physical unit and the batch history of what is on it.
When lot numbers are recorded against the plate at receiving, every subsequent movement inherits that association automatically. A recall then becomes a query rather than an investigation: the system already knows which plates carried the affected lot, where each one went, and which orders drew from them. Without that link, tracing the same lot means reconstructing movements from paperwork.
The same mechanism handles expiry. Because the system knows what is on each unit and when it arrived, first-expiry-first-out picking is a rule it can enforce rather than a discipline the team has to remember. For operations handling food, cosmetics or anything with a shelf life, this is usually the argument that justifies the whole exercise.
What does implementation actually involve?
Less disruption than most teams expect, provided it is sequenced properly. The work divides into a decision, a setup and a habit.
The decision is the numbering scheme and whether you need SSCC. The setup is label design, printer placement at the receiving dock, and confirming your system can hold handling units. The habit is the part that takes real time: operators have to scan the plate at every move rather than working from memory on familiar stock, and that consistency is what determines whether the data stays trustworthy after month three.
Plating on movement rather than in one pass is what keeps the transition calm. Existing stock earns a plate the next time it is touched, new receipts are plated from day one, and within a normal turnover cycle the whole building is covered without a shutdown.
What goes wrong with LPN barcodes in practice?
Most failures are procedural rather than technical, and they repeat across operations of every size.
Reusing numbers
An LPN must never be reissued. The moment a number is reused, historical movement becomes ambiguous and traceability breaks retroactively. Sequences are cheap; exhaust them rather than recycle them.
Printing quantities that change
A label that says forty-eight units becomes a lie the first time somebody picks from the pallet. Print what is stable, keep what moves in the system.
Labelling at the wrong moment
A plate applied before the unit is confirmed records an intention rather than a fact. Issue the LPN when the contents are known and agreed, which in most operations is the end of the receiving check rather than the start of it.
Nesting without modelling it
Cartons on a pallet, each with its own plate, is a legitimate and useful pattern. It only works if the system understands the parent-child relationship. Where it does not, scanning the pallet misses the cartons and inventory drifts quietly.
One label, two barcodes
Leaving the supplier's barcode next to yours invites the wrong scan. Cover it, or place your label where theirs is not.
How do LPNs fit with the rest of the system?
An LPN is only as useful as the record behind it, which means the value sits in the warehouse system rather than the label. The barcode is an index; the system is the book.
That is worth saying plainly because LPN projects sometimes start at the printer. Numbering scheme, label stock and scanner choice are the easy decisions. The one that determines whether any of it works is whether your system can hold a handling unit as a first-class object, track its contents over time, and let a single scan act on all of them. If it cannot, printing plates produces stickers rather than accuracy. Our overview of warehouse inventory management systems covers what to look for.
Frequently asked questions
Is an LPN the same as an SSCC?
Not quite. An SSCC is a specific 18-digit GS1 standard for identifying a logistics unit, and it is one valid way to issue an LPN. An LPN is the general concept: any unique identifier for a handling unit. Every SSCC is an LPN; not every LPN is an SSCC.
Can one LPN hold more than one SKU?
Yes, and this is where license plates are most valuable. A mixed pallet with one plate lets a single scan move six products at once. The system holds the breakdown; the label does not need to.
What happens when a pallet is split?
The system decrements the original plate and, if the removed portion becomes its own handling unit, issues a new one. The original number is never reused for the new unit.
Do LPNs replace SKU barcodes?
No. They work at different levels and most operations scan both. The SKU identifies the product, the LPN identifies the unit it is travelling in.
What barcode symbology should an LPN use?
Code 128 for internal-only numbers, GS1-128 when the unit will be handled by other parties. Both encode long numeric strings compactly and are read by standard warehouse scanners.
How long should an LPN number be?
Long enough never to run out. An 18-digit SSCC is standard for external use; internally, a sequence with room for years of growth is the only requirement. Short numbers create the pressure to reuse them, which is the failure to avoid.
Do I need a WMS to use LPNs?
You need something that can hold a handling unit as its own record with contents attached. That is usually a warehouse management system, though some inventory platforms model it adequately. A spreadsheet cannot, because the relationship between a unit and its changing contents is the whole mechanism.
Can LPNs be applied to existing stock?
Yes, and the usual approach is to plate on movement rather than all at once. Stock that is already put away gets a plate the next time it is touched, which spreads the work across normal operations instead of stopping the warehouse for a labelling exercise.
Where this fits in a wider system
License plates solve one problem well: making a physical unit addressable so it can be moved, counted and traced in one action. They do not solve allocation, replenishment logic or order routing, and they are worth introducing only once the record behind them can carry the weight.
If you are working out whether your operation is at that point, these cover the neighbouring decisions:
Not sure whether you need license plates yet?
We build operational software for wholesale, distribution and warehousing, and the honest answer is often that a simpler change comes first. A short call is enough to work out which.
