An automated pallet racking system can increase storage capacity and reduce some manual pallet movements, but the highest-density design is not automatically the most productive. The right choice depends on how quickly pallets must move, how many different products are stored, whether stock rotation must follow FIFO, and how the system fits the building and existing warehouse processes. Compare the full pallet journey—from receiving and storage to retrieval and dispatch—not just the number of pallet locations. A system that stores more but creates queues at its lifts, conveyors or dispatch area can constrain the operation it was meant to improve.
The term covers more than the rack itself. An installation may combine the storage structure with cranes or shuttle carriers, conveyors or transfer cars, pallet inspection points, control software and connections to warehouse or enterprise systems. The degree of automation varies: some setups automate movement deep inside a rack while workers still load pallets at the aisle; others coordinate storage and retrieval through a largely automated flow.
That distinction matters when comparing proposals. Ask which movements are automated, where people or forklifts still handle pallets, and what happens when a pallet cannot proceed. A highly automated storage aisle may still rely on manual checks, replenishment or dispatch work at its edges.
Different technologies solve different problems. Use the table as a starting point, then assess each option against your pallet mix, peak workload and building constraints.
| System type | How pallets move | Often suitable for | Main constraint to assess |
|---|---|---|---|
| Unit-load crane AS/RS | A crane travels along a storage aisle to place and retrieve pallets. | Planned, repeatable flows where automated handling across rack height is useful. | Crane aisles, transfer points and equipment availability can shape overall throughput. |
| Automated shuttle-based storage | Shuttles carry pallets through storage channels, with lifts or transfer equipment serving levels and aisles. | Dense storage of suitable pallet groups with coordinated automated transfers. | Channel design, shuttle allocation and transfer capacity need to match the required flow. |
| Semi-automated pallet shuttle | A forklift places a shuttle in a lane; the shuttle moves pallets within that lane. | Businesses seeking deeper lane storage while reducing forklift travel into rack channels. | Forklifts still serve the lane face, and lane access and stock rotation depend on the design. |
| AGV or AMR pallet handling | Automated vehicles transport pallets between defined pickup and drop-off points. | Operations needing automated transport between processes or a layout that may change. | Routes, crossing traffic, hand-off points and vehicle charging can affect flow. |
These categories can also be combined. For example, a shuttle or crane storage area may connect to automated vehicles or conveyors that move pallets to production, picking or dispatch. Each additional interface is a place where capacity, controls and exception handling must be planned.
Storage capacity answers how many pallets can be held. Throughput answers how many pallets the system can receive, store, retrieve and hand over within the operating period that matters. A design can perform well on the first measure and poorly on the second if several processes depend on one constrained aisle, lift, conveyor or staging point.
Build the assessment around actual movement requirements. Separate inbound put-away, outbound retrieval, replenishment and any production or cross-docking flows. Then consider when they overlap. Average daily volume can hide a busy dispatch window or a receiving period that competes for the same equipment.
Do not treat a supplier’s headline capacity as a guarantee of end-to-end performance. Request the assumptions behind any throughput estimate: pallet characteristics, travel distances, task mix, operating schedule and the performance of connected equipment. The answer should cover the whole process, not just the movement speed of one crane or shuttle.
Automation depends on repeatable load units. Before selecting a system, document pallet dimensions, total loaded height, weight, overhang, load stability and condition. Include variations rather than relying on the most common pallet alone. A unit that is damaged, poorly wrapped or outside the agreed profile may need to be rejected or corrected before it enters automated equipment.
Inventory characteristics matter just as much. A small number of products stored in large quantities may suit deep-lane storage, while many products with modest quantities may need more direct access to individual pallet positions. Faster-moving products may also need locations near suitable transfer points, subject to the system’s operating rules.
Check stock rotation requirements before choosing channel depth. FIFO (first in, first out) and LIFO (last in, first out) are not interchangeable: the rack configuration and access arrangement determine how pallets can be loaded and retrieved. If product age, batch tracking or expiry control matters, confirm how the proposed layout supports those rules and how the warehouse software will enforce them.
An automated pallet racking system must fit the usable building, not just its floor area. Measure clear height and available width, and account for columns, doors, loading areas, service access and the routes pallets need to take before and after storage. Consider floor condition and load capacity, as well as the location of power, data connections and other building services.
In New Zealand, site-specific structural, seismic and fire design should be reviewed by appropriately qualified professionals against the requirements that apply to the project. Do not assume an existing warehouse or rack arrangement can simply accept a new automated installation. The project team should also establish how fire protection, maintenance access and emergency arrangements work with the proposed layout.
Draw the full material flow on a plan. Mark receiving, inspection, storage, replenishment, picking, consolidation and dispatch, then show the interfaces between them. A compact storage block may leave too little room for pallet staging or create crossing traffic around the infeed. Those problems can reduce the benefit of automation even when the rack itself operates as designed.
Controls determine how tasks are assigned and how the equipment communicates. Clarify how the automated system will connect to the warehouse management system (WMS), warehouse control system (WCS) or other software in use. Establish which system records inventory location, releases work, prioritises tasks and reports faults. Responsibility for each function should be clear before commissioning.
Exception handling deserves specific attention. Ask what happens when a pallet fails an inspection, a label cannot be read, stock data does not match the physical load, or a destination is unavailable. The design should provide a defined route for resolving these cases rather than allowing exceptions to block normal operations.
Discuss recovery and maintenance with the people who will run the warehouse. Find out how faults are reported, what access technicians need, how a failed component affects nearby processes and what manual procedures are available. A system that is difficult to recover can create a bottleneck even if its normal operating flow is well designed.
Capital cost is only one part of the decision. A fair comparison should include the rack and handling equipment, building changes, software integration, safety provisions, installation, testing, training and commissioning. Ongoing costs may include planned maintenance, replacement parts, energy, technical support and the staff needed to manage exceptions and keep the system operating.
Ask suppliers to state what is included and what is excluded, and compare proposals using the same operating assumptions. Consider the cost of disruption during installation, the consequences of downtime and the resources needed to support the equipment over its working life. If the business expects changes in product mix, throughput or storage policy, ask how expensive or difficult it would be to adapt the layout.
Automation may reduce some manual pallet movements, but it does not remove the need for labour across receiving, quality checks, inventory control, maintenance and dispatch. Base any labour or productivity benefit on the tasks that will actually change in your operation, rather than assuming every manual role disappears.
No. It can improve storage and pallet movement when its capacity and interfaces match the operation, but a poorly balanced design may create queues at lifts, conveyors or staging areas. Assess end-to-end flow and exception handling alongside storage density.
Not necessarily. In a semi-automated arrangement, a forklift may still place and retrieve the shuttle at the lane entrance, while the shuttle moves pallets inside the channel. Fully automated shuttle installations add handling equipment and controls to perform more of the transfer process.
Compare the required access pattern, pallet mix, storage depth, throughput and building layout. A crane-based system retrieves pallets along defined aisles; shuttle systems move pallets within channels and depend on their lifts and transfers. The suitable choice depends on the task profile and complete system design, not a single density measure.
Some designs can accommodate a defined range, but the acceptable limits must be specified and verified for the equipment. Record the actual pallet and load variations, and ask how out-of-profile units are detected and diverted before they cause a blockage or handling problem.
Confirm the throughput assumptions, pallet specifications, building work, software scope, safety and maintenance arrangements, commissioning tests and exclusions. Make sure the proposal explains how the system handles exceptions and what operational support is available when equipment is unavailable.
The strongest automated pallet racking system is the one that fits the warehouse’s pallet profile, inventory rules and movement requirements without overwhelming its transfer points. Compare complete configurations, validate assumptions with operating data, and include building, software, safety and ongoing support in the decision. Before committing, test the proposed flow from receiving through dispatch and agree how the system will perform when normal conditions change.
