Commissioned Research
Top 10 Best Business Process Automation Software of 2026

GITNUXSOFTWARE REVIEW

Business & Finance

Top 10 Best Business Process Automation Software of 2026

Compare business process automation software options from Moxo and Grok Bot, with features and tradeoffs for teams assessing workflow tools.

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

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

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

Operations leaders, process analysts, and technical evaluators use business process automation software to route work across applications, teams, and approval steps. The key tradeoff is how much orchestration, integration configuration, and audit control a platform provides versus how easily business users can adapt workflows, especially when automation must hand decisions or exceptions to people.

Moxo is the strongest fit for mid-market and enterprise operations, finance, and shared-services teams automating judgment-heavy work because its agents prepare cases and hand decisions to accountable people with an audit trail, whereas Microsoft Power Automate suits teams bridging Microsoft 365 and Windows apps since cloud flows can trigger desktop workflows.

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

Moxo

Moxo blends AI agents and people to automate the document-heavy, judgment-heavy work inside business processes: self-learning agents read, check and prepare each case and escalate to a person when a decision is needed, so every outcome has an accountable owner and an audit trail.

Best for: Moxo is best for operations, finance and shared services teams at mid-market and enterprise organizations that want AI agents and people to automate end-to-end processes together, with clear accountability for every decision, especially in financial services and insurance.

2

Microsoft Power Automate

Editor pick

Cloud flows can trigger attended or unattended Windows desktop flows within the Power Automate environment.

Best for: Fits when teams need to connect Microsoft 365 processes with Windows applications that lack suitable connectors.

3

Workato

Editor pick

Agent Studio connects AI agents to enterprise systems through defined actions and recipe capabilities.

Best for: Fits when enterprise teams coordinate complex work across applications, APIs, and AI agents.

Comparison Table

1
MoxoBest overall
Human-AI process orchestration platform
9.5/10
Overall
2
8.7/10
Overall
3
enterprise
8.6/10
Overall
4
enterprise
8.4/10
Overall
5
8.2/10
Overall
6
7.8/10
Overall
7
AI assistant and productivity automation
7.6/10
Overall
8
7.0/10
Overall
9
6.9/10
Overall
10
6.6/10
Overall
#1

Moxo

Human-AI process orchestration platform

Moxo is business process automation software that blends AI agents and people: agents automate end-to-end processes across teams and systems, people own the exceptions and decisions, and governance and accountability are built in.

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

Moxo blends AI agents and people to automate the document-heavy, judgment-heavy work inside business processes: self-learning agents read, check and prepare each case and escalate to a person when a decision is needed, so every outcome has an accountable owner and an audit trail.

Moxo is a human-AI orchestration platform for business operations. Mid-market and enterprise operations teams use Moxo to orchestrate complex business processes with humans and AI agents. Moxo blends AI agents and people in the same process, so governance and accountability are built in: agents do the running work, a named person or team owns every decision, and every action lands on the audit trail. Moxo automates whole processes from intake to final sign-off: self-learning AI agents take on many kinds of work, such as reviewing an application, reconciling an account or preparing a decision, while people review exceptions and approve outcomes. Moxo is human-in-the-loop by design, so teams decide which steps agents run on their own and which need a person's sign-off.

Moxo automates across the systems you already run, such as ERP, CRM and document stores, through integrations, a REST API and MCP, and threads many agents through one process, in sequence or in parallel. Operations teams describe a process in plain language or build it in a no-code builder, and can run it the same day, without specialized developers or a separate implementation project. Built-in functionality includes AI document extraction, branching logic, SLA deadlines with escalation, exception routing to people, e-signatures, bulk starts for high-volume processes, and connectors to ERP, CRM and messaging tools. For professional services firms, Moxo runs client engagement, approvals and delivery handoffs across teams.

Pros
  • +Moxo's blend of AI agents and people gives every process built-in governance and accountability: each decision has a named owner, agents work within the rules people set, and every human and agent action is recorded on the audit trail.
  • +Moxo lets operations teams build automations without specialized developers: describe a process in plain language and Moxo builds the steps, forms, approvals and agents.
  • +Moxo connects to ERP, CRM and document systems through integrations, a REST API and MCP, with SSO, multi-factor authentication and a full audit trail of every human and agent action.
  • +Moxo extracts data from documents with AI, routes exceptions to the right people, and starts high-volume processes in bulk.
Cons
  • –Moxo automates through APIs and integrations. Teams that need screen-level automation of legacy desktop applications without APIs pair Moxo with an RPA tool.
  • –Moxo is designed for business processes that involve people and AI agents. Teams that only need system-to-system data pipelines or ETL jobs will find a dedicated integration platform a closer fit.
Use scenarios
  • Shared services and HR operations teams

    Employee and HR service requests

    Service requests completed faster, with every step tracked.

  • Finance operations teams

    Invoice exception handling across AP, procurement and budget owners

    Invoice exceptions resolved inside one tracked process, with a complete audit trail for every decision.

Show 1 more scenario
  • Procurement and finance teams

    Purchase requests and procure-to-pay approvals

    Purchases approved on policy, with no manual re-keying into the ERP.

    Moxo agents check each purchase request against budget and policy, route it through the approval matrix, and create the purchase order in the ERP once it is approved.

Best for: Moxo is best for operations, finance and shared services teams at mid-market and enterprise organizations that want AI agents and people to automate end-to-end processes together, with clear accountability for every decision, especially in financial services and insurance.

#2

Microsoft Power Automate

enterprise

Microsoft's automation platform spanning cloud workflows, desktop RPA, and process mining.

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

Cloud flows can trigger attended or unattended Windows desktop flows within the Power Automate environment.

Power Automate can pair cloud flows with attended or unattended desktop flows, extending automation from connector-based tasks to Windows applications without a suitable connector. Its Microsoft 365 and Dynamics 365 connectors cover common business systems, while custom connectors can link internal services. Solutions and data policies give administrators controls for deploying flows and managing connector use.

Desktop flows require configured Windows machines and can fail when an application interface changes. A finance team can collect invoice approvals through a cloud flow, then use a desktop flow to enter approved invoices into older accounting software.

Pros
  • +Cloud flows can hand work to attended or unattended Windows desktop flows.
  • +Connectors span Microsoft 365, Dynamics 365, and external services.
  • +Solutions and data policies give administrators deployment and connector controls.
Cons
  • –Desktop flows require configured Windows machines and can fail after interface changes.
  • –Troubleshooting can span cloud actions, desktop sessions, and connector responses.
  • –Custom connectors and environment policies add administration for small teams.
Use scenarios
  • HR operations teams

    Employee onboarding approvals

    Faster onboarding handoffs

  • Finance operations teams

    Legacy invoice entry

    Reduced invoice rekeying

Show 1 more scenario
  • IT administrators

    Access request routing

    Consistent access decisions

    Forms, manager approvals, and directory actions can route access requests with recorded execution history.

Best for: Fits when teams need to connect Microsoft 365 processes with Windows applications that lack suitable connectors.

#3

Workato

enterprise

Enterprise automation platform combining integration, workflow automation, and conversational triggers.

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

Agent Studio connects AI agents to enterprise systems through defined actions and recipe capabilities.

Workato suits organizations coordinating processes across many business applications, especially when teams need reusable logic and centralized administration. Recipe functions can package common steps for reuse, and Agent Studio gives AI agents access to connected systems and defined actions. The API Platform extends the same environment to API creation and management.

Recipe-based design does not provide native BPMN process diagrams, and intricate branching can make workflows harder to maintain. For employee onboarding across HR, identity, and collaboration systems, Workato can coordinate data movement and approvals, but process owners need to define clear recipe ownership and error handling.

Pros
  • +Agent Studio connects AI agents to enterprise data and defined recipe actions.
  • +Reusable recipe functions reduce duplicated logic across automations.
  • +API Platform supports API creation within the integration environment.
Cons
  • –Recipe-based design lacks native BPMN 2.0 process diagrams.
  • –Complex branching and error handling require experienced recipe authors.
Use scenarios
  • IT operations teams

    Employee onboarding coordination

    Faster employee setup

  • Finance operations teams

    Invoice exception routing

    Fewer manual handoffs

Show 1 more scenario
  • Enterprise integration teams

    Internal API delivery

    Consistent API access

    The API Platform lets teams expose application data and manage endpoints alongside recipe-based integrations.

Best for: Fits when enterprise teams coordinate complex work across applications, APIs, and AI agents.

#4

Camunda

enterprise

Process orchestration platform built on BPMN for automating complex business processes.

8.4/10
Overall
Features8.4/10
Ease of Use8.4/10
Value8.4/10
Standout feature

Zeebe executes BPMN 2.0 models as long-running process instances with retry handling and visibility in Operate.

In business process automation, Camunda is distinct for executing visual process models through the Zeebe engine. Teams can combine BPMN 2.0 processes, service workers, connectors, and human tasks in one orchestration flow.

Pros
  • +Operate shows process-instance status and helps teams investigate failed or delayed executions.
  • +Tasklist assigns human tasks within processes that also call automated services.
  • +Connectors and worker clients support different approaches to service integration.
Cons
  • –Building custom workers and maintaining integrations require engineering ownership.
  • –Moving Camunda 7 processes to Camunda 8 requires workflow and infrastructure changes.
Use scenarios
  • Platform engineering teams

    Microservice process coordination

    Traceable service execution

  • Financial operations teams

    Invoice approval routing

    Controlled approval routing

Show 1 more scenario
  • Customer onboarding teams

    KYC review workflows

    Fewer manual handoffs

    Camunda connects document checks and staff review tasks in one process with visible execution status.

Best for: Fits when engineering teams coordinate long-running processes across services, human approvals, and operational monitoring.

#5

Pipefy

SMB

No-code workflow automation platform for managing recurring business processes and requests.

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

Pipe-and-card process builder links intake forms, phase-based work queues, and rule-triggered actions.

Pipefy turns requests, approvals, and recurring operations into configurable card-based processes, with each pipe organizing work into phases. Teams collect submissions through forms, route cards with rule-based automation, and track owners, due dates, and status. Shared databases and integrations connect processes to business records, while a GraphQL API supports custom connections.

Pros
  • +Public forms create trackable cards without requiring submitters to access the workspace.
  • +Phase-based boards display ownership, status, and due dates for each request.
  • +GraphQL API and native integrations connect processes to external business systems.
Cons
  • –Advanced rules can take time to configure and maintain.
  • –Native dashboards focus on operational reporting rather than process-mining analysis.
Use scenarios
  • Human resources teams

    Employee onboarding requests

    Coordinated onboarding tasks

  • Procurement teams

    Purchase request approvals

    Traceable purchase decisions

Show 1 more scenario
  • IT service desks

    Internal support intake

    Visible request status

    Employees submit support requests through forms, while cards track assignment, status, and resolution dates.

Best for: Fits when operations teams need configurable intake, approvals, and recurring work tracked in one workspace.

#6

Monday.com

SMB

Work management platform with no-code automation recipes for task and project workflows.

7.8/10
Overall
Features7.8/10
Ease of Use7.8/10
Value7.8/10
Standout feature

Cross-board recipes create linked work items and copy selected column values.

Monday.com fits operations teams coordinating repeatable work across customizable boards, with cross-board item creation as a distinctive capability. Teams can trigger status updates, notifications, date changes, and item creation from board events, then connect work to services such as Slack, Gmail, and Jira.

Pros
  • +Cross-board recipes create destination items and copy selected column values.
  • +Forms, boards, and dashboards cover request intake through status reporting.
  • +GraphQL API and webhook support extend connections beyond built-in integrations.
Cons
  • –Complex branching may require external services or custom API work.
  • –Board-centered records are less suited to deeply relational process data.
  • –No native BPMN modeling or process-mining tools.
Use scenarios
  • Operations coordinators

    Route internal service requests

    Clear request ownership

  • Marketing project teams

    Coordinate campaign deliverables

    Visible campaign progress

Show 1 more scenario
  • IT service teams

    Manage recurring operational tasks

    Fewer missed handoffs

    Status changes can create follow-up items and notify responsible technicians across connected boards.

Best for: Fits when operations teams need configurable work tracking and repeatable processes across connected boards.

#7

Grok Bot

AI assistant and productivity automation

Grok Bot supports task-oriented AI automation alongside research, writing, coding, and creative work for individuals and teams.

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

Grok Bot unites the Grok assistant, developer-facing model access, Cursor coding tools, access to current information from X, and X Premium benefits in one AI-oriented service.

Grok Bot brings conversational assistance and task-oriented AI workflows together with developer access to Grok models and AI-assisted coding through Cursor. It supports text, voice, image, and video generation, and can draw on information from the X social network for current-event research.

Pros
  • +Combines the Grok assistant, developer model access, Cursor coding tools, and X benefits in one service.
  • +Supports text, voice, image, and video generation.
Cons
  • –Organizations requiring self-hosted AI in air-gapped environments should consider tools designed for that deployment; Grok Bot has limited evidence of support for it.
  • –Organizations looking for formal business process design and execution should consider a dedicated process platform; Grok Bot's automation is centered on task-oriented AI workflows.

Best for: Developers building AI applications, teams combining research and software development, and creators or knowledge workers using AI for research, writing, reasoning, coding, and media generation.

#8

Zapier

SMB

Connects thousands of web apps to automate multi-step workflows without code.

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

Paths adds conditional branches inside a Zap, letting one trigger route records to different actions.

Among business process automation tools, Zapier’s distinction is its broad app catalog and trigger-to-action builder for connecting everyday business software. Teams can assemble multi-step Zaps, branch conditions with Paths, and apply filters or delays to route work.

Pros
  • +Large app catalog covers common CRM, marketing, support, and productivity systems.
  • +Paths adds conditional branching without requiring separate Zaps for every route.
  • +Tables and Interfaces support lightweight internal data capture and workflow front ends.
Cons
  • –No native BPMN modeling or process-mining workspace.
  • –Complex multi-app runs can make failures harder to trace and diagnose.
  • –Advanced approval chains often need workarounds compared with dedicated case-management tools.
Use scenarios
  • Marketing operations teams

    Route form leads to CRM

    Faster lead handoff

  • Customer support managers

    Escalate urgent support tickets

    Quicker ticket escalation

Show 1 more scenario
  • Small finance teams

    Collect expense approval requests

    Fewer manual transfers

    Forms can capture expense details and trigger notifications or record updates across connected apps.

Best for: Fits when teams need to connect routine tasks across business apps without building custom integrations.

#9

IBM Business Automation Workflow

enterprise

IBM Business Automation Workflow supports workflow orchestration, case management, and process automation.

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

Process Designer and Case Builder let teams create structured processes and variable case work within the same workflow environment.

IBM Business Automation Workflow coordinates structured business processes and variable case work within one authoring and runtime environment. Process Designer models BPMN 2.0 flows, while Case Builder supports work that changes as documents, evidence, and decisions arrive.

Pros
  • +Process Designer and Case Builder handle structured processes and variable case work in one environment.
  • +Workflow Center versions process applications and supports controlled promotion between environments.
  • +Task interfaces support assignment, review, and completion within process flows.
Cons
  • –Authoring and administration require training in IBM tooling and deployment practices.
  • –Self-managed installations add infrastructure and upgrade work for platform teams.
  • –The enterprise workflow stack can be excessive for small teams handling simple approvals.
Use scenarios
  • banking operations teams

    Account servicing casework

    Consistent case handling

  • HR shared services

    Employee policy exceptions

    Traceable request decisions

Show 1 more scenario
  • insurance claims teams

    Complex claims review

    Coordinated claim resolution

    Adjusters can coordinate evidence collection, approvals, and follow-up tasks when a claim needs manual review.

Best for: Fits when large enterprises need governed workflows spanning structured processes and variable case work.

#10

Creatio

SMB

Creatio combines no-code workflow automation with customer relationship management applications.

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

A shared no-code workspace configures CRM records, user screens, and process logic.

Creatio suits CRM-led teams that need to adapt customer applications and business processes in the same low-code environment. Its visual process designer links user tasks, timers, signals, and subprocesses to configured CRM records.

Pros
  • +Visual process designer supports user tasks, timers, signals, and subprocesses.
  • +CRM records, screens, and process logic share one configurable environment.
  • +Integration options connect workflows with external business systems.
Cons
  • –Process automation is most natural inside Creatio's CRM and application environment.
  • –Complex configurations require administrators who understand data structures and access controls.
  • –Teams seeking process discovery need a separate process mining tool.
Use scenarios
  • Sales operations teams

    Lead assignment and qualification

    Consistent lead handling

  • Customer service managers

    Case escalation workflows

    Faster case escalation

Show 1 more scenario
  • Business application teams

    Internal request approvals

    Fewer manual handoffs

    Administrators can create request screens and approval steps around shared Creatio records.

Best for: Fits when CRM teams need to change customer workflows and applications together.

Conclusion

After evaluating 10 business process automation software, Moxo 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
Moxo

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 Business Process Automation Software

What separates options is how far their automation control goes past a simple flow—especially on integration depth, audit log visibility, and how fast you can change process logic without breaking runs. We recommend judging each tool by its API surface, audit log detail, and configuration workflow.

Integration depth via native connectors

Why it matters

Integration depth via native connectors matters because real automation depends on how reliably the tool connects to the systems that already hold customers, orders, and operations data. Shallow connector coverage usually forces manual workarounds that break end-to-end throughput.

How to check

In a demo, ask the vendor to connect three real sources your team uses and show end-to-end data mapping into one automation. Verify what happens when a field is missing or a target rejects the write, and whether the run stays consistent.

Automation configuration and version control

Why it matters

Automation configuration and version control matters because process logic changes happen often, and you need predictable updates to running and future workflows. Without clear version behavior, teams lose trust in outcomes.

How to check

Ask to edit a live workflow and show the option to create a new version for future runs. Then run a small test that compares old vs new behavior, including how the tool labels which version handled which run.

Automation API surface for programmatic control

Why it matters

Automation API surface matters when you want other apps to start processes, query status, or adjust parameters without screen-driven steps. A documented surface also shortens time to automate reporting and orchestration around the tool.

How to check

Request an API walkthrough and show endpoints for starting a run, checking status, and retrieving run details. Try a demo call (or sample script) that passes inputs and then confirms the same inputs show up in the run view.

Audit log and run trace visibility

Why it matters

Audit log and run trace visibility matters because process automation often fails in specific steps, and teams need evidence for debugging and accountability. If logs are vague, you’ll spend time reconstructing what happened manually.

How to check

Trigger a run that intentionally fails one step and inspect the audit view. Confirm the log includes step-level timestamps, actor identity when a human intervenes, and the inputs that were used for that run.

Admin controls and RBAC for workflow steps

Why it matters

Admin controls and RBAC for workflow steps matter when multiple teams design and operate processes, but not everyone should change logic or approve exceptions. Clear permissions reduce accidental changes and improve operational safety.

How to check

During the demo, ask to create at least three roles (designer, operator, approver) and set permissions around editing, running, and approving. Then verify the UI and API behavior for each role when they attempt to perform restricted actions.

Exception handling for human and system faults

Why it matters

Exception handling matters because automation breaks at boundaries—bad data, outages, and rule conflicts—and the tool should guide what happens next. Good exception flows reduce rework and keep outcomes consistent.

How to check

Ask for a scenario with an expected exception (missing required field) and an unexpected one (downstream system unavailable). Confirm the tool supports a clear recovery path, retains run context, and lets you route to an approval or retry step.

Red flags

  • Audit logs hide step details or inputs, making failures hard to prove.
  • Workflow edits affect prior runs unpredictably or only by manual cleanup.
  • RBAC cannot separately control design, operation, and approvals.

Fit by situation

  • If you rely on multiple business systems for every run, prioritize integration depth via native connectors.
  • If you regularly revise process logic and need predictable outcomes, prioritize automation configuration and version control.
  • If other apps must start and monitor workflows without manual screens, prioritize automation API surface for programmatic control.

Frequently Asked Questions About Business Process Automation Software

How do business process automation tools coordinate work between people and AI agents?
Moxo combines AI agents and people in the same process, with named owners for decisions and an audit trail of actions. Workato Agent Studio connects agents to enterprise systems through defined actions and recipes.
Which tools support integrations through APIs and custom connections?
Workato combines app integrations with an API Platform, while Zapier supports webhooks and API Request steps alongside its app catalog. Moxo connects to business systems through integrations, a REST API, and MCP.
When should a team migrate a legacy process to a workflow orchestration platform?
Migration makes sense when a legacy process needs coordinated service calls, long-running state, or human approvals that are difficult to manage across separate tools. Camunda executes BPMN models through Zeebe, while IBM Business Automation Workflow combines structured process work with variable case work.
What tradeoffs arise when teams use app-based automations for regulated or complex processes?
Zapier supports multi-step workflows with conditional paths, but its review data identifies stronger process modeling and governance as a consideration for complex regulated work. Monday.com supports conditional board workflows but does not provide native BPMN modeling or process mining.
How can teams keep decisions accountable when software automates document-heavy work?
Moxo assigns a person or team ownership of each decision and records actions on an audit trail, while agents handle tasks such as document review and preparation. IBM Business Automation Workflow routes assignments to staff through task interfaces for processes and cases that require human work.
Which business process automation tools can connect cloud workflows to desktop applications?
Microsoft Power Automate combines cloud flows with attended or unattended Windows desktop flows, which helps connect processes to applications without suitable connectors. Zapier instead focuses on connecting business apps through its catalog, webhooks, and API Request steps.
How do process modeling needs distinguish Camunda from low-code workflow builders?
Camunda executes BPMN 2.0 models as long-running process instances and provides monitoring through Operate. Creatio focuses on configuring CRM records, screens, and process logic together, while Pipefy organizes intake and recurring work into forms, phases, and cards.
What admin and security controls should teams assess before automating sensitive work?
Power Automate provides environment and data policies through Power Platform administration, while Moxo records process actions and assigns decision ownership. Teams with SSO or role-based access requirements should check that each product's available controls cover their identity, workflow-step, and audit needs.
What should teams map before building their first automated process?
Teams should define intake fields, decision points, exception routes, system connections, and the people responsible for approvals. Pipefy structures intake and recurring work with forms and phase-based queues, while Moxo supports process descriptions in plain language or a no-code builder.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.