Mixed palletising is the most critical step in warehouse order preparation: building a single pallet from items that differ in size, weight and strength, to obtain a stable, well-filled and traceable load unit. It is also the last warehouse step that is still manual, and almost always the only one nobody measures.
This guide explains what mixed palletising is, which technical constraints a mixed pallet must meet and how the dedicated modules of WMS software act on the composition of the load unit.
What is mixed palletising
Mixed palletising is the building of a pallet containing several different items, intended for the same order or the same customer. It differs from homogeneous palletising, in which the pallet contains a single item. It requires handling different sizes, weights and strengths at the same time while keeping the load unit stable and traceable.
In the warehouse this activity is also called pallet build or mixed build, and in distribution people speak of a mixed pallet or rainbow pallet. They are the same process: turning a set of picked cases into a single logistics unit that is identified and ready to ship.
The difference from homogeneous palletising is not one of degree but of nature. A single-item pallet is built by applying a pattern defined once in the item master data. A mixed pallet requires a new decision for every order: which cases go at the bottom, which at the top, how to split the load if the order does not fit on one pallet.
Homogeneous and mixed palletising: the differences
A homogeneous pallet contains a single item and, as a rule, a single batch. The stacking pattern is defined once in the item master data and remains valid for every subsequent order. The dominant constraint is layer fill, the risk of error is low and traceability stays simple, because there is one batch for the whole pallet. The software just applies a standard pattern. This is the typical configuration for stock shipped to distribution centres.
A mixed pallet, on the other hand, contains several items and almost always several batches. The pattern has to be recalculated for every order and the dominant constraint shifts to the stacking sequence and the compatibility between cases. The risk of error rises to medium-high levels, traceability requires the batch to be recorded at the level of each individual case, and the software has to do much more than apply a pattern: it has to calculate the composition and sequence the picking accordingly. This is the configuration for multi-item customer orders and delivery rounds.
There is a third configuration, the delivery-round pallet, which contains goods for several customers served by the same trip. On top of the complexity of the mixed pallet it adds a sequence constraint: loading a vehicle works on a last-in-first-out basis, so the goods for the first customer to be unloaded must be loaded last.
Where palletising fits in the warehouse flow
Palletising sits downstream of picking and upstream of packing and goods dispatch.
The distinction between the two steps is decisive in operational terms. Picking answers the question of which cases to pick and by what route; palletising answers a different, later question: how those cases become one or more compliant load units.
They are activities with different objective functions. Picking is optimised on the distance travelled, palletising on the geometry and stability of the load. When they are treated as a single undifferentiated activity, optimising one systematically degrades the other: picking optimised only on the route delivers cases in the order dictated by the warehouse map, not in the order in which they need to be stacked.
This is the technical reason why mixed palletising has to be managed upstream, within the picking logic, and not at the end as a separate activity.
Which constraints a mixed pallet must meet
A mixed pallet is compliant when it meets five families of constraints at the same time. They are competing constraints: optimising on just one leads to non-compliance on the others.
Weight and height of the load unit
The weight limit is not a universal value. It depends on the load capacity of the pallet used, the capacity of the destination racking, the handling equipment and the customer’s requirements. The GS1 Italy guidelines on deliveries to warehouses set requirements both on the overall weight of the load unit, which must be related to the load capacity of the pallet used, and on the load allowed per layer.
The height limit depends instead on the vehicle’s load space and on any double stacking. Both limits should be defined as system parameters for each combination of pallet type and destination, not left to the operator’s visual judgement.
Overhang and footprint
Goods must not overhang the perimeter of the pallet. The prevailing size reference in Europe is the 800 × 1,200 mm EPAL Euro pallet: this is why manufacturers tend to size their packaging as submultiples of 800 and 1,200, reducing the space wasted on each layer.
Stacking sequence and crushability
The operating rule is well known, heavy and rigid at the bottom, light and crushable on top, but it can only be applied if the cases reach the station in the right sequence. Otherwise the operator piles them on the floor and rebuilds, or stacks them sub-optimally.
Product compatibility and batch constraints
In regulated sectors, composition is subject to separation constraints: food and non-food, allergens, products that give off odours, chemical incompatibilities. On top of this comes traceability: a mixed pallet typically contains several batches, and if the system records the batch only at order level, reconstruction in the event of a recall becomes impossible. FEFO logic must therefore be maintained and recorded during pallet building too.
Loading sequence
For pallets destined for multi-customer rounds, the building order must be the reverse of the unloading order. It is a constraint the warehouse can only meet if it knows the delivery sequence at the moment it builds the pallet.
What are the pallet stacking patterns
The stacking pattern determines how cases are arranged on each layer and how the layers relate to one another. The choice directly affects the stability and strength of the load.
In column stacking, cases are aligned vertically, corner on corner. This pattern offers the highest compression strength, because the load bears on the edges, the structurally strongest part of the case. In return it has low lateral cohesion and requires more effective stretch wrapping or strapping.
The interlocking pattern, also called brick stacking, staggers and rotates the layers like the courses of a brick wall. It gains lateral stability and withstands transport stresses better, but reduces vertical compression strength, precisely because the load no longer bears on the edges.
The choice between the two is not a matter of style: it depends on how much lateral stress the load will undergo in transport and how many pallets will be stacked on top of each other in the warehouse. It should be set as a parameter by product family, not decided case by case by the operator.
What are the most common mistakes in mixed palletising
- Building by guesswork: weight or height over the limit discovered at the loading bay, with the whole load unit having to be rebuilt.
- Unsequenced picking: cases arriving in an order incompatible with stacking, piled on the floor and handled twice.
- Uncontrolled fill rate: orders that generate one pallet more than necessary, with a direct impact on transport costs.
- Unmanaged “remainder” pallet: the surplus that does not complete a pallet is left without identification or location.
- Batches not recorded at case level: traceability broken at exactly the point where goods leave the plant.
- Load unit not uniquely identified: without a unique code, the link between what was shipped and what was documented can only be reconstructed on paper.
- Load overhang: cases sticking out beyond the pallet perimeter, with the risk of damage and rejection at goods-in.
How WMS software optimises mixed palletising
WMS software acts on mixed palletising through dedicated modules that turn a discretionary step into a guided, verified process.
Case and load unit master data
The prerequisite for any optimisation is that the system knows the objects it is putting together: case dimensions and weight, cases per layer, layers per pallet, crushability class, stackability, permitted pallet type. Without this foundation, every subsequent logic works on estimates.
Advance pallet calculation and order splitting
Starting from the order lines, the WMS determines before picking begins how many load units are needed and how to distribute the cases. The operator receives a mission that is already sized. This is where fill rate is recovered: the decision is made by the system with a complete view of the order, not by the operator once building has already started.
Picking sequenced according to stacking
The module reorders the picking missions so that cases reach the station in the correct stacking sequence: heavy, rigid base first, light, crushable top last. The route is optimised under the stacking-sequence constraint, not by ignoring it. This is the clearest difference between a WMS that manages picking and one that manages the load unit.
Real-time weight and volume checks
With every case assigned, the system updates the cumulative weight and volume and flags when the threshold is being approached, before it is exceeded. Non-compliance is caught during building, when the cost of correction is one case, not at the bay, when it is the whole pallet.
SSCC load unit identification
When the pallet is closed, the WMS generates the unique identifier and the logistics label. The reference standard is the SSCC (Serial Shipping Container Code), the 18-digit code that uniquely identifies a single logistics unit, carried in GS1-128 symbology.
The GS1 Italy guidelines are precise on a point that matters for mixed palletising: when several pallets are shipped as a single unit, each one must still have its own SSCC, with a master label applied to the outside of the group packaging. Adopting the standard is not a formality: it is often a contractual requirement in large-scale retail.
Traceability: case, batch, pallet, order
Each case is confirmed by barcode when it is assigned. The system builds the chain that links item, batch, load unit, order and delivery note, updating stock levels at the same time and making the shipment traceable months later.
Integration with ERP and production
The data feeds the generation of packing lists and delivery notes (DDT, the Italian transport document) in the ERP without manual re-entry. Where the warehouse supplies production directly, integration with the MES software makes it possible to build load units linked to specific production orders.
What changes compared with manual building
The difference can be read activity by activity. In manual palletising the number of pallets per order is decided as you go, while with the WMS it is calculated upstream on the complete order. The sequence in which cases arrive is dictated by the picking route in the first case, by the stacking sequence in the second. Weight and height checks move from visual, with verification at the bay, to progressive, with the threshold flagged before it is exceeded.
Everything to do with checks and documentation changes just as much. Contents are spot-checked, when they are checked at all, versus barcode confirmation of every single case assigned. Identification moves from an internal label, where there is one, to the SSCC with a GS1-128 label. Batch traceability rises from order level to case level on the load unit. And documents are no longer filled in by hand but generated directly from the building data.
How to calculate the number of pallets needed for an order
The calculation is carried out in five steps, which a WMS automates on the whole order before picking starts.
- Retrieve the master data for each item in the order: case dimensions, weight, cases per layer, maximum layers, stackability class.
- Determine the load unit limits for the destination: maximum permitted weight, maximum usable height, pallet type.
- Calculate the total volume and weight of the order by adding up the cases line by line.
- Distribute the cases across the pallets while respecting the stacking sequence, product compatibility constraints and weight and height limits.
- Check the resulting fill rate and assess whether a different distribution reduces the number of load units.
The fourth step is what separates a theoretical calculation from a usable one: an algorithm that optimises only volume produces pallets that are geometrically full but unstable or non-compliant with separation constraints.
Which KPIs measure the efficiency of mixed palletising
- Average building time per load unit: from the first assignment to closing the pallet. It is the basic figure for sizing workstations.
- Volume fill rate: volume occupied relative to the usable volume of the pallet. It has a direct impact on transport cost per unit shipped.
- Weight fill rate: weight loaded relative to the permitted limit. Read together with volume fill rate, it distinguishes volume-limited loads from weight-limited ones.
- Rebuild rate: percentage of pallets rebuilt after closing. It is the most diagnostic indicator: a high value signals constraints that have not been set as parameters in the system.
- Load unit accuracy: correct cases out of the total assigned. It correlates directly with delivery complaints.
- Pallets completed per labour hour: always to be read together with accuracy, never on its own.
Conclusions
Mixed palletising is the last point at which the warehouse can correct a mistake before it becomes a complaint, and it is also the point at which you decide how much it will cost to transport that order.
Treating it as a manual appendix to picking means giving up two concrete levers: the fill rate of load units and the traceability of goods at the moment they leave the plant. Managing it with dedicated modules within the WMS means setting the constraints once, enforcing them on every pallet and having measurable data on a step that today, in most warehouses, produces no data at all.




