Vendor-funded research
Top 10 Best Credit Union Management Software of 2026

GITNUXSOFTWARE ADVICE

Finance Financial Services

Top 10 Best Credit Union Management Software of 2026

Ranked roundup of credit union management software tools for teams comparing DNA by Fiserv, Symitar by Jack Henry, Phoenix by Finastra.

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

Before any source is gathered, an editor locks the question, what qualifies, and how the piece will be judged.

02Source Research

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

Read our full methodology →

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

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

This ranked list targets credit union operations leads, technologists, and vendor evaluators who must replace or modernize core processing, member servicing, and lending workflows with clear integration points. The ranking prioritizes automation surfaces like APIs and data schemas, governance controls such as RBAC and audit logs, and measured deployment realities, with DNA by Fiserv used only as a reference example for core processing scope. Credit union management software matters because core data models, provisioning patterns, and service orchestration determine cycle time, risk controls, and delivery of digital member experiences.

DNA by Fiserv is the strongest fit if you need governed, department-wide core processing and lending automation for a credit union, whereas FLEX works better when you want coordinated onboarding, servicing, and transactions with integration control in one environment.

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

DNA by Fiserv

DNA’s workflow-driven task routing connects operational steps to account and lending outcomes for controlled member servicing.

Best for: Fits when a credit union needs unified core processing, lending workflows, and governed automation across departments.

2

Symitar by Jack Henry

Editor pick

Symitar’s loan and account servicing workflow support covers end-to-end operational event handling inside the core.

Best for: Fits when a credit union standardizes servicing and account operations with Jack Henry-adjacent integrations.

3

Phoenix by Finastra

Editor pick

Case-driven servicing workflows that coordinate approvals and downstream actions from member and account events.

Best for: Fits when a credit union needs event-based workflow automation with strong governance for shared servicing processes.

Comparison Table

1
DNA by FiservBest overall
enterprise
9.5/10
Overall
2
9.2/10
Overall
3
8.9/10
Overall
4
vertical specialist
8.6/10
Overall
5
vertical specialist
8.3/10
Overall
6
cloud-native
7.9/10
Overall
7
7.6/10
Overall
8
enterprise
7.3/10
Overall
9
7.0/10
Overall
10
6.7/10
Overall
#1

DNA by Fiserv

enterprise

DNA is a core processing platform designed for credit unions and financial institutions.

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

DNA’s workflow-driven task routing connects operational steps to account and lending outcomes for controlled member servicing.

DNA by Fiserv combines core banking functions with lending and member servicing in an integrated workflow model. Core deposit and share processing connects to loan origination and servicing so changes to member or account records can follow through operational steps. Automation is applied to case handling and back-office tasks, which reduces manual handoffs between operations, lending, and servicing teams.

A key tradeoff is that deeper customization and process automation tend to require governance from administrators to keep workflows consistent across departments. DNA fits best when a credit union has established procedures that need systemized routing and when external channel integration must follow repeatable back-office handling patterns.

The governance and audit trail expectations typical for regulated financial operations are addressed through controlled configuration and operational histories tied to transactions and workflow steps. Where multiple teams manage overlapping touchpoints, DNA’s structured operational flows help prevent task drift and inconsistent documentation.

Pros
  • +Integrated core deposit and lending processing reduces cross-system reconciliation
  • +Workflow routing supports consistent task handling across operations and lending
  • +Extensibility supports external channel and document-connected business flows
  • +Operational histories help trace transaction and workflow steps during reviews
Cons
  • –Complex workflow changes require disciplined administration and testing cycles
  • –Advanced automation depends on configuration maturity across departments
  • –Some specialized processes may need additional integrations or add-ons
  • –User training is required for administrators managing multi-step workflows
Use scenarios
  • Back-office operations teams

    Route member servicing tasks end-to-end

    Fewer manual handoffs

  • Lending operations teams

    Standardize origination and servicing steps

    Reduced process variation

Show 2 more scenarios
  • Digital channel integration teams

    Connect online requests to back-office processing

    Faster request turnaround

    Integration points support syncing member events and documents tied to core and lending actions.

  • Compliance and risk teams

    Review operational histories for actions

    Improved audit readiness

    Transaction-linked operational histories support tracing workflow steps during regulatory reviews.

Best for: Fits when a credit union needs unified core processing, lending workflows, and governed automation across departments.

#2

Symitar by Jack Henry

enterprise

Symitar provides core processing and operational software for credit unions.

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

Symitar’s loan and account servicing workflow support covers end-to-end operational event handling inside the core.

Symitar covers core banking processes used in credit union operations, including deposit account administration, share account administration, and loan servicing. Member workflows connect to account setup activities such as member onboarding and operational tasks that follow account creation. Configuration and automation features help reduce manual handoffs across servicing events and payment-related operations.

A tradeoff appears when credit unions require deep native support for non-Jack Henry channels, because third-party integrations can add project scope. Symitar fits best when a credit union wants consistent operations around servicing and accounts, and already plans to integrate with Jack Henry-adjacent systems for cards, payments, or related processing.

Pros
  • +Strong loan servicing workflow coverage across operational event lifecycles
  • +Deep operational fit for deposit and share account administration
  • +Configuration options support repeatable back-office automation
  • +Integration alignment with Jack Henry systems reduces bridging effort
Cons
  • –Non-Jack Henry channel requirements can increase integration delivery time
  • –Governance-heavy operations demand careful role setup
  • –User experience can feel process-driven rather than task-driven
  • –Advanced automation changes may require formal change control discipline
Use scenarios
  • Operations managers

    Standardize servicing event workflows

    Fewer manual handoffs

  • Digital banking teams

    Connect onboarding to core setup

    Faster account readiness

Show 2 more scenarios
  • Compliance leads

    Govern operational control processes

    Clearer operational accountability

    Compliance teams apply audit trail practices and role-based governance to operational changes and approvals.

  • IT integration teams

    Integrate with Jack Henry processing

    Lower integration overhead

    IT teams align core operations with adjacent Jack Henry processing capabilities to reduce connector work.

Best for: Fits when a credit union standardizes servicing and account operations with Jack Henry-adjacent integrations.

#3

Phoenix by Finastra

enterprise

Phoenix is a core banking platform used by credit unions and other financial institutions.

8.9/10
Overall
Features8.5/10
Ease of Use9.2/10
Value9.1/10
Standout feature

Case-driven servicing workflows that coordinate approvals and downstream actions from member and account events.

Phoenix by Finastra targets credit union core banking workflows and then extends those workflows into onboarding, servicing, and digital access patterns. The automation surface is driven by configurable process steps tied to operational events, which helps teams standardize handoffs from origination to servicing. The integration approach typically relies on documented interfaces for connecting online and internal systems to core data and transaction flows.

A key tradeoff is that deep workflow configuration can require a structured governance process for changes, especially when multiple servicing lines share process logic. Phoenix fits best when a credit union needs tighter operational control across loan servicing and deposit administration while keeping integrations aligned to member and channel events.

Pros
  • +Event-driven workflow automation across onboarding, servicing, and channel touchpoints
  • +RBAC controls tied to operational areas for servicing and account administration
  • +Audit trail coverage for operational activities and configuration changes
  • +Integration support for payments and account transaction flows
Cons
  • –Workflow configuration requires disciplined governance and change control
  • –Many advanced workflows depend on enabling related modules and integrations
  • –UI complexity rises with deep configuration and multi-product setups
Use scenarios
  • Loan operations teams

    Automate servicing actions after origination

    Fewer manual transfers between teams

  • Digital operations managers

    Coordinate onboarding steps with core processes

    More consistent onboarding completion

Show 2 more scenarios
  • Payments integration teams

    Route ACH and payment-related events

    Lower integration effort per channel

    Integration points connect transaction events to operational processing and monitoring.

  • Compliance and risk teams

    Track operational activity across processes

    Faster remediation during reviews

    Audit trails support investigations into who performed which operational actions.

Best for: Fits when a credit union needs event-based workflow automation with strong governance for shared servicing processes.

#4

FLEX

vertical specialist

Credit union core banking software with enterprise feature set.

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

Configurable workflow automation that coordinates loan and account tasks across processing stages within one operational control layer.

FLEX is credit union management software aimed at unifying core operations with member account and workflow capabilities. The system is positioned around loan, deposit, and administration workflows, with extensibility for integrations that need controlled automation.

Pros
  • +Automation for account and loan workflows reduces manual handoffs
  • +Integration-first design supports core and member-facing system connectivity
  • +Role-based permissions help separate operator duties by function
  • +Operational traceability supports audit review of workflow actions
Cons
  • –More governance and configuration work is required for consistent controls
  • –Depth of reporting for niche compliance cases can require configuration
  • –Some setup-heavy integrations may need dedicated integration engineering
  • –Workflow customization can add complexity when many teams operate in parallel

Best for: Fits when a credit union needs coordinated onboarding, servicing, and transaction workflows with controlled integrations.

#5

Sharetec

vertical specialist

Sharetec provides core processing software and related operational tools for credit unions.

8.3/10
Overall
Features8.5/10
Ease of Use8.2/10
Value8.0/10
Standout feature

Servicing workflow automation tied to configurable member account and loan status transitions for consistent back office execution.

Sharetec provides credit union management software focused on core operations that cover member accounts, share account administration, and loan origination and loan servicing workflows. The system supports workflow automation for common back office tasks and produces transaction histories and operational audit trails used for reviews and reporting.

Pros
  • +End-to-end handling of member share and loan lifecycle workflows
  • +Workflow automation reduces manual routing for servicing tasks
  • +Operational audit trail supports internal and regulatory review needs
  • +Role-based administration helps separate teller, servicing, and reporting work
Cons
  • –Core workflow coverage can require configuration to match local processes
  • –Integration depth varies by connected system and interface availability
  • –Report customization can take more effort than prebuilt extracts
  • –Higher-volume operations depend on careful operational tuning

Best for: Fits when a credit union needs integrated share and loan servicing workflows with controlled staff roles.

#6

Nymbus SmartCore

cloud-native

SmartCore is a cloud-based core banking platform offered by Nymbus.

7.9/10
Overall
Features8.1/10
Ease of Use7.9/10
Value7.7/10
Standout feature

SmartCore workflow configuration ties loan and share processing steps to enforced audit trail events.

Nymbus SmartCore targets credit union core operations with a configuration-led approach that keeps workflows close to day-to-day lending and deposit administration. The software covers share and deposit account administration, member onboarding, and loan origination and servicing workflows.

Pros
  • +Workflow configuration keeps lending and account processing aligned to operations
  • +Audit trail records changes across member, account, and loan workflow steps
  • +API-first integration approach supports online banking and external system connectivity
  • +Unified handling of onboarding, origination, and servicing reduces handoffs
Cons
  • –Depth varies by workflow and may require add-on modules for full coverage
  • –Integration mapping can be time-consuming for complex payment and document flows
  • –Governance setup requires careful RBAC scoping to avoid over-permissioning
  • –Advanced automation depends on available workflow hooks and connector breadth

Best for: Fits when credit unions need configurable lending and deposit workflows with strong auditability and integration control.

#7

FIS AffinityEdge

enterprise

Open-architecture core banking platform for credit unions with integrated card management, payments, CRM, and digital banking capabilities.

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

AffinityEdge workflow automation for lending and servicing cases with rule-driven exception handling and configurable state transitions.

FIS AffinityEdge targets credit union operations by combining member onboarding, loan origination, loan servicing, and deposit and share administration into one operational workflow environment.

Pros
  • +Strong loan servicing workflow coverage for exceptions and ongoing maintenance
  • +Digital onboarding workflows support straight-through handoffs from applications
  • +Integration depth aligns with core banking and payment processing ecosystems
  • +Configurable workflow steps reduce hard-coded process variations
Cons
  • –Workflow configuration can require analyst time for complex branching rules
  • –Non-core integrations often depend on FIS middleware or certified adapters
  • –RBAC and audit visibility depend on how integrations are configured
  • –Some channel capabilities rely on coordinated enablement across modules

Best for: Fits when a credit union needs end-to-end lending and servicing workflows with deep core integration.

#8

Q2

enterprise

Digital banking platform serving credit unions and banks with online banking, mobile banking, account opening, and member engagement tools.

7.3/10
Overall
Features7.6/10
Ease of Use7.0/10
Value7.2/10
Standout feature

Event-driven automation that coordinates member engagement actions with back-office account activity.

Q2 is a credit union management software option built around member relationship management workflows and digital channels, with an emphasis on coordinating service journeys across onboarding, servicing, and payments. Its core strength is integration-first behavior that connects member data, account events, and engagement actions through an API surface designed for operational automation.

Pros
  • +Strong automation of member journeys across onboarding and service workflows
  • +Integration and API surface supports event-driven actions tied to member activity
  • +Configuration supports governance needs for day-to-day operational workflows
  • +Digital experience coverage aligns with member authentication and engagement flows
Cons
  • –Workflow configuration can require sustained admin attention for consistent outcomes
  • –Core credit union servicing depth may depend on connected systems for full coverage
  • –Some operational processes may add complexity when integrating multiple back-office tools
  • –RBAC granularity can be harder to tune for highly segmented internal roles

Best for: Fits when a mid-size credit union needs automated, API-driven member journeys tied to digital servicing workflows.

#9

ESP FORZA3

SMB

Credit union core processing platform with real-time ATM and debit processing, lending, accounting, reporting, and digital banking in one system.

7.0/10
Overall
Features7.3/10
Ease of Use6.7/10
Value6.8/10
Standout feature

Rule-driven work queues that route operational tasks by configuration for loan and account servicing cycles.

ESP FORZA3 performs credit union operations management across member, deposit, and loan lifecycles with workflow-driven processing. It is positioned around configurable back-office modules for onboarding, account servicing, and transaction posting, with controls intended for audit trail continuity.

Pros
  • +Workflow routing supports repeatable back-office processing
  • +Configurable module coverage for onboarding through loan servicing
  • +Operational audit trail focus supports internal review workflows
  • +Interface-oriented integration for core and payment adjacent systems
Cons
  • –Advanced automation depends on careful configuration and governance discipline
  • –Digital onboarding depth can be limited without external channel integrations
  • –Reporting breadth may require add-on exports for specialized regulatory views
  • –Role management may be less granular than multi-team operating models need

Best for: Fits when a credit union needs configurable back-office workflows across member, deposit, and loan operations.

#10

Temenos for Credit Unions

enterprise

Cloud-native core banking platform with modules for member onboarding, loan origination, collections, and recovery tailored to credit unions and community banks.

6.7/10
Overall
Features6.7/10
Ease of Use6.6/10
Value6.7/10
Standout feature

Unified Temenos workflow and audit trail design that ties operational steps to compliance-ready history across member servicing.

Temenos for Credit Unions targets credit unions that need an integrated core banking and member lifecycle stack across deposits, loans, and member relationship workflows. It is differentiated by Temenos’ enterprise-grade integration approach for channel experiences like online and mobile banking and by the way it supports operational controls for regulatory reporting and audit traceability. The solution also covers the day-to-day work of member onboarding, loan origination and servicing, and account administration that spans share and deposit activities.

Pros
  • +End-to-end coverage for deposits, loans, and member lifecycle workflows
  • +Enterprise integration orientation supports core banking and digital channel connectivity
  • +Strong audit trail for operational and compliance verification workflows
  • +Configuration-first approach supports governance across multiple operational processes
Cons
  • –Implementation projects demand deep integration and conversion planning
  • –Customization requires disciplined change control to avoid workflow drift
  • –Feature breadth can increase training requirements for back-office teams
  • –API and automation extensibility depends heavily on chosen architecture

Best for: Fits when a credit union needs enterprise integration across core, digital channels, and loan and deposit operations.

Conclusion

After evaluating 10 credit union management software, DNA by Fiserv 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
DNA by Fiserv

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 Credit Union Management Software

We separate credit union management software options by how tightly they connect day-to-day member and account work to the systems credit unions already run, then how reliably they can automate updates. In practice, integration depth, automation and API surface, and admin and governance controls show up as concrete demo behaviors you can verify.

Core and lending data integration depth

Why it matters

Core and lending data integration depth matters because member changes and loan/share updates must stay consistent across modules. If data updates drift, you end up re-keying information and reconciling differences.

How to check

Ask the vendor to show how a single member profile update propagates across savings and loans, including what happens to balances and statuses. Request a sample of an import or sync cycle and confirm whether it updates in near-real time or only on a scheduled batch.

Automation rules and documented API surface

Why it matters

Automation rules and documented API surface matter because staff workflows and file transfers often need predictable triggers, not manual steps. Strong automation reduces exceptions and keeps operations auditable.

How to check

In the demo, ask for an example workflow that triggers on an event like a new loan account or a share balance change, then show the configuration screen. Request the API documentation scope (endpoints or resources) for member and account objects and confirm whether the sandbox mirrors production behavior.

RBAC roles and audit log visibility

Why it matters

RBAC roles and audit log visibility matter because credit union staff need controlled access, and managers need traceability when actions affect accounts. Without clear role boundaries and audit logs, troubleshooting and governance become time-consuming.

How to check

Ask to see role configuration (who can view vs change member, loan, and share records) and confirm how access is enforced. Then run a demo action, such as editing an account status, and show the resulting audit log entry with timestamps and actor identity.

Configurable workflows and safe data migrations

Why it matters

Configurable workflows and safe data migrations matter because each credit union runs slightly different servicing and onboarding steps. If migrations are fragile, routine updates can create operational risk.

How to check

Request a walkthrough of how they configure a policy-driven workflow, such as how account flags route to a queue. Ask what the migration approach is for mapping fields from a prior system, and request a sample transformation report for a test conversion.

Operational reporting on account events

Why it matters

Operational reporting on account events matters because supervisors need to monitor exceptions, aging work, and throughput without building custom extracts each time. Good reporting also helps validate that automations are behaving as configured.

How to check

Ask for standard reports tied to account events (new accounts, status changes, returned items, and exceptions) and show how filters apply to a date range and member segment. If the product supports scheduled exports, request an example and confirm what fields are included.

Red flags

  • Account changes do not propagate consistently across modules without manual follow-up.
  • Audit logs show actions but omit who changed what and when.
  • Core objects require repeated custom extracts because reports and automation are incomplete.

Fit by situation

  • If you rely on frequent member and lending updates across multiple departments, prioritize core and lending data integration depth.
  • If your team wants event-driven operations and system-to-system updates, prioritize automation rules and documented API surface.
  • If you need strict access separation across staff roles and clear traceability, prioritize RBAC roles and audit log visibility.

Frequently Asked Questions About Credit Union Management Software

How do workflow task routing and work queues differ across DNA by Fiserv, FLEX, and ESP FORZA3?
DNA by Fiserv routes operational steps using workflow-driven task routing that links account and lending outcomes. FLEX uses one operational control layer to coordinate onboarding, servicing, and transaction workflows through configurable automation. ESP FORZA3 relies on rule-driven work queues routed by configuration, which changes task assignment without code changes.
Which tool is most suitable for case-driven servicing that coordinates approvals across member events?
Phoenix by Finastra is built around case-driven servicing workflows that coordinate approvals and downstream actions from member and account events. Temenos for Credit Unions ties operational steps to compliance-ready history across member servicing, but it is not centered on case-driven approval coordination. DNA by Fiserv uses workflow automation connected to core processing, which supports governed task handling without Phoenix-style case workflows.
When an institution needs governed governance controls like RBAC and audit trails, how do Phoenix, Nymbus SmartCore, and Temenos compare?
Phoenix by Finastra provides role-based access controls and audit trails designed to support governance across business processes. Nymbus SmartCore enforces governance using role-based access controls and an audit trail that records key changes across banking processes. Temenos for Credit Unions provides operational controls for regulatory reporting and audit traceability across deposits, loans, and member relationship workflows.
What data migration steps usually differ between core-first suites like Symitar by Jack Henry and workflow suites like Q2?
Symitar by Jack Henry is core banking adjacent, so migration commonly centers on mapping onboarding and servicing processes to an existing Jack Henry environment while standardizing operational controls. Q2 is integration-first with an API surface designed for operational automation, so migration typically focuses on connecting member data and account events to digital service journeys. Phoenix by Finastra usually requires migrating event models and case workflows so member-facing and back-office actions remain coordinated.
How do integrations and APIs show up in Nymbus SmartCore, Q2, and DNA by Fiserv during online and mobile channel delivery?
Nymbus SmartCore supports integrations for online delivery and payment-related flows using published APIs and integration tooling. Q2 emphasizes an API surface that connects member data, account events, and engagement actions for automated digital journeys. DNA by Fiserv provides extensibility points so external channels and payment or document flows connect to day-to-day operations.
Which platform best supports end-to-end operational handling for loan and account servicing events inside the core workflow?
Symitar by Jack Henry supports loan and account servicing workflow coverage that handles end-to-end operational event handling inside the core. FLEX coordinates loan and account tasks across processing stages within one operational control layer, which supports end-to-end workflow coverage but not through Symitar’s specific servicing model. Sharetec focuses on share and loan servicing workflows with configurable member account and loan status transitions tied to back-office execution.
Where does Sharetec tend to fall short if a credit union needs broad extensibility beyond documented interfaces?
Sharetec external connectivity depends on its integration options and documented data interfaces, which can constrain extensibility to what is exposed through those interfaces. It still supports role-based staff controls and workflow automation for back-office tasks, but it is not positioned as an extensibility platform with deep integration hooks like DNA by Fiserv. Nymbus SmartCore and Q2 present stronger integration surfaces for online and engagement automation.
What breaks if RBAC provisioning and audit trail configuration are not aligned with operational roles in Phoenix by Finastra?
If role-based access controls and audit trail configuration are misaligned in Phoenix by Finastra, approvals and downstream actions can be blocked or logged inconsistently across business processes. Case-driven servicing depends on coordinated operational steps, so missing permissions can interrupt task completion and change audit continuity. Workflow governance across member and account events relies on consistent access and event recording.
Which tool is more appropriate for automated member onboarding tied to digital channels and back-office event processing?
Q2 is designed for API-driven member journeys that coordinate online banking and mobile banking actions with back-office account activity. FIS AffinityEdge includes onboarding workflows and digital account openings plus channel support such as online and mobile banking. Nymbus SmartCore supports member onboarding and configurable lending and deposit workflows with stronger auditability and integration control around published APIs.
How should admin teams compare configuration effort for loan and account servicing between FIS AffinityEdge and FLEX?
FIS AffinityEdge delivers workflow automation for lending and servicing cases with rule-driven exception handling and configurable state transitions, which concentrates configuration in lending and servicing workflows. FLEX coordinates loan and account tasks across processing stages using configurable workflow automation and an integration surface aimed at controlled automation. A tradeoff appears in governance workload, because each system’s configuration model determines how exceptions and processing stages are expressed for staff operations.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Vendor-funded 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.