When a national retail chain operating 300 stores across 28 states attempted to benchmark RTU maintenance performance across its portfolio, it found an uncomfortable truth: no two stores were maintaining their rooftop units the same way, contractor invoices for identical repairs varied by up to 340% between regions, and the central facilities team had no visibility into which stores were one compressor failure away from a customer-facing temperature complaint. Sign in to OxMaint to start standardizing RTU maintenance across your retail portfolio, or book a demo to see the multi-site dashboard in action.
Case Study / Multi-Site Retail
Retail Chain Saves $2.1M by Standardizing RTU Maintenance Across 300 Stores
How a national retail chain eliminated maintenance inconsistency, contractor invoice variance, and reactive RTU failures across 300 stores — and documented $2.1M in annual savings within Year 1 of deploying OxMaint Multi-Site Dashboard.
$2.1M
Annual savings — documented in Year 1
300Stores on one CMMS
63%Fewer emergency RTU callouts
340%Invoice variance eliminated
11 moPayback period
Facility Profile
Chain TypeNational specialty retailer — 300 stores, 28 states
Store Size4,200–8,500 sq ft per store — average 2–4 RTUs per location
RTU Portfolio820+ rooftop units — mix of 3–15 ton units, average age 8.3 years
Maintenance ModelRegional contractors — 14 different vendors across 28 states, no standardised PM scope
Prior CMMSNone — work orders managed through email, spreadsheets, and contractor invoices
OxMaint FeatureMulti-Site Dashboard + AI-Powered PM Optimisation + Contractor Management
The Problem in Three Numbers
$7,100
Average annual RTU maintenance spend per store — with no benchmark to know if this was competitive
340%
Variance in contractor invoice amounts for identical repairs across different regions
0%
Of stores had a standardised PM checklist — every contractor used their own scope and schedule
What "No Standardisation" Actually Looks Like at Scale
Across 300 stores and 820+ RTUs, the absence of a standardised maintenance programme was not abstract — it had specific, measurable costs that the facilities team could trace once they began collecting data.
Reactive Repair Domination
78% of all RTU work orders were reactive — emergency callouts after failure, not scheduled PM. Reactive repairs cost 3–5× more than planned repairs. The 300-store estate was generating emergency callouts at a rate of 23 per week across all stores.
Contractor Invoice Variance
Identical repair — compressor replacement on a 5-ton RTU — invoiced at $1,840 in one region and $6,250 in another. No visibility into whether either price was justified. No scope standard to compare against. Facilities team was approving invoices on trust, not data.
PM Gaps by Region
Stores in contractor-rich markets received quarterly PM from vendors eager to protect service agreements. Stores in contractor-scarce markets received PM once yearly — or not at all. Equipment age and failure rates directly correlated with PM frequency, but nobody was tracking either.
No Portfolio Visibility
The VP of Facilities could not answer basic questions: Which stores have the oldest RTUs? Which regions have the highest emergency callout rates? Which contractors have the best first-call resolution? These questions required weeks of spreadsheet work — if they were answered at all.
OxMaint Implementation: Standardisation Across 300 Stores in 90 Days
Phase 1
Asset Registry — 6 Weeks
All 820+ RTUs entered into OxMaint with nameplate data, refrigerant type, age, and criticality classification. Stores ranked by RTU age profile and historical callout frequency — identifying the 47 stores at highest failure risk as priority targets for immediate PM attention.
Phase 2
Standard PM Scope — 4 Weeks
A single standardised RTU PM checklist deployed across all 300 stores and all 14 contractor vendors. Quarterly PM tasks defined, documented, and mandatory — coil cleaning, filter replacement, refrigerant check, electrical inspection, belt and bearing check. Contractors submit completion records against the standard scope, not their own format.
Phase 3
Contractor Benchmark — Ongoing
OxMaint Multi-Site Dashboard surfaces contractor performance data across all vendors: average invoice per task type, first-call resolution rate, PM completion rate, and response time. The facilities team renegotiated contracts with the bottom-quartile performers and consolidated volume with top-quartile vendors within 6 months.
See How the Multi-Site Dashboard Works Across Your Store Portfolio
One dashboard. Every store. RTU health status, PM completion rates, contractor performance, and cost benchmarks — updated in real time across every location you operate.
Year 1 Financial Results — $2.1M Documented
| Savings Category | Before OxMaint | After OxMaint (Year 1) | Annual Saving |
|---|---|---|---|
| Emergency callout reduction | 23 callouts/week chain-wide avg. | 8.5 callouts/week — 63% reduction | $640,000 |
| Contractor invoice normalisation | 340% variance by region — no benchmark | Regional variance reduced to 28% | $490,000 |
| PM scope standardisation (unnecessary tasks eliminated) | Scope driven by contractor — over-servicing in high-competition regions | Standard scope — documented tasks only | $280,000 |
| RTU lifespan extension (deferred replacement) | 3.2-year average RTU lifespan on reactive estates | Structured PM extending lifespan on 210 units | $390,000 |
| Energy savings from optimised RTU performance | Coil fouling, refrigerant undercharge common — unmeasured | 6.8% average energy reduction per monitored unit | $300,000 |
| Total documented Year 1 saving | $2,100,000 |
Multi-Site Dashboard: What the VP of Facilities Sees Every Morning
Portfolio View
RTU Health by Store
Heat-map view of all 300 stores — green for stores with no open corrective work orders, amber for stores with open P3 tasks, red for stores with P1 or P2 open. The VP of Facilities sees the entire estate health in 30 seconds.
Cost Intelligence
Contractor Invoice Benchmarking
Every contractor invoice tagged against task type and equipment class. Average cost per task displayed by vendor and region. Outliers flagged automatically — any invoice more than 40% above the regional benchmark triggers a review flag before approval.
Compliance
PM Completion Rate by Store & Region
Quarterly PM completion tracked per RTU per store. Stores falling behind schedule are surfaced automatically — not discovered during the next emergency callout. Regional FM receives a weekly digest of PM compliance across their store cluster.
Capital Planning
RTU Age & Replacement Forecast
RTU age distribution across the portfolio with replacement cost forecasting. Stores with 3+ RTUs over 12 years old are flagged for capital budget inclusion. The chain replaced 38 units on a planned basis in Year 1 — avoiding 38 emergency replacements at premium cost.
The single biggest misconception in multi-site retail facilities management is that having multiple contractors is a cost-saving strategy. In reality, it is a cost-obscuring strategy. You cannot benchmark what you cannot measure, and without a centralised CMMS that standardises work order scope, tracks invoice data by task type, and surfaces contractor performance across all vendors simultaneously, you have no idea whether your maintenance spend is efficient or not. The retail chain in this case study was not overpaying because of bad contractors — they were overpaying because they had no system to know what a fair price was. The $2.1M saving did not come from squeezing vendors; it came from knowing, for the first time, what the right price actually was.
Sandra Okafor, CFM, RPA
Certified Facility Manager · Real Property Administrator · 19 years multi-site retail facilities operations · Former VP Facilities, 400+ location retail chain · Specialist in multi-contractor management, RTU lifecycle planning, and CMMS-driven cost benchmarking
300 Stores. One Dashboard. Every RTU Accounted For.
OxMaint Multi-Site Dashboard gives retail facilities teams the portfolio-level visibility, standardised PM scope, contractor benchmark data, and capital planning intelligence to manage an RTU estate of any size — without building a team proportional to the portfolio.
Frequently Asked Questions
How does OxMaint handle multi-site RTU maintenance with different contractors in different regions?
OxMaint assigns contractors at the store level — each location's work orders route to the assigned vendor for that region, while all completion records, invoices, and performance data flow back into a single centralised dashboard. The facilities team sees every contractor's performance in the same format and can benchmark invoice amounts by task type across all vendors simultaneously. This is what eliminated the 340% invoice variance in this case study — not by changing contractors, but by making the variance visible. Sign in to OxMaint to configure your contractor and store structure from day one.
How long does it take to deploy OxMaint across a 300-store retail chain?
The retail chain in this case study completed asset registry, PM scope standardisation, and contractor onboarding across all 300 stores in 90 days — a phased rollout starting with the 47 highest-risk stores and expanding region by region. The OxMaint mobile app allows store managers and contractors to begin logging work orders from day one of their store's activation, with no hardware installation required. Most multi-site retail deployments reach full operational coverage within 60–90 days depending on portfolio size and data availability for the asset registry.
What RTU data does OxMaint need to start generating portfolio-level insights?
The minimum viable dataset is asset name, location (store address), equipment model and serial number, and refrigerant type. OxMaint AI begins generating PM schedule recommendations as soon as unit age and model data are entered. Full predictive analytics — failure probability scoring, replacement forecasting, energy performance trending — develop over the first 3–6 months as work order history accumulates. Many multi-site retailers start with the data they already have in spreadsheets or contractor invoices and supplement with field verification during the first PM cycle. Book a demo to see the multi-site onboarding workflow for retail chains.
