GITNUXSOFTWARE ADVICE
Video Games And ConsolesTop 9 Best Poker Analysis Software of 2026
Ranked roundup of Poker Analysis Software for tracking and studying hands. Includes PokerTracker 4, Holdem Manager 3, and PokerSnowie.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
PokerTracker 4
HUD stat profiles with customizable layouts for context-specific table views.
Built for fits when solo analysts need fast local stats with repeatable HUD and report configuration..
Holdem Manager 3
Editor pickConfigurable HUD statistics derived from the same underlying hand-history database schema.
Built for fits when serious players need schema-driven reports and HUD-ready stats across many sessions..
PokerSnowie
Editor pickDecision comparison during hand review based on ingested hand-history inputs.
Built for fits when solo analysts or small study groups need repeatable decision review without team governance..
Related reading
Comparison Table
The comparison table maps poker analysis tools by integration depth, data model design, and how automation and API surface support hand import, reporting, and study workflows. It also contrasts configuration options, schema behavior, and admin and governance controls such as RBAC and audit log coverage to show where each platform fits into managed environments. A second layer highlights extensibility paths and provisioning patterns so readers can predict throughput and operational overhead for shared setups.
PokerTracker 4
hand history databaseWindows poker hand history database with stats, HUD integration, database schema management, and configurable import plus ongoing automation via plugins.
HUD stat profiles with customizable layouts for context-specific table views.
PokerTracker 4 functions as an analysis workspace that stores hands in a local schema and derives stats for opponents, sessions, and strategies. The core workflow covers hand import, database curation, and report views that can be filtered by player, position, and game conditions. HUD layout and stat selection can be configured per profile, which supports repeatable table view setups across different formats and stakes. This makes governance and change management mostly configuration driven rather than code or API driven.
A key tradeoff is limited extensibility beyond the built-in import sources, HUD stat set, and report types. Automation and integrations largely stop at configuration and workflow repeatability, not external system synchronization. PokerTracker 4 fits situations where analysis throughput matters and a consistent local data model is the priority over pushing events into an external analytics stack.
- +Local hand-history database enables consistent cross-session stat calculations
- +Configurable HUD profiles support repeatable table views per game type
- +Report filters provide targeted analysis by player, position, and context
- +Import and data curation workflows reduce manual analysis overhead
- –Automation surface is configuration driven, not a public automation API
- –Extensibility is limited compared with systems that support webhooks or custom pipelines
- –External data synchronization requires export and manual routing
Individual grinders
Review sessions by opponent and position
Faster leak identification
Coaching and mentorship
Generate consistent session review packs
Standardized feedback workflow
Show 2 more scenarios
Poker operations analyst
Audit database hygiene for imports
Lower analysis variance
Supports data curation steps that keep the hand-history model consistent for analysis.
Multi-format players
Switch HUD profiles per game type
Less configuration churn
Applies separate HUD configurations to match different stat needs across formats.
Best for: Fits when solo analysts need fast local stats with repeatable HUD and report configuration.
Holdem Manager 3
hand history databaseHand history and session database for No-Limit Hold'em with configurable stat views, HUD workflows, and extensible analysis features via add-ons.
Configurable HUD statistics derived from the same underlying hand-history database schema.
Holdem Manager 3 fits analysts and serious players who need repeatable stats generation across many sessions and tables. The hand-history import pipeline builds a central database schema that drives reports, leak-style filtering, and player comparisons. Configuration supports selection of stat categories and thresholds that affect both analysis views and HUD outputs.
A tradeoff appears in automation and integration surface compared with tools that expose broader API endpoints. Holdem Manager 3 can be scripted indirectly through configuration, database exports, and how hand capture and HUD rules are wired. It fits when steady throughput of imported hand histories and consistent schema-driven reporting matter more than custom external workflows.
- +Database-backed hand analysis supports repeatable session and player reporting
- +HUD-compatible statistic configuration connects analysis output to live table reads
- +Flexible filters and tags improve leak analysis across large hand volumes
- +Database exports support offline review workflows and external reporting
- –External automation relies more on exports and configuration than a broad API surface
- –Custom data modeling for nonstandard schemas requires careful setup work
- –Large imports demand disciplined maintenance of database health and indexing
Tournament analysts
Analyze multi-day tournament hand volumes
Faster identify recurring leaks
Cash game grinders
Tune HUD reads from imported sessions
More consistent in-session decisions
Show 2 more scenarios
Coaching teams
Review students with tagging and filters
Clearer feedback with evidence
Tag hands and sessions, then produce repeatable report sets for coach feedback.
Data-minded solo players
Export hands for custom offline analysis
Custom reports beyond HUD limits
Use database exports to move data into external tooling for deeper transformations.
Best for: Fits when serious players need schema-driven reports and HUD-ready stats across many sessions.
PokerSnowie
solver-assisted analysisTraining and analysis software that uses scenario input and outputs strategy guidance with a computational engine behind a structured analysis workflow.
Decision comparison during hand review based on ingested hand-history inputs.
PokerSnowie focuses on ingesting hand histories and running analysis that maps decisions to tactical outcomes. Review sessions support branching comparisons across alternatives, which makes it suitable for disciplined study based on concrete decision points. Integration depth is primarily user-facing through manual input workflows rather than broad enterprise data connections, so extensibility depends on the available hand-history and analysis interfaces.
A tradeoff is limited admin and governance control for multi-user teams, since RBAC, provisioning, and audit logging are not a primary surfaced feature set. PokerSnowie fits best when an individual or small study group needs repeatable decision review with minimal setup overhead and consistent analysis runs.
- +Hand-history based analysis with decision-focused study loops
- +Replay-style review that compares candidate lines
- +Structured outputs that support repeatable practice patterns
- –Limited evidence of enterprise RBAC and provisioning controls
- –Narrow integration surface compared with tools offering broad APIs
- –Automation options appear focused on review workflows, not orchestration
Solo poker analysts
Analyze recurring leaks across hand histories
Cleaner baselines for study
Coaches and small teams
Compare alternative lines from client hands
More specific feedback cycles
Show 1 more scenario
Grinders in training
Practice post-session analysis loops
Faster concept repetition
Turn session hands into a consistent review flow to reinforce study routines.
Best for: Fits when solo analysts or small study groups need repeatable decision review without team governance.
Flopzilla
range analysisPreflop and flop range analysis tool that models equity outcomes for fixed or filtered ranges and produces shareable analysis outputs.
Range versus board equity computation with interactive scenario selection.
Flopzilla is a poker analysis tool focused on range work, equity breakdowns, and scenario filtering for hand history studies. It supports interactive board and hand selection to compute outcomes against configurable opponent ranges.
Analysis results can be exported for review workflows and reproducible decision documentation. Compared with broader ecosystems, Flopzilla centers on repeatable range evaluation with clear configuration surfaces rather than heavy automation.
- +Interactive range versus board evaluation for fast what-if testing
- +Scenario filtering by hand and board gives repeatable comparison runs
- +Exportable results support external documentation and review workflows
- +Constrained configuration reduces analysis drift across sessions
- –Limited automation and API surface for programmatic analysis pipelines
- –No documented provisioning or schema for integration at scale
- –Automation depth is constrained compared with workflow-first analysis systems
- –Audit log and RBAC controls are not emphasized for governance
Best for: Fits when solo analysts or small groups need deterministic range analysis without external automation.
GTO Wizard
solver analysisSolver-backed hand analysis with scenario configuration and output views that support systematic study workflows.
Hand-history driven scenario setup that maps solver outputs to specific decision points.
GTO Wizard generates and serves GTO hand analysis training outputs for specific game formats, including precomputed strategy and play lines. The system organizes study content around hand history inputs and solver results so users can query, review, and practice decision points.
Integration depth is geared toward exporting and importing analysis artifacts into external workflows, with extensibility centered on automation rather than UI-only actions. Admin and governance controls focus on managing access to stored workspaces and configurations used for study and analysis runs.
- +Solver-backed ranges and lines tied to hand states for consistent review
- +Study workflow supports reusable scenarios and decision-point queries
- +Export and import of analysis artifacts fits external tooling pipelines
- +Automation-friendly configuration reduces repetitive manual setup
- –Automation surface is limited to file-based exchanges rather than programmatic services
- –Less granular RBAC compared with enterprise collaboration suites
- –Workspace organization can require manual upkeep for larger libraries
- –Audit logging details for administrative actions are not exposed in a configurable way
Best for: Fits when small teams need repeatable solver review workflows with limited governance overhead.
PioSOLVER
solver analysisGame-theory solver for extensive-form games that supports analysis trees and strategy output generation for postflop spots.
Configurable analysis run automation with parameterized inputs and API-accessible outputs.
PioSOLVER targets poker analysis workflows that need repeatable computations and controlled configuration across users. It centers on a structured data model for hands, scenarios, and solver outputs, enabling consistent analysis runs.
Automation support is geared toward rerunning analyses with parameter changes while preserving traceability of inputs. Integration depth is strongest when analysis outputs must feed downstream reporting and internal tools through an API and defined schemas.
- +Structured data model for hands, scenarios, and solver outputs
- +API surface supports automation of analysis runs and parameterization
- +Config-driven workflows reduce manual setup between iterations
- +Extensibility through schema alignment between inputs and outputs
- +Automation supports repeatable throughput for batch analysis
- –RBAC and permission granularity may require careful upfront provisioning
- –Admin governance controls can feel heavy for small single-user setups
- –Audit log visibility may be limited without disciplined workflow conventions
- –Schema changes can require coordinated updates across pipelines
Best for: Fits when teams need controlled, automated poker analysis runs with API-driven integration.
GTO+
solver analysisSolver workflow application that computes strategies for configured game trees and provides analysis layers for decision points.
Saved analysis sessions with structured range and context schema for consistent reruns and comparisons.
GTO+ targets poker analysis workflows that need repeatable computation and structured outputs, not just study views. It focuses on hand and range analysis with GTO-oriented tooling and scenario comparison tied to an explicit analysis data model.
Integration depth centers on how analysis runs can be saved, organized, and reused across sessions. Automation and extensibility depend on a documented API surface for provisioning, running analysis tasks, and syncing data into external systems.
- +Analysis runs can be saved and organized for repeatable scenario comparison
- +Structured data model supports consistent tagging of hands, ranges, and contexts
- +API surface enables automation for analysis job orchestration and data sync
- +Extensibility options support integration into existing tooling and pipelines
- +Configuration supports environment-specific setup for repeatable experiments
- –Automation depth depends on available endpoints for full workflow coverage
- –Governance controls like RBAC and audit logs are limited by feature exposure
- –Schema flexibility may constrain custom data mapping for edge cases
- –Throughput for batch analysis can require careful job scheduling
Best for: Fits when teams need automated, repeatable GTO analysis runs integrated into internal tools.
CardRunners EV
EV calculatorBrowser-based EV and range analysis tools that run equity and scenario calculations from provided hand or range inputs.
EV calculation with range-based scenario evaluation for hands and decision review.
CardRunners EV focuses on poker-focused analysis workflows built around hand and range evaluation inputs rather than generic database reporting. The core loop centers on EV calculations, range manipulation, and scenario comparisons that support study and decision review.
Integration depth is limited to CardRunners ecosystem outputs and user-driven export or sharing workflows rather than a documented external API and automation pipeline. Automation and configuration are centered on analysis session setup and repeatable inputs instead of provisioning, RBAC, or audit-log governed operations.
- +EV and range workflow matches common study and analysis loops
- +Scenario comparisons support decision refinement across multiple inputs
- +Hand and range inputs keep the data model poker-native
- +Repeatable session configuration reduces manual setup effort
- –Limited evidence of a documented external API for programmatic automation
- –RBAC and audit log controls are not exposed through a governance surface
- –Automation depth is constrained to in-app workflows versus extensible integrations
- –Data model schema control is not presented as configurable or export-first
Best for: Fits when poker study depends on EV and range comparisons more than system integration.
DriveHUD
HUD overlayHUD and analysis tool that connects to supported tracking backends and overlays stats for table-time decision support.
Hand-history to analysis schema mapping for decision breakdowns by spot and range.
DriveHUD performs poker-specific analysis by ingesting hand history, mapping it into an analysis schema, and producing breakdowns for decisions and outcomes. Integration breadth centers on how reports and filters connect to a repeatable workflow for ranges, sizing, and positional contexts.
Automation and extensibility depend on the available API surface for programmatic hand import, data queries, and scheduled recomputation of derived stats. Admin and governance controls focus on access separation through user roles and configuration of workspaces and data scopes.
- +Poker hand history parsing maps into analysis-friendly data structures
- +Report filters support consistent breakdowns by position, range, and spot
- +API-oriented integration enables programmatic imports and analysis queries
- +Workspace scoping limits analysis visibility across teams
- –Automation depth is limited if API endpoints lack bulk recompute controls
- –Schema flexibility is constrained when custom metrics are not first-class
- –Auditability depends on available admin logs for data and config changes
- –Throughput for large hand volumes may require batching support
Best for: Fits when mid-volume poker teams need repeatable analysis with controlled access and API automation.
How to Choose the Right Poker Analysis Software
This buyer's guide covers PokerTracker 4, Holdem Manager 3, PokerSnowie, Flopzilla, GTO Wizard, PioSOLVER, GTO+, CardRunners EV, and DriveHUD. It focuses on integration depth, data model fit, automation and API surface, and admin and governance controls.
The guide explains how each tool’s ingestion pipeline, schema design, and automation options affect repeatability across sessions. It also maps common failure points like export-driven workflows and limited governance to concrete alternatives among the nine tools.
Poker tools that turn hand histories and solver outputs into queryable decisions
Poker analysis software ingests hand histories, EV inputs, range assumptions, or solver artifacts and then produces structured outputs like HUD-ready stats, filtered reports, decision comparisons, or equity computations.
These tools solve the operational problem of turning raw hands into repeatable decision evidence. PokerTracker 4 turns imported hand histories into a local database that drives HUD stat profiles and configurable report filters, while Flopzilla turns selected hands and boards into deterministic range versus board equity outputs.
Evaluation criteria for integration, data schema control, automation, and governance
Integration depth determines whether hand-history ingestion and derived metrics stay inside one system or require export and manual routing. PokerTracker 4 and Holdem Manager 3 keep analysis consistent through a structured local hand-history database model that supports repeatable HUD and reporting.
Automation and API surface determine whether workflows can be scheduled, parameterized, and connected to internal tooling. PioSOLVER and GTO+ emphasize API-driven automation of analysis runs, while PokerTracker 4 and Holdem Manager 3 rely more on configuration-driven pipelines than a public automation API.
Data model continuity from hand history to derived metrics
Tools like PokerTracker 4 and Holdem Manager 3 compute player, session, and HUD-compatible statistics from a structured hand-history database schema. This continuity supports consistent calculations across sessions and reduces analysis drift when importing new hands.
HUD schema wiring for repeatable table reads
PokerTracker 4 offers HUD stat profiles with customizable layouts for context-specific table views, and Holdem Manager 3 provides configurable HUD statistics derived from the same database schema. This wiring matters when HUD setup must match the filters used for offline review.
API and automation surface for analysis run orchestration
PioSOLVER and GTO+ expose automation oriented around API-accessible outputs and saved analysis runs that can be rerun with parameter changes. This matters when batch processing, internal dashboards, or job scheduling is required beyond file-based exchanges.
Scenario configuration tied to decision points
GTO Wizard maps hand-history driven scenario setup to specific decision points so study queries land on the right state transitions. PokerSnowie compares candidate lines during replay-style review based on ingested hand-history inputs, which improves decision traceability.
Deterministic range versus board or EV calculation workflows
Flopzilla provides interactive range versus board equity computation with scenario filtering by hand and board, which supports repeatable what-if comparisons. CardRunners EV focuses on EV and range evaluation from provided hand or range inputs, which supports decision review centered on EV deltas.
Admin and governance controls for access separation and auditability
DriveHUD scopes workspaces and analysis visibility by user roles and data scopes, which supports controlled access for mid-volume poker teams. PioSOLVER and GTO+ support controlled configuration but can require careful upfront provisioning for RBAC and audit log visibility.
A decision path from ingestion and schema control to automation and team governance
Start with the source of truth for analysis and confirm whether the tool keeps ingestion, schema, and derived metrics in one consistent data model. PokerTracker 4 and Holdem Manager 3 excel when local database consistency and HUD workflows are the primary integration pattern.
Then decide whether the required workflow needs API-driven orchestration or configuration-driven repeats. PioSOLVER and GTO+ fit when automation must drive batch reruns and internal sync, while Flopzilla and CardRunners EV fit when repeatable scenario computations matter more than programmatic automation.
Choose the system’s data model anchor
If the primary workflow depends on a consistent hand-history database for stats, select PokerTracker 4 or Holdem Manager 3 because both compute HUD and reporting outputs from a structured schema. If the workflow depends on solver artifacts and extensive-form game analysis, select PioSOLVER, GTO+, or GTO Wizard based on how their scenario setup maps to decision points.
Match HUD and reporting wiring to the same filters
For live table decision support, prioritize PokerTracker 4 HUD stat profiles and its HUD configuration pipeline tied to report filters. For serious session review across many hands, select Holdem Manager 3 because its configurable HUD statistics are derived from the same underlying hand-history schema used for database exports.
Validate automation depth and API expectations early
If the workflow requires programmatic orchestration of analysis runs, choose PioSOLVER or GTO+ because they emphasize API-accessible outputs and parameterized reruns. If automation is mostly repeatable UI-driven configuration and export-driven review, choose PokerTracker 4, Holdem Manager 3, Flopzilla, or CardRunners EV because automation is centered on configurable import, scenario setup, and repeatable outputs rather than broad endpoints.
Pick scenario tooling based on the decision artifacts needed
If the deliverable is deterministic equity analysis from ranges, choose Flopzilla because it computes equity for fixed or filtered ranges against selected boards. If the deliverable is EV-focused decision refinement from hand or range inputs, choose CardRunners EV because its core loop centers on EV and scenario comparisons.
Assess governance controls before adding collaborators
For teams needing access separation and limited data visibility, evaluate DriveHUD because it uses user roles and workspace scoping for analysis visibility. For teams that need RBAC and auditability around solver runs, evaluate PioSOLVER and GTO+ because permission granularity and audit log visibility depend on how provisioning and workflow conventions are implemented.
Which poker analysis workflows fit each tool
PokerTracker 4 and Holdem Manager 3 fit players who want database-backed analysis tied to HUD workflows and repeatable filters across long hand histories. PioSOLVER and GTO+ fit teams that want automated reruns of solver analysis with API-accessible outputs.
Training and study loops split into scenario replay and decision comparison in PokerSnowie and decision-point scenario mapping in GTO Wizard. Range and EV specific workflows map to Flopzilla and CardRunners EV when deterministic equity or EV computations are the key deliverable.
Solo analysts who need fast local stats plus repeatable HUD views
PokerTracker 4 fits because it maintains a local hand-history database and supports HUD stat profiles with customizable layouts for context-specific table views. It also provides import and data curation workflows that reduce manual analysis overhead.
Serious players managing large hand volumes and schema-driven review
Holdem Manager 3 fits when database exports, tagging, and session grouping are used to drive HUD-ready statistics across many sessions. Its configurable HUD statistics come from the same database schema as its database-backed hand analysis.
Small study groups that focus on decision review loops rather than team governance
PokerSnowie fits because its replay-style review compares candidate lines based on ingested hand-history inputs. GTO Wizard also fits small teams because it maps hand-history-driven scenario setup to specific decision points with reusable study workflows.
Teams that require API-driven automation for repeatable GTO run orchestration
PioSOLVER fits because it supports configurable analysis run automation with parameterized inputs and API-accessible outputs. GTO+ fits when teams need saved analysis sessions tied to structured range and context schemas that can be rerun consistently.
Mid-volume teams that need controlled access to analysis workspaces and filters
DriveHUD fits because it connects hand-history ingestion into an analysis schema and scopes visibility through user roles and workspace scoping. Its report filters support consistent breakdowns by position, range, and spot for team review.
Pitfalls that break repeatability, automation, or governance in poker analysis toolchains
Many failures come from selecting a tool that does not match the workflow’s integration pattern. Export-driven workflows can introduce manual routing and reduce the consistency required for repeatable HUD and reporting setups.
Governance issues appear when RBAC and auditability are assumed without a governance surface that actually supports provisioning and traceability at the desired granularity. Automation gaps also show up when automation needs programmatic endpoints but the tool is configuration-driven or file-based.
Assuming a public automation API when the tool is configuration-driven
PokerTracker 4 and Holdem Manager 3 center automation on configurable HUD and reporting pipelines rather than a public automation API surface. PioSOLVER and GTO+ are the better fit when programmatic orchestration and API-accessible outputs are required.
Mixing scenario outputs from different tools without a shared schema contract
Flopzilla and CardRunners EV exportable results can be harder to keep consistent across automated pipelines when the data model schema is not explicitly carried into downstream systems. PioSOLVER and GTO+ keep a structured analysis run model aligned to repeatable inputs and outputs, which helps maintain a stable schema contract.
Overlooking governance and access scoping when adding multiple analysts
PokerSnowie and Flopzilla do not emphasize provisioning and governance controls, which can limit controlled collaboration. DriveHUD supports user roles and workspace scoping, while PioSOLVER and GTO+ require careful upfront provisioning for RBAC and audit visibility.
Assuming throughput will work for batch workloads without job orchestration controls
GTO+ notes that batch analysis throughput can require careful job scheduling when running many parameterized experiments. PioSOLVER supports configurable analysis run automation and parameterized reruns with API-accessible outputs, which aligns better with batch throughput needs.
How We Selected and Ranked These Tools
We evaluated PokerTracker 4, Holdem Manager 3, PokerSnowie, Flopzilla, GTO Wizard, PioSOLVER, GTO+, CardRunners EV, and DriveHUD using a criteria-based scoring approach that emphasized features, ease of use, and value. Features accounted for the largest share of the overall rating, while ease of use and value each carried a meaningful portion of the final score. Every tool was assessed on integration depth, data model alignment, automation and API surface, and admin and governance controls as represented in the available tool descriptions.
PokerTracker 4 is set apart by its HUD stat profiles with customizable layouts tied to a structured local hand-history database and report filters. That capability lifts the features factor because it connects ingestion, schema-driven stats, and repeatable table views into one workflow rather than relying primarily on export and manual routing.
Frequently Asked Questions About Poker Analysis Software
Which tool is better for local HUD and repeatable report generation from hand histories?
How do Flopzilla and CardRunners EV differ for range and equity or EV scenario work?
What tool is best when solver outputs must map to specific decision points in hand history review?
Which option supports API-driven integration with defined schemas and parameterized analysis runs?
How do DriveHUD and poker-specific database tools handle access separation and admin controls?
Which tools provide extensibility through export, import, or programmable automation surfaces?
What is the typical data migration pain point when moving from one hand-history analysis workflow to another?
Why might an analyst choose PokerSnowie over a solver pipeline like PioSOLVER for review and learning loops?
Which tool is more appropriate for scheduled recomputation and programmatic hand import workflows?
Conclusion
After evaluating 9 video games and consoles, PokerTracker 4 stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Video Games And Consoles alternatives
See side-by-side comparisons of video games and consoles tools and pick the right one for your stack.
Compare video games and consoles tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.