GITNUXSOFTWARE ADVICE
Healthcare MedicineTop 10 Best Med Manager Software of 2026
Top 10 ranking of Med Manager Software with comparison notes for medication management buyers, including iMedication and Omnicell.
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.
iMedication
Event-aware administration capture that reconciles administered records against scheduled dosing data.
Built for fits when regulated teams need controlled medication automation with documented API integration and audit visibility..
Omnicell
Editor pickEvent-level audit logging that ties dispensing and administration actions to authenticated users.
Built for fits when multi-location teams need auditable automation with controlled access and strong integrations..
Welligent Medication Management
Editor pickMedication workflow state engine tied to a structured medication data model and automated routing rules.
Built for fits when organizations need medication workflow automation with documented API integration and strong governance..
Related reading
Comparison Table
The comparison table evaluates Med Manager Software tools across integration depth, data model alignment, and automation and API surface for med workflows and clinical documentation. It also contrasts admin and governance controls, including RBAC, provisioning, audit log coverage, and extensibility through configuration and schema support. Readers can map tradeoffs between platform throughput, integration effort, and governance requirements when selecting a system such as iMedication, Omnicell, Welligent Medication Management, Net Health, and WellSky.
iMedication
care workflowMedication management software for care teams with medication lists, adherence workflows, and documentation for long-term care and assisted living environments.
Event-aware administration capture that reconciles administered records against scheduled dosing data.
iMedication is used to coordinate medication management tasks across the medication lifecycle, including order intake, schedule setup, administration capture, and review workflows. The data model links residents to medication regimens and dosing schedules, then records administered events so downstream reports can reconcile with the source schedule. Automation is expressed as configuration rather than ad-hoc process steps, so rule execution can maintain consistent handling of refill triggers, status changes, and exception paths.
Integration depth targets the med tech stack through API endpoints and event-oriented flows for provisioning data and synchronizing updates. A key tradeoff is that deeper integrations require mapping internal schemas to iMedication’s schema conventions for residents, medications, and administration events. This fits best in organizations that need governance controls such as RBAC scoping and audit logs, plus predictable automation throughput during high-volume medication rounds.
- +API-driven integration supports medication and administration event synchronization
- +Consistent data model links residents, regimens, schedules, and administered events
- +Configuration-based automation reduces ad-hoc workflow drift
- +RBAC and audit logs improve medication record traceability
- +Schema-aligned provisioning helps keep external systems in sync
- –Schema mapping work is required for nonstandard medication models
- –Automation complexity increases when exceptions need many conditional branches
- –Advanced integrations need careful data contract management for throughput
Best for: Fits when regulated teams need controlled medication automation with documented API integration and audit visibility.
More related reading
Omnicell
dispensingAutomated medication dispensing and inventory control software that manages medication supply, utilization, and reporting for healthcare facilities.
Event-level audit logging that ties dispensing and administration actions to authenticated users.
Omnicell fits care organizations that need med manager workflows anchored to a consistent schema for orders, dispenses, and administration events. The system supports automation at the workflow layer, and it exposes an API surface that can connect formulary data, inventory state, and event history into downstream integrations. Audit log trails align operational actions to user and device context, which helps with incident review and regulatory reporting.
A key tradeoff is configuration complexity, because deeper automation depends on correctly mapping items, locations, roles, and event states. Omnicell is a strong fit when multiple connected endpoints must maintain event integrity, such as pharmacy devices and bedside documentation systems feeding one consolidated medication record flow.
- +Audit logs connect user actions to dispensing and administration events
- +Integration mapping helps keep medication, inventory, and MAR states consistent
- +RBAC supports role-based access across pharmacy, nursing, and admin users
- +API and data model support automated synchronization of medication events
- –Deep automation requires careful schema and workflow configuration
- –Multi-site deployments can demand more governance setup for roles and mappings
Best for: Fits when multi-location teams need auditable automation with controlled access and strong integrations.
Welligent Medication Management
clinical recordsMedication management software for care plans that supports medication orders, administration records, and reconciliation workflows.
Medication workflow state engine tied to a structured medication data model and automated routing rules.
Welligent Medication Management centers on a medication data model that supports structured fields for orders, administrations, and reconciliation steps. The workflow engine can automate state transitions and routing rules, which helps reduce manual coordination between clinicians and med management staff. Integration depth is strengthened by an API surface and extensibility hooks designed for provisioning and data synchronization across connected systems.
A common tradeoff is that deeper configuration requires careful schema governance to avoid brittle integrations when workflows evolve. Teams with multi-site operations benefit most when onboarding and role-based permissions must stay consistent across locations. A typical usage situation involves integrating EHR or workflow tools to synchronize medication tasks while enforcing RBAC controls and reviewing audit logs for compliance.
- +Medication-first schema with consistent order, admin, and reconciliation fields
- +API surface supports structured integrations and data synchronization
- +Workflow automation reduces manual handoffs between med roles
- +RBAC and audit log support governance and traceability
- –Workflow and schema changes require disciplined configuration management
- –Automation rules can be complex for organizations with minimal admin tooling
- –Integration onboarding may demand coordinated mapping across systems
Best for: Fits when organizations need medication workflow automation with documented API integration and strong governance.
Net Health
post-acuteCare management and clinical documentation tools that include medication-related workflows for rehabilitation and post-acute settings.
Order-to-administration linkage with configurable discrepancy workflows and MAR state transitions.
Net Health focuses on medication management workflows built around a configurable data model for MAR, orders, and administration events. The integration surface centers on EHR connectivity, scheduling signals, and inbound orders so med administration throughput can stay aligned with clinical documentation.
Automation is driven through rules and workflow configuration that reduce manual reconciliation between orders and administered doses. Governance relies on role-based access control and auditable change history across configuration and order lifecycle events.
- +EHR integration keeps medication orders and MAR events in sync
- +Configurable data model supports order, administration, and discrepancy states
- +Workflow rules reduce manual reconciliation between orders and administration
- +RBAC plus audit trails support governance of clinical and admin actions
- –Complex workflow configuration can increase implementation and change-management effort
- –Automation coverage depends on available event mappings from connected systems
- –API extensibility requires careful schema alignment for custom integrations
- –Admin reporting granularity may require additional data extraction paths
Best for: Fits when med workflows must integrate tightly with EHR order flow and maintain audit-grade governance.
WellSky
care platformHealthcare software with care documentation workflows that include medication-related data capture for behavioral health and home and community services.
RBAC plus medication-event audit logs tie medication state changes to actors and administration events.
WellSky supports medication management workflows for healthcare organizations by integrating medication orders, eMAR views, and care-plan context across connected systems. Its data model centers on medication definitions, patient medication records, and administration events, which makes state changes auditable for governance.
Automation is driven through configurable workflows and a documented API surface that supports provisioning, data exchange, and event-driven updates. Admin controls emphasize RBAC and traceability through audit logs tied to changes in medication state.
- +Medication administration tracking connects order intent to documented administration events
- +API supports integration patterns for medication data exchange and workflow triggers
- +Audit logs provide traceability for medication-related configuration and state updates
- +RBAC restricts access to medication workflows and patient medication records
- +Extensibility via integrations supports connecting EHR, pharmacy, and care operations
- –Medication data schema mapping can require significant integration work
- –Complex workflow configurations can increase time-to-go-live for new sites
- –API coverage across every medication edge case may require custom handling
- –High governance demands can add overhead for role setup and review cycles
- –Throughput and event ordering requirements need careful design in downstream systems
Best for: Fits when health systems need controlled medication workflows with deep integration to existing clinical systems.
SureScripts Medication History
medication historySurescripts provides medication history exchange used by prescribers and dispensers to populate and reconcile a patient medication list.
Medication History exchange integration that retrieves and delivers reconciled history through API-driven workflows.
SureScripts Medication History centralizes medication-history exchange across participating providers using SureScripts clinical data services. The distinct value is integration depth with prescription and medication-history workflows, tied to an explicit medication-history data model.
Configuration and governance controls focus on who can access history records, how data flows between organizations, and how auditability is maintained in exchange operations. Automation relies on API-driven connectivity and provisioning so systems can request, receive, and persist medication-history results at operational throughput.
- +High integration depth for medication-history exchange with prescribing and dispensing workflows
- +API surface supports automated retrieval and synchronization of medication-history records
- +Data model aligns medication-history content to exchange and reconciliation use cases
- +Governance supports controlled access patterns across participating organizations
- –Automation depends on correct provisioning and partner-specific exchange configuration
- –Schema and normalization work may be needed for local EHR medication-history representation
- –Debugging data mismatches can require deep knowledge of exchange payload mapping
- –RBAC controls may be limited to integration-level permissions rather than field-level policy
Best for: Fits when clinics need automated medication-history ingestion with strong governance and auditability requirements.
Doctor on Demand Medications (Hims & Hers ownership line)
telehealth RxMedication ordering and follow-up tooling tied to telehealth encounters that manages prescriptions and patient medication instructions.
Clinician-driven medication workflow orchestration tied to prescribing and refill follow-up events.
Doctor on Demand Medications focuses medication workflow administration around clinician-led prescribing and ongoing management, with integration depth driven by its supporting systems rather than a broad med-ops toolchain. The medication-specific data model centers on patient context, clinical state, prescriptions, and follow-up tasks, so automation can align to prescribing and refill lifecycles.
Automation and API surface are practical for operational integration, but the exposed schema boundaries and extensibility mechanisms are less transparent than tools that publish developer-first provisioning and RBAC controls. Admin and governance controls appear geared toward care operations, with auditability and access controls tied to user roles across the platform.
- +Medication lifecycle workflows align to prescribing and follow-up steps
- +Care-oriented data model links patient context to prescription outcomes
- +Integration supports operational handoffs between care steps and services
- +Role-based access controls cover clinical and administrative usage
- –API and automation schema details are less documented for custom workflows
- –Extensibility options for external med operations are limited
- –Governance coverage is narrower than enterprise RBAC and audit-first tools
- –Provisioning and environment configuration controls are harder to validate
Best for: Fits when medication administration needs care-aligned workflows with limited external automation.
Walgreens Prescription Management
pharmacy refillsPharmacy-facing prescription management system that supports refill scheduling, medication list viewing, and pharmacy pickup or delivery workflows.
Prescription workflow event mapping that ties patient, prescriber, and dispense steps to Walgreens fulfillment status
Walgreens Prescription Management centers on medication workflows tightly coupled to Walgreens pharmacy operations and benefit data. Integration depth tends to come from prescription-specific endpoints that map patient, prescriber, and medication fulfillment events into a pharmacy-oriented data model.
Automation and extensibility are constrained by the vendor's API and configuration surface, with limited visibility into raw schema control compared with platforms built for custom med-data models. Admin and governance features focus on operational access and tracking within the Walgreens ecosystem rather than broad RBAC and policy enforcement across external systems.
- +Prescription-focused integration reduces mapping gaps across patient and dispense events
- +Workflow states align closely to fulfillment steps used by Walgreens pharmacies
- +Operational event tracking supports auditability for pharmacy-run medication processes
- +Admin access follows Walgreens system roles tied to prescription operations
- –Limited published data model controls for custom med schema extensions
- –API surface appears narrow to Walgreens-centric medication and fulfillment workflows
- –RBAC granularity and policy configuration options are not clearly exposed
- –Automation throughput depends on external system coordination outside vendor boundaries
Best for: Fits when pharmacy-linked medication management needs tight Walgreens workflow alignment and minimal custom schema work.
CVS Pharmacy Prescription Management
pharmacy refillsRetail pharmacy prescription workflow that manages refills, prescription status, and medication information for customers.
Operational prescription status updates tied to dispensing workflow stages
CVS Pharmacy Prescription Management performs prescription fulfillment and medication management workflows through CVS’s pharmacy operations and account-linked access. The integration depth is mainly driven by patient and provider account interactions rather than a published, developer-facing API surface in common documentation.
Automation is oriented around prescription lifecycle steps, status updates, and service workflows, not custom rule execution or event webhooks. Governance is constrained to account-level roles and operational controls, with limited visibility into a configurable data model schema, provisioning flows, and audit-log export mechanisms.
- +Prescription lifecycle status reflects operational handling across fulfillment steps
- +Account-based access supports coordinated medication management workflows
- +Broad pharmacy network coverage improves throughput for dispensing operations
- –API and automation surface is not clearly documented for custom integrations
- –Data model details and schema extensibility are limited for external systems
- –RBAC granularity and audit log export controls are not clearly described
Best for: Fits when teams need managed prescription workflows tied to CVS operations, not custom integration automation.
RxRelief
Rx supportMedication access and prescription refill support platform that manages requests, refills coordination, and medication-related patient communication.
Configurable workflow triggers that update medication task status from medication events.
RxRelief targets medication management workflows that need tight integration between prescriptions, medication records, and patient-facing tasks. The data model centers on medication entities, administration or adherence status, and care instructions tied to patient records.
Automation relies on configurable workflows and triggers, with an API surface intended to support external system provisioning and operational events. Admin governance is oriented around user roles and auditability for medication-related changes rather than broad clinical documentation.
- +Workflow triggers connect medication events to patient task updates
- +API-oriented integration supports provisioning of medication data
- +Role-based access controls limit medication record changes
- +Audit trails track who modified medication and instructions
- –Automation granularity can feel constrained for complex multi-step protocols
- –External system schemas may require careful mapping to the RxRelief model
- –API coverage for edge-case medication events can be limited
- –Bulk changes and throughput controls are not clearly exposed for high volume
Best for: Fits when care teams need controlled medication workflow automation with external system integration.
How to Choose the Right Med Manager Software
This buyer's guide covers med manager software tools including iMedication, Omnicell, Welligent Medication Management, Net Health, WellSky, SureScripts Medication History, Doctor on Demand Medications, Walgreens Prescription Management, CVS Pharmacy Prescription Management, and RxRelief.
The guide focuses on integration depth, data model control, automation and API surface, and admin and governance controls that affect medication record accuracy and audit traceability.
Medication data orchestration that links orders, dispense, and MAR events to governed workflows
Med manager software coordinates medication orders, administration or dispensing events, and reconciliation states inside a controlled workflow so medication records remain consistent across updates.
Tools like iMedication tie residents, regimens, schedules, and administered events into an explicit data model while automating MAR changes and tasking with configurable rules. Tools like Omnicell represent medication, dispensing, and MAR events with an auditable data model that supports role-based access and audit logging for controlled substances.
Evaluation criteria for med workflow automation with governed data contracts
Integration depth determines whether medication orders, dispensing events, and administration capture stay aligned across systems like EHRs, pharmacies, and medication-history exchanges.
Data model control and schema-aligned provisioning reduce drift when external systems send different representations of the same medication. Automation and API surface decide whether workflows can be executed via documented interfaces at operational throughput instead of manual reconciliation.
Event-aware reconciliation between scheduled and administered doses
iMedication reconciles administered records against scheduled dosing data using event-aware administration capture, which reduces inconsistencies when administrations do not match the planned schedule. Net Health also uses order-to-administration linkage with configurable discrepancy workflows and MAR state transitions.
Medication-first or medication-specific data model with stable schema links
Welligent Medication Management uses a medication-specific data model that keeps order, administration, and reconciliation fields consistent so workflow state changes can route correctly. iMedication similarly links residents, regimens, schedules, and administered events to keep records consistent across MAR updates.
Event-level audit logging tied to authenticated actors
Omnicell provides event-level audit logging that ties dispensing and administration actions to authenticated users, which supports traceability for controlled processes. WellSky pairs RBAC with medication-event audit logs that tie medication state changes to actors and administration events.
RBAC that matches operational roles and supports governance at scale
iMedication includes role-based access control and audit log visibility for traceability across medication workflow changes. Omnicell supports RBAC across pharmacy, nursing, and admin users, and it adds governance setup needs that grow with multi-site deployments.
Documented API and automation surface for provisioning and event-driven integration
iMedication uses an API surface that supports data exchange and event-driven automation, and it uses schema-aligned provisioning to keep external systems synchronized. SureScripts Medication History offers API-driven connectivity that retrieves and delivers reconciled medication-history results through automated exchange workflows.
Workflow state engines and configurable routing rules for medication lifecycle
Welligent Medication Management provides a medication workflow state engine tied to a structured medication data model and automated routing rules. RxRelief uses configurable workflow triggers that update medication task status from medication events, which helps translate clinical changes into care tasks.
Pick the med manager that matches the integration contract and governance depth required
The decision should start with the integration contract because mismatched schemas create manual mapping work and reconciliation exceptions.
The second step should verify automation and API coverage for the specific medication events that must flow through the system, including administration, dispensing, and discrepancy states.
Map the required event types and reconcile points
List the events that must be captured or exchanged, including medication orders, administered events, dispensing events, and discrepancy outcomes. Choose iMedication when administered records must be reconciled against scheduled dosing data. Choose Net Health when the order-to-administration linkage must drive configurable discrepancy workflows and MAR state transitions.
Verify the medication data model matches the systems of record
Confirm how each tool represents residents or patients, medication definitions, regimens, dosing schedules, and administered records. Choose Welligent Medication Management when a medication-first schema must keep order, administration, and reconciliation fields consistent. Choose iMedication when schema-aligned provisioning is needed to keep external systems synchronized with its explicit data model.
Assess API and automation surface for event-driven throughput
Check whether integration relies on a documented API surface and event-driven automation rather than manual status updates. Choose iMedication when API-driven integration supports medication and administration event synchronization. Choose SureScripts Medication History when automated retrieval and synchronization of reconciled medication-history records must run through API-driven workflows.
Confirm governance controls for medication audit traceability
Require RBAC and audit logging that tie medication changes to actors and events so regulated teams can trace who did what and when. Choose Omnicell for event-level audit logging tied to authenticated users and RBAC across pharmacy, nursing, and admin roles. Choose WellSky when medication-event audit logs must tie medication state changes to actors alongside RBAC for medication workflows.
Evaluate configuration governance and change-management complexity
Review how workflow and schema changes are managed because complex automation increases implementation and exception handling complexity. Choose Welligent Medication Management when a structured workflow state engine can be configured with disciplined configuration management. Choose iMedication when configurable automation rules can reduce workflow drift, but plan for schema mapping work for nonstandard medication models.
Who med manager software fits best based on integration and governance needs
Different med manager tools target different integration targets and governance depths, so the strongest fit depends on where medication truth is maintained.
Teams that need auditable medication-event synchronization choose tools with explicit data models, RBAC, and event-aware audit logs that tie actions to administration or dispensing events.
Regulated care teams coordinating MAR updates and administered-event reconciliation
iMedication fits regulated teams because it uses an explicit data model that links residents, regimens, schedules, and administered events with event-aware administration capture that reconciles administered records against scheduled dosing data. This segment also benefits from iMedication RBAC and audit log visibility for controlled medication automation.
Multi-location healthcare teams needing auditable automation across pharmacy, nursing, and admin roles
Omnicell fits multi-location teams because event-level audit logging ties dispensing and administration actions to authenticated users and RBAC supports role-based access across pharmacy, nursing, and admin users. The tool also represents medication, dispensing, and MAR events with consistent mapping to reduce state drift.
Organizations with medication-order workflows that must route through structured states and reconciliation
Welligent Medication Management fits organizations that need medication workflow automation with a structured medication data model and automated routing rules. Its medication workflow state engine ties workflow state transitions to medication-first schema fields used in order, admin, and reconciliation.
Clinical teams integrating med workflows tightly with EHR order flow and discrepancy handling
Net Health fits teams when medication workflows must integrate with EHR order flow and preserve audit-grade governance for clinical documentation events. It links orders to administration with configurable discrepancy workflows and MAR state transitions that reduce manual reconciliation.
Clinics that must ingest reconciled medication history through exchange rather than full med-ops
SureScripts Medication History fits clinics that need automated medication-history ingestion with governance and auditability across participating organizations. Its API-driven workflow retrieves and delivers reconciled history results and persists medication-history records for downstream reconciliation.
Pitfalls that cause medication record drift, slow automation, or weak audit traceability
Many failures trace back to schema mismatch, unclear event mapping, or insufficient governance controls for medication events and configuration changes.
Avoid selecting tools without confirming how scheduled, administered, and dispensing events relate in the underlying data model and audit logs.
Choosing a tool without confirming event-level reconciliation between schedule and administration
If administered events must reconcile against scheduled dosing, iMedication provides event-aware administration capture that reconciles administered records against scheduled dosing data. Net Health also supports order-to-administration linkage with configurable discrepancy workflows and MAR state transitions.
Underestimating schema and mapping work for nonstandard medication models
iMedication requires schema mapping work for nonstandard medication models, and WellSky can require significant medication data schema mapping during integration. Welligent Medication Management and Net Health also require disciplined configuration management when schema and workflow changes are introduced.
Treating RBAC as sufficient without event-tied audit logs for medication state changes
Omnicell provides event-level audit logging tied to authenticated users, which connects dispensing and administration actions to actor identity. WellSky pairs RBAC with medication-event audit logs that tie medication state changes to actors and administration events.
Assuming the automation surface can handle complex medication exceptions without governance overhead
iMedication automation complexity increases when exceptions require many conditional branches, and Omnicell deep automation requires careful schema and workflow configuration. Net Health can increase implementation and change-management effort when workflow configuration becomes complex.
Selecting a pharmacy-branded workflow tool when custom med schema control is required
Walgreens Prescription Management and CVS Pharmacy Prescription Management focus on prescription workflow and fulfillment steps tied to Walgreens and CVS operations with limited published data model controls for custom med schema extensions. Use these only when tight Walgreens-centric or CVS-centric workflow alignment is the primary requirement, not when external systems need broad schema extensibility.
How We Selected and Ranked These Tools
We evaluated each med manager tool by scoring features, ease of use, and value, with features weighted most heavily because medication automation hinges on concrete integration mechanics and governed data models. We rated each tool using the capabilities described in its workflow automation, integration surface, data model consistency, and governance controls like RBAC and audit logs. Ease of use and value were then used to separate tools with similar capability sets based on operational clarity and practical fit for medication workflows.
iMedication separated from lower-ranked tools because its event-aware administration capture reconciles administered records against scheduled dosing data, which improved the ability to keep medication records consistent across updates. That strength directly lifted its features score through integration depth and automation correctness, while its schema-aligned provisioning and RBAC with audit log visibility supported governance expectations that many other tools describe only at a higher level.
Frequently Asked Questions About Med Manager Software
Which med manager platforms publish the most explicit, developer-facing integration surfaces?
How do iMedication, Omnicell, and WellSky handle auditability for medication state changes?
What are the typical approaches to SSO or identity federation for RBAC-controlled access?
Which tools are best suited for ingesting medication history from external providers or clinical data services?
How do Net Health and Welligent Medication Management reduce order-to-administration discrepancies?
Which med manager options are strongest when the EHR order flow is the system of record?
What data model tradeoffs affect migration projects into a med manager system?
When configuration extensibility matters, which tools expose more controllable workflow and schema boundaries?
Which platforms fit multi-location operations with controlled access and per-role auditing?
How do pharmacy-linked prescription workflows differ from medication-led MAR workflows?
Conclusion
After evaluating 10 healthcare medicine, iMedication 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.