WMS and ERP Pallet Management: Tracking License Plates and Tier Locations

The number of units, cases, or sellable packs loaded on a pallet.

Pallet Quantity is the number of units, cases, or sellable packs loaded on a pallet, and modern warehouse systems track it most reliably by assigning each pallet a license plate number (LPN). The LPN acts like a digital identity for the pallet, linking the quantity, SKU, lot, expiration date, condition, owner, and location in the WMS while the ERP maintains the broader financial, purchasing, and sales record. When this architecture is set up correctly, a warehouse can see exactly what is on a pallet, where it sits in reserve racking, whether it is available for picking, and when it should be moved to a pick face for replenishment.

For beginners, the easiest way to understand this is to separate the physical pallet from the system record. A pallet on the receiving dock may contain 48 cases of one SKU, 24 cases each of two SKUs, or several sellable inner packs depending on the operation. The WMS does not simply record “one pallet.” It records the pallet quantity by unit of measure and attaches that record to an LPN barcode that warehouse staff scan at receiving, putaway, movement, replenishment, picking, cycle counting, and shipping.

How Pallet Quantity Fits Into WMS And ERP Architecture

The ERP and WMS usually have different responsibilities. The ERP is commonly the system of record for purchase orders, sales orders, item master data, costing, inventory valuation, customer ownership, and invoicing. The WMS is usually the operational system of record for dock activity, bin locations, pallet IDs, task execution, replenishment, picking status, and inventory availability inside the facility.

Pallet quantity must flow between these systems without losing detail. For example, the ERP may tell the WMS that purchase order 4500123 includes 960 cases of a beverage SKU. The WMS receives those cases as 20 pallet LPNs of 48 cases each, or perhaps 19 full pallets and one partial pallet. The ERP may only need to know that the purchase order was received and inventory is available, while the WMS must know every pallet’s exact quantity and location.

This split is why good integration design matters. If the ERP only sees total inventory and the WMS sees pallet-level detail, the two systems must reconcile at agreed points such as receipt confirmation, inventory adjustment, shipment confirmation, and cycle count posting. Poor integration creates common problems: pallets that physically exist but are not system-available, inventory that appears in the ERP but cannot be located in the WMS, or replenishment tasks that fail because the system does not trust the pallet quantity in reserve.

What The System Must Track

A pallet-level WMS record needs more than a quantity field. The LPN should carry enough information to make correct storage, replenishment, compliance, and shipping decisions. At minimum, the system should know the item, quantity, unit of measure, location, status, and ownership. In regulated or date-sensitive operations, it also needs lot code, serial number, expiration date, country of origin, production date, and hold status.

• LPN ID: The unique barcode or identifier assigned to the pallet, carton pallet, or palletized handling unit.
• SKU And Unit Of Measure: The item number and whether the pallet quantity is measured in eaches, inner packs, cases, layers, or full pallets.
• Quantity On Pallet: The current number of units, cases, or sellable packs tied to the LPN after receipts, moves, picks, adjustments, or replenishments.
• Bin Location: The exact dock door, staging lane, reserve rack slot, pick-face location, or outbound door where the pallet is stored.
• Inventory Status: Whether the pallet is available, damaged, on quality hold, allocated to an order, in transit within the building, or pending count.
• Product Attributes: Lot, expiration date, temperature requirement, hazmat class, stackability, rotation rule, or customer-specific handling rule.

These data points allow the WMS to make decisions without relying on tribal knowledge. A receiver scans a pallet once, prints or applies the LPN label, confirms the pallet quantity, and the system can then direct the pallet through the rest of the warehouse. If the pallet is later split, the WMS should either reduce the original LPN quantity or create a child LPN for the partial quantity moved elsewhere.

Dock Intake And Receiving

Pallet quantity tracking begins at dock intake. When inbound freight arrives, the receiving team validates the shipment against an advance ship notice, purchase order, transfer order, or blind receipt process. The WMS should prompt the receiver to confirm SKU, quantity, pallet condition, lot details if required, and any discrepancy such as overage, shortage, or damage.

At this stage, the system may create one LPN per physical pallet. For a uniform inbound load, this can be fast: scan the item, enter or confirm 50 cases per pallet, apply 20 LPN labels, and close the receipt. For mixed-SKU pallets, the WMS must support pallet detail records with multiple inventory lines under the same LPN or force the operator to break the pallet into separate LPNs depending on operational policy.

Good receiving design prevents downstream confusion. If the WMS records 60 cases on a pallet but the actual pallet has 54, putaway, replenishment, and order allocation will all be wrong. The goal is not just to receive inventory quickly; it is to create accurate LPN records that match the physical pallet quantities entering the building.

System-Directed Putaway And Bin Allocation

After receiving, the WMS should assign the pallet to an appropriate location. System-directed putaway uses item rules, pallet quantity, dimensions, weight, velocity, storage type, zone, and availability of open bins to recommend a reserve rack slot or forward pick location. This reduces travel time and prevents operators from placing pallets wherever space appears open.

Bin location allocation depends heavily on clean master data. The WMS must know how many cases fit on a standard pallet, how tall the pallet is, whether it can be stacked, and which rack levels can hold the weight. A pallet quantity of 80 small cartons may fit safely in a high reserve bay, while a pallet quantity of 12 heavy drums may require floor storage or a lower rack position.

Tier locations, such as rack levels A, B, C, and D, add another layer of control. Fast-moving SKUs are often stored in lower or easier-to-access tiers, while slower-moving pallets can go higher in the rack. The WMS should understand these tier rules so a forklift operator receives a clear task: move LPN 000453218 from receiving lane RCV-03 to reserve location A12-B-03, rather than relying on verbal instructions or handwritten notes.

Reserve Racking And Inventory Visibility

Reserve racking is where pallet quantity tracking becomes especially valuable. A warehouse may have thousands of pallets stored above or behind the pick face. Without LPN-level visibility, the operation may know it has 10,000 cases in the building but not know which rack locations contain full pallets, partial pallets, or inventory on hold.

With LPN tracking, supervisors can search by SKU, lot, customer, expiration date, or available quantity. They can see that a full pallet of 72 cases is in reserve slot C05-D-02, a partial pallet of 18 cases is in C05-A-01, and another pallet is on quality hold in inspection. This matters for rotation rules such as FIFO and FEFO, where the oldest or earliest-expiring inventory should be used before newer stock.

Inventory visibility also improves exception handling. If an operator scans the wrong location, attempts to move the wrong LPN, or tries to pick from a pallet on hold, the WMS can stop the transaction. The system becomes a control layer between physical activity and inventory accuracy.

Pick-Face Replenishment

Pick-face replenishment moves inventory from reserve storage into forward picking locations where selectors fill orders. The WMS should monitor minimum and maximum quantities for each pick face and generate replenishment tasks when inventory falls below the trigger point. Pallet quantity is central to this process because the system needs to know whether a full pallet, partial pallet, case quantity, or split quantity should be moved.

For example, a pick face may hold 36 cases, while reserve pallets arrive with 72 cases each. If the pick face drops to 8 cases, the WMS may direct a forklift driver to bring one LPN from reserve, replenish 28 cases into the pick face, and leave 44 cases on a new or remaining reserve LPN. More advanced systems can manage this through partial pallet moves, child LPN creation, or directed decanting into a forward location.

Replenishment rules should also consider order demand. If a wave is about to require 200 cases, the WMS may trigger multiple replenishments before picking begins. This prevents selectors from reaching an empty pick face, stopping the line, or waiting for a forklift during peak activity.

Common Configuration Mistakes

Many pallet tracking issues come from weak configuration rather than weak software. One common mistake is treating pallet quantity as a fixed number when inbound pallets vary by supplier, product, or trailer build. Another is allowing operators to move inventory without scanning both the LPN and the destination bin, which breaks the link between quantity and location.

• Missing Unit Conversions: If eaches, inner packs, cases, and pallets are not mapped correctly, the WMS may replenish or allocate the wrong quantity.
• Loose Location Controls: Allowing unconfirmed moves creates inventory that appears in one bin but physically sits in another.
• No Partial Pallet Process: Picking from reserve without splitting or updating the LPN causes inflated pallet quantities.
• Poor ERP-WMS Timing: Delayed receipt or shipment messages can make one system show inventory before the other is updated.
• Weak Exception Workflows: Damage, shortages, overages, and holds need clear transaction codes so inventory stays accurate.

Practical Controls For Better Pallet Management

A strong pallet management process uses both system rules and disciplined floor execution. Operators should scan the LPN and location at every movement point, including receiving, putaway, replenishment, consolidation, staging, and shipping. Supervisors should review open tasks, negative inventory warnings, aging pallets, and location mismatches daily.

Cycle counting should be designed around LPNs as well as locations. Instead of only asking whether a bin contains the right SKU, the count should confirm which LPNs are present and what quantities they hold. This approach catches hidden problems such as swapped pallets, unrecorded partials, and reserve pallets that were moved during a rush without proper confirmation.

For 3PLs and multi-client warehouses, LPN-level control is even more important. The same SKU may be owned by different merchants, subject to different allocation rules, or stored under different customer accounts. A pallet quantity record must therefore identify not only what product is present, but also whose inventory it is and whether it can be used for a specific order.

In short, the pallet quantity becomes operationally useful when it is tied to an LPN, controlled by bin-level WMS transactions, synchronized with the ERP, and visible from dock intake through reserve storage and pick-face replenishment. The physical pallet may look simple, but the system record behind it is what keeps inventory accurate, available, and ready to ship.