GITNUXSOFTWARE ADVICE
Healthcare MedicineTop 9 Best Lis System Software of 2026
Top 10 Lis System Software tools ranked for lab workflow, interfaces, and reporting. Includes Meditech LIS, Epic Beaker, Orion Health LIS.
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.
Meditech LIS
Specimen and result workflow routing driven by configuration rules across order lifecycle states.
Built for fits when labs need controlled automation and governed integration for orders and results..
Epic Beaker
Editor pickSchema-driven entity configuration tied to workflow automation and API payload validation.
Built for fits when lab workflows need governed integrations and schema-stable result ingestion at scale..
Orion Health LIS
Editor pickSchema-governed result and order integration with API-driven workflow automation and audit traceability.
Built for fits when mid-size to enterprise labs need controlled integrations and audit-governed workflow automation..
Related reading
Comparison Table
This comparison table maps LIS System Software tools against integration depth, with emphasis on API surface, automation paths, and how each data model defines lab entities like orders, specimens, and results. It also highlights automation and extensibility mechanisms, plus admin and governance controls such as RBAC, configuration scoping, provisioning workflows, and audit log coverage. Readers can use the table to weigh throughput and schema constraints across vendor implementations rather than relying on feature lists.
Meditech LIS
enterprise LISEnterprise laboratory information system capabilities for configuring laboratory workflows, orders, results, and interfaces across hospital environments.
Specimen and result workflow routing driven by configuration rules across order lifecycle states.
Meditech LIS processes inbound orders into an internal schema that links order records, specimen tracking, and downstream result workflows. Results pass through configuration-driven routing for verification, sign-off, and reporting, which supports consistent throughput across high volume batches. Integration is built around defined interface points for orders and results, plus an API for extending exchange patterns where internal systems need structured access. Admin governance relies on role based access control to constrain actions by function, and it records activity for traceability.
A tradeoff appears with complex custom workflows because rule configuration and interface mapping require disciplined change control. The most common fit is a hospital or reference lab that already has HL7 oriented upstream systems and needs tight control over how specimen lifecycle states and result messages are generated. Another usage situation is multi site deployments that require consistent RBAC policies, audit trails, and interface governance across production environments. Extensibility works best when integration requirements map cleanly onto the existing schema rather than requiring heavy remapping.
- +Configurable LIS workflow ties orders, specimens, results, and reporting in one data model
- +Integration points include interface mapping plus an API for structured exchange
- +Rule driven automation reduces manual status updates and standardizes result handling
- +RBAC plus audit log supports traceability for verification and reporting actions
- –Complex custom workflow changes require careful configuration management and testing
- –Interface and schema alignment can slow projects when upstream data formats differ
Best for: Fits when labs need controlled automation and governed integration for orders and results.
Epic Beaker
enterprise LISLaboratory information system features for test ordering, specimen workflow, results display, and bidirectional integration with clinical applications.
Schema-driven entity configuration tied to workflow automation and API payload validation.
Epic Beaker is a Lis system software option when teams need more than device orchestration and instead require a defined data model spanning instruments, specimen records, and derived results. The configuration layer supports schema-driven entities so integrations can use stable fields and validation rules across workflow steps. Its API and automation hooks make it practical to connect scheduling, result ingestion, and downstream reporting without manual handoffs.
A tradeoff appears in setup effort because the schema and governance model need intentional design before high throughput runs. Beaker fits situations where multiple systems push and pull results and where consistent field mapping matters for downstream analytics and compliance reporting. It also fits teams that need controlled extensibility through API-based integration points and governed role access rather than ad hoc scripts.
For admin and governance, RBAC restricts who can create integrations, modify configurations, or trigger workflow actions. The audit log captures changes and activity, which supports operational review when troubleshooting data lineage or configuration drift across environments.
- +Schema-driven data model reduces field mapping drift across integrations
- +API supports provisioning, automation triggers, and workflow coordination
- +RBAC and audit logs provide governance across projects and environments
- +Event-driven workflow steps support instrument and results ingestion
- –Requires upfront schema design to avoid later rework
- –Throughput tuning depends on workflow configuration choices
- –Complex integrations demand disciplined versioning of API payloads
Best for: Fits when lab workflows need governed integrations and schema-stable result ingestion at scale.
Orion Health LIS
enterprise LISLaboratory workflow and results management capabilities designed to integrate with enterprise clinical data flows and external systems.
Schema-governed result and order integration with API-driven workflow automation and audit traceability.
Orion Health LIS is designed for integration breadth across LIS, order management, and downstream result consumption where schema mapping must stay consistent over time. The automation and API surface is oriented around provisioning of lab objects and message-driven updates, including how results propagate to other systems that rely on stable identifiers. The data model supports lab-specific structure for orders, specimen and result life cycles, and reference data governance so integrations can enforce predictable state transitions.
A key tradeoff is that deeper integration and schema governance require upfront configuration discipline and strong interface ownership across teams. This makes Orion Health LIS a better fit for organizations that already run an integration layer or have clear responsibility for API contracts, message schemas, and test harnesses in a sandbox. A typical usage situation involves connecting outbound result feeds and inbound order or accession events while preserving audit traceability across roles.
- +Integration oriented around governed data exchange with external clinical systems
- +Configurable data model for orders, specimens, and results life-cycle control
- +Automation and API support for provisioning workflows and message-driven updates
- +RBAC and audit log support for multi-role governance in lab operations
- –Upfront schema mapping effort is required to keep integrations stable
- –Workflow changes can depend on configuration and interface contract alignment
- –Extensibility favors structured schema extensions over rapid UI-only tweaks
Best for: Fits when mid-size to enterprise labs need controlled integrations and audit-governed workflow automation.
SoftCare LIS
hospital LISLaboratory information system software for specimen management, test ordering, and results reporting with configurable laboratory workflows.
Schema-based workflow provisioning that keeps orders, results, and worklists consistent across integrations.
SoftCare LIS focuses on integration depth through configurable interfaces and an explicit data model for lab workflows. The system supports automation by wiring worklists, orders, results, and instrument connectivity into a controlled schema that can be extended through configuration and integration points.
Admin governance centers on role-based access, controlled provisioning of organizations and users, and audit-oriented traceability across key events. The API and automation surface emphasizes extensibility for external systems that need structured schemas, event timing, and consistent identifiers.
- +Configurable data model for orders, specimens, and results mapping
- +Integration points for instrument and external system data exchange
- +Automation via workflow rules tied to structured lab entities
- +Role-based access controls support controlled permissions boundaries
- +Audit-oriented traceability across workflow actions and data changes
- –Schema customization can require careful governance to avoid drift
- –Complex integrations may need dedicated integration work and testing
- –Automation configuration depth may demand strong change management
- –API coverage depends on the configured workflow scope and entities
Best for: Fits when mid-size labs need schema-driven integration and governed automation.
StarLIMS
LIMS-LISLaboratory information management software for managing samples, tests, workflows, and reporting with configurable data structures.
Schema-driven workflow configuration for samples, tests, and results with audit-tracked transitions.
StarLIMS provisions laboratory workflows and manages samples through a configurable data model aligned to lab entities. Its integration depth shows through an API and automation hooks that connect instrument data flows, external systems, and operational triggers.
The platform supports schema-level configuration for forms and fields, and it can model processes like receipt, testing, analysis, and results release. Governance depends on role-based access controls and audit trails that track record changes and execution outcomes.
- +Configurable schema maps lab entities to forms, fields, and test results
- +API and automation hooks support instrument and system integrations
- +Workflow configuration enables process control across sample lifecycle stages
- +Audit trails record data edits and workflow status transitions
- +RBAC gates access to records, actions, and administration features
- –Deep configuration can require strong data-model discipline
- –API coverage can feel uneven across all workflow and administrative actions
- –Complex automation may increase operational overhead for maintainers
- –Reporting depth depends on how well schemas are standardized upfront
Best for: Fits when labs need controlled workflow automation and an API-driven integration surface.
LabWare
LIMS-LISLaboratory information management system software for sample tracking, workflows, analytics, and results management across lab operations.
LabWare instrument and workflow integration that persists traceable results into governed LIS records.
LabWare targets regulated lab operations with an integration-focused Lis system software that maps lab processes to a controlled data model. Its automation and API surface support external instrument workflows, custom scheduling, and event-driven actions across assays and results.
Admin and governance features cover structured configuration, role-based access control, and auditability for changes to orders, runs, and results. Extensibility centers on consistent schemas and integration patterns that maintain traceability from sample intake through reporting.
- +Integration patterns align lab events to structured sample and test records
- +Automation hooks support instrument and workflow-driven updates to results
- +API surface enables external scheduling, orchestration, and data exchange
- +RBAC and audit trails support controlled changes to results and configurations
- –Schema design decisions require careful upfront mapping to lab workflows
- –High customization can increase maintenance across lab-specific extensions
- –Throughput depends on correct indexing and run configuration choices
- –Admin workflows can be complex for teams without governance ownership
Best for: Fits when labs need controlled data lineage, automation via API, and governance over results.
ClinCapture
clinical dataClinical data management software that supports electronic data capture, audit trails, and validation workflows for study and lab-related data collection.
Configurable data model tied to sample lifecycle events for schema-driven automation.
ClinCapture focuses on integration depth for LIS workflows through a configurable data model and automation hooks around sample lifecycle events. The system supports schema-driven test definitions and result publication flows that reduce manual mapping between instruments, orders, and reports.
A documented API surface enables provisioning, status updates, and workflow actions, which helps teams build reliable integrations and higher throughput. Admin controls center on RBAC, audit logging, and governance over configuration changes across environments.
- +Event-driven automation around sample status, orders, and result publication
- +Schema-driven test definitions reduce instrument and LIS mapping drift
- +API surface supports provisioning, status updates, and workflow actions
- +RBAC and audit logs support governed configuration changes
- –Complex configuration requires careful schema planning and validation
- –Automation rules can be harder to troubleshoot without test harnesses
- –Integration projects may need custom adapters per instrument model
Best for: Fits when lab teams need governed LIS integrations with API-driven automation and a controlled data model.
LabVantage
LISLaboratory information management system software for managing sample tracking, testing workflows, results, and configurable reporting across lab operations.
Workflow configuration tied to specimen and test state transitions for accession to result release.
LabVantage provides a laboratory informatics LIS suite built around configurable screens, workflows, and a schema-driven data model for specimens, tests, and results. Integration depth centers on provisioning-friendly data entities and an automation surface that supports electronic ordering, result capture, and system-to-system exchange.
The automation story relies on configurable workflow states plus extensibility points that support lab-specific rules. Administrative control focuses on access control, audit visibility, and configuration governance for assay and instrument processes.
- +Schema-driven specimen, test, and result data model supports consistent mapping
- +Configurable workflow states handle accession, ordering, and result release
- +Integration via defined entities supports electronic data exchange patterns
- +Extensibility points allow lab-specific rules without changing core entities
- +RBAC style access control limits who can edit results and definitions
- +Audit log coverage supports traceability across edits and releases
- –Automation surface details are implementation-specific and require integration design work
- –Workflow configuration can become complex with many nested states
- –API and extension capability coverage varies by module and integration target
- –High-volume throughput tuning depends on deployment configuration choices
- –Admin governance requires careful change control for assay definitions
Best for: Fits when mid-size labs need configurable LIS workflows with controlled integrations and auditability.
WinLIMS
LISLaboratory information system software focused on specimen tracking, test catalog management, and results reporting.
Role-based access control tied to workflow states for editing and releasing laboratory results.
WinLIMS records laboratory work items, sample tracking, and results through configurable forms and workflows. Its data model centers on analytes, specimens, methods, and test outcomes, with schema-driven configuration for assay-specific fields.
Integration depth relies on administrative configuration plus data exchange points that support automation and external system handoff. Governance depends on role-based access controls and operational logging to control who can provision, edit, and release laboratory data.
- +Configurable sample and test forms using a schema-like data model
- +Workflow controls support status transitions from receipt to result release
- +Role-based access gates actions across users and lab groups
- +Audit logging tracks edits and approvals for released results
- –Automation surface lacks a documented, developer-first API workflow
- –Extensibility depends more on configuration than programmable integrations
- –Throughput tuning options are not clearly exposed for high-volume batching
- –Cross-lab governance features like granular per-field policies are limited
Best for: Fits when labs need controlled result release with configuration-driven workflows and basic integration.
How to Choose the Right Lis System Software
This buyer's guide covers Meditech LIS, Epic Beaker, Orion Health LIS, SoftCare LIS, StarLIMS, LabWare, ClinCapture, LabVantage, and WinLIMS. It focuses on integration depth, the LIS data model, automation and API surface, and admin and governance controls, using concrete capabilities like schema-driven workflows and audit logging.
It also maps common configuration risks to specific tools, including interface mapping friction in Meditech LIS and API payload versioning discipline in Epic Beaker. The guide concludes with a selection methodology and a set of evaluation questions that tie directly to the stated best-fit use cases.
Laboratory order-to-result systems built on governed data models and workflow automation
Lis System Software records specimen and test workflows end-to-end from orders through accession, results capture, and release. It solves operational problems like status drift across order lifecycle states, inconsistent field mappings between instruments and systems, and missing traceability for result edits and workflow transitions.
Tools such as Meditech LIS and Orion Health LIS use configurable workflow engines tied to a controlled data model so integrations exchange structured orders, specimens, and results with predictable identifiers. Other tools like Epic Beaker emphasize schema-driven entity configuration that supports workflow automation and API payload validation for steadier result ingestion at scale.
Evaluation criteria that map integrations, automation, and governance to the LIS data model
Lis System Software succeeds when the same data model powers UI workflows, instrument ingestion, and integration messaging. Integration depth also matters because interface mapping and API payload contracts determine whether result handling stays consistent across sites.
Automation and admin governance then decide whether teams can change workflows safely, because rule-driven status changes and audit log coverage determine operational traceability. The most decision-useful checks are API and automation surface documentation, schema discipline for entity configuration, and governance controls like RBAC and audit logging.
Schema-driven entity and workflow configuration
Epic Beaker ties entity configuration to workflow automation and API payload validation so integrations can avoid field mapping drift. Orion Health LIS and StarLIMS also use schema-governed order and result integration patterns that keep workflow transitions consistent with defined entities and fields.
Integration depth built on governed exchange contracts
Meditech LIS centers integration on configurable interfaces and a controlled messaging model for exchanging orders, specimens, and results through a structured workflow engine. LabWare and Orion Health LIS also persist traceable results into governed LIS records by aligning lab events to structured sample and test records.
Automation hooks tied to lifecycle events and workflow states
Meditech LIS uses rule-driven status changes and specimen and result workflow routing across order lifecycle states. ClinCapture and LabVantage use event-driven or state-transition automation around sample status, accession, ordering, and result release to reduce manual mapping and handling.
Developer-facing API and workflow automation surface
Epic Beaker supports a workflow automation surface that includes provisioning and event triggers coordinated with API payload validation. SoftCare LIS, Orion Health LIS, and StarLIMS also emphasize an API and automation hooks designed for structured schemas, workflow provisioning, and message-driven updates.
Admin controls with RBAC and audit logging for traceability
Meditech LIS, Epic Beaker, Orion Health LIS, and SoftCare LIS include RBAC plus audit logging so verification and reporting actions can be traced to specific users and workflow actions. StarLIMS and LabWare extend this with audit trails that record record edits and workflow status transitions for sample and result lifecycle control.
Extensibility model that favors structured schema extensions over UI-only tweaks
Orion Health LIS and SoftCare LIS focus extensibility on schema alignment and workflow automation rather than rapid UI-only customization. WinLIMS and LabVantage rely more on configuration-driven workflows and nested state configuration, so integration extensibility depends heavily on the configured entities and modules.
Choose by matching the integration contract, automation surface, and governance model to lab operations
Selection works best when the evaluation starts with integration contracts and ends with governance controls that prevent uncontrolled workflow drift. The goal is to ensure instrument data ingestion, external system exchanges, and internal results release all use the same schema and workflow state logic. The decision framework below maps directly to how Meditech LIS, Epic Beaker, Orion Health LIS, SoftCare LIS, and WinLIMS behave in real configuration and integration work.
Validate the LIS data model approach for orders, specimens, and results
For governed lifecycle control, check whether the tool anchors workflow routing to a controlled data model, as Meditech LIS does across specimen and result routing states. For schema stability and payload validation, evaluate Epic Beaker and Orion Health LIS because both base workflow automation on schema-driven entity configuration that can enforce contract alignment during API exchanges.
Confirm automation and event timing across workflow states
Map the exact lifecycle points where automation must run, including accession, instrument ingestion, result handling, and release, then compare how Meditech LIS and LabVantage implement state-transition driven workflows. If sample lifecycle events drive the integration, ClinCapture’s event-driven automation around status and result publication offers a direct match to that requirement.
Audit the API and message surface for provisioning and workflow coordination
For integration-heavy environments, prioritize Epic Beaker, Orion Health LIS, StarLIMS, and SoftCare LIS because their API and automation surfaces emphasize provisioning, workflow coordination, and message-driven updates. Also test whether API payload contracts can be versioned and maintained through disciplined schema design to reduce rework, which Epic Beaker explicitly requires when payload contracts change.
Require governance controls that cover edits, approvals, and workflow transitions
For regulated traceability needs, verify that RBAC and audit logging cover both data edits and workflow status transitions, as Meditech LIS, Epic Beaker, Orion Health LIS, and StarLIMS provide. If governance must focus on result release controls, WinLIMS is structured around role-based access tied to workflow states for editing and releasing results.
Plan change management for schema and workflow configuration complexity
If workflow changes are expected frequently, Meditech LIS offers rule-driven automation but complex custom workflow changes require careful configuration testing. Epic Beaker and Orion Health LIS also require upfront schema design discipline, while LabVantage and ClinCapture can become harder to troubleshoot without structured validation and test harnesses for automation rules.
Which teams fit each LIS System Software profile
Lis System Software fits organizations where laboratory workflows need controlled automation, structured integration, and auditable result handling. The best-fit choices depend on whether the primary workload is schema-stable API ingestion at scale, multi-role governance across environments, or instrument and workflow orchestration with traceable lineage. The segments below map directly to the tools’ best_for statements and their stated standout mechanisms.
Hospital labs that need governed order-to-result routing and workflow rule automation
Meditech LIS fits when specimen and result workflow routing must be driven by configuration rules across order lifecycle states, and when rule-driven status changes reduce manual updates. Epic Beaker and Orion Health LIS also fit governance-heavy hospitals, but Meditech LIS specifically emphasizes workflow routing control tied to its LIS workflow engine.
Labs prioritizing schema-stable, payload-valid API ingestion at scale
Epic Beaker fits teams that need schema-driven entity configuration tied to workflow automation and API payload validation for steadier results ingestion. Orion Health LIS targets the same schema-governed integration direction for multi-role audit visibility across enterprise clinical data flows.
Mid-size labs that need schema-driven integration plus governed automation across organizations and users
SoftCare LIS fits mid-size labs because it focuses on configurable interfaces and a controlled data model with role-based access and audit-oriented traceability for workflow actions. Orion Health LIS and ClinCapture also fit mid-size to enterprise contexts when API-driven workflow automation and controlled data models are required for integration.
Organizations with strong requirements for audit-tracked transitions in sample, test, and results workflows
StarLIMS fits labs needing schema-driven workflow configuration for samples, tests, and results with audit-tracked transitions. LabWare fits teams that need instrument and workflow integration that persists traceable results into governed LIS records for controlled data lineage.
Labs that emphasize result release governance through workflow-state permissions and configuration
WinLIMS fits when controlled result release depends on role-based access tied to workflow states for editing and releasing results. LabVantage also fits mid-size labs for accession through result release using workflow state transitions, with RBAC style access control and audit visibility for traceability.
Configuration and integration pitfalls that cause drift, rework, and governance gaps
Common failures come from treating LIS workflow configuration and integration contracts as independent tasks. Schema decisions and payload validation expectations can force rework when interface and upstream data formats do not align. Troubleshooting automation also becomes difficult when rule logic has no structured validation path or when governance coverage does not match the actual edit and release lifecycle.
Underestimating schema alignment work for integration messaging
Meditech LIS can slow projects when interface and schema alignment depends on upstream data formats that differ, so mapping work needs to start early. Epic Beaker and Orion Health LIS both require upfront schema design discipline so later API contract changes do not force broad rework.
Assuming automation rules will be easy to change without test discipline
Meditech LIS supports rule-driven status changes but complex custom workflow changes require careful configuration management and testing. ClinCapture can require dedicated troubleshooting support for automation rules unless validation and test harnesses are built for complex configuration.
Selecting a tool with governance that does not cover edits and workflow transitions end-to-end
WinLIMS provides role-based access tied to workflow states for editing and releasing results, but teams that need broader audit traceability across data changes and configuration actions may need Meditech LIS, Epic Beaker, or Orion Health LIS with RBAC plus audit logging coverage. StarLIMS and LabWare also emphasize audit trails for record edits and workflow status transitions, which should be verified against actual release and approval processes.
Treating API coverage as uniform across modules and actions
StarLIMS notes that API coverage can feel uneven across all workflow and administrative actions, which can cause gaps during automation expansion. LabVantage also states that API and extension capability coverage varies by module and integration target, so module-level capability checks should happen before locking the integration plan.
Overbuilding workflow state complexity without governance ownership
LabVantage can become complex with many nested workflow states, and admin governance requires careful change control for assay definitions. LabWare flags that high customization can increase maintenance across lab-specific extensions, which can overload teams without clear governance ownership.
How We Selected and Ranked These Tools
We evaluated Meditech LIS, Epic Beaker, Orion Health LIS, SoftCare LIS, StarLIMS, LabWare, ClinCapture, LabVantage, and WinLIMS using the provided feature scores, ease-of-use scores, and value scores, then converted those into an overall rank using a weighted average where features carries the most weight at 40%. Ease of use and value each account for 30% of the overall score to reflect operational adoption and ongoing fit with lab execution needs.
The ranking emphasizes integration depth, data model control, automation and API surface, and admin governance controls because those mechanisms determine whether orders, specimens, and results stay consistent across instruments and external systems. Meditech LIS separated from lower-ranked tools because its specimen and result workflow routing driven by configuration rules across order lifecycle states scored highest on features at 9.5 And combined rule-driven status automation with RBAC plus audit logging for traceability, lifting it on the integration and governance factors.
Frequently Asked Questions About Lis System Software
How do LIS systems expose integrations for orders, specimens, and results?
Which LIS tools are strongest for schema-driven data models and payload validation?
What mechanisms support RBAC and audit logging for configuration changes?
How do LIS systems handle authentication and single sign-on in enterprise deployments?
What data migration approach is most compatible with a schema-aligned LIS?
How does admin control differ when provisioning organizations, users, and workflows across sites?
Which LIS tools provide the most direct automation hooks for workflow state transitions?
How do these LIS systems integrate with instruments and external systems without breaking traceability?
What common integration problem occurs when external systems send inconsistent identifiers or schemas?
Which LIS tool best fits teams that need extensibility beyond UI configuration?
Conclusion
After evaluating 9 healthcare medicine, Meditech LIS 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
Healthcare Medicine alternatives
See side-by-side comparisons of healthcare medicine tools and pick the right one for your stack.
Compare healthcare medicine 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.