Commissioned Research
Top 10 Best Insurance Claims Processing Software of 2026

GITNUXSOFTWARE ADVICE

Financial Services Insurance

Top 10 Best Insurance Claims Processing Software of 2026

Ranked roundup of top insurance claims processing software with notes on Sapiens Claims, Guidewire ClaimCenter, ClaimLogiq, and Snapsheet.

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

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 rankings. Editorial policy

Insurance claims processing software determines how claims are routed, adjudicated, and paid through configurable workflows, data models, and audit-ready controls. This ranked list targets analysts and operators comparing automation depth, integration and API fit, and throughput across carriers, TPAs, and captives, using verified evaluation criteria rather than vendor claims.

Choose ClaimLogiq if you’re a health insurer that needs rule-driven FNOL intake routing and controlled automation with audit-ready case history, while Claimable is the better fit when TPAs or self-insured teams want workflow automation across intake to handling with external payments and reporting.

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

ClaimLogiq

Rule-driven assignment and escalation logic that ties triage outcomes to adjuster work queues and stage tasks.

Best for: Fits when carriers need rule-based FNOL intake routing and controlled automation with audit-ready case history.

2

Claimable

Editor pick

Adjuster workbench workflows that keep intake fields, tasks, and document attachments linked to each claim lifecycle.

Best for: Fits when claims teams need workflow automation for intake through handling, with external systems for payments and reporting.

3

Snapsheet

Editor pick

Inspection-centric claim intake that uses photo evidence to drive routing and adjuster review tasks.

Best for: Fits when property teams need image-centric FNOL intake with automated routing and adjuster task coordination.

Comparison Table

1
ClaimLogiqBest overall
enterprise
9.5/10
Overall
2
9.2/10
Overall
3
8.9/10
Overall
4
8.5/10
Overall
5
8.2/10
Overall
6
7.9/10
Overall
7
enterprise
7.5/10
Overall
8
7.2/10
Overall
9
enterprise
6.9/10
Overall
10
6.6/10
Overall
#1

ClaimLogiq

enterprise

Claims payment integrity platform for health insurers detecting waste and fraud.

9.5/10
Overall
Features9.6/10
Ease of Use9.4/10
Value9.6/10
Standout feature

Rule-driven assignment and escalation logic that ties triage outcomes to adjuster work queues and stage tasks.

ClaimLogiq is engineered for claim lifecycle workflow control, starting with FNOL intake routing into a case workbench for adjusters. The workflow layer uses configurable assignment and triage rules to direct claims into the right queue based on rule outcomes and supporting data from the intake packet. Document ingestion feeds a structured claim record, which supports proof-of-loss attachment handling and case notes tied to each stage.

A key tradeoff is that complex carrier-specific governance, including settlement authority limits and state-specific compliance branching, depends on careful rule and workflow configuration rather than out-of-the-box coverage. ClaimLogiq fits best when an insurer or third-party administrator needs consistent automation for frequent claim types and then controlled escalation paths for high-severity work.

Pros
  • +Configurable triage rules route claims into the correct adjuster queues
  • +Case workbench keeps tasks, notes, and document links within one audit trail
  • +Automation supports low-complexity handling with structured escalation triggers
  • +API access supports integration with surrounding carrier and administrator systems
Cons
  • –State-specific rule branching requires disciplined configuration and testing
  • –High-complexity litigation workflows may need additional process mapping
Use scenarios
  • Claims operations teams

    Standardize FNOL triage and routing

    Reduced misrouted workload

  • Third-party administrators

    Scale adjuster capacity per territory

    Lower claim backlogs

Show 2 more scenarios
  • Insurance IT integration teams

    Connect claim workflow to core systems

    Fewer manual data transfers

    Use the product API surface to exchange claim events and update case state across systems.

  • Claims QA and compliance

    Maintain an audit trail across stages

    Faster file reviews

    Rely on stage-linked notes and document associations to support claim file audit trail needs.

Best for: Fits when carriers need rule-based FNOL intake routing and controlled automation with audit-ready case history.

#2

Claimable

SMB

Claims management software for third-party administrators and self-insured organizations.

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

Adjuster workbench workflows that keep intake fields, tasks, and document attachments linked to each claim lifecycle.

Claimable fits teams that need a configurable adjuster workbench without building custom screens for each carrier line or office. The workflow layer supports routing claim work, managing diaries and task queues, and tracking the work history inside a claim record. Document handling is built around intake through structured fields and attachments that remain tied to the claim lifecycle. Integrations target common insurance system touchpoints so claims can start with existing policy and loss information and then continue with updates.

A key tradeoff is that Claimable’s automation tends to be workflow-driven rather than a deep set of adjudication and accounting modules for reserves, payments, and reporting that carriers expect from dedicated core claim suites. It is a strong fit when the goal is faster internal handling and better adjuster execution on low-to-mid complexity matters. It is a weaker fit when the organization requires heavy native support for regulatory reporting extracts, detailed payment reconciliation, and line-of-business specific rating and settlement logic.

Pros
  • +Configurable adjuster workflow with clear task progression per claim
  • +Case history keeps notes, documents, and actions tied to one lifecycle
  • +Integration points help move claim data between external systems
  • +Automation reduces manual status chasing for follow-up work
Cons
  • –Limited depth for reserves, settlement accounting, and reporting workflows
  • –Workflow automation still depends on careful configuration of routing rules
  • –Advanced line-of-business adjudication requires external systems
  • –Deep analytics and audit reporting can require extra setup work
Use scenarios
  • Third-party administrators and service firms

    Route FNOL intake to adjuster tasks

    Lower internal handling delays

  • Independent adjuster networks

    Standardize work steps across offices

    More consistent case handling

Show 2 more scenarios
  • Claims operations teams

    Automate status updates between systems

    Fewer manual status syncs

    Integrations support pushing claim status and syncing claim context during ongoing handling.

  • Mid-size insurers and MGAs

    Streamline low-complexity claim handling

    Faster claim file readiness

    Guided task execution reduces manual chasing for proofs of loss, documentation, and contact steps.

Best for: Fits when claims teams need workflow automation for intake through handling, with external systems for payments and reporting.

#3

Snapsheet

SMB

Digital claims management platform with virtual appraisal and payment capabilities.

8.9/10
Overall
Features8.8/10
Ease of Use9.1/10
Value8.8/10
Standout feature

Inspection-centric claim intake that uses photo evidence to drive routing and adjuster review tasks.

Snapsheet’s differentiator is an inspection-driven workflow that treats photographs and field notes as primary claim inputs, which reduces reliance on static forms for initial evaluation. The system organizes each claim around an adjuster workbench, with configurable intake steps, diary notes, and task handoffs across claim lifecycle stages. Integration is geared toward operational throughput, with API access used to connect claim management records, file retrieval, and external event updates.

A tradeoff is that image-first processing can require stricter front-end data capture to avoid downstream review gaps for low-information FNOL submissions. It fits teams that handle property damage inventories and early damage assessment at scale, especially when adjuster teams need consistent assignment routing and faster proof-of-loss collection.

Pros
  • +Photo-first intake supports faster early damage assessment workflows
  • +Rule-based routing keeps assignments aligned with configurable triage criteria
  • +Adjuster workbench consolidates images, notes, and task status per claim
  • +Carrier-to-claimant interactions support proof-of-loss attachment collection
Cons
  • –Image-first intake can penalize claims with incomplete evidence capture
  • –Complex enterprise governance for routing rules needs disciplined configuration
  • –Deep policy and coverage rule automation may require additional system integration
  • –Large litigation and subrogation workflows can feel lighter than document-heavy suites
Use scenarios
  • Claims operations managers

    Automate early triage assignment decisions

    Fewer manual handoffs

  • Staff adjusters

    Review damage evidence in one workbench

    Shorter review cycles

Show 2 more scenarios
  • Third-party administrators

    Coordinate claim lifecycle tasks at scale

    Higher operational throughput

    Workflow automation maintains consistent status updates across claim stages and external triggers.

  • Carrier digital claims teams

    Collect proof-of-loss through portal

    Less evidence chasing

    Portal-based submission streamlines photo uploads and status notifications for policyholders.

Best for: Fits when property teams need image-centric FNOL intake with automated routing and adjuster task coordination.

#4

Duck Creek Claims

enterprise

Claims management system for P&C insurers with automated adjudication and payment processing.

8.5/10
Overall
Features8.8/10
Ease of Use8.3/10
Value8.4/10
Standout feature

Claims workflow configuration tied to Duck Creek’s broader platform event model supports enterprise routing and document orchestration in one execution path.

Duck Creek Claims is an insurance claims processing software suite used to manage end-to-end claim lifecycle workflows. Its differentiator is deep integration with the Duck Creek ecosystem, including configurable work routing, adjuster-centric processing screens, and document and data handling tied to the carrier claims workflow.

Pros
  • +Workflow orchestration supports detailed claim lifecycle state management
  • +Extensive integration options support enterprise system event handoffs
  • +Adjuster-focused work queues and tasks align with day-to-day handling
  • +Configuration options reduce custom code needs for common routing patterns
Cons
  • –Configuration depth can increase implementation and change-control overhead
  • –API and automation coverage depends on connected modules and integrations
  • –Admin governance for complex routing logic requires ongoing operational discipline
  • –Reporting and analytics breadth depends on integration with downstream systems

Best for: Fits when carriers need configurable claim workflows with strong enterprise integration and adjuster task management.

#5

ClaimFlow

SMB

Automated claims routing and processing for digital insurers.

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

Workflow checkpoint gating that ties required documents and approvals to each claim lifecycle step.

ClaimFlow is a claims processing workflow system built to manage claim intake through adjuster handling and claim closure. It focuses on routing work items, supporting adjuster workbenc h timelines with audit trail, and automating status-driven notifications and tasks.

Pros
  • +Configurable lifecycle states that map to claim handling steps and approvals
  • +Work routing rules reduce manual triage and keep tasks aligned to ownership
  • +Document attachments can be tied to workflow checkpoints for file completeness
  • +Status-driven notifications support consistent claimant and internal updates
Cons
  • –Limited visibility into reserve setting workflows and reserve adequacy reporting
  • –API depth is unclear for standards like ACORD forms and X12 claim submissions
  • –Advanced automation beyond routing and notifications depends on careful configuration
  • –Fine-grained governance controls like RBAC scope and audit log retention need validation

Best for: Fits when mid-market carriers or TPAs need workflow-driven claim handling with configurable routing and task orchestration.

#6

Guidewire ClaimCenter

enterprise

Claims management software for property and casualty insurers with workflow and settlement tools.

7.9/10
Overall
Features7.7/10
Ease of Use8.0/10
Value7.9/10
Standout feature

Authority and workflow control around settlement handling, including supervisory and committee style approvals tied to claim activity.

Guidewire ClaimCenter is an enterprise claim lifecycle system built for insurance carriers that need configurable workflows for FNOL intake through claim closure. Its claim handling depth focuses on adjuster workbenches, assignment and triage rules, reserve setting support, and multi-line processing with document and status tracking.

Pros
  • +Configurable claim lifecycle workflows with adjuster workbench for day-to-day handling
  • +Strong assignment routing support using triage rules and workload balancing patterns
  • +Integration surfaces for claim events and data exchange with other enterprise systems
  • +Detailed claim activity tracking for audit trails across claim status and handling steps
Cons
  • –Significant implementation effort is needed to tailor workflows and authority controls
  • –Straight-through processing depends on configuration depth and rules completeness
  • –User experience can feel complex when many claim types and coverage paths are enabled
  • –Customization often requires platform specialists to avoid workflow sprawl

Best for: Fits when large carriers need configurable claim processing with strong governance and integration depth across systems.

#7

Sapiens Claims

enterprise

Claims management solution supporting personal and commercial lines with configurable workflows.

7.5/10
Overall
Features7.3/10
Ease of Use7.8/10
Value7.6/10
Standout feature

Enterprise workflow orchestration that keeps claim routing, tasking, and case progression tightly governed across the lifecycle.

Sapiens Claims is positioned for insurance carriers that want claim lifecycle processing with deep integration into enterprise insurance stacks. It emphasizes workflow orchestration around adjuster workbenches, triage logic, and case progression across first notice through resolution.

Pros
  • +Rules-driven routing and workflow orchestration for claim lifecycle management
  • +Adjuster workbench supports case context and day-to-day handling in one workspace
  • +Extensibility supports carrier-specific business logic without replacing core workflow
  • +Governance controls support role-based access and auditable claim activity
Cons
  • –Configuration depth increases change-management effort for new states or workflows
  • –Touchless straight-through processing depends on integration quality and exception design
  • –External system dependencies can slow issue resolution during complex integrations
  • –Admin tools feel workflow-heavy compared with simpler case management products

Best for: Fits when large carriers need rules-driven claim workflows with integration into core insurance systems.

#8

ClaimCenter by Origami Risk

enterprise

Claims and risk management platform for captives, TPAs, and risk pools.

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

Workflow-driven claims case management with extensible event handling for outbound claim status changes and external system coordination.

ClaimCenter by Origami Risk is a claims processing system built around insurer adjuster workflows and integration for policy, coverage, and claim operations. Core capabilities include configurable assignment and work routing, claims case management with task diaries, and automation hooks for status updates and outbound notifications.

Pros
  • +Configurable workflow and task routing aligned to adjuster day-to-day operations
  • +Strong extensibility for integrating claim events with external enterprise systems
  • +Case-oriented claim handling supports consistent lifecycle tracking and closure controls
  • +Audit-friendly claim file structure supports review and supervisory oversight workflows
Cons
  • –Workflow configuration requires disciplined governance to avoid inconsistent routing logic
  • –Complex deployments can need specialist implementation for deep integration scenarios
  • –Document and form-heavy workflows may demand significant mapping work to external sources
  • –Granular automation across many claim types can increase change-management overhead

Best for: Fits when carriers need workflow governance, adjuster workbench controls, and deep enterprise integration for multiple claim lines.

#9

FRISS

enterprise

Fraud detection and claims automation platform for P&C insurers.

6.9/10
Overall
Features6.6/10
Ease of Use7.0/10
Value7.1/10
Standout feature

Case referrals that combine analytical scoring with evidence packaging to support SIU action and documented decision trails.

FRISS processes insurance claims through a fraud and claims intelligence layer that feeds triage, allocation, and investigation workflows. It ingests claim and policy data to score suspicious activity and generate case referrals that adjusters and SIU teams can act on.

Pros
  • +Fraud scoring and referral outputs are designed for adjuster and SIU workflows
  • +Rules and analytics support repeatable triage decisions across claim intake
  • +Audit-ready evidence packaging supports investigation documentation needs
  • +Automation can route and prioritize cases without manual rework
Cons
  • –Effective scoring depends on data quality and feed coverage into FRISS
  • –Fraud-focused outputs require downstream configuration in case management

Best for: Fits when carriers and third-party administrators need standardized fraud triage and SIU referrals feeding claim workflows.

#10

Shift Technology

enterprise

AI-driven claims automation and fraud detection for insurers.

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

Workflow configuration that ties document intake outputs to claim routing and task creation across multiple claim stages.

Shift Technology supports insurance claims processing workflows that run from first notice of loss through adjuster handling and downstream payment execution. Its distinct focus is on automating claim operations with configurable rules, document intake, and integration hooks for exchange with external claim and payment systems.

Pros
  • +Configurable routing and work management that supports consistent claim lifecycle steps.
  • +Document intake and OCR-oriented processing reduces manual transcription across claim files.
  • +Integration-focused workflow design for connecting claim systems and downstream operations.
  • +Audit trail support helps maintain a claim file record across workflow transitions.
Cons
  • –Automation depth depends heavily on configuration work and workflow design quality.
  • –Coverage for complex settlement authority and litigation workflows can require additional tailoring.
  • –External system integration mapping can be a time sink during initial onboarding.
  • –Reporting granularity for reserve and analytics needs careful alignment with internal data sources.

Best for: Fits when carriers or TPAs need configurable claim workflows with strong audit traceability and external system integration.

Conclusion

After evaluating 10 insurance claims processing software, ClaimLogiq 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
ClaimLogiq

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 Insurance Claims Processing Software

What separates options in insurance claims processing software is not the presence of features—it’s how they move a claim from intake to decision with auditable automation. We focus on Claim lifecycle workflow because it shows whether actions, data, and decisions stay consistent across the whole file.

FNOL to decision workflow coverage

Why it matters

When FNOL intake to decision workflow coverage is broad, you spend less time re-keying claim details and less time stitching steps together later. Coverage gaps usually surface as manual handoffs that slow cycle time and increase errors.

How to check

Ask for a live walkthrough with a sample claim from first notice through decisioning. Note whether the workflow covers key handoffs like triage, assignment, evidence intake, and final disposition in one consistent process.

Triage rules automation depth

Why it matters

Triage rules automation depth matters because it decides what gets routed or escalated before a human touches the file. Strong rule handling can keep similar losses treated consistently and improve straight-through processing for low complexity claims.

How to check

Request a demo where they configure a triage rule, then run it on multiple sample files. Ask what inputs the rule uses, how exceptions are handled, and whether the app logs why routing or automation happened.

Assignment routing transparency

Why it matters

Assignment routing transparency matters because adjusters need to understand why a claim landed where it did. When routing is opaque, you’ll see reassignments and audit friction during reviews.

How to check

Have them show the claim assignment rules screen and how a claim’s destination updates as key fields change. Ask to view a claim’s routing history and the rule outcomes that drove the current assignment.

Reserve setting and adjustment support

Why it matters

Reserve setting and adjustment support matters because reserves are where processing mistakes become financial misstatements. Good systems help keep reserve changes traceable to events, reviews, and decisions.

How to check

In a demo, request a case where reserves change after new information is added. Check whether the tool records reserve change history, who changed it, and what triggered or documented the adjustment.

Recovery and subrogation tracking

Why it matters

Recovery and subrogation tracking matters because recoveries can’t be managed if subrogation steps are scattered across emails and spreadsheets. If tracking is weak, you lose visibility into demands, yields, and closure.

How to check

Ask for a workflow demo that includes a subrogation path and recovery updates over time. Confirm whether the system ties demands and payment events back to the same claim file with timestamps and status.

Claim file audit trail and exports

Why it matters

Claim file audit trail and exports matter because insurance claims processing requires defensible history during audits, disputes, and reopen activity. Missing audit trail or incomplete exports forces manual reconstruction.

How to check

Request to open a claim and review the full activity timeline from intake through closure, including notes, decisions, and document events. Then ask to export a claim file audit trail or equivalent report format and verify required fields are present.

Red flags

  • Workflow coverage stops at early steps and pushes later decisions into manual off-system work.
  • Automation depth changes outcomes without showing the inputs and reasons behind routing or escalations.
  • Reserve or recovery actions appear without a clear timeline, ownership, or linkage to claim events.

Fit by situation

  • If your team receives many FNOLs and needs consistent routing decisions, prioritize Triage rules automation depth.
  • If different handlers touch the same file and you need defensible history, prioritize Claim file audit trail and exports.
  • If recoveries and subrogation drive meaningful dollars, prioritize Recovery and subrogation tracking.

Frequently Asked Questions About Insurance Claims Processing Software

How do ClaimLogiq and Guidewire ClaimCenter implement rule-based triage from FNOL intake to adjuster work queues?
ClaimLogiq ties triage outcomes to stage tasks and routes them into adjuster work queues based on configurable rules. Guidewire ClaimCenter applies assignment and triage rules through its configurable workflow engine, with adjuster workbench screens that track claim activity across FNOL to closure.
Which tools support document-driven intake so images and attachments drive routing instead of rekeying packets?
Snapsheet routes and assigns based on uploaded photos, with adjuster workbench review built around image evidence tied to lifecycle documents. Claimable also links document intake into guided workflows, but its adjuster experience is centered on task progression and in-case activity rather than photo-first triage.
When do administrators choose authority limits and approval gates, and how do Sapiens Claims and Guidewire ClaimCenter differ here?
Guidewire ClaimCenter enforces settlement authority through supervisory and committee-style approvals tied to claim activity. Sapiens Claims focuses on enterprise workflow orchestration with governance shaped by role-based access and auditable configuration, which governs routing and progression rather than only settlement approvals.
How do Claimable and Shift Technology handle integrations for pushing claim status updates into external systems?
Claimable supports outbound claim status updates so external payment and reporting systems can stay synchronized with claim lifecycle events. Shift Technology uses integration hooks so document intake outputs map to claim routing and task creation, then aligns downstream payment execution with external claim and payment systems.
What data migration and claim history import capabilities matter when replacing a legacy claims system?
Duck Creek Claims supports enterprise workflow orchestration across its ecosystem, which reduces the friction of migrating claim events into a managed event model. Shift Technology emphasizes keeping claim history consistent across channels and stages, which supports controlled migration of lifecycle records into the workflow states used for routing and audit visibility.
Which products provide extensibility for carrier-specific business logic without custom workflow rewrites?
Sapiens Claims includes extensibility to support carrier-specific logic while keeping governed workflow orchestration across first notice through resolution. ClaimCenter by Origami Risk adds extensible event handling so carriers can coordinate external system feeds and outbound claim status changes tied to its case management and routing.
Where does fraud triage integrate into claims workflows, and how do FRISS and the others handle it differently?
FRISS adds a fraud and claims intelligence layer that generates referrals for SIU and investigation workflows and routes that work into claim and SIU processes. The core platforms like Guidewire ClaimCenter and Snapsheet focus on end-to-end claim administration and routing, so fraud scoring depends on dedicated intelligence feeds rather than being the primary claim engine.
How do ClaimFlow and Snapsheet enforce claim file completeness before moving work forward?
ClaimFlow uses workflow checkpoint gating so required documents and approvals must be present at each lifecycle step. Snapsheet drives completeness through inspection-centric intake where image evidence and document attachments are tied to routing and adjuster review tasks.
What tradeoff appears when a team standardizes on adjuster workbench configuration versus relying on custom code?
ClaimFlow emphasizes configuration of assignment rules and lifecycle states, which reduces the need for custom code changes but limits deep deviations from its workflow checkpoints. Guidewire ClaimCenter and Sapiens Claims support richer enterprise orchestration, yet deeper customization still requires governance around role-based configuration patterns and audit trails to prevent inconsistent lifecycle behavior.
How do multi-line claim handling and event routing differ across Duck Creek Claims and Guidewire ClaimCenter?
Duck Creek Claims connects deeply with the Duck Creek ecosystem and routes claim events through configurable workflow orchestration tied to the broader platform event model. Guidewire ClaimCenter supports multi-line processing with assignment and triage rules, reserve setting, diary management, and controlled settlement workflows that coordinate across policy and payment integrations via APIs.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

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.