Tracking Cases on Pallets: Do You Need Nesting?
November 20, 2026
Software that handles nested tracking is usually a warehouse management system with parent and child containers, where a pallet ID holds case IDs and each case holds units. Many teams do not need that much nesting, and a simpler model of one record per pallet of one SKU and one lot keeps lot traceability intact with far less scanning.
This guide explains the packaging levels you will meet, the two main ways software models them, when true nesting is worth the labor and when it is not, and how to keep lots traceable when cases come off a pallet. Near the end, we explain honestly how Swift WMS handles it, including what it does not do.
Units of measure and packaging levels
Most physical products move through a ladder of packaging levels. The names change from plant to plant, but the ladder looks like this:
- Each: the single unit a consumer buys, such as one bottle of capsules or one bag of granola.
- Inner pack: a small bundle of eaches inside a case, such as a shrink-wrapped six-pack. Not every product has one.
- Case: the shipping carton, such as 12 bottles or 4 inner packs. Cases are what people lift by hand.
- Pallet: a stack of cases, wrapped and moved by forklift, such as 80 cases in 8 layers of 10.
Each level is a unit of measure. The relationship between levels is a conversion: 12 eaches to a case, 80 cases to a pallet. Software that “handles units of measure” usually means it can store those conversions and let people receive in cases, count in eaches, and ship in pallets while it does the math.
Before you compare systems, write your own ladder down for your top products. Note which levels you actually handle. A supplement co-packer may receive raw material in drums and bags, then ship finished goods in cases on pallets. An ingredient warehouse may never break a pallet at all. The ladder you really use decides how much tracking you need.
Two ways software models a pallet
There are two broad models for tracking stock above the each level. Both are legitimate. They trade detail for labor.
Model one: nested parent and child containers
In a nested model, every container is its own record, and records point to the container they sit in. A pallet has an ID. Each case on that pallet has its own ID and a link to the pallet. In the deepest setups, each inner pack has an ID and a link to its case.
The pallet ID is often a GS1 SSCC, an 18-digit Serial Shipping Container Code printed on a GS1-128 pallet label. Cases may carry their own serialized labels. When the pallet ships, the receiver scans one SSCC and the system knows every case inside it.
This model shines when the contents of a pallet differ case by case, or when a trading partner requires a case-level manifest. It also lets you answer “which pallet was case 4471 on?” without guessing.
Model two: one record per pallet of one SKU and one lot
In the simpler model, a pallet is one record, often called a license plate. The record says which SKU is on it, which lot, how many units, and where it sits. There is no separate record for each case. The case count is just the quantity divided by the case size.
If you are new to plates, our explainer on what a license plate number is covers the basics. The key rule is that a plate holds one SKU and one lot. That rule is what keeps traceability simple. If you know the plate, you know the lot, and every unit on it shares the same history.
For most manufacturers, the lot is the level that matters for a recall. Regulators and customers ask which lots went where. They rarely ask which numbered carton went where, unless the product is serialized. A plate per pallet answers the lot question directly.
When true nesting is worth the scanning labor
Nesting is not free. Every case that gets its own ID needs a label printed and applied, and a scan every time it joins or leaves a pallet. On a line packing 40 cases a minute, that adds up fast. Nesting is usually worth it when:
- A major retail customer requires SSCC pallet labels with an electronic manifest of the cases inside.
- You build mixed pallets often, with several SKUs or lots on one pallet that ships as a unit.
- Your product is serialized, so each case or each unit must be traceable on its own.
- Cases are high value, and a missing case triggers a claim you must prove or disprove.
- Your customers return partial pallets and you need to know exactly which cases came back.
When nesting is not worth it
Nesting is often overhead when:
- Most pallets hold one SKU from one lot, which is common for both raw materials and finished goods from a single run.
- Recalls and customer questions are asked by lot, not by carton.
- Cases leave the building in round numbers on orders you already record by lot.
- Your team is small, and every extra scan competes with production work.
A practical test: list the last ten traceability questions anyone asked you. If every one of them was answered by “which lot, how much, where did it go,” you probably do not need case-level IDs. If several needed a specific carton, nesting may earn its keep.
Handling mixed pallets
Mixed pallets are where the two models differ most. A pallet with three SKUs, or one SKU from two lots, cannot be one plate in a one-SKU, one-lot model. It becomes several plates that happen to share a physical pallet.
That works fine in practice if you are disciplined about it. Give each SKU and lot group its own plate and its own label, and put all of the labels on the same face of the pallet. Store and move the plates together. When the pallet ships, ship each plate. The lot record stays clean because no plate ever mixes lots.
What you give up is the single scan. In a nested model, one SSCC scan moves everything on the pallet. In the plate model, you scan each plate. For a pallet with two or three groups, that is a few extra seconds. For a pallet with thirty SKUs, it is a real cost, and it is a sign that nesting may suit you better.
Splitting a pallet
Pallets get broken all the time. Production needs 20 cases, a customer orders 15, or a damaged layer has to come off. How the software handles a split decides whether your counts stay right.
In a nested model, you scan the cases that leave, and the system removes their link to the pallet. In a plate model, you split the plate. The cases that leave go onto a new plate with its own ID and label, and the original plate’s quantity goes down by the same amount.
Either way, the rule is the same: the stock that moves must get its own identity before it moves. An unlabeled stack of cases sitting next to the rack is the most common way counts drift. Our guide to cycle counting versus physical inventory covers how to catch the drift that slips through anyway.
How lot traceability survives cases leaving a pallet
The worry behind the original question is usually traceability. If cases come off a pallet, do you lose track of which lot they were?
You do not, as long as two things are true. First, every container carries exactly one lot. Second, every split creates a new record that inherits that lot. When a new plate is split from an old one, it carries the same SKU and lot by definition, because it came from a plate that had only one. When cases ship, the shipment records the lot. The chain from receipt to customer stays unbroken.
Traceability breaks in three common ways:
- Cases are pulled without a split, so the system still thinks they are on the pallet.
- Leftover cases from two lots are stacked onto one pallet and recorded as one lot.
- Shipments record the SKU and quantity but not the lot.
Each of these is a process gap, not a software gap. Close them with a rule at the point of work, and a mock recall will show whether the rule held.
How this works in Swift WMS
Swift WMS uses the plate model. It does not nest containers. There is no parent pallet record that holds child case records, and Swift does not print SSCC pallet labels. If you must send case-level SSCC manifests to a retail partner, Swift is not the right tool for that part of the job, and you should plan for it separately.
Here is what Swift does do, on every plan:
- A license plate holds one quantity of one SKU and one lot at one location. A pallet that arrives with two lots becomes two plates.
- Each plate has a printable barcode label, and each location has its own label, so moves are scanned, not typed.
- Plates can be split. You enter the quantities for the new plates, Swift creates their IDs, and the original plate goes down by the split amount.
- A split plate remembers the plate it came from, and it has a Return to parent action that puts the stock back on the original plate.
- Plates can be combined, but only when they share the same lot. Swift will not merge two lots onto one plate.
- Plates can be moved, moved in bulk, adjusted with a required reason, and shipped in full or in part.
- Each plate has its own history of what happened to it.
Units of measure in Swift are simple. Each SKU has one unit of measure, such as eaches or pounds, and plate quantities are in that unit. Swift does not convert plate quantities between eaches, cases, and pallets, so you cannot receive in cases and have the plate convert to eaches. Teams choose the unit they count in and stay with it.
Case size does appear in production, which needs Core. When you build a bill of materials, the box component carries a units per case figure, and a work order can print case labels that show the item, lot, expiration date, and units per case. A finished product spec sheet can also record the pallet pattern, such as cases per layer and layers per pallet. Those are documents and labels for people and customers. They are not separate tracked records in inventory.
For lot questions, Lot Trace and Recall Impact are part of Quality on Core. Lot Trace shows which plates a lot went into and where they shipped. Recall Impact finds downstream lots and shipped destinations and can hold the impacted lots. Because no plate ever mixes lots, those answers hold up after a pallet has been split many times. The lot traceability page shows how they fit together.
So how do teams model a pallet of cases in Swift? Most use one plate per pallet, with the quantity in eaches or cases, whichever they count in. When cases leave for production or a customer, they split the plate, label the new plate, and move or ship it. Mixed pallets become one plate per SKU and lot, with all labels on the same face.
The takeaway
Nested tracking sounds thorough, and for serialized goods, mixed retail pallets, and SSCC manifests it is the right answer. For most small manufacturers and co-packers, the question customers and regulators ask is about lots, not cartons. One plate per SKU and lot, a split every time stock leaves a pallet, and a lot on every shipment will answer that question with far less scanning.
Write down your packaging ladder, check what your customers actually require, and pick the simplest model that answers your real questions. To see plates, splits, and labels in practice, read about license plate inventory in Swift WMS.
