Back to blog
Inventory Management

What Is a License Plate Number (LPN) in a Warehouse?

October 2, 2026· Updated November 17, 2026

Walk into most small warehouses and ask where a certain lot is. Someone will open a spreadsheet, then walk the aisles to check. A license plate number exists to end that walk. It gives every pallet, case, or tote of stock its own ID, so the system knows exactly what is on it and where it sits.

This guide explains what an LPN is and how it differs from the other numbers in your warehouse. It covers when LPN tracking is worth the effort, how labels and scanning work day to day, and the mistakes teams make when they start.

What a license plate number is

A license plate number, or LPN, is a unique ID given to one physical unit of stock. That unit is usually a pallet, but it can also be a case, a tote, or a drum. The LPN is printed as a barcode label and fixed to the unit, the same way a car carries a plate.

Behind the label is a record. That record says which SKU is on the unit, how much of it, which lot, and which location it is in. When someone scans the label, they see the whole record. When someone moves the unit and scans its new location, the record updates.

The idea is simple. Instead of tracking stock only as a total per SKU, you track it as a set of physical units that each have an address. Your on-hand total is still there. It is just the sum of the plates.

How an LPN differs from a SKU, a lot, and a location

New teams often mix these four up, because they appear on the same screen. Each one answers a different question.

  • SKU: what the product is. A SKU is a product definition, such as a 25 kg bag of a certain whey protein. Thousands of units can share one SKU.
  • Lot: which production run or supplier batch the stock came from. A lot ties units to a shared history, which is what you need for an expiration date or a recall.
  • Location: where something sits. A location is a fixed place, such as rack A, level 01, position 02. It does not move, and it can hold many units.
  • LPN: which physical unit this is. An LPN names one unit of stock. It moves from location to location, and it carries its SKU, lot, and quantity with it.

A simple way to keep them straight: the SKU is the what, the lot is the which batch, the location is the where, and the LPN is the this one. Many systems hold a plate to one SKU and one lot, because mixing lots on a plate makes every later question harder.

Swift WMS follows that rule. A plate holds one SKU and lot quantity at one location, so a pallet that arrives with two lots on it becomes two plates. That one rule keeps lot records clean from the dock to the shipment.

When LPN tracking is worth it

LPN tracking adds a step. Someone has to print and apply a label, and someone has to scan it on every move. In some operations that step pays for itself many times over, and in others it is overhead. It is usually worth it when:

  • You handle lots and expiration dates, as most food, supplement, and cosmetics operations do.
  • The same SKU sits in more than one place, so a SKU total does not tell anyone where to go.
  • You store stock that your clients own and need to show each one exactly what is theirs.
  • You need to answer recall questions by lot, down to the pallet.
  • Pallets get split, partly used, or combined, and your counts drift as a result.
  • Stock moves between storage, staging, and production during the day.

On recalls in particular, a plate per unit is what lets you say exactly which pallets of a lot are still in the building. Our guide on how to run a mock recall shows how to test that before a real recall tests you.

LPN tracking may not be worth it for a small stockroom with a handful of SKUs, one location each, and no lot control. If one person can see every item from one spot, a plate per unit adds labels without adding answers. Many growing manufacturers cross that line as they add SKUs, lots, and customers.

How LPN labels work

An LPN label needs very little. It carries a barcode that encodes the plate ID, with the same ID printed below it in plain text. Some teams also add the SKU, lot, and expiration date in large print, so a forklift driver can read it from the seat. The barcode is the part the system needs; the rest is for people.

Print the label at receiving, before the stock leaves the dock. A pallet that reaches the rack without a label is a pallet the system cannot see. Put the label on the same face of every pallet, at the same height, so nobody has to hunt for it with a scanner.

Locations need labels too. A plate scan says what the unit is, and a location scan says where it went. Without both, a move is just a guess typed into a box. Our guide to warehouse location naming covers how to build location codes that people can read and scanners can trust.

In Swift WMS, each plate has a print label action that produces its barcode, and each location has its own printable label. When you receive a delivery against a receiving order, which needs Core or the Receiving + POs add-on, you can print all of the labels for that delivery at once.

Choosing an LPN barcode system

People shopping for an "LPN barcode system" are usually choosing four things: a numbering rule, a barcode type, a printer, and a scanner. None of them needs to be fancy.

  • The LPN number. Use a format that is unique and never reused, for example a short prefix and a running number. Keep it short enough to type if a label is torn. Do not build the SKU or lot into the number. Those belong in the plate's record, where they can be read and corrected.
  • The barcode type. Most warehouses print internal LPNs as Code 128 barcodes, which hold letters and numbers and scan quickly. If a retail customer asks for pallet labels to its own standard, that is usually a GS1 SSCC in a GS1-128 barcode. Treat it as a separate shipping label, not as your internal plate ID.
  • The printer. A thermal label printer at the receiving desk prints labels that stay readable on stretch wrap. Keep it where plates are created, so nobody carries a pallet away to label it.
  • The scanner. A handheld keyboard-wedge scanner works with most browser-based systems with no setup, because it types each scan like a keyboard.

The best LPN barcode system is the one your team uses on every move. A basic scanner that gets used every time beats a better one left on the charger.

How scanning works, step by step

Scanning is what turns labels into live inventory. A typical life for a plate looks like this:

  1. Receive. The receiver scans or enters the SKU, then records the quantity, the lot, and the expiration date. The system creates a plate, and the plate gets its label.
  2. Put away. The driver scans the plate, then scans the location label on the rack. The plate now has an address.
  3. Move. When stock moves to staging or to another rack, the same two scans record the move.
  4. Split. When only part of a plate is needed, the part that moves goes onto a new plate with its own label. The rest stays on the old plate.
  5. Adjust. If a count finds a different quantity, the plate is adjusted with a reason that explains the change.
  6. Ship. The plate, or part of it, is scanned out and leaves the building with its lot recorded on the shipment.

Most warehouses scan with handheld devices or tablets. A common setup is a keyboard-wedge scanner, which types the barcode into whatever field is open, like a very fast and very accurate keyboard. Swift WMS supports this in Floor Mode, a large-text browser view for Receive, Move, Ship, and Lookup.

The receiving step deserves the most care, because every mistake made there travels with the plate. Our warehouse receiving best practices go through it in more detail.

Common LPN mistakes

Most LPN problems are not software problems. They are habits that creep in during a busy week and then become the way things are done. Watch for these:

  • Mixing lots on one plate. It feels faster at the dock, but it breaks every trace afterward. Give each lot its own plate.
  • Labeling after putaway. If the label goes on later, the stock is invisible in the meantime, and someone will move it.
  • Skipping the location scan. A plate with an old location is worse than no plate, because people trust it.
  • Reusing plate numbers. An LPN should mean one unit, once. Reusing IDs mixes two histories into one.
  • Typing instead of scanning. Hand-typed IDs bring back the errors that scanning was meant to remove.
  • Adjusting without a reason. A quantity change with no reason cannot be checked later, so make the reason required.
  • Leaving split remainders unlabeled. Every new plate needs its own label the moment it exists.

Each of these is easy to fix with a short rule and a supervisor who checks it for the first few weeks. Write the rules down and post them at the dock, where the habits form.

Practical takeaway

An LPN is a small idea: one label, one unit, one record. Its value comes from discipline. Label at the dock, keep one lot per plate, scan every move, and give every adjustment a reason. Do those four things, and your system can tell you where stock is, which lot it is, and how much is left, without anyone walking the aisles.

Start small if you need to. Choose one product family or one customer, label it on receipt, and run it alongside your current method for a few weeks. To see how plates, locations, and Floor Mode fit together in one system, read about license plate inventory tracking in Swift WMS.

How Swift WMS does itLicense plate inventory tracking