GITNUXSOFTWARE ADVICE
Facilities Property ServicesTop 10 Best Building Management Software of 2026
Top 10 building management software picks ranked for modern facilities, comparing Archibus, Yardi Breeze, MRI Software, Condo Control, Building Engines.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Condo Control is the best fit for HOA and condo managers who need auditable maintenance workflows rooted in resident communication and clear work orders, while UpKeep suits facilities teams that want recurring maintenance processes with strong mobile documentation.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Condo Control
Built-in request and work-order lifecycle tracking with status history tied to communities and units.
Built for fits when HOA and condo managers need auditable maintenance workflows without BAS-style device control..
Building Engines
Editor pickAsset and workflow mapping that ties inspections to follow-up work orders with consistent operational history.
Built for fits when facilities teams need traceable maintenance execution and inspections across multiple properties..
UpKeep
Editor pickOn-mobile photo attachments tied to work orders to preserve visual proof through task closure.
Built for fits when facilities teams need recurring maintenance workflows with strong mobile documentation..
Related reading
Comparison Table
Building management software runs tenant requests, work orders, inspections, documents, and audit trails across one operational data model. This ranked list targets analysts and operators who need concrete automation details and integration paths, and it compares platforms by workflow throughput, RBAC controls, extensibility, and data alignment instead of marketing claims.
Condo Control
vertical specialistCondominium management software for resident communication, work orders, documents, and amenities.
Built-in request and work-order lifecycle tracking with status history tied to communities and units.
Condo Control’s core data flow starts when a resident request or staff task is created, then it routes through assignment and status steps until closure. The system supports recurring maintenance activities and supports multiple buildings or communities under shared administrative control. Reporting centers on operational throughput and maintenance outcomes, which helps managers spot backlog and recurring issues across properties. Support for third-party integration is narrower than general-purpose BMS suites, so performance and interoperability depend more on configuration than on open protocol connectivity.
A tradeoff appears with deep building-control integration because Condo Control is not positioned as a BAS or SCADA-grade controller. It fits situations where property operations teams need consistent request-to-work order handling and auditable histories for residents and vendors. It is less ideal when the primary requirement is direct device-level automation such as HVAC control points, lighting circuits, or access-control event streaming.
- +Request-to-work-order workflow keeps resident and vendor tasks traceable
- +Recurring maintenance scheduling supports repeat inspections and service cycles
- +Role-based access controls separate resident visibility from staff operations
- +Operational reporting highlights backlog and repeated issue patterns
- –Limited fit for device-level building automation and protocol integrations
- –Advanced workflow automation needs more configuration discipline
- –Deep custom fields and rules can require admin attention
- –Document storage is secondary to maintenance and request workflows
HOA property management staff
Route resident issues to vendors
Faster resolutions and clearer accountability
Facilities supervisors
Run recurring inspections and tasks
Consistent cadence and fewer missed cycles
Show 2 more scenarios
Community administrators
Manage multi-building operations
Better governance across properties
Configure community settings and roles while monitoring operational workload.
Resident services coordinators
Provide status context for tickets
Reduced back-and-forth communication
Maintain structured request histories residents can reference through the workflow.
Best for: Fits when HOA and condo managers need auditable maintenance workflows without BAS-style device control.
More related reading
Building Engines
vertical specialistCommercial property operations software for work orders, inspections, tenant requests, and compliance.
Asset and workflow mapping that ties inspections to follow-up work orders with consistent operational history.
Building Engines supports preventive maintenance scheduling, asset-driven work orders, and inspection workflows that tie issues to corrective actions. It includes document management and reporting that help link recurring tasks to completion history. Admin controls focus on controlling process steps and permissions for operational roles, with audit-style traceability through activity records.
A common tradeoff is that deeper BAS and control integration work can depend on system-specific data sources and integration projects rather than pre-built connectivity for every control stack. Building Engines works best when maintenance and inspections are the primary operating motion, such as retail or mixed-use portfolios that need consistent service delivery across properties.
- +Workflow-driven work order execution with recurring task scheduling
- +Inspection and corrective action trails that connect field outcomes to follow-up
- +Portfolio operations reporting that aggregates status across assets
- +Automation hooks that connect operational events to external systems
- –BAS and sensor data integration may require custom effort
- –Advanced configuration depth can increase implementation time
- –Some analytics and dashboards may be less control-centric than CMMS-first tools
- –Complex multi-system environments can increase integration governance load
Facilities operations managers
Run preventive maintenance across sites
Fewer missed maintenance events
Regional maintenance supervisors
Convert inspection findings to work
Faster issue resolution
Show 2 more scenarios
Property operations coordinators
Track vendor and field execution
Clearer execution accountability
Captures field updates and produces portfolio-level reporting on open and completed items.
Enterprise integration teams
Automate operational event handoffs
Reduced manual coordination
Connects maintenance events to external systems using integration and automation capabilities.
Best for: Fits when facilities teams need traceable maintenance execution and inspections across multiple properties.
UpKeep
SMBMobile-first maintenance management software for work orders, assets, inspections, and facilities.
On-mobile photo attachments tied to work orders to preserve visual proof through task closure.
UpKeep centers on work orders, inspections, and asset-linked maintenance records, so operational context stays attached to the task lifecycle rather than living in separate spreadsheets. The platform’s mobile capture includes photo documentation and field-friendly execution, which reduces friction for documenting defects and closing work in place. For facilities teams, the best fit appears when maintenance is the coordination hub and other building systems remain separate but can be referenced through assets.
A key tradeoff is limited governance depth compared with enterprise IWMS-style suites that include broader tenant, leasing, or multi-department real-estate workflows. UpKeep works well when a single operations team needs consistent routing, checklists, and follow-up for recurring maintenance and inspections across multiple sites.
- +Mobile-first work capture with photo evidence on each job
- +Asset-linked work orders keep history attached to maintenance objects
- +Recurring inspections and checklists support consistent field execution
- +Workflow automation reduces manual status updates between crews
- –Governance controls are narrower than enterprise IWMS suites
- –Deeper building-system integrations require careful mapping to assets
- –Reporting breadth is less aligned to finance-grade operational analytics
- –Complex multi-department workflows can require extra configuration
Property operations teams
Route recurring inspections across multiple sites
Fewer missed items, faster closures
Maintenance supervisors
Track asset-linked work order histories
Better repeat-failure tracking
Show 2 more scenarios
Field service coordinators
Automate request-to-assign status flows
Reduced handoff delays
Teams convert requests into work orders and trigger assignments based on workflow rules.
Multi-site facility managers
Standardize maintenance checklists for crews
More uniform maintenance records
Managers roll out the same inspection structure to ensure consistent field documentation.
Best for: Fits when facilities teams need recurring maintenance workflows with strong mobile documentation.
More related reading
Yardi Voyager
enterpriseProperty management software with accounting, maintenance, leasing, and building operations modules.
Work order execution workflows that directly map to resident and account activity inside the same operational data set.
Yardi Voyager is positioned for building management within property operations, where day-to-day maintenance, approvals, and resident-facing processes share the same underlying operational context.
Core capabilities center on work order and task execution, operational reporting tied to those workflows, and configuration that enforces portfolio rules around how tasks move through approvals.
- +Tight linkage between work orders, residents, and account activity reduces reconciliation work
- +Portfolio configuration supports consistent approvals and task routing across many properties
- +Operational reporting reflects building workflows rather than generic ticketing patterns
- +Extensible integration options for property and operations data reduce duplicate entry
- –Workflow configuration can require heavy initial process mapping for new teams
- –Granular field-level customization may take advanced admin time
- –Deep facilities integrations can depend on specific connected modules and data setups
- –User interface navigation feels dense when teams only need a small subset of modules
Best for: Fits when multi-property teams need operational workflows tied to resident and work order records.
Spacewell
enterpriseBuilding operations software covering maintenance, workplace management, and energy performance.
Event-to-workflow automation that maps operational signals into routed tasks with traceable audit trails.
Spacewell coordinates building operations through an integration-focused workflow layer that connects facilities data to actions in real time. The solution centers on automated operational processes, including alarm and event handling, work routing, and maintenance execution tied to live building signals.
Spacewell also emphasizes extensibility via an API surface and configurable integrations for pulling sensor, system, and asset context into operational workflows. Governance is handled through role-based access controls and audit logging tied to configuration and user activity.
- +API-first integration approach for wiring building signals to workflows
- +Event-to-action automation reduces manual triage and routing work
- +Role-based access controls support controlled operational changes
- +Audit logging tracks configuration and user activity for governance
- –Setup requires careful mapping between building signals and workflow logic
- –Advanced automation design needs staff time for test and stabilization
- –UI configuration can feel procedural when workflows span many asset types
- –Integration coverage depends on the connected systems and adapters used
Best for: Fits when facilities teams need event-driven automation that ties building signals to actionable work across portfolios.
Facilio
API-firstCloud software for connected facilities, maintenance, energy, and building performance management.
Workflow automation that maps service-request data into work order creation and routing rules.
Facilio targets facilities teams that need end-to-end workflows for helpdesk, maintenance, and asset operations. It ties work orders to service requests, schedules preventive maintenance, and supports equipment and location hierarchies for recurring tasks.
The system adds digital-ops automation through configurable triggers and cross-team routing rather than only ticket logging. Integration coverage is strongest when utilities, metering, or external building systems can be connected through Facilio’s supported import, export, and API interfaces.
- +Configurable maintenance workflows connect requests to scheduled work
- +Asset and location structure supports recurring upkeep across portfolios
- +Automation rules route tasks based on priority, category, and status
- +Audit-friendly histories for requests, approvals, and work completion
- –Building-system integrations depend on supported connectors and endpoints
- –Complex governance needs careful role design and workflow ownership
- –Advanced reporting requires more configuration than basic dashboards
- –On-site execution features can lag behind CMMS depth for specialists
Best for: Fits when facilities teams want CMMS-style workflows plus request automation without building-system rewrites.
More related reading
Planon
enterpriseIntegrated workplace, facilities, real estate, and maintenance management software.
Workflow and execution models that bind master data for assets and locations to scheduled and on-demand field work.
Planon is a building management system vendor focused on asset, space, and workplace workflows rather than only maintenance ticketing. It connects facilities data to operational processes through configurable master data, scheduled activities, and document-driven field execution.
Planon’s integration story is shaped around an API and integration options that support event and master-data synchronization across other enterprise systems. The strongest fit shows up when governance over locations, assets, and work instructions needs to drive downstream automation.
- +Configurable workflows link assets, locations, and work instructions to execution
- +API-centric integration supports bidirectional synchronization with enterprise systems
- +Master data management for locations and assets improves reporting consistency
- +Automation based on schedules and task definitions reduces manual coordination
- –Initial configuration work is heavy when modeling assets and space hierarchies
- –Advanced automation depends on well-defined processes and consistent data entry
- –Reporting customization can require admin effort to match specific KPI layouts
- –Integration depth varies by external system and may need implementation support
Best for: Fits when facilities teams need governed asset and space workflows with API-driven integrations.
RealPage
enterpriseProperty management software for leasing, resident operations, maintenance, and portfolio administration.
Native work-order workflow automation that routes service tasks from operational events to tenant-facing updates through connected systems.
RealPage brings building operations under a property-centric workflow that ties maintenance requests, service scheduling, and resident communication to facility outcomes. The platform emphasizes integrations across property systems such as billing, work orders, and reporting so building leaders can run recurring operational processes without duplicating data.
Automation is oriented around property operations cadence, including task routing and exception handling triggered by operational events. RealPage also provides an API surface for system-to-system connectivity, which matters when integrations must feed operational dashboards and downstream tools.
- +API-first integration for connecting property systems to operational workflows
- +Work order and maintenance routing supports recurring service processes
- +Operational reporting ties maintenance activity to building performance views
- +Resident communication links service events to tenant-facing updates
- –Building automation and HVAC control integrations are not a primary focus
- –Governance for custom workflows requires careful role and permission design
- –Data consistency across multiple property systems can demand disciplined configuration
- –Advanced analytics often depend on exporting data to external tools
Best for: Fits when property operations teams need integrated work orders and resident updates tied to reliable system integrations.
More related reading
AppFolio
SMBProperty management software with leasing, maintenance, accounting, and resident communication tools.
Resident-facing maintenance intake flows into tracked work orders with inspection linkage for recurring property routines.
AppFolio manages multi-tenant property operations through modules for leasing, maintenance work orders, inspections, and accounting workflows. Building management teams use its maintenance intake and ticket routing to track preventive work, vendor activity, and resident-facing requests in one operational system.
Integration and automation are driven through appfolio integrations and web-facing service options that can connect operational events to other systems. Admin control is centered on role-based access inside AppFolio and process configuration for recurring tasks like inspections and recurring charges.
- +Maintenance work orders support resident requests and vendor assignment workflows
- +Inspections can be scheduled and documented as part of ongoing property routines
- +Accounting and tenant ledgers connect to operational charges and credits
- +RBAC supports separating admin, operations, and accounting permissions
- –No native building automation integration for HVAC or lighting controls
- –Work-order automation depends on configured forms and internal routing rules
- –Energy benchmarking and utility analytics are not a core operations focus
- –Governance over data integrations requires consistent admin configuration across teams
Best for: Fits when property operations teams need unified maintenance, inspections, and accounting workflows without BAS integrations.
MRI Software
enterpriseProperty and facilities software for commercial, residential, and public-sector buildings.
Workflow-driven maintenance and service operations that connect directly to tenant and unit context.
MRI Software fits organizations that need enterprise-grade property and facility workflows tied to rent and maintenance data. It combines property operations modules with maintenance work management, service request handling, and billing support for commercial portfolios.
Automation centers on configurable workflows and recurring processes across tenants, units, assets, and service histories. Integration depth is shaped by its API and export formats that support downstream reporting and operational systems.
- +Strong maintenance work management linked to property and tenant records
- +Configurable workflow automation for service requests and recurring tasks
- +API and data export support integration with external reporting and systems
- +Portfolio-oriented capabilities for multi-building operations
- –Operational setup breadth can require longer implementation cycles
- –BMS-specific integrations can depend on project-specific interfaces and partner inputs
- –Role separation and audit visibility may be limited for fine-grained governance
- –Advanced automation often needs administrative tuning of processes
Best for: Fits when facilities and property teams need integrated maintenance plus tenant and billing workflows across many assets.
Conclusion
After evaluating 10 facilities property services, Condo Control 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.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right building management software
Building management software in this buyer’s guide is evaluated around how work requests, inspections, and execution histories move through configured workflows in tools like Condo Control, Building Engines, UpKeep, and Yardi Voyager. The remaining picks address event-to-workflow automation and tenant-linked operations, including Spacewell, Facilio, Planon, RealPage, AppFolio, and MRI Software.
Across these tools, the practical difference comes from integration depth, automation wiring between signals and tasks, and governance mechanics that control who can route and close work items. Each section below ties capability to operational workflows tied to communities, units, assets, and tenant or resident records.
Building management software that ties maintenance workflows to assets, units, and operational events
Building management software coordinates maintenance execution using structured requests, asset or location mapping, scheduled recurring routines, and inspection-to-work-order follow-up. Condo Control is built around a request-to-work-order lifecycle with status history tied to communities and units. Building Engines extends that same inspection-to-follow-up model by mapping inspections to corrective work orders with consistent operational history across multiple properties.
In this guide, the key differentiators are how teams automate task routing from operational signals, and how each platform connects those tasks back to tenant, resident, or unit context. Spacewell is evaluated for event-to-workflow automation that maps building signals into routed tasks with traceable audit trails, while Facilio focuses on mapping service-request data into work order creation and routing rules.
Workflow visibility, asset mapping, and automation wiring
Building management software becomes operational only when requests, inspections, and field outcomes move through configured workflows with consistent auditability. These features define whether teams can route work from operational triggers to execution records, then close the loop back to residents, tenants, communities, and units.
Request-to-work-order lifecycle with status history
Condo Control ties request capture to work-order status history that stays associated with communities and units, which keeps resident and vendor tasks traceable. AppFolio also routes resident maintenance intake into tracked work orders, but it lacks building automation integration for HVAC or lighting controls.
Inspection mapping to follow-up work orders
Building Engines connects inspections to corrective work orders with inspection and corrective action trails that connect field outcomes to follow-up. Spacewell instead emphasizes event-to-workflow automation that routes building signals into actionable tasks with traceable audit trails.
Mobile evidence for closure and recurrence
UpKeep attaches on-mobile photo evidence to work orders so visual proof stays attached at task closure. Building Engines and Condo Control also support recurring workflows, but UpKeep’s mobile-first evidence workflow is the distinguishing execution detail.
Event-driven automation that turns signals into routed tasks
Spacewell is evaluated for event-to-workflow automation that maps operational signals into routed tasks with traceable audit trails. RealPage provides native work-order workflow automation that routes service tasks into tenant-facing updates through connected systems, but building automation and HVAC control integration is not its primary focus.
Bidirectional integration surface and automation extensibility
Planon is built around API-centric integration that supports bidirectional synchronization with enterprise systems and governed asset and space workflows. Spacewell is evaluated as API-first for wiring building signals to workflows, while RealPage and MRI Software can depend on project-specific interfaces and partner inputs for deeper BMS integrations.
Configuration governance for workflow routing and approvals
Yardi Voyager includes portfolio configuration that supports consistent approvals and task routing across many properties. Facilio focuses on request-to-work-order creation and routing rules, and governance depends on careful role design and workflow ownership to keep routing predictable.
Choose by automation philosophy, integration shape, and governance needs
The fastest path to clean operations comes from matching the platform’s workflow model to how work is initiated, routed, and closed in the facility environment. The key difference across these picks is whether operational signals and tenant-facing context are wired through a work-order workflow layer, a workflow automation layer, or an inspection-driven corrective loop.
Start from the event source that triggers work
Select Condo Control when work starts as resident or vendor requests and status history must remain tied to communities and units. Select Spacewell when operational signals must route directly into workflows through event-to-workflow automation with traceable audit trails.
Pick the execution model that matches inspections and recurrence
Choose Building Engines when inspections must map into corrective work orders and create consistent operational history across multiple properties. Choose UpKeep when mobile photo attachments are required for visual proof at the moment of task closure.
Decide how much wiring effort the team can run in the workflow layer
If the team can run careful mapping between building signals and workflow logic, Spacewell’s event-to-workflow automation fits operational triage and routing needs. If the team prefers request-to-work-order routing with connectors and supported endpoints, Facilio fits service-request data into work order creation with configurable routing rules.
Match tenant or resident context handling to operational data flows
Choose Yardi Voyager when work-order execution workflows must map directly to resident and account activity in the same operational data set. Choose RealPage when operational routing needs tenant-facing updates tied to reliable system integrations, not building automation as a primary integration target.
Use integration depth criteria to avoid BMS mismatch risk
Choose Planon when asset and space modeling needs API-driven integrations and bidirectional synchronization with enterprise systems. Avoid assuming broad BMS-specific integrations when the workflow needs partner-specific interfaces, which is highlighted in MRI Software’s BMS integration dependency.
Confirm governance mechanics for workflow ownership and admin time
Select Yardi Voyager when portfolio configuration needs consistent approvals and task routing across many properties with a defined admin model. Select Facilio or Planon when governance discipline is available because role design and workflow ownership determine whether request routing and advanced automation stay predictable.
Teams that benefit from specific workflow and automation wiring
Facilities, property operations, and HOA teams usually adopt building management software to reduce rework between intake, inspections, vendor assignment, and closure. These tools separate into distinct operational needs based on whether work begins from requests, inspection outcomes, or operational events, and whether tenant or resident records must stay tightly linked to execution histories.
HOA and condo managers managing resident and vendor maintenance requests
Condo Control is built around a request-to-work-order lifecycle with status history tied to communities and units, which keeps auditable workflows aligned to community boundaries.
Multi-property facilities teams that rely on inspections and corrective follow-up
Building Engines ties inspection and corrective action trails to follow-up work orders with operational history across multiple properties, which reduces the gap between field checks and remediation.
Property operations teams that need resident-facing work intake without BAS device control
AppFolio routes resident maintenance intake into tracked work orders with inspection linkage for recurring routines, while explicitly lacking native building automation integration for HVAC or lighting controls.
Portfolios that require event-driven routing from operational signals into tasks
Spacewell maps operational signals into routed tasks with traceable audit trails and uses an API-first integration approach for wiring signals to workflows.
Enterprises that model assets and locations with governed workflows and bidirectional sync
Planon binds master data for assets and locations to scheduled and on-demand field work, and it supports API-driven bidirectional synchronization with enterprise systems.
Pitfalls that break workflow execution and automation reliability
Many failed deployments come from choosing a workflow layer that does not match how work is initiated in the field, or from underestimating the mapping work needed for automation logic. Other failures come from governance gaps where workflow ownership and admin time are not planned for, which leads to inconsistent routing and incomplete closure evidence.
Assuming building automation integration is a primary capability in workflow-first property platforms
AppFolio and RealPage emphasize tenant-facing workflows, and both highlight that building automation and HVAC control integration is not their core focus, which can block BAS-level device workflows.
Building event automation without allocating mapping and stabilization cycles
Spacewell’s event-to-workflow automation requires careful mapping between building signals and workflow logic, and advanced automation design needs staff time for test and stabilization.
Leaving mobile evidence requirements out of the closure workflow
UpKeep’s standout feature is mobile photo attachments tied to work orders, so teams that need consistent visual proof should confirm that photo evidence is mandatory in the closure flow.
Underestimating workflow configuration effort for routing and approvals
Yardi Voyager can require heavy initial process mapping for new teams, and Facilio requires careful role design and workflow ownership, which can derail routing consistency if governance is not planned.
Over-modeling assets and space hierarchies without a clear data entry discipline
Planon’s initial configuration work is heavy when modeling asset and space hierarchies, and advanced automation depends on well-defined processes and consistent data entry.
How We Selected and Ranked These Tools
We evaluated each platform on workflow-driven work order execution clarity, inspection or request traceability, and how operational events get wired into routed tasks. Features account for 40% of the ranking because tools like Condo Control and Building Engines demonstrate distinct workflow lifecycles tied to communities, units, assets, and follow-up work.
Ease and value each account for 30% because teams need predictable configuration and admin effort to keep routing and closure consistent across properties. Condo Control earned the top position because its request-to-work-order lifecycle keeps status history tied to communities and units while also supporting recurring maintenance scheduling for repeat inspections and service cycles.
Frequently Asked Questions About building management software
How should a facilities team compare workflow depth between Archibus, Yardi Voyager, and Building Engines?
Which tools support API-driven extensibility for event-to-work automation?
How do SSO and RBAC controls typically differ across enterprise-focused suites like MRI Software and AppFolio?
When is data migration most risky, and how do these systems reduce friction?
What breaks if a building management system lacks a clear work-order lifecycle and status history?
How should admin controls be evaluated for multi-property operations in Yardi Voyager versus RealPage?
Which tools work well when request intake must map directly to vendor activity or field completion?
How do event-driven workflows differ from master-data driven workflows in Spacewell versus Planon?
What integration assumptions should teams validate before implementing Spacewell, Facilio, or MRI Software?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Facilities Property Services alternatives
See side-by-side comparisons of facilities property services tools and pick the right one for your stack.
Compare facilities property services tools→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 ListingWHAT 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.