AS/RS ROI & Payback Period

There is no universal AS/RS payback period

Current vendor evidence shows very different outcomes.

AutoStore currently cites:

• PUMA in Indiana: planned around five years, achieved payback in 12 months;
• a Forrester composite organization: 18-month payback and 79% ROI;
• THG in the UK: two-year payback;
• other customers with results below two years.

Yet another current AutoStore case, Pietsch, reports a much longer current payback with improvement as utilization and planned scale increase.

Those cases do not contradict each other.

They show that payback depends on:

• baseline labor cost;
• facility constraint;
• system utilization;
• volume growth;
• system price;
• what conventional capital is avoided;
• what new recurring costs are introduced.

Define the alternative before calculating ROI

Swisslog's current warehouse-automation business-case guidance makes this one of its central points: the same automation system can look very different depending on the comparison scenario.

A project that looks weak against “do nothing” can be financially strong when doing nothing is not actually available because inventory and volume are growing.

The simple AS/RS payback formula

The calculator above keeps one-time offsets and recurring savings separate.

Do not subtract avoided forklifts twice

Suppose the AS/RS allows a greenfield project to avoid purchasing $250,000 of conventional forklifts and rack.

That can reduce the initial capital gap once.

Then the annual model can separately include:

• forklift maintenance avoided;
• fuel/energy avoided;
• annual inspections;
• rental costs;
• related labor.

Do not count the $250,000 purchase as both an upfront offset and a yearly saving.

Labor is important—but Swisslog warns that it is not the whole return

Swisslog's current U.S. guidance identifies four broad value categories:

1. labor savings;
2. storage efficiency and facility avoidance;
3. capital-equipment offsets;
4. operational and strategic value.

That is a strong AS/RS-specific ROI structure.

Labor savings should include more than pickers

Time saved is not automatically cash saved

If AS/RS saves 10,000 walking and handling hours/year at $32/hour:

the arithmetic is $320,000/year.

But the business only receives the full economic value if those hours are captured through:

• lower paid hours;
• less overtime;
• less temporary labor;
• avoided hiring;
• measurably greater productive output.

The calculator uses a realization factor precisely because forecast labor capture is often less than 100%.

Facility avoidance can be the dominant AS/RS benefit

The important economic question is not the percentage.

It is what the released capacity prevents.

Examples:

• a second lease;
• external overflow storage;
• building expansion;
• multi-building duplication;
• additional material-handling equipment.

Do not call empty floor space a cash saving

Dense storage can create enormous operational value.

But if the warehouse:

• cannot sublease the released area;
• does not avoid expansion;
• has no alternative productive use for the area

then the entire theoretical rent value should not automatically appear as annual savings.

Use facility avoidance only when an actual cost or investment changes.

Swisslog recommends a lifecycle model much longer than simple payback

Swisslog's current automation-cost guidance recommends evaluating total cost of ownership over roughly a 20-year lifecycle rather than stopping at equipment payback.

Its recurring cost list includes:

• WMS/WCS/WES licensing;
• software support and upgrades;
• integration middleware;
• preventive maintenance;
• break-fix service;
• spare-parts inventory;
• maintenance staffing.

Simple payback is useful.

It is not a replacement for lifecycle economics.

The Forrester composite gives a useful—but vendor-sponsored—reference point

AutoStore also currently highlights:

• 50% labor savings worth $2.9 million over three years;
• 33% peak cost savings worth $451,073;
• theft-prevention benefits worth $539,901

for the composite analysis.

Those results should not become default values in another warehouse's model.

PUMA is a strong U.S. example of forecast versus realized payback

AutoStore currently says PUMA planned around a five-year return when it automated its Indiana distribution center.

The published result was 12 months.

AutoStore also says the site:

• handles more than 100,000 wholesale and e-commerce orders in the same day;
• covers more than 80,000 SKUs;
• operates at 99.8% accuracy.

Use the case to understand upside from strong utilization.

Do not use it as a guaranteed U.S. payback period.

THG shows the labor-cost mechanism clearly

AutoStore reports that THG achieved:

• a two-year ROI/payback;
• a 40% reduction in variable labor costs;
• an approximately 1.8 percentage-point reduction in distribution costs over two years.

THG also increased throughput and reduced the need for additional warehouse space.

This is a useful example of multiple benefit categories funding the same investment.

Pietsch is arguably the more educational payback case

AutoStore's current Pietsch case says:

• 65% of order lines now run through AutoStore;
• throughput doubled;
• the system uses 50% less space;
• headcount did not increase;
• current activity is around 3,300 bin presentations/day;
• the system was designed for 7,800/day;
• it is scalable to 11,200/day.

The same published case reports current payback around 7.5 years, with approximately 2.5 years possible if the business plan is achieved and under two years at greater scale.

This makes a crucial point:

the hardware can already be installed while the financial return is still waiting for planned volume.

Utilization is one of the biggest AS/RS ROI variables

Fixed AS/RS capital does not shrink because current volume is low.

If the system was designed for 8,000 presentations/day but runs at 3,000:

• labor savings may be lower;
• facility value may still exist;
• annual benefit can sit below business-plan expectations.

As volume rises, more benefit can be captured without repeating the full initial CAPEX.

Model year-by-year ramp, not only steady state

A realistic business case can use:

• Year 1: ramp and training;
• Year 2: base utilization;
• Year 3: planned growth;
• later years: additional robots, shuttles or workstations if required.

Simple payback based on mature Year 5 benefits can be misleading if the system needs four years to reach that volume.

Do not use “future growth” without a source

Support growth assumptions with:

• customer contracts;
• approved commercial forecast;
• historical growth;
• planned SKU expansion;
• known facility constraint.

An optimistic growth slide is not a payback input.

Capital-equipment offsets are especially important in greenfield projects

Swisslog's current guidance says automated storage can reduce or remove the need for:

• forklifts;
• reach trucks;
• conventional racking;
• pick modules.

In a greenfield comparison, those avoided assets can reduce the incremental capital required for automation.

In a brownfield project where the forklifts and rack already exist and will remain in service elsewhere, the offset can be much smaller.

Use residual value carefully

Existing equipment can produce:

• resale proceeds;
• redeployment value;
• scrap value.

Do not credit original purchase price as an avoided cost if the equipment is already sunk.

Accuracy savings should be measured from actual error cost

AS/RS can improve:

• inventory control;
• product identification;
• picking consistency;
• damage prevention.

Value:

• rework;
• reshipping;
• claims;
• inventory adjustment;
• expedited freight

from the warehouse's actual history.

Do not assign a generic “accuracy = 2% savings” line.

Shipping-window performance can produce a direct P&L benefit

Swisslog specifically identifies avoided carrier upcharges from missed cutoffs as an automation value category.

That is unusually straightforward to measure:

Only include events the AS/RS actually prevents.

Safety and ergonomics can justify AS/RS without fake annual savings

Swisslog includes injury / workers' compensation exposure among strategic automation benefits.

Kardex's 2025 VLM customer survey even describes a roughly $300,000 automation investment where repetitive-strain injury economics alone produced about a one-year payback.

That is a specific component-AS/RS customer example.

If your facility lacks reliable injury-cost history, present safety as a separate capital reason instead of inventing an expected annual accident saving.

Component AS/RS can pay back much faster than structural AS/RS

Kardex's 2025 survey of its Remstar customers reported:

• 80% seeing ROI before the first year;
• 33% reaching payback in the first three months.

Kardex associates those results with dynamic AS/RS such as VLMs.

Do not generalize that survey to a $1–$5 million structural mini-load or unit-load system.

Smaller component automation often has:

• less integration;
• less building work;
• lower CAPEX;
• a more localized labor problem.

The denominator matters

If one VLM costs $150,000 and removes $100,000/year of capturable cost, payback can be short.

A $3 million mini-load project may create far more annual value while still requiring a longer absolute payback because the initial capital is much larger.

Compare ROI percentages and strategic capacity—not just months to payback.

Do not ignore new maintenance labor

Swisslog explicitly warns that larger automated systems can require dedicated on-site maintenance technicians.

The AS/RS may reduce:

• pickers;
• forklift operators;
• replenishment labor.

It can add:

• controls technicians;
• maintenance specialists;
• software support;
• service agreements.

Net the two labor categories.

Software should appear every year in the model if the contract charges every year

Swisslog identifies recurring:

• WMS licensing;
• WCS/WES licensing;
• support contracts;
• version upgrades;
• middleware

as lifecycle cost categories.

A payback model that includes software in Year 1 and forgets Years 2–20 will overstate return.

Underscoping can destroy apparent ROI

Swisslog warns that a system running at roughly 95% capacity on day one leaves little room for:

• growth;
• peak demand;
• new customer requirements.

A second capital project arriving years earlier than planned can erase much of the first investment's expected economics.

Overscoping can destroy ROI too

Installing:

• five-year robot count;
• five-year workstations;
• five-year shuttle capacity

on day one can leave capital idle.

Separate:

• infrastructure needed now for future expansion;
• capacity modules that can be added later.

Scalability can have measurable option value

The Pietsch case is a good illustration: current activity, design capacity and scalable capacity are all different.

A modular system can let the business defer:

• robots;
• ports;
• stations;
• some throughput hardware

until volume exists.

That timing can improve capital efficiency even when long-term total spending is similar.

A 10-year simple ROI is useful—but still incomplete

The calculator reports this as a simple screening metric.

For serious multi-million-dollar capital decisions, finance may also require:

• NPV;
• IRR;
• inflation;
• tax effects;
• depreciation;
• financing;
• year-by-year benefit ramp;
• terminal / residual value.

Do not invent a discount rate if corporate finance owns that assumption.

Use the calculator to set a maximum investment

If annual net benefit is known and the company requires a four-year simple payback:

Then add any verified upfront conventional-capital offset to determine the maximum gross AS/RS CAPEX consistent with that hurdle.

This is useful when:

• vendor quotes increase;
• scope changes;
• another workstation is added;
• building modifications emerge.

Do not let a target payback dictate unsafe or undersized scope

If a compliant, reliable system costs more than the payback ceiling:

the answer is not to remove:

• required guarding;
• fire protection;
• redundancy that the operation requires;
• necessary maintenance access.

The correct conclusion may be that the project does not meet the financial hurdle yet.

Post-installation ROI should be measured

Kardex notes that teams often revisit actual payback after the predicted date to determine whether the investment delivered.

Measure:

• labor hours;
• temporary labor;
• throughput;
• storage occupancy;
• external storage;
• forklift/rack spend;
• maintenance;
• software/service;
• errors / damage;
• carrier upcharges.

This creates a much better baseline for the next automation project.

Stress-test five assumptions before approval

The practical recommendation

Do not begin with:

“AS/RS normally pays back in two years.”

Begin with:

what does the alternative cost, what annual costs will the AS/RS genuinely remove, what capital will it avoid, what new lifecycle cost will it create, and how quickly will the system reach planned utilization?

Current published examples prove that one-year and two-year paybacks can happen.

Pietsch's current case also proves that installed capacity can sit at a much longer payback until planned volume arrives.

Frequently asked questions

What is a typical AS/RS payback period?

There is no reliable universal period. Current published supplier/customer examples range from roughly one year to several years depending on utilization, labor economics, facility avoidance and project scope.

Can AS/RS pay back in one year?

Yes in some cases. AutoStore currently reports that PUMA's Indiana project, originally planned around a five-year return, reached payback in 12 months. That is a customer case, not a universal forecast.

What does the AutoStore Forrester study report?

AutoStore currently cites a Forrester composite with $11.8 million in benefits, $6.2 million in costs, $5.3 million NPV, 18-month payback and 79% ROI over the study period. Treat it as a composite study, not a project benchmark.

How do I calculate AS/RS payback?

Subtract verified one-time conventional capital avoided from installed AS/RS CAPEX, then divide that net investment by the annual recurring benefit after subtracting new AS/RS maintenance, software and service costs.

Should facility savings be included?

Yes when the AS/RS genuinely avoids or defers an actual facility or external storage cost. Do not monetize unused floor area automatically if no cash or capital requirement changes.

Should forklift and rack costs be included?

Yes when the project genuinely avoids those purchases. Treat avoided upfront capital separately from recurring fleet maintenance/energy savings to prevent double counting.

How should labor savings be calculated?

Use labor hours actually eliminated or redeployed × loaded labor cost and validate how those hours become lower payroll, overtime, temporary labor, headcount avoidance or additional useful output.

What recurring costs should be included in AS/RS ROI?

Include maintenance, spare parts, software licensing/support, service contracts, energy, maintenance staffing and other recurring support costs that the manual alternative does not have.

Why can AS/RS payback improve over time?

Fixed infrastructure can support higher future volume without repeating all initial CAPEX. As utilization rises, labor, space and throughput benefits can increase faster than recurring cost.

Why can AS/RS payback be worse than planned?

Common causes include slower volume growth, incomplete labor capture, higher integration/building costs, excess day-one capacity and underestimated software or maintenance expense.

Should I use a 20-year model?

Swisslog currently recommends lifecycle analysis over roughly 20 years for warehouse automation TCO. Simple payback is still useful, but it should not be the only financial metric on a long-lived automated system.

Does the calculator include NPV and IRR?

No. It deliberately provides simple payback and simple 10-year ROI without inventing corporate discount rates, financing, tax or depreciation assumptions.

How should I validate AS/RS ROI after go-live?

Compare actual labor, throughput, occupancy, external storage, conventional equipment costs, maintenance, software/service, errors and shipping-cost performance with the approved business-case baseline.

Sources and methodology

Warehouse Fieldbook treats published ROI and payback results as case evidence, not universal benchmarks. AutoStore's current site supplies the Forrester composite figures and published customer examples for PUMA, THG and Pietsch. Swisslog's current U.S. automation-cost and ROI guidance supplies the 20-year lifecycle framework, comparison scenarios, recurring cost categories, facility avoidance, conventional-equipment offsets and the supplier claim that AS/RS can reduce storage footprint by up to 85% in suitable applications. Kardex's December 2025 VLM guide supplies a separate component-AS/RS customer survey, which is explicitly not generalized to structural mini-load, unit-load or cube systems. Calculator defaults are illustrative only and are not derived from these vendor case studies.

• Swisslog — current U.S. automation TCO, ROI drivers, facility avoidance and comparison-scenario guidance
• AutoStore — current Forrester composite ROI, payback, benefits and cost figures
• AutoStore — current published PUMA, Elektroimportøren and Davcor payback examples
• AutoStore — published PUMA and THG throughput / ROI examples
• AutoStore — THG two-year ROI and variable-labor-cost reduction case
• AutoStore — Pietsch utilization, throughput, space and payback case
• Kardex — December 2025 VLM ROI/payback customer survey and safety example