Commissioned Research
Top 10 Best IT Change Management Software of 2026

GITNUXSOFTWARE REVIEW

Technology & Digital Media

Top 10 Best IT Change Management Software of 2026

Compare it change management software options and where they fit, with tradeoffs for teams using tools like Freshservice.

20 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

Agents extract product evidence with provenance, then collect written reviews and transcribe 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

IT teams use change management software to control release throughput with structured planning, impact analysis, and governed approvals logged for audit. This comparison helps technical evaluators weigh tradeoffs in automation depth, CMDB or service graph integration, and extensibility when systems like ServiceNow, BMC Helix, and TOPdesk act as process engines.

TeamDynamix is the best choice for mid-market IT orgs because its workflow-driven approvals keep clear decision points and audit history attached to each change record, while Freshservice is the better fit for SMB teams that want emergency and normal handling with configurable approvals tied into the same change lifecycle.

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

TeamDynamix

Workflow-driven change approvals that keep decision points and audit history attached to each change record.

Best for: Fits when mid-market IT organizations need configurable approvals and traceability in change requests.

2

Agiloft

Editor pick

Model-driven change lifecycles that enforce allowed transitions and approval gates across standard, normal, and emergency flows.

Best for: Fits when enterprises need highly configurable change record workflows with controlled approvals and strong integration.

3

Freshservice

Editor pick

Emergency change handling with a separate workflow path tied into the same change record lifecycle.

Best for: Fits when IT teams need configurable approvals and change context linking without custom tooling.

Comparison Table

1
TeamDynamixBest overall
enterprise
9.0/10
Overall
2
enterprise
8.9/10
Overall
3
8.6/10
Overall
4
enterprise
8.5/10
Overall
5
8.3/10
Overall
6
enterprise
7.9/10
Overall
7
7.4/10
Overall
8
enterprise
7.2/10
Overall
9
SMB
6.9/10
Overall
10
6.5/10
Overall
#1

TeamDynamix

enterprise

ITSM and ITAM platform with change management, CMDB, and project portfolio integration.

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

Workflow-driven change approvals that keep decision points and audit history attached to each change record.

TeamDynamix fits IT teams that already run ITSM processes in a web work-management environment and need change workflows with clear approvals and traceability. The solution supports change request lifecycles, configurable approval paths, and audit-focused reporting across change records.

TeamDynamix also provides integration and extensibility options through an API and workflow configuration patterns that connect change with related work items. For organizations that require governance around change types and execution steps, TeamDynamix can centralize those controls without breaking the surrounding IT ticketing workflows.

Pros
  • +Approval workflow configuration tied to change records for consistent governance
  • +Audit-friendly change history with links to related work artifacts
  • +API-based integrations for connecting change with other IT systems
  • +Configurable fields and statuses to fit common change lifecycle variations
Cons
  • –Complex workflows take careful setup to avoid inconsistent approval routing
  • –Change models and templates require admin maintenance as process rules evolve
  • –Reporting depth depends on how metadata is captured in each change record
  • –Deep automation beyond standard workflow steps can require custom development
Use scenarios
  • IT operations and change managers

    Analyze impacted services before approving changes

    Better affected service visibility

  • IT service desks

    Standardize intake for incidents and requests

    More consistent ticket handling

Show 2 more scenarios
  • PMOs and IT delivery teams

    Convert requests into project execution

    Connected demand to execution

    Transforms service or work requests into project records and execution tasks.

  • IT and shared service teams

    Route requests through approvals and fulfillment

    Controlled lifecycles with audits

    Collects requests through catalog forms and moves them through approved lifecycle steps.

Best for: Fits when mid-market IT organizations need configurable approvals and traceability in change requests.

#2

Agiloft

enterprise

No-code ITSM platform with change management workflows, approval routing, and audit trails.

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

Model-driven change lifecycles that enforce allowed transitions and approval gates across standard, normal, and emergency flows.

Agiloft focuses on workflow-driven change management built around configurable change record lifecycles. Strong automation is delivered through rule-driven tasking tied to approval steps, status changes, and controlled transitions between change models.

The system supports integration and extensibility via an API for connecting change requests to external ticketing, CMDB, and reporting systems. Admin governance is reinforced with role-based access controls and audit logging for who changed records, when decisions were made, and which fields were updated.

Pros
  • +Configurable change record workflows with rule-based transitions and approvals
  • +API-first integration for syncing change requests with external systems
  • +Audit logging for field-level history tied to approvals and status changes
  • +Role-based access controls support segregation of duties across workflow steps
Cons
  • –Complex workflow configuration can slow initial build and iteration
  • –Reporting breadth depends heavily on how fields and views are modeled
  • –Some change model patterns require deeper customization to fit tightly
  • –Automation design needs governance discipline to prevent approval bypasses
Use scenarios
  • Contract administrators and business owners

    Coordinate renewals and notice actions

    Clear upcoming contract actions

  • Legal, procurement, and contract teams

    Retrieve agreements by business metadata

    Easier lifecycle review

Show 2 more scenarios
  • Legal operations and contract owners

    Monitor post-signature obligations

    More structured obligation follow-up

    Tracks commitments, milestones, and lifecycle actions after contract execution.

  • Legal operations and compliance teams

    Review audit history of contract changes

    Traceable contract activity history

    Uses version and workflow histories to examine approvals, amendments, and record changes.

Best for: Fits when enterprises need highly configurable change record workflows with controlled approvals and strong integration.

#3

Freshservice

SMB

Cloud-based ITSM tool with change management module included in higher-tier plans.

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

Emergency change handling with a separate workflow path tied into the same change record lifecycle.

Freshservice focuses on IT change request workflows with role-based approvals and configurable change types, including normal and emergency paths. It ties changes to related work such as incidents and problems so change execution can account for prior context.

Administration centers on audit-ready activity history, workflow configuration controls, and a permissions model that supports segregation of duties. Extensibility is available through APIs and automation hooks that fit change intake, approvals, and downstream notifications.

Pros
  • +Configurable approval workflows for change requests with emergency and normal handling
  • +Links changes to related incidents and problems for execution context
  • +Audit history tracks key actions on change records
  • +APIs enable automation for intake, state changes, and notifications
Cons
  • –Some advanced governance steps require additional workflow configuration effort
  • –Change model reuse is available but limited for deeply tailored submission forms
  • –Granular reporting across approval outcomes needs extra setup beyond defaults
  • –Deep change calendar controls rely on workflow discipline rather than scheduling enforcement
Use scenarios
  • IT operations and change managers

    Record approvals and execution evidence

    Traceable execution history

  • Infrastructure and release teams

    Govern changes inside approved windows

    Controlled maintenance timing

Show 2 more scenarios
  • Service desk managers and support operations

    Escalate when SLA thresholds approach

    Service performance visibility

    Applies response and resolution targets and escalates when tickets near or breach thresholds.

  • IT support teams handling phone calls

    Turn calls into structured updates

    Continuity between calls and records

    Converts phone interactions into incident or request updates with follow-up actions.

Best for: Fits when IT teams need configurable approvals and change context linking without custom tooling.

#4

BMC Helix ITSM

enterprise

Enterprise ITSM suite with change management built on AI-driven automation.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

BMC Helix ITSM keeps execution status, approvals, and history on each change record for end-to-end traceability.

BMC Helix ITSM supports end-to-end change workflows with structured change records, mandatory fields per process design, and gated approvals based on risk and change type. Change scheduling and blackout awareness help prevent approvals that conflict with maintenance windows or restricted periods. Audit-ready traceability is maintained through versioned work steps and history on key change decisions.

Pros
  • +Workflow governance supports multi-stage approvals and enforced required fields
  • +Automation and integrations connect change execution with downstream operations
  • +Change history retains decision context for later operational review
  • +Scheduling controls reduce conflicts with planned maintenance periods
Cons
  • –Process design requires disciplined configuration before broad rollout
  • –Advanced automation often depends on external integration points
  • –Large deployments can increase admin overhead for workflow tuning
  • –Role and approval logic can be harder to debug than simple ticketing
Use scenarios
  • IT operations governance teams

    Enforce approval rules on all changes

    Fewer unauthorized or late approvals

  • Service desk change coordinators

    Schedule work around restricted windows

    Fewer calendar conflicts

Show 2 more scenarios
  • Platform engineering operations

    Link change outcomes to service impact

    Faster change failure analysis

    Connect change records to incidents and service operations to speed up root-cause review.

  • Compliance and audit stakeholders

    Retain decision history for reporting

    Cleaner audit trails

    Use built-in change history to demonstrate who approved what and when execution completed.

Best for: Fits when enterprises need controlled change workflows with scheduling gates and operational traceability.

#5

TOPdesk

SMB

ITSM platform with change management, CMDB integration, and change calendar for ITIL-aligned workflows.

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

Change calendar planning tied to change models, including enforceable timing constraints across requests.

TOPdesk handles IT change requests through configurable approval workflows, change records, and linked implementation details for each change.

Pros
  • +Change models reduce duplicate authoring for repeatable standard change types.
  • +Change calendar helps coordinate change windows and blackout periods for planning.
  • +Workflow configuration supports layered approvals tied to change records.
  • +Audit trails provide traceability across status changes and decision points.
Cons
  • –Complex approval chains need careful setup to avoid stalled change requests.
  • –Deep integration into non-TOPdesk ITSM processes depends on available connectors.
  • –Cross-system impact assessment workflows require external data inputs.
  • –Bulk change operations are limited compared with tools built for high volume governance.
Use scenarios
  • IT operations and change managers

    Run risk assessment and CAB approvals

    Traceable decision history

  • IT support and asset managers

    Link changes to affected assets

    Better affected equipment visibility

Show 2 more scenarios
  • Service desk managers and support agents

    Generate knowledge from recurring issues

    More repeatable guidance

    Creates and publishes knowledge content that supports repeatable resolution during ticket handling.

  • Facilities and shared service teams

    Coordinate facilities work alongside IT

    Common operational request workflow

    Runs facilities requests through work orders, assignments, and status updates in shared workflows.

Best for: Fits when mid-size IT teams need calendar-driven change planning with configurable approvals.

#6

EasyVista

enterprise

ITSM platform with automated change approvals, impact analysis, and CMDB-driven risk assessment.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Change calendar controls with window and blackout enforcement tied to approval and execution steps.

EasyVista manages IT change workflows through a structured change request to approval to implementation flow. It integrates change planning with service and asset context so change records can link to configuration items and operational impact.

Pros
  • +Linkage from change records to configuration items supports impact traceability
  • +Approval workflows can incorporate multi-step roles and conditional routing
  • +Change calendars and blackout windows help enforce change windows discipline
  • +Execution checklists and evidence capture support consistent implementation records
Cons
  • –Workflow modeling takes configuration discipline to avoid inconsistent approvals
  • –Deep integration requires careful mapping between change objects and external sources
  • –Reporting requires tuning to align with internal change KPIs
  • –Complex emergency handling workflows need explicit guardrails in process design
Use scenarios
  • Change managers and IT operations teams

    Handle assessment and conditional approvals

    Controlled traceable changes

  • Release managers and infrastructure teams

    Coordinate work with blackout controls

    Better maintenance window adherence

Show 2 more scenarios
  • IT asset managers and configuration managers

    Assess impact using service and asset context

    Improved service and asset traceability

    Connects service and change records with asset or configuration information for operational impact.

  • IT service desk managers and agents

    Centralize workflow-driven service support

    More consistent routing and resolution

    Centralizes incident handling, service requests, and fulfillment using workflow-driven support activities.

Best for: Fits when enterprises need governed change workflows linked to asset and service context.

#7

Spiceworks IT Department

SMB

Free IT management toolset with basic change request ticketing for small IT teams.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Spiceworks change requests connect to the same device inventory used for tickets, keeping impact context in one workflow.

Spiceworks IT Department organizes change requests as actionable records and keeps change visibility connected to configuration context from asset inventories. Teams can route work through approval workflows and attach implementation and backout plans to the change record for operational continuity. Emergency handling can be tracked separately from normal work so reviews and sequencing stay readable during urgent windows.

Pros
  • +Change records can link to discovered devices and services
  • +Approval routing stays inside the same operational workflow
  • +Emergency versus normal change tracking is built into request handling
  • +Plans and notes can be kept attached to each change record
Cons
  • –Audit log depth across approval and execution steps is limited
  • –Enterprise RBAC for change roles needs careful configuration discipline
  • –API and automation coverage is narrower than developer-first change tools
  • –Complex change models and multi-step governance can feel constrained
Use scenarios
  • IT service desk teams

    Record approvals for routine updates

    Faster scheduling and fewer context gaps

  • Infrastructure administrators

    Track emergency changes during outages

    Clearer emergency decision trails

Show 1 more scenario
  • Change coordinators

    Communicate planned work across teams

    More consistent execution and recovery

    Store implementation and backout instructions on the change record for handoffs.

Best for: Fits when mid-size IT teams want change records tied to ticket and asset context, with lightweight approval workflow.

#8

ServiceNow ITSM

enterprise

Enterprise ITSM with structured change planning, approvals, risk assessment, and audit controls.

7.2/10
Overall
Features7.2/10
Ease of Use7.1/10
Value7.3/10
Standout feature

Change records can inherit rules from change models and execution plans, then propagate approvals and documentation automatically.

ServiceNow ITSM supports standard, normal, and emergency change processing with configurable approval flows, required fields, and stage gates tied to the change record. Change advisory board activities can be represented with scheduled review tasks, decision capture, and workflow-driven notifications. CMDB-linked dependencies let risk and impact assessment reference configuration items and their relationships.

Pros
  • +Workflow-driven approval routing tied to change records
  • +CMDB dependency context helps drive impact assessment decisions
  • +Automated post-implementation review artifacts and follow-up tasks
  • +Extensibility through platform APIs and integration capabilities
Cons
  • –Governance consistency requires careful configuration of change models and states
  • –Complex rule sets can make troubleshooting routing and approvals harder
  • –Cab scheduling and decision workflows may need additional workflow design
  • –Deep customization increases admin overhead for larger estates
Use scenarios
  • Enterprise IT operations

    CAB-managed change execution with documentation

    Fewer approval misses

  • Infrastructure and SRE teams

    Emergency change with controlled backout planning

    Faster, safer change handling

Show 2 more scenarios
  • Service management governance

    Dependency-driven risk assessment

    More consistent risk reasoning

    Leverage CMDB relationships to inform impact assessment and standardize risk documentation.

  • IT change managers

    Post-implementation review linkage

    Better change learning loop

    Create post-implementation review tasks tied to the change record and relevant outcomes for follow-up.

Best for: Fits when enterprises need dependency-aware change workflows and enforceable approval gates.

#9

Giva

SMB

Cloud-based ITSM tool with change management, approval workflows, and SLA tracking.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Stage-driven approval workflows that automatically route based on change model selection and urgency handling.

Giva centers IT change management on structured change request lifecycles that record decisions, approvals, and implementation artifacts.

Pros
  • +Configurable approval paths aligned to change stage and urgency
  • +Change models reduce duplicate effort for repeat request patterns
  • +Workflow automation moves requests via timers and conditional actions
  • +Governance permissions restrict who can view and act per change state
Cons
  • –Advanced automation needs governance discipline to avoid misrouted approvals
  • –Role setup for CAB and emergency paths can be time consuming
Use scenarios
  • IT service management teams

    Standardize change requests across services

    Reduced approval and rework

  • Change managers in enterprises

    Run emergency and normal workflows

    Faster recovery with control

Show 2 more scenarios
  • IT governance and compliance

    Control who can act on changes

    Stronger audit readiness

    Permissioning ties user access to change states and actions for governance-friendly oversight.

  • Automation and operations leaders

    Automate approval timelines and routing

    Fewer stalled change records

    Timers and conditional routing advance workflow steps when configured states are reached.

Best for: Fits when IT teams need configurable change request routing with governance controls and automated timers.

#10

Motadata ServiceOps

SMB

ITIL 4 change enablement software with CAB/ECAB workflows, change calendar, and backout planning.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Evidence-linked change records that tie implementation outcomes back to the same operational context used for planning and approval.

Motadata ServiceOps targets IT change management teams that need audit-ready change records tied to a defined service and configuration context. It emphasizes controlled workflows for approvals and implementation steps, plus evidence capture to support change reviews.

Pros
  • +Approval workflows can enforce multi-step gating per change type
  • +Change records stay linked to affected services and operational artifacts
  • +Automation hooks reduce manual status updates during execution
  • +Evidence capture supports repeatable post-change review
Cons
  • –Configuration item mapping requires careful alignment with existing CMDB structure
  • –Complex governance flows can slow change submission throughput
  • –API depth for end-to-end workflow state modeling is less granular than process-centric tools
  • –Advanced reporting needs tighter setup of required fields and transitions
Use scenarios
  • IT change manager teams

    Track standard and emergency changes end-to-end

    Audit-ready change documentation

  • IT operations analysts

    Link change execution to services and configurations

    Aligned change and operations status

Show 2 more scenarios
  • Compliance and internal audit staff

    Verify controlled workflows and decision records

    Faster compliance verification

    The workflow captures who approved steps and what evidence was produced for compliance checks.

  • Service desk and ITSM coordinators

    Coordinate implementations with workflow-driven steps

    More consistent implementation records

    Coordinators manage change steps and capture outcomes to support consistent implementation handling.

Best for: Fits when change coordinators need audit-ready workflows with execution-linked traceability for service operations.

Conclusion

After evaluating 10 it change management software, TeamDynamix 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
TeamDynamix

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 It Change Management Software

Which tool supports change models that automatically govern approvals and documentation across change classes?
ServiceNow ITSM supports change models that can drive distinct authorization and documentation paths for different change classes. Agiloft also enforces allowed transitions and approval gates by using model-driven change lifecycles.
How does emergency change handling differ from standard change workflows in leading IT change management tools?
Freshservice runs an emergency workflow path tied to the same change record lifecycle, while keeping the approval steps configurable for emergency handling. Giva uses stage-driven approval workflows that route based on change model selection and urgency handling.
Which platforms provide role-based access control and audit history for change record governance?
Agiloft includes role-based access controls and audit logging that records who changed records and which fields were updated. TOPdesk provides audit visibility across the change lifecycle using assignment controls and role-based permissions.
How do integrations and APIs typically connect change management to incident and problem processes?
BMC Helix ITSM connects change execution to incident and problem lifecycles through configurable processes and integration options. TeamDynamix provides an API and workflow configuration patterns to connect change records to related work items in a work-management environment.
Which tools keep implementation outcomes and evidence linked back to the same context used during planning and approval?
Motadata ServiceOps emphasizes evidence-linked change records so implementation outcomes tie back to the operational context used for planning and approval. Giva also stores traceable implementation artifacts as part of the change request lifecycle stages.
What breaks if change calendar constraints are required, but the workflow lacks window and blackout enforcement?
EasyVista enforces change calendar controls with window and blackout enforcement tied to approval and execution steps. Without that enforcement, scheduling gates that depend on change windows and blackout periods can fail to prevent execution outside approved time controls.
How is segregation of duties enforced during approval workflow configuration?
Freshservice supports role-based approvals and a permissions model designed to support segregation of duties. Agiloft reinforces governance with controlled transitions between change models and approval steps.
Which tool is best suited for enterprises that need dependency-aware change workflows with enforceable approval gates?
ServiceNow ITSM fits enterprise dependency-aware workflows because it provides dependency-aware change workflows and enforceable approval gates inside the lifecycle. BMC Helix ITSM fits teams that need scheduling gates and operational traceability tied to change records.
How does data migration impact adoption when moving change records and historical audit data into a new system?
Agiloft is migration-sensitive because change record lifecycles and rule-driven tasking depend on configuration and allowed transitions that must be mapped to the target data model. Freshservice also relies on workflow configuration controls and audit-ready activity history, so migrated field mappings must preserve the change state history.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right It Change Management Software

We look at how reliably it change management software routes, records, and enforces change work across teams. The biggest differences show up in audit log depth, automation and API surface, and how well approval workflow rules reflect real operational throughput.

Request-to-approval traceability

Why it matters

Request-to-approval traceability matters because change work fails when people cannot see who approved what and when, especially during high volume. It also affects audit log usefulness during post-implementation review.

How to check

Create a sample change request and walk it through approval to completion. Then open the record and confirm each step shows the approver, timestamp, and resulting implementation status in one view.

Approval workflow with role rules

Why it matters

Approval workflow with role rules matters because teams need consistent gating without manual follow-up. Strong admin and governance controls reduce bypass risk and keep RBAC aligned with responsibilities.

How to check

On a demo, ask to configure different approvals based on team and change type. Verify the system blocks completion until required approvals are recorded, and that role changes immediately update who can approve.

Audit log across lifecycle edits

Why it matters

Audit log completeness matters because governance requires seeing every meaningful edit, not just final outcomes. It helps detect unauthorized change and supports accountability after implementation.

How to check

Edit a request field, then resubmit, then update implementation notes. Confirm the audit log captures the actor, field changed, and before/after values for each lifecycle stage.

Automation and API surface for updates

Why it matters

Automation and API surface matters because teams often push tickets from other systems and want consistent lifecycle transitions. Better extensibility reduces manual retyping and keeps throughput steady.

How to check

Ask what events trigger automation (for example, status changes) and what endpoints support reading and updating request fields. In a sandbox, try importing one request via API and verify it still lands with correct workflow and audit history.

Change record structure and retrieval

Why it matters

Change record structure and retrieval matter because people need to find prior work quickly and reuse it. A clear data model supports fast lookups during impact follow-ups and post-implementation review.

How to check

Search for a previously completed change by a keyword and by fields you would actually maintain (like owner, service area, status). Check whether the system returns the full change record and its linked artifacts in a predictable layout.

Red flags

  • Approvals show up, but the lifecycle timeline is missing key steps
  • Audit log records only status changes, not field edits and resubmissions
  • API or automation can move requests, but it breaks workflow history and permissions

Fit by situation

  • If you run approvals across multiple teams and need consistent gating, prioritize approval workflow with role rules.
  • If you rely on after-the-fact investigations, prioritize audit log across lifecycle edits.
  • If you import and update change work from other systems, prioritize automation and API surface for updates.
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.