Automated storage systems: plan goods and flows
Pallet storage, tote storage and systems for long or differently packaged goods are different projects. Compare the required process before selecting a machine. Decide whether the first order is a feasibility study or an operational installation. Goods, building and interfaces need assessment before quotes become comparable.
Define the goal and scope first
Is the project a new warehouse, an expansion or replacement of manual storage? Describe receiving, storage, picking and dispatch as one flow. A storage component does not automatically include conveyors, picking stations or building work. Expansion needs an inventory of existing equipment, retained functions and transitions.
Describe load units, not just product names
State pallets, totes, cartons or special loads with known dimensions and weights. Overhangs, unstable packaging and different bases affect handling. Mixed goods need capacity allocated by load type; one total cannot size the system. Temperature, hygiene and hazardous contents need early clarification without copying business secrets into the initial request.
| Load unit | Useful for planning |
|---|---|
| Pallets | Dimensions, weight, base and overhang |
| Totes or cartons | Formats, stability and contents |
| Mixed or special goods | Allocation, exceptions and handling |
Separate capacity from peak throughput
How many load units must fit at once, and how many put-away or retrieval movements are needed in a peak hour? Stock and movements are different measures. Record normal flows, order mix and seasonal peaks. If target values are missing, commission their assessment first. Evaluate promised throughput against an agreed mix, simultaneous operations and test conditions.
Check the building and installation early
Usable height, footprint, columns, floor capacity and routes constrain the layout. Surveying and structural assessment are separate tasks; estimated hall dimensions do not replace them. Clarify installation access, power, escape routes and building adaptations. In an operating warehouse, plan protected work areas, temporary storage and agreed interruptions.
Plan material and data flows together
Storage must work with inventory, orders and neighbouring equipment. Give only general names of existing warehouse or business software. Assign responsibility for interfaces, test data, stock migration, licences and updates. Credentials and real customer datasets belong in an agreed project process, not the initial quote comparison.
Include safe operation and fault access
Moving loads, transfer points and maintenance access need coordinated protection. Agree responsibilities, instructions, training and the evidence required for the actual system. Changes must assess effects on existing protective functions. A brochure or isolated inspection does not replace assessment of the real installation; customers need not select a safety standard themselves.
Compare investment and ongoing costs fully
Compare equivalent capacity, performance and system boundaries. Racking, machinery, conveyors, software, building adaptations and commissioning may be allocated differently. Itemise maintenance, spares, licences and support separately. Consumption and savings forecasts need operating assumptions. A low equipment price alone does not establish the lowest total cost or a fixed payback period.
| Cost area | Clarify in the quote |
|---|---|
| Equipment and building | Boundaries, connections, fitting and adaptations |
| Software and startup | Interfaces, tests, data migration and training |
| Ongoing operation | Licences, maintenance, spares and support terms |
Agree phases and acceptance before ordering
Start with load profiles, targets and a site visit, followed by an agreed concept, firm boundaries and a confirmed implementation plan. Define tests using representative loads, handling of unsuitable loads and transition from the old operation. Record outstanding items, training and service start. Future expansion needs concrete provision in capacity, building and software.
- Before comparing. Collect load types, target capacity, peaks and existing systems.
- Before implementation. Agree boundaries, responsibilities, interruptions and tests.
Frequently asked questions
Must I select a particular storage technology?
No. Load profiles and processes are enough initially; the supplier should justify suitable options.
Is storage capacity the same as hourly throughput?
No. Units held at once and movements per hour are separate targets.
Can an existing building be used?
After assessment. Height, footprint, capacity, routes and installation access must suit the system.
Is software integration automatically included?
Not automatically. Agree interfaces, migration, testing and ongoing licences explicitly.
Does automation guarantee savings?
No. Benefits and costs depend on utilisation, processes and the actual scope.
What is enough for an initial request?
Site, goods and load units, known target capacity, processes and existing systems. No credentials or mandatory files.
