Commissioned Research
Top 9 Best Elevator Monitoring Software of 2026

GITNUXSOFTWARE REVIEW

Facilities & Property Services

Top 9 Best Elevator Monitoring Software of 2026

Compare elevator monitoring software options for building teams, including Advantech iBuilding, MAX, and Schindler Ahead, with key tradeoffs.

18 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Elevator monitoring software connects machine and building signals into a usable data model for maintenance teams, then applies diagnostics that can feed work orders and scheduling. This comparison helps technical evaluators weigh the tradeoff between vendor-specific monitoring suites and multi-vendor IoT platforms, including data access via APIs, integration depth, and operational controls such as RBAC and audit logging.

Advantech iBuilding is the best choice for building operations teams that want centralized elevator signals because its monitoring workflow links remote faults to investigation-ready operational history, whereas MAX fits owners who need consistent remote incident timelines since controller event logs correlate into an audit-friendly fault timeline.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Advantech iBuilding

Elevator fault investigations link remote events to operational histories inside an iBuilding monitoring workflow.

Best for: Fits when building operations teams need elevator signals centralized with plant-wide monitoring workflows.

2

MAX

Editor pick

Controller event log to fault timeline correlation for incident history across trips and alarms in one operational view.

Best for: Fits when building owners need consistent remote elevator monitoring with incident timelines and configurable alerting.

3

Schindler Ahead

Editor pick

Inspection and compliance records are directly linked to elevator fault and alarm timelines for end-to-end traceability.

Best for: Fits when Schindler-managed multi-building fleets need fault-to-service workflows with audit-friendly history.

Comparison Table

1
API-first
9.3/10
Overall
2
enterprise
8.9/10
Overall
3
enterprise
8.6/10
Overall
4
vertical specialist
8.3/10
Overall
5
enterprise
8.2/10
Overall
6
enterprise
7.7/10
Overall
7
7.6/10
Overall
8
vertical specialist
7.0/10
Overall
9
vertical specialist
6.8/10
Overall
#1

Advantech iBuilding

API-first

IoT platform for elevator monitoring providing sensor data collection, edge analytics, and cloud visualization.

9.3/10
Overall
Features9.0/10
Ease of Use9.5/10
Value9.5/10
Standout feature

Elevator fault investigations link remote events to operational histories inside an iBuilding monitoring workflow.

Advantech iBuilding is positioned for remote elevator monitoring by collecting status, event, and fault information and turning it into actionable fault and alarm history. The solution is built to operate alongside building systems so elevator signals can be correlated with site context during investigations. Configuration supports mapping elevator signals into monitoring views and histories so maintenance teams can trace incidents from detection to resolution.

A key tradeoff is that achieving clean, consistent signal coverage depends on the connected elevator gateway and the controller data available from each equipment set. It fits sites that already run centralized building monitoring and want elevator telemetry to follow the same operational governance and integration approach rather than living in an isolated elevator tool.

Pros
  • +Building-system integration orientation supports cross-system fault context
  • +Event and fault history preserves investigation trails for recurring issues
  • +Alert workflows attach fault context to maintenance handling
  • +Signal mapping enables consistent monitoring views across elevators
Cons
  • –Signal coverage depends on controller integration quality per elevator set
  • –Advanced tuning needs deliberate configuration across buildings and assets
  • –Complex deployments require coordination between field gateway and central monitoring
Use scenarios
  • Facilities operations managers

    Centralize elevator incident history

    Faster incident triage

  • Building automation engineers

    Integrate elevator signals into building network

    Consistent cross-system visibility

Show 1 more scenario
  • Maintenance dispatch coordinators

    Route alerts with equipment context

    Reduced mean time to repair

    Alerting workflows provide fault details so dispatch can assign work based on event history.

Best for: Fits when building operations teams need elevator signals centralized with plant-wide monitoring workflows.

#2

MAX

enterprise

Cloud-connected elevator monitoring platform that analyzes equipment data for predictive maintenance.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Controller event log to fault timeline correlation for incident history across trips and alarms in one operational view.

MAX from tkelevator.com focuses on remote elevator monitoring with event-driven fault and alarm history. It collects controller and device telemetry into a unified timeline for escalations tied to elevator incidents.

It supports administrator workflows for alert rules and operational oversight across monitored sites. MAX is strongest when organizations need consistent monitoring from building equipment into maintenance action pipelines.

Pros
  • +Event timeline makes fault and alarm history easier to audit operationally
  • +Alert rules reduce noise by tying notifications to specific elevator conditions
  • +Site administration supports multi-building monitoring with centralized oversight
  • +Monitoring view ties ongoing issues to controller event logs
Cons
  • –Integrations depend on the connected elevator gateway path used in deployment
  • –Automation beyond alerting appears limited without additional workflow tooling
  • –Thoroughness of RBAC and audit log controls is not obvious from the interface alone
  • –Setup complexity increases when edge connectivity must be standardized across fleets
Use scenarios
  • Multi-site facilities managers

    Track elevator faults across buildings

    Faster fault triage

  • Elevator service operations leads

    Trigger alerts from incident history

    Lower missed escalations

Show 1 more scenario
  • On-call maintenance supervisors

    Review fault patterns before dispatch

    More targeted repairs

    Surfaces controller and device event history to identify recurring failures tied to specific cars and times.

Best for: Fits when building owners need consistent remote elevator monitoring with incident timelines and configurable alerting.

#3

Schindler Ahead

enterprise

Digital elevator monitoring suite offering predictive maintenance, remote diagnostics, and building integration.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Inspection and compliance records are directly linked to elevator fault and alarm timelines for end-to-end traceability.

Schindler Ahead centralizes remote elevator monitoring for fleets managed under Schindler, with visibility into controller event logs, fault and alarm history, and service-relevant operational status. The system focuses on inspection and compliance records tied to elevator assets, and it supports operational workflows like incident handling and maintenance follow-up from telemetry and alert trails.

Automated notifications connect detected faults to the people and schedules that handle escalation and callbacks. For teams standardizing reporting across multiple buildings, Schindler Ahead provides a consistent asset view and audit-oriented history across monitored devices.

Pros
  • +Controller event logs and fault history are tied to the monitored elevator asset
  • +Inspection and compliance records support audit-style traceability for maintenance work
  • +Automated notifications connect detected faults to escalation workflows
  • +Fleet-wide asset visibility keeps operational reporting consistent across buildings
Cons
  • –Best results depend on deeper integration with Schindler-managed devices and configurations
  • –Extensibility and external automation pathways are limited compared with API-first competitors
  • –Some alert interpretation requires familiarity with controller event patterns
  • –Reporting depth can require hands-on setup per building and asset grouping
Use scenarios
  • Schindler fleet operations teams

    Manage incidents using asset telemetry

    Consistent response workflows

  • Maintenance compliance coordinators

    Audit elevator inspection records

    Cleaner audit trails

Show 2 more scenarios
  • Dispatch and callback coordinators

    Route alarms to correct schedules

    Reduced callback delays

    Automates notifications so detected faults connect to the people and schedules responsible for escalation.

  • Operations reporting managers

    Standardize history across buildings

    Comparable operational metrics

    Provides a consistent asset view and audit-oriented timeline across monitored devices for reporting.

Best for: Fits when Schindler-managed multi-building fleets need fault-to-service workflows with audit-friendly history.

#4

DATOMS

vertical specialist

IoT platform for elevator and escalator monitoring with predictive maintenance and multi-vendor controller integration.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Fault and alarm history is organized as a per-car event timeline for faster recurrence triage and escalation context.

DATOMS provides remote elevator monitoring that collects controller event data and elevator telemetry for fault and alarm history.

Pros
  • +Event timeline ties elevator faults to car and site context
  • +Alert conditions map cleanly to maintenance response workflows
  • +Historical fault and alarm views support triage and recurrence tracking
  • +Designed around connected elevator telemetry streams
Cons
  • –Gateway and controller connectivity requires careful on-site setup discipline
  • –Limited room for custom analytics beyond the provided event views
  • –Automation depth depends on the available integration endpoints
  • –Admin governance controls feel lighter than enterprise CMMS-style models
Use scenarios
  • Residential tower maintenance teams

    Trace recurring elevator faults

    Fewer repeated service trips

  • Emergency callback dispatchers

    Make dispatch decisions from alerts

    Quicker incident routing

Show 1 more scenario
  • Building automation integration engineers

    Connect controller gateways to monitoring

    Centralized device visibility

    Connects controllers and gateways into a DATOMS data pipeline for historical reporting and status.

Best for: Fits when maintenance teams need event-driven monitoring with clear fault timelines across multiple cars.

#5

Otis ONE

enterprise

IoT-based elevator and escalator monitoring system providing real-time diagnostics and predictive maintenance.

8.2/10
Overall
Features8.2/10
Ease of Use8.1/10
Value8.3/10
Standout feature

Event history normalization across elevator assets into a single fault and alarm timeline for remote operations review.

Otis ONE aggregates elevator telemetry and turns controller activity into structured fault and service visibility for remote monitoring teams. It supports configuration of connected gateway setups and surfaces event history for operations reviews and escalation workflows.

Pros
  • +Turns controller events into searchable fault and service history
  • +Alert rules map to elevator state changes instead of generic notifications
  • +Gateway configuration is centralized for remote monitoring rollouts
  • +Supports building management integration patterns like BACnet
Cons
  • –Coverage depends on connected interface availability per equipment type
  • –Deep automation needs careful alignment of alert thresholds and responsibilities
  • –Event granularity can vary by controller data exposure
  • –Workflows for complex dispatch often require external maintenance tooling
Use scenarios
  • Remote monitoring operations teams

    Review structured fault history

    Faster fault comprehension

  • Service dispatch managers

    Escalate door and machine states

    More precise escalations

Show 1 more scenario
  • Building system integrators

    Route events via BACnet links

    Less manual event mapping

    Supports connected gateway setups and integration paths like BACnet and building event flows.

Best for: Fits when building operators want state-based fault visibility and alarm handling tied to elevator equipment.

#6

KLEEMANN Live

enterprise

Remote elevator management platform with real-time monitoring, ride quality analytics, and preventive maintenance alerts.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

Live monitoring screens linked to KLEEMANN fleet operations, with controller event history used directly in day-to-day troubleshooting.

KLEEMANN Live provides remote elevator monitoring for organizations that service KLEEMANN lifts and need a centralized operational view.

Pros
  • +Live fleet status reporting aligned to KLEEMANN lift operations
  • +Controller event history supports targeted troubleshooting workflows
  • +Works well for multi-elevator oversight across a single operator network
  • +Operational screens reduce time spent switching between tools
Cons
  • –Best fit for KLEEMANN-installed fleets, with narrower coverage elsewhere
  • –Limited visibility into cross-vendor controller data paths
  • –Automation depth depends on operational maturity of the service process
  • –Integration needs may require custom edge-to-cloud or gateway work
Use scenarios
  • KLEEMANN lift service providers

    Track KLEEMANN incidents centrally

    Improved incident continuity

  • Dispatch operations roles

    Prioritize dispatch using event trends

    Better triage accuracy

Show 1 more scenario
  • Technicians on site

    Confirm fault context before arrival

    Reduced repeat visits

    Provides incident history that helps technicians plan diagnostics and replacement steps.

Best for: Fits when a maintenance organization primarily manages KLEEMANN elevators and needs consistent remote monitoring for service dispatch and follow-up.

#7

Mitsubishi ElevatorGroup Monitoring System

enterprise

Remote elevator monitoring system providing real-time status, fault alerts, and maintenance scheduling for Mitsubishi equipment.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Group monitoring view that ties controller event logs to persistent fault and alarm history for fleet-wide escalation.

Facilities and elevator maintenance organizations typically use Mitsubishi ElevatorGroup Monitoring System to track controller event logs and correlate faults with active alarms. The monitoring workflow centers on fault and alarm history plus status trending, which reduces manual log review during incident response. Group-level management helps teams handle fleet sprawl across multiple buildings without relying on one-off scripts.

Pros
  • +Uses controller event logs to populate fault and alarm history
  • +Supports group-wide monitoring across multiple cars and sites
  • +Improves incident response by surfacing active alarms consistently
  • +Gateway-focused integration fits edge-to-cloud telemetry patterns
Cons
  • –Best outcomes depend on Mitsubishi equipment group alignment
  • –Deep third-party data modeling requires tighter integration work
  • –Alert tuning can take time for mixed traffic patterns
  • –Limited visibility into nonstandard telemetry formats without adapters
Use scenarios
  • Building operations managers

    Handle active alarm triage

    Reduced time to escalation

  • Maintenance dispatch coordinators

    Prioritize repair work orders

    Fewer repeat callouts

Show 2 more scenarios
  • Facility compliance teams

    Document inspection and compliance records

    Cleaner incident documentation

    Compliance workflows use structured fault and alarm history timelines for audit-ready references.

  • Service engineering teams

    Investigate fault sequences

    Faster root-cause narrowing

    Engineering reviews controller event logs to map alarm onset to specific controller behaviors.

Best for: Fits when fleet ops need group-level alarm history and event-driven maintenance without custom telemetry pipelines.

#8

Tsaro AI

vertical specialist

Vertical transportation intelligence platform combining IoT monitoring, AI analytics, and communication line monitoring.

7.0/10
Overall
Features7.0/10
Ease of Use7.0/10
Value7.0/10
Standout feature

Event-to-escalation workflow rules that turn controller notifications into routed emergency callback alerts with history context.

Tsaro AI is designed for remote elevator monitoring workflows where controller events and alarm states must be tracked over time, not just displayed at point-in-time. The system centers on fault and alarm history timelines and rule-driven notifications that reduce manual checking during service windows. Admin workflows emphasize governing what gets monitored and who receives alerts, which fits multi-elevator operations across several sites.

Pros
  • +Correlation across fault and alarm history reduces repetitive manual investigations
  • +Configurable escalation routing supports emergency callback monitoring workflows
  • +Normalization of telemetry events helps keep operational views consistent across sites
  • +Rule-driven notifications target specific conditions instead of broad email blasts
Cons
  • –High-quality alerts depend on consistent upstream controller and gateway event inputs
  • –Advanced workflows can require more configuration time than dashboard-only tools
  • –Deep integration beyond event ingestion may demand engineering involvement
  • –Exception handling for unusual controller behaviors can require iterative rule tuning
Use scenarios
  • Building operations managers

    Centralize elevator alarm visibility

    Fewer missed escalation events

  • On-call maintenance teams

    Handle rapid fault escalations

    Faster incident triage

Show 2 more scenarios
  • Service dispatch coordinators

    Automate service assignment triggers

    More consistent dispatch timing

    Use notification rules to initiate response workflows when defined faults recur or persist.

  • Multi-site engineering admins

    Standardize monitoring across sites

    Lower cross-site operational drift

    Apply monitoring and alert configuration so teams see comparable elevator event behavior per location.

Best for: Fits when multi-elevator operators need rule-based escalation from controller events to on-call response.

#9

Symphony EYC

vertical specialist

Elevator and escalator monitoring software providing remote diagnostics and predictive maintenance analytics.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Symphony EYC correlates controller event logs into fault and alarm history timelines for incident-level triage and escalation context.

Symphony EYC focuses on elevator telemetry workflows that connect controller events to operational monitoring for remote fault response. The product centers on fault and alarm history views plus escalation-ready alerts driven by controller event logs and elevator fault codes.

Pros
  • +Event-to-incident timelines tie elevator fault codes to actionable alarm history
  • +Alerting workflow supports escalation-focused monitoring rather than status-only dashboards
  • +Gateway-oriented integrations fit edge-to-cloud elevator monitoring deployments
  • +Operational views prioritize controller event context for faster triage
Cons
  • –Integration onboarding depends on connected gateway setup and site-by-site configuration
  • –Extensibility depth via API is limited for teams needing custom telemetry pipelines
  • –RBAC controls can be restrictive for multi-vendor maintenance organizations
  • –High-frequency telemetry visualizations are less detailed than event history
Use scenarios
  • Elevator service control centers

    Respond using controller fault codes

    More reliable fault response

  • Operations analysts

    Study incident context and timelines

    Better root-cause investigations

Show 2 more scenarios
  • Gateway integration teams

    Monitor through gateway-style deployments

    Unified telemetry capture

    Supports building-system connectivity by integrating with connected elevator gateway deployments.

  • On-call supervisors

    Escalate based on controller events

    Fewer delayed escalations

    Uses alerting driven by controller event logs to coordinate escalation during fault conditions.

Best for: Fits when maintenance teams need controller-event-driven fault monitoring and escalation-ready history across multiple buildings.

Conclusion

After evaluating 9 elevator monitoring software, Advantech iBuilding stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Advantech iBuilding

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Elevator Monitoring Software

How do Tsaro AI and MAX map controller event logs into an alerting workflow?
Tsaro AI ingests controller notifications and applies event-to-escalation workflow rules that route emergency callback alerts with history context. MAX correlates controller event log entries into a fault timeline so admin-defined alert rules trigger against incident history rather than live status alone.
Which tool provides group-wide visibility for fleet operators across multiple cars and sites?
Mitsubishi ElevatorGroup Monitoring System is designed for elevator groups and focuses on group-level alarm history tied to controller event data. DATOMS also supports multi-car fault timelines, but DATOMS organizes history as per-car event timelines for recurrence triage.
When does Schindler Ahead link faults to inspection and compliance records in the same workflow?
Schindler Ahead connects inspection and compliance records directly to elevator fault and alarm timelines so incident handling and follow-up stay traceable. That linkage is built around Schindler-managed fleets rather than a generic monitoring workflow in Otis ONE.
What breaks if an elevator monitoring deployment lacks consistent gateway connectivity, as seen in Advantech iBuilding and Symphony EYC?
Advantech iBuilding depends on building-automation integration patterns to centralize elevator telemetry and controller events into a managed monitoring workflow. Symphony EYC relies on gateway-style connectivity tied to connected elevator gateway deployments, so missing or intermittent gateway telemetry creates gaps in fault and alarm history timelines and reduces escalation readiness.
How do Otis ONE and KLEEMANN Live handle door and equipment-state signals in fault history reviews?
Otis ONE surfaces event history for operations reviews with state-based handling tied to equipment states, including door and machine related signals where the connected interface provides them. KLEEMANN Live maps monitoring inputs directly into KLEEMANN fleet service operations, and its troubleshooting workflow is centered on KLEEMANN lifts rather than a general equipment-state model.
Which integration path is more common for building-automation environments, and how do Advantech iBuilding and Otis ONE compare?
Advantech iBuilding is oriented toward building-automation environments and routes elevator signals into plant-wide monitoring workflows. Otis ONE also targets building system connections like BACnet, and it focuses on normalizing connected gateway data into a single fault and alarm timeline for remote teams.
How does Tsaro AI differ from ServiceChannel-style triage flows in automation depth?
Tsaro AI emphasizes event-to-escalation workflow control that turns controller notifications into routed alerts with history context. MAX and Symphony EYC also use event history normalization, but Tsaro AI’s distinguishing element is workflow rules that manage escalation routing based on defined conditions.
What role do audit logs and administrative controls play in incident oversight for MAX and Symphony EYC?
MAX includes administrator workflows for alert rules and operational oversight across monitored sites, so alert handling is controlled at the rule and incident level. Symphony EYC emphasizes ongoing operations by tracking incident context and operational timelines driven by controller event logs, which supports repeatable triage even when live status changes quickly.
How should security teams validate SSO and RBAC for elevator monitoring tools like Schindler Ahead and Mitsubishi ElevatorGroup Monitoring System?
Schindler Ahead targets audit-friendly history and fleet operational workflows for monitored devices, so security validation must cover access control boundaries around incident and compliance records. Mitsubishi ElevatorGroup Monitoring System is built for fleet-wide visibility and escalation readiness, so validation should include RBAC coverage for group-level alarm history views and any administrative configuration access.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Elevator Monitoring Software

What separates options for elevator monitoring software is how they turn raw controller and sensor data into a consistent event timeline, then let us act on it with clear automation and reporting. The biggest gaps show up in integration depth, admin controls, and auditability of changes across sites.

Event timeline diagnostics

Why it matters

Event timeline diagnostics matter because elevator issues rarely appear as one alarm. You need a connected view of what happened first, what changed in the controller, and what symptoms followed.

How to check

Ask the vendor to show a sample of a real incident and the linked timeline from fault/alarm occurrence through subsequent states. Confirm you can filter by elevator, time window, and incident type, and that the timeline uses consistent labels rather than only numeric codes.

Alarm escalation automation

Why it matters

Alarm escalation automation matters when response time affects downtime. The best systems route the right severity to the right group and apply schedules without manual chasing.

How to check

In the demo, create an escalation rule from an example alarm to a workflow step (notification, acknowledgment requirement, or service routing). Verify you can test it end-to-end and that the logic supports different severities and time-of-day behavior.

Data export and API coverage

Why it matters

Data export and API coverage matter when we need monitoring to feed other maintenance tools or reporting. We should be able to pull the same fields the UI shows, not just screenshots.

How to check

Request a walkthrough of available exports (events, status, device inventory) and the API endpoints or sample requests. Check whether exports include stable identifiers (building, floor, car/elevator) and timestamps with timezone clarity.

Site hierarchy and configuration

Why it matters

Site hierarchy and configuration determine whether the system stays usable across buildings and properties. We need clean separation of settings, devices, and users so one site’s changes don’t break another’s workflows.

How to check

Ask to provision two buildings with different groups and show how you configure device mapping and alert destinations per building. Confirm configuration changes are scoped correctly and you can review what changed for each elevator.

RBAC and audit log trails

Why it matters

RBAC and audit log trails matter because monitoring setups affect reliability and accountability. Admin actions like changing escalation logic should be traceable to a user and a time.

How to check

In the admin area, show role creation and permission boundaries for viewing events vs editing automations. Then change an escalation setting and verify the audit log records who changed what, when, and the before/after values where available.

Red flags

  • You only get separate alarms without a coherent timeline that explains sequence and follow-on effects
  • Escalation rules require manual steps or lack severity and schedule controls you can validate
  • Exports or API responses don’t match the UI fields or omit stable elevator identifiers and timestamps

Fit by situation

  • If we need to investigate recurring faults across multiple elevators, prioritize event timeline diagnostics.
  • If we must reduce time-to-response, prioritize alarm escalation automation.
  • If we plan to connect monitoring data into our maintenance workflows, prioritize data export and API coverage.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.