Commissioned Research
Top 9 Best Pharmacokinetic Software of 2026

GITNUXSOFTWARE REVIEW

Healthcare & Medicine

Top 9 Best Pharmacokinetic Software of 2026

A market-style roundup of pharmacokinetic software options, covering typical use cases and tradeoffs for teams choosing a workflow, including Julia.

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

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

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

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Pharmacokinetic software tools turn clinical study data into parameter estimates through population models and simulation workflows. This comparison helps analysts and drug development teams weigh model-building mechanics, inference approach, automation and API fit, and integration into their analysis pipeline.

SAS Drug Development is the best overall pick for teams using SAS for regulated analytics that run population PK and simulations because its SAS-based pharmacometrics workflows strengthen end-to-end modeling, simulation, and diagnostics in clinical datasets, whereas NONMEM fits groups who need rigorous nonlinear mixed-effects control streams and diagnostics for complex PK/PD.

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

SAS Drug Development

Population pharmacokinetic modeling and simulation using SAS-based pharmacometrics workflows

Best for: Teams using SAS for regulated analytics that run population PK and simulations

2

NONMEM

Editor pick

NONMEM control stream for nonlinear mixed-effects estimation with covariate and variability modeling

Best for: Population PK teams needing rigorous nonlinear mixed-effects modeling and diagnostics

3

Julia

Editor pick

Multiple dispatch with just-in-time compilation for fast custom PK solver development

Best for: Teams building custom PK/PD models needing speed and modeling flexibility

Comparison Table

1
enterprise analytics
9.4/10
Overall
2
population modeling
8.8/10
Overall
3
high-performance
8.7/10
Overall
4
Bayesian modeling
8.3/10
Overall
5
8.0/10
Overall
6
open-source
7.9/10
Overall
7
R mixed-effects
7.4/10
Overall
8
model-based
7.1/10
Overall
9
open-source
6.8/10
Overall
#1

SAS Drug Development

enterprise analytics

SAS modeling and simulation capabilities support pharmacokinetic analysis workflows with statistical inference for clinical research datasets.

9.4/10
Overall
Features9.4/10
Ease of Use9.5/10
Value9.3/10
Standout feature

Population pharmacokinetic modeling and simulation using SAS-based pharmacometrics workflows

SAS Drug Development differentiates with an integrated modeling and simulation workflow that supports population pharmacokinetics and pharmacometrics studies within SAS’s analytics stack. Core capabilities include nonlinear mixed-effects modeling support, simulation and post-processing, and structured dataset handling designed for clinical drug development pipelines.

The toolset also emphasizes reproducible analysis via scripted data preparation, model fitting, and reporting artifacts. It fits teams that already rely on SAS for statistical governance, data transformation, and validated compute environments.

Pros
  • +Strong population PK modeling workflows integrated with SAS data preparation
  • +Simulation and diagnostics support model refinement and scenario planning
  • +Reproducible scripted analyses align with regulated development documentation
Cons
  • –Workflow depth can require SAS programming skill for efficient use
  • –Less beginner-friendly than GUI-first pharmacometrics tools
  • –Tight SAS ecosystem alignment can limit interoperability choices
Use scenarios
  • Clinical pharmacometrics teams

    Population PK model estimation on SAS data

    Typical parameters with variability

  • SAS-centric biostatistics groups

    Scripted model fitting and reporting

    Reproducible analysis outputs

Show 1 more scenario
  • Modeling and simulation teams

    Simulate dose regimens and post-process

    Actionable simulation results

    Generates simulated exposure profiles and uses structured post-processing for downstream PK evaluation.

Best for: Teams using SAS for regulated analytics that run population PK and simulations

#2

NONMEM

population modeling

NONMEM builds and validates population pharmacokinetic and pharmacodynamic models from clinical study data using nonlinear mixed effects methodology.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

NONMEM control stream for nonlinear mixed-effects estimation with covariate and variability modeling

NONMEM stands out as a modeling workbench for nonlinear mixed-effects pharmacokinetics and pharmacodynamics with a long track record in regulated workflows. It supports nonlinear model estimation, complex residual error structures, covariate modeling, and advanced diagnostics for population PK.

The software integrates with external toolchains for data preparation and result review, and it is used to quantify inter-individual variability and parameter correlations. NONMEM’s strength is statistical rigor for heterogeneous patient and formulation variability using control stream driven model specifications.

Pros
  • +Nonlinear mixed-effects estimation supports complex population PK and PD models
  • +Covariate modeling estimates effects with structured variability and correlations
  • +Robust diagnostics support model qualification workflows
Cons
  • –Control-stream based modeling increases setup time for first-time users
  • –Computational tuning and convergence troubleshooting require expert experience
  • –Workflow integration depends on external scripting and downstream analysis tools
Use scenarios
  • Pharmacometricians

    Build population PK compartment models

    Population PK model

  • PK/PD modelers

    Link exposure to response in PD

    Explainable exposure-response link

Show 2 more scenarios
  • Advanced PK/PD researchers

    Run mechanistic PK/PD with ODEs

    Dynamic mechanistic model

    Represents complex biological and exposure-response processes using compartmental structures with ordinary differential equations.

  • Pharmacometrics statisticians

    Test covariates for PK variability

    Covariate-driven variability

    Evaluates demographic and clinical factors as explanations for variability in PK or PD parameters.

Best for: Population PK teams needing rigorous nonlinear mixed-effects modeling and diagnostics

#3

Julia

high-performance

Julia enables high-performance pharmacokinetic modeling and simulation workflows with scientific computing libraries and custom model code.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Multiple dispatch with just-in-time compilation for fast custom PK solver development

Julia is a high-performance scientific programming language used for building pharmacokinetic and pharmacodynamic models with near-C speeds. Core capabilities include fast numerical computing, first-class differential equation support, and seamless interoperability with optimized C and Fortran libraries.

Model development can span standalone scripts to production-grade solvers by combining automatic differentiation, extensive package ecosystem, and reproducible computation. For pharmacometrics workflows, it supports parameter estimation and uncertainty analysis by pairing with probabilistic and optimization tooling.

Pros
  • +High performance ODE and SDE computations for PK model simulations
  • +Automatic differentiation enables gradient-based parameter estimation
  • +Large scientific package ecosystem supports calibration and inference workflows
Cons
  • –Requires programming skills for model implementation and maintenance
  • –PK-specific modeling abstractions are less turnkey than dedicated suites
  • –Tooling and validation workflows depend heavily on custom project structure
Use scenarios
  • Clinical pharmacometricians

    Build ODE-based PK models rapidly

    Faster model development cycles

  • Biostatistics and modeling teams

    Run Bayesian parameter estimation pipelines

    More stable uncertainty estimates

Show 2 more scenarios
  • Research software engineers

    Integrate PK solvers with C libraries

    Lower runtime and integration effort

    Julia interoperates with optimized C and Fortran code for production-ready PK computations.

  • Translational modeling scientists

    Perform sensitivity analysis for dosing

    Clear drivers of exposure

    Julia enables derivative-based sensitivity and uncertainty analyses for key dosing decision variables.

Best for: Teams building custom PK/PD models needing speed and modeling flexibility

#4

Stan

Bayesian modeling

Stan supports Bayesian pharmacokinetic parameter estimation and posterior simulation using probabilistic programming for hierarchical models.

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

Hamiltonian Monte Carlo with automatic differentiation for Bayesian parameter inference

Stan is distinct for turning pharmacokinetic modeling into a probabilistic programming workflow built around Hamiltonian Monte Carlo. It supports Bayesian estimation of ordinary differential equation based PK models, including hierarchical population structures and custom likelihoods.

Pros
  • +Bayesian PK via Stan language with fast gradient-based sampling
  • +Flexible hierarchical models for population PK and covariate effects
  • +Supports ODE likelihoods for dynamic PK models and simulation outputs
  • +Posterior uncertainty drives rigorous parameter and prediction inference
Cons
  • –Requires coding a model and interpreting sampling diagnostics
  • –ODE models can be slow and sensitive to solver and parameterization
  • –Tuning sampler settings can be necessary for stable convergence
  • –Workflow lacks GUI-first fit, inspection, and model selection tooling
Use scenarios
  • Bayesian pharmacometricians

    Estimate hierarchical Bayesian PK parameters

    Posterior parameter uncertainty

  • Mechanistic PK modelers

    Fit ODE-based PK models in Stan

    Mechanistic posterior predictions

Show 1 more scenario
  • Advanced model developers

    Use custom likelihoods for PK data

    Flexible likelihood modeling

    Writes custom probability models to support nonstandard error and likelihood structures for PK fitting.

Best for: Teams building custom Bayesian PK models needing ODEs and rigorous uncertainty quantification

#5

Certara Monolix alternative workflows

pharmacometrics

Certara’s pharmacometrics software ecosystem supports pharmacokinetic and pharmacodynamic modeling, simulation, and reporting for drug development teams.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Monolix-compatible run workflow automation for estimation and simulation scenario execution

Certara Monolix alternative workflows focus on PK modeling execution through Monolix-compatible workflows that support simulation and parameter estimation runs in repeatable pipelines. Core capabilities center on nonlinear mixed-effects modeling workflows, including model building, estimation settings management, and simulation output handling across study iterations.

Pros
  • +Supports repeatable PK modeling and simulation workflows across study iterations
  • +Improves operational consistency by standardizing estimation and simulation configurations
  • +Handles outputs for downstream analysis and reporting-focused PK work
Cons
  • –Workflow depth can add complexity for teams without PK automation experience
  • –Greater setup effort is needed than for single-session modeling usage
  • –Customization for edge-case model steps may require additional engineering
Use scenarios
  • Clinical pharmacometrics teams

    Automate Monolix PK estimation runs

    Faster reproducible parameter estimation

  • Translational science groups

    Batch-run PK simulation scenarios

    Consistent decision-ready simulation outputs

Show 2 more scenarios
  • Regulatory submission teams

    Reproduce modeling results for reports

    Reduced reporting rework

    Track and reuse estimation and simulation configurations across iterations to support auditability.

  • Biostatistics operations

    Manage study iterations in pipelines

    Lower operational modeling overhead

    Operationalize PK workflow automation so model runs and outputs are reused across versions.

Best for: PK teams operationalizing nonlinear mixed-effects modeling into repeatable run pipelines

#6

gpkmodel

open-source

gpkmodel provides code for pharmacokinetic model specification, fitting, and simulation workflows that can be integrated into analysis pipelines.

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

Scriptable compartmental PK modeling with simulation and fitting driven by model code

gpkmodel stands out as a GitHub-hosted pharmacokinetic modeling codebase that targets reproducible, script-driven workflows. It focuses on building and evaluating PK models such as compartmental structures, fitting them to concentration-time data, and producing simulated responses.

Pros
  • +Code-first PK model specification supports version control and reproducible experiments
  • +Compartmental modeling and simulation workflows fit common concentration-time analyses
  • +Batch runs enable consistent refits and scenario testing across datasets
Cons
  • –Workflow setup and debugging require strong modeling and software proficiency
  • –Limited evidence of polished graphical diagnostics compared with dedicated PK suites
  • –Model customization can be time-consuming for teams needing guided templates
Use scenarios
  • Data scientists in version control

    Reproducible PK modeling from scripts

    Repeatable model results

  • PK modelers

    Fit compartment models to concentration data

    Estimated PK parameters

Show 1 more scenario
  • Simulation-driven analysts

    Simulate responses from fitted PK models

    Simulated response profiles

    Generates simulated responses after fitting and applies model evaluation outputs for iterative refinement.

Best for: Research teams automating compartmental PK modeling in reproducible, code-driven pipelines

#7

nlmixr

R mixed-effects

nlmixr supplies R-based nonlinear mixed effects pharmacokinetic and pharmacodynamic modeling tools focused on hierarchical model fitting and inference.

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

Stan-backed Bayesian inference for nonlinear mixed effects PK model estimation

nlmixr stands out as an open-source modeling tool that integrates nonlinear mixed effects modeling into an R workflow with a Stan backend. It supports PK model specification for population analysis, including common compartmental structures and covariate effects using estimated random effects.

Pros
  • +Uses Stan-backed inference for nonlinear mixed effects PK models
  • +Enables posterior predictive checks and simulation-driven model diagnostics
  • +Keeps model code, data handling, and results in a single R pipeline
  • +Rich support for covariates and random effects in population PK
Cons
  • –Model syntax and debugging can be harder than GUI-based PK tools
  • –Computational cost can be high for large datasets and complex random effects
  • –Advanced diagnostics require familiarity with Bayesian concepts and Stan outputs
Use scenarios
  • Data scientists in version control

    Reproducible PK modeling from scripts

    Repeatable model results

  • PK modelers

    Fit compartment models to concentration data

    Estimated PK parameters

Show 1 more scenario
  • Simulation-driven analysts

    Simulate responses from fitted PK models

    Simulated response profiles

    Generates simulated responses after fitting and applies model evaluation outputs for iterative refinement.

Best for: Teams building reproducible Bayesian population PK models in R

#8

Certara mRx

model-based

Certara mRx supports model-based simulations and population modeling workflows for pharmacometrics and pharmacokinetic decision-making.

7.1/10
Overall
Features7.1/10
Ease of Use7.0/10
Value7.2/10
Standout feature

Integrated model evaluation and simulation workflow for dose and exposure scenario planning

Certara mRx focuses on pharmacokinetic modeling workflows that connect analysis, simulation, and reporting for regulated decision-making. The solution supports NONMEM-ready modeling practices and integrates model building, evaluation, and scenario simulations for exposure and dose optimization. It is designed for teams that need traceable outputs and consistent PK evidence packages rather than standalone exploratory analytics.

Pros
  • +Strong support for PK model building and scenario simulation workflows
  • +Designed for regulated, traceable pharmacometrics deliverables
  • +Integrates with NONMEM-centric modeling practices for established pipelines
Cons
  • –Workflow setup and governance can feel heavy for smaller teams
  • –Specialized pharmacometrics expertise is needed to use outputs correctly
  • –Less suited for quick, lightweight exploratory PK analysis
Use scenarios
  • Regulated modeling teams

    Create traceable exposure simulations

    Traceable PK evidence package

  • Pharmacokinetic modelers

    Use NONMEM-aligned modeling practices

    Consistent mRx workflows

Show 1 more scenario
  • Dose optimization groups

    Compare dosing scenarios for exposure

    Dose scenario ranking

    Performs scenario-based simulations for exposure and dose optimization with structured reporting artifacts.

Best for: Pharmacometric teams producing regulated PK evidence packages using standard modeling pipelines

#9

R

open-source

R provides pharmacokinetic modeling and nonlinear mixed effects tooling through packages used for fitting, diagnostics, and simulation.

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

Integration with nonlinear mixed effects modeling packages for population PK estimation and simulation

R is distinct as a general-purpose statistical computing environment with a large ecosystem of pharmacokinetic packages. It supports nonlinear mixed effects modeling, nonlinear regression workflows, and extensive data import and transformation for PK datasets.

Pros
  • +Rich PK ecosystem with nonlinear mixed effects and simulation workflows
  • +Custom model building via user-defined functions and extensible model syntax
  • +Strong graphics support for concentration-time views and diagnostic plots
Cons
  • –Requires R scripting for reproducible end-to-end PK analysis workflows
  • –Setup and package-specific learning curve can slow model implementation
  • –No single unified PK interface for validation, reporting, and QA
Use scenarios
  • Pharmacometric software teams

    Run nonlinear mixed effects PK in R

    Fitted PK parameter estimates

  • Custom PK model developers

    Implement bespoke PK models and likelihoods

    Custom model implementation

Show 1 more scenario
  • PK analysts

    Simulate predictions and diagnostic plots

    Diagnostic-ready visual outputs

    Generates simulated predictions from fitted models and uses plotting for concentration-time and model diagnostics.

Best for: Teams needing flexible PK modeling, simulation, and analysis automation via code

Conclusion

After evaluating 9 pharmacokinetic software, SAS Drug Development 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
SAS Drug Development

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Pharmacokinetic Software

How do teams integrate pharmacokinetic model outputs with downstream reporting in Certara mRx versus NONMEM?
Certara mRx connects model building, model evaluation, and dose or exposure scenario simulations into a single workflow aimed at regulated decision evidence packages. NONMEM produces estimation and diagnostic outputs from control stream runs, and teams typically route results through external data preparation and review steps to match reporting needs.
Which toolchains fit automation requirements for repeatable PK model run pipelines, especially when scenarios must be rerun consistently?
gpkmodel supports script-driven compartmental PK modeling where model code and parameter files support version-controlled repeats across datasets. Certara Monolix alternative workflows focus on repeatable Monolix-compatible estimation and simulation scenario execution, so teams standardize run configuration and reuse scenario outputs across study iterations.
When a workflow requires provisioning and consistent access controls for multiple model authors, how do RBAC and audit logging typically show up?
SAS Drug Development fits teams with governed SAS compute environments where access and audit trails align with existing analytics governance. For code-centric stacks like gpkmodel and Julia, access control is usually enforced at the repository, compute, and execution layers rather than inside a packaged pharmacometrics interface.
What data migration steps are usually needed when moving concentration-time data and model artifacts from R workflows into NONMEM control stream processes?
R workflows using nonlinear mixed-effects packages often involve custom data transformations and model objects that do not map directly to NONMEM control stream inputs. Teams typically reformat concentration-time and covariate datasets into NONMEM-compatible structures and regenerate model specifications using NONMEM control streams, while preserving covariate definitions and variability assumptions from the R scripts.
How do extensibility and schema-level configuration differ between nlmixr and SAS Drug Development for PK/PD modeling pipelines?
nlmixr keeps model code, inference configuration, and diagnostics within an R scripting environment backed by a Stan engine, which makes extending model components a coding change. SAS Drug Development keeps configuration and dataset handling inside SAS processes, so extensibility often happens through SAS data models, structured transformation steps, and controlled reporting artifacts.
What tradeoff appears when using Stan for population PK Bayesian estimation compared with NONMEM’s control stream workflow?
Stan provides posterior distributions via Hamiltonian Monte Carlo and automatic differentiation, so teams can quantify uncertainty but must manage sampling diagnostics and model debugging in the Stan model language. NONMEM focuses on nonlinear mixed-effects estimation driven by control streams with established residual error and covariate modeling patterns, which can reduce workflow friction for teams already standardized on NONMEM practices.
How does simulation throughput differ between Julia-based model development and tool suites that emphasize ready-made PK modeling interfaces?
Julia targets high-performance numerical computing for custom PK and PK/PD solver development, so simulation speed depends on how well the model and ODE solvers are written and compiled. R-based workflows like nlmixr and Stan-based estimation also support simulation, but throughput is constrained by the inference and sampling workload rather than only by the simulator.
Which workflow fits sparse sampling analysis needs when the team already uses NLME-style population modeling assumptions?
NONMEM supports NLME-style estimation with covariate model building and residual error structures that can be configured for sparse sampling designs. nlmixr supports posterior predictive checks and Bayesian population PK model estimation, which can handle sparse observations by propagating uncertainty through the posterior.
Where does data model alignment break most often when teams attempt to reuse model diagnostics across gpkmodel, R, and Stan?
gpkmodel generates results from script-defined model logic and simulation outputs, so diagnostic outputs can differ in structure from R plotting and diagnostics conventions. R and Stan share a scripting workflow in different forms, but posterior predictive checks and residual summaries often differ in outputs and data shapes, requiring explicit diagnostic mapping rather than reuse by filename or object name.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Pharmacokinetic Software

Pharmacokinetic software options differ most in how far their integration and automation go when you build, run, and operationalize models. We recommend you compare integration depth and data model behavior, then verify update frequency and auditability during real workflows.

Workflow integration and API automation

Why it matters

Pharmacokinetic work often spans modeling, import/export, reporting, and re-runs. Workflow integration and API automation reduce manual handoffs when you iterate on models and results.

How to check

Ask to see a run that starts from an external dataset and returns outputs back into your environment using the documented API or scheduled automation. Confirm whether the API can trigger a batch, collect run logs, and write artifacts in a repeatable folder structure.

Data model mapping for studies and runs

Why it matters

Data model behavior determines whether the tool stays consistent across study versions, multiple cohorts, and repeated analyses. If mapping is unclear, you risk mismatched inputs and confusing outputs.

How to check

Bring a small sample study with at least two dataset versions (e.g., revised covariates). During the demo, trace how fields flow from import into outputs, and ask what happens when columns change or units differ.

Update frequency for modeling features

Why it matters

Update frequency matters because PK tooling evolves with better diagnostics, import support, and workflow changes. Frequent, controlled updates help avoid breaking changes mid-project.

How to check

Ask for the release cadence and a changelog showing modeling- and workflow-relevant updates. Confirm whether outputs remain comparable across versions by checking how the tool labels runs and stores version metadata.

Run provenance and audit log depth

Why it matters

Run provenance and audit log depth are critical when you must reproduce results for review. It also helps you debug why a re-run changed outputs.

How to check

Request a demo of re-running the same configuration after a minor change. Check whether the tool records inputs used, configuration parameters, environment/version details, and produces a traceable run history.

Diagnostics output coverage and export

Why it matters

Diagnostics output coverage shows whether reviewers can assess fit quality and assumptions without exporting everything into custom scripts. Export capability speeds up documentation and internal checks.

How to check

During the demo, generate diagnostics for a saved example and verify what plots/tables you can export (including underlying data, not only images). Ask how diagnostics behave when you change one modeling option.

Batch reproducibility for repeated studies

Why it matters

Batch reproducibility reduces time spent rebuilding project structure for each study or cohort. It also helps you compare outcomes across runs in a controlled way.

How to check

Ask them to run a small batch across two cohorts and then rerun after a configuration change. Verify whether batch jobs can be parameterized, whether outputs keep consistent naming, and whether prior artifacts remain accessible.

Red flags

  • API automation exists, but manual steps are required between run and outputs.
  • Run provenance is thin, so we can’t reproduce which inputs and settings produced results.
  • Data model mapping breaks when dataset columns or units change between versions.

Fit by situation

  • If we need to trigger modeling runs from our existing pipelines, prioritize workflow integration and API automation.
  • If our team frequently revises study datasets and wants comparable outputs, prioritize data model mapping for studies and runs.
  • If review and rework require strict traceability, prioritize run provenance and audit log depth.
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.