GITNUXSOFTWARE ADVICE
Data Science AnalyticsTop 10 Best Printing Counting Software of 2026
Ranking and side-by-side review of Printing Counting Software for label and printer workflows, covering BarTender, PrinterLogic, and more.
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.
BarTender
BarTender automation interface that submits print jobs while binding template fields to structured data inputs.
Built for fits when mid-size teams need controlled label automation with strong governance and traceability..
ZebraDesigner for iOS
Editor pickTemplate variables and batch print generation tied to Zebra printer language settings.
Built for fits when line teams need template-based printing and counting without custom backend development..
PrinterLogic
Editor pickPrinter and user mapping via policy rules for automated attribution and usage reporting.
Built for fits when IT teams need printer counting automation with directory-based attribution and governance..
Related reading
Comparison Table
This comparison table maps printing counting and label workflows to integration depth, focusing on how each tool fits into existing print, asset, and inventory systems. It also contrasts the data model and schema design, including how automation and the API surface support provisioning, configuration, and extensibility. Admin and governance controls are evaluated across RBAC, audit log coverage, and operational controls that affect throughput and change management.
BarTender
Barcode printingLabel and barcode design with a publishing and printing stack supports print counting, job auditing, and automation interfaces for external orchestration.
BarTender automation interface that submits print jobs while binding template fields to structured data inputs.
BarTender’s core capability is template-driven print generation where variable fields pull from structured inputs such as records, databases, or external files. The integration depth typically shows up through automation interfaces that submit print requests and populate fields from external data sources. Automation and extensibility are supported by an API and execution components that fit into line-of-business workflows. The data model stays explicit because templates define the schema mapping between fields and job inputs.
A tradeoff appears in heavy customization of complex workflows, because the flexibility of template logic and external data binding can raise configuration effort. BarTender fits best when print throughput and data accuracy matter and when governance is required across multiple users and stations. A common usage situation is controlled label production where the system must enforce consistent templates while consuming changing product and batch attributes.
- +Schema-driven variable binding from external records into templates
- +Automation interfaces support print job submission and field population
- +Governance controls cover template management and execution authorization
- +Audit-style execution history supports traceability for print runs
- –Template logic complexity can increase configuration time
- –Deep integration requires careful mapping between data sources and fields
- –Operational troubleshooting may require knowledge of print pipeline components
Manufacturing operations teams
Batch label printing from database records
Fewer labeling errors at throughput
Quality and compliance leads
Traceable label output for audits
Clear audit evidence for labeling
Show 2 more scenarios
Integration engineers
System-to-label workflows via API
Reduced manual steps in labeling
Print requests and field values can be passed through an automation surface into template-driven output.
IT and admin teams
RBAC-based control of template execution
Tighter change control on outputs
Identity and permissions govern who can run which templates and under what configurations.
Best for: Fits when mid-size teams need controlled label automation with strong governance and traceability.
More related reading
ZebraDesigner for iOS
Printer workflowZebra label designer tooling supports Zebra printer workflows and device integration patterns used to track print jobs and counters in production environments.
Template variables and batch print generation tied to Zebra printer language settings.
ZebraDesigner for iOS targets teams that already rely on Zebra printer languages and want label content generated with consistent schemas. The app supports template-driven layouts and variable substitution so the print-counting workflow stays tied to a repeatable data model rather than ad hoc screens.
A concrete tradeoff is limited extensibility compared with full admin platforms that expose broad automation endpoints. ZebraDesigner for iOS fits warehouse and line-of-work runs where mobile operators need controlled template selection and accurate counts without engineering involvement.
- +Template-driven label generation with structured field substitution
- +Mobile workflows for consistent prints during line production
- +Configuration tied to Zebra printer language and device settings
- –Automation surface is narrower than enterprise admin systems
- –Admin governance controls depend on external Zebra tooling
- –Complex multi-system counting logic needs more backend support
Warehouse operations teams
Scan-based label runs with accurate counts
Fewer count mismatches
Manufacturing line supervisors
Repeat SKU label batches
Higher throughput per shift
Show 1 more scenario
Field technicians
Mobile reprinting for asset tags
Faster tag replacement
Mobile template selection speeds reprints while keeping printer settings aligned to the device.
Best for: Fits when line teams need template-based printing and counting without custom backend development.
PrinterLogic
Print managementPrinterLogic centralizes printer deployment and print management with administrative controls and reporting output that can feed counting and audit datasets.
Printer and user mapping via policy rules for automated attribution and usage reporting.
PrinterLogic focuses on integration depth through its device and job data model, connecting user identity, printer configuration, and usage capture in a consistent schema. Provisioning is driven by configurable policies so printers and mappings can be created and updated without manual per-site work. Reporting and audits are grounded in the captured print events, with governance controls that support RBAC and traceability.
A tradeoff is that accurate counts depend on correct identity mapping and printer discovery, so misconfigured directory attributes can create attribution errors. PrinterLogic fits best when organizations already manage users via directory services and need automated printer setup, consistent counting attribution, and controlled reporting for chargeback or compliance.
- +Policy-driven printer provisioning reduces manual site configuration work.
- +API-backed integration moves counting data into existing IT and finance systems.
- +RBAC and audit-oriented governance support controlled administration.
- +Consistent data model links users, printers, and job usage for reporting.
- –Identity mapping errors can misattribute print usage.
- –Agent deployment and discovery setup require careful change management.
IT operations teams
Automate printer discovery and provisioning
Lower setup time per site
Finance chargeback teams
Attribute prints to departments
More consistent departmental billing
Show 2 more scenarios
Identity and access admins
Enforce RBAC over usage data
Controlled access to reports
RBAC controls and audit history limit who can access configuration and reporting outputs.
Custom workflow developers
Sync counts into internal apps
Automated reporting workflows
API and automation endpoints support pushing usage and printer metadata into other systems.
Best for: Fits when IT teams need printer counting automation with directory-based attribution and governance.
PaperCut MF
Print accountingPaperCut provides print release and print accounting with audit logs, usage reports, and administrative governance for print throughput measurement.
Event-driven automation for print job accounting, enabling custom workflows tied to job and user records.
PaperCut MF is printing counting software with deep integration into network print infrastructure and a mature policy engine for quota and reporting. Its data model centers on user, device, print job, and accounting events that feed dashboards and audit workflows.
Administration supports role-based access, policy configuration, and exportable reporting for governance. Extensibility uses documented automation hooks so custom logic can react to job events and accounting records.
- +Strong accounting data model for user, device, and print job events
- +Wide integration options for network print queues and auth systems
- +Automation hooks for reacting to print events and accounting records
- +RBAC and configuration controls for limiting admin actions
- +Audit-oriented reporting exports for governance and reconciliation
- –Queue and server scope must be designed carefully for accurate attribution
- –Automation setups require more configuration than simple counting deployments
- –Scaling log volume needs capacity planning for sustained throughput
- –Customization work can increase operational overhead across print sites
Best for: Fits when mid-size orgs need controlled print accounting with automation and governed administration.
Kofax
Document automationKofax capture and workflow products include document output handling patterns that connect print jobs with data pipelines for downstream counting and reporting.
Event-to-document counting model that ties output totals to workflow and reconciliation records.
Kofax performs print and document output counting for monitored devices and print workflows. It maps capture events into a data model that supports document routing, reconciliation, and reporting across enterprise output streams.
Integration is centered on workflow connectivity and system-to-system data exchange, with an API and automation surface aimed at scaling governance and extraction. Admin controls focus on configuration management, role-based access patterns, and audit-ready operational logs for counted transactions.
- +Device and job counting tied to workflow events and output streams
- +Document-oriented data model supports reconciliation across channels
- +Automation surface supports integration with upstream capture and downstream reporting
- +Configuration and governance controls help standardize counting rules
- –Counting accuracy depends on correct device and job metadata mapping
- –Automation and API use require careful schema alignment for integration
- –Operational setup overhead is higher than lightweight counting tools
Best for: Fits when enterprise print counting needs workflow integration, governance, and audit-ready reporting.
GoFrugal Print Management
Print trackingPrint management software integrates with network printing to centralize job tracking data and produce usage metrics suitable for print counting.
Governed audit logs for printer mapping and counting policy changes.
GoFrugal Print Management targets organizations that need printing count control across multiple locations with centralized reporting and policy enforcement. It provides a data model for print events, device mapping, user or cost-center attribution, and configurable rules that convert raw job data into managed counters.
The automation surface centers on administrative configuration and integration points that support provisioning, reporting exports, and workflow triggers. Governance hinges on role-based administration, with audit trail visibility used to track changes to mappings and counting policies.
- +Centralized device and printer mapping for consistent counting across sites
- +Configurable attribution rules for users and cost centers
- +Administrative RBAC supports separation between config and reporting users
- +Audit log records policy and configuration changes for governance
- –Automation depends on available integration endpoints and export formats
- –Counting accuracy requires correct device registration and job metadata
- –Data model customization can add admin overhead for complex org structures
- –Automation scope may be limited without deeper API coverage
Best for: Fits when multi-site operations need controlled print counting with governed configuration changes.
ThinPrint
Print mediationThinPrint mediates print streaming and can provide hooks for print job metrics that enable counting and operational telemetry.
Central print release and routing policies that enforce job attribution before printing.
ThinPrint differentiates through print workflow control that couples device-agnostic job routing with centralized administration. It tracks and governs print activity via a data model tied to print release, quotas, and user or cost-center attribution.
Automation is driven by well-defined configuration and integration points that support policy enforcement before jobs reach endpoints. Through extensibility hooks and integration surface around print management components, governance rules can be applied across distributed sites.
- +Print accounting tied to user and workgroup attribution for chargeback reporting
- +Central administration supports consistent release and routing policies across sites
- +Integration points align with workflow automation and pre-endpoint policy enforcement
- +Audit-friendly operational records for governance and operational verification
- –Counting accuracy depends on correct driver and connector deployment coverage
- –Complex policy configurations can increase operational overhead for admins
- –Automation relies on ThinPrint-specific integration model rather than generic event hooks
- –Throughput and queue behavior require careful tuning for high-volume print fleets
Best for: Fits when enterprises need governed print counting with policy-driven release across many endpoints.
PrintNode
API printingPrintNode exposes APIs for network printing operations and can be used to record and count print requests as part of an integration data model.
Printer provisioning plus job and event webhooks for automation without manual reconciliation.
PrintNode focuses on connecting print ordering workflows to a counting and fulfillment data model. It centralizes printer provisioning, job submission, and webhook delivery around a consistent API surface.
Automation is driven through API calls and event webhooks that support status tracking and downstream synchronization. Administration centers on workspace-level configuration, API key management, and auditable operational events for governance.
- +API-first workflow with job submission and status webhooks
- +Consistent data model for printers, jobs, and counting states
- +Provisioning supports printer registration and configuration per workspace
- +Event-driven automation fits integrations that need near-real-time updates
- –Operational governance relies on API key management rather than granular RBAC
- –Complex multi-tenant role separation requires external access control
- –Throughput tuning depends on integration design and webhook handling
- –Advanced reporting needs custom aggregation from webhook and API data
Best for: Fits when mid-size teams need print counting automation with documented API and webhook events.
PrinterShare
Remote printingPrinterShare supports remote print operations from managed environments and generates print activity records useful for counting workflows.
Device-based page counting that aggregates usage across a printer fleet.
PrinterShare counts and manages print usage by collecting device and job data from printers installed in managed environments. It centralizes fleet-level visibility so administrators can monitor pages and usage patterns across locations.
Integration is built around printer discovery and reporting workflows rather than an external analytics-first data model. Automation depends on configuration and administrative controls tied to printer sources, not a documented event-first API surface.
- +Printer discovery and data collection for usage reporting across installed devices
- +Centralized page-count reporting by printer and job source
- +Administrative configuration supports multi-printer fleet management workflows
- +Operational reporting reduces manual meter reading across sites
- –Automation relies more on setup than on extensible external integrations
- –API and schema extensibility for custom automation are not a primary surface
- –Governance controls for granular RBAC and audit logs are not clearly structured for automation
- –Data model is printer-and-count centric rather than event-driven for downstream systems
Best for: Fits when centralized print metering and reporting matter more than custom API automation.
CUPS Filters
Open print stackCUPS filter tooling can be extended to capture printing events, allowing event schema and counters to be built from print processing logs.
Filter pipeline configuration that controls job conversion stages that counting systems can observe.
CUPS Filters serves printing workflows where detailed filter pipelines matter and device handling must be consistent across hosts. It centers on PPD and filter execution to transform print jobs into device-ready formats before counting or accounting hooks.
Integration depth comes from the Unix plumbing around CUPS, including configuration files and spool-to-filter execution behavior. Core capabilities include managing filter chains and controlling where job transformations occur for predictable throughput.
- +Tight integration with CUPS filter chain execution for deterministic job transformations
- +Configuration-driven pipeline mapping to align job formats with counting points
- +Strong automation leverage through standard CUPS mechanisms and scripts
- –Limited RBAC and admin governance features compared with centralized SaaS consoles
- –Automation surface is mostly indirect through CUPS hooks, not a purpose-built API
- –Audit log depth depends on external components rather than built-in reporting
Best for: Fits when teams need host-level control of CUPS filter behavior for consistent job accounting.
How to Choose the Right Printing Counting Software
This guide covers ten printing counting software options including BarTender, PaperCut MF, and PrinterLogic through implementation-focused criteria. It helps buyers judge integration depth, data model fit, automation and API surface, and admin and governance controls across label templates, network print accounting, and API-first job workflows.
The guide also maps tool strengths to specific environments such as directory-attributed IT metering and workflow event reconciliation. It highlights concrete evaluation points for tools like Kofax, ThinPrint, and PrintNode, then identifies recurring setup and governance pitfalls across the same set of products.
Printing counting stacks that convert print events into governed counters and audit records
Printing counting software turns print job activity into structured accounting data such as pages, jobs, user attribution, device usage, and audit-ready execution history. The output supports reporting, reconciliation, chargeback style workflows, and automated downstream actions based on job and accounting events.
Tools differ by where counting is derived, such as network print job accounting in PaperCut MF or API and webhook-driven job state tracking in PrintNode. Label and template printing stacks like BarTender also generate print jobs from structured data bindings so counting aligns with repeatable template execution.
Evaluation criteria for counting accuracy, automation extensibility, and controlled administration
Counting accuracy depends on the data model linking users, devices, and job events to accounting records. PaperCut MF ties its accounting data model to user, device, and print job events so reporting and audit workflows stay consistent.
Integration depth determines whether counting data can flow into existing IT and finance systems through an automation surface. PrinterLogic focuses on API-backed integration for moving counting data into existing systems, while PrintNode provides API-first job submission plus job and event webhooks.
Event-driven data model tied to accounting records
PaperCut MF uses a data model centered on user, device, print job, and accounting events to feed dashboards and audit workflows. Kofax uses an event-to-document counting model that ties output totals to workflow and reconciliation records, which matters for environments where output is owned by document routing.
Integration depth through documented API and webhook or automation interfaces
PrintNode exposes job submission plus status tracking via APIs and delivers event webhooks for downstream synchronization. PrinterLogic adds an API-backed integration surface so printer counting data can be pushed into IT and finance systems without manual exports.
Automation surface for print decisioning and template-bound execution
BarTender includes an automation interface that submits print jobs while binding template fields to structured data inputs. ThinPrint applies policy enforcement through centralized print release and routing policies so job attribution can be applied before endpoints receive jobs.
Admin and governance controls with RBAC, authorization, and audit trails
PaperCut MF supports RBAC and configuration controls that limit admin actions and backs governance with audit-oriented reporting exports. BarTender governs template management and execution authorization and records execution history for traceability across connected systems.
Attribution model that maps identity or cost centers to usage
PrinterLogic maps printers and users via policy rules so automated attribution drives usage reporting. GoFrugal Print Management includes configurable attribution rules for users and cost centers and tracks audit log visibility for printer mapping and counting policy changes.
Provisioning and deployment workflow tied to counting correctness
PrinterLogic deploys agents and policies that map jobs and usage to managed printer objects, which improves consistency when printers scale across sites. GoFrugal Print Management and ThinPrint also rely on correct device registration and connector deployment, which directly affects counting accuracy for distributed fleets.
A decision framework for selecting the right printing counting tool for the target control point
The first decision is where counting is derived in the print path, such as at the network accounting layer in PaperCut MF or at the integration layer in PrintNode. This determines which metadata is available for attribution and which failure modes create misattributed usage.
The second decision is how automation and governance must work together. BarTender and ThinPrint emphasize controlled execution and policy enforcement, while PrinterLogic and PaperCut MF emphasize RBAC and audit-ready accounting records for admins and stakeholders.
Choose the control point that matches where attribution metadata already exists
If attribution already lives in directory and network print identities, PrinterLogic maps printers and users via policy rules for directory-based attribution. If attribution must be enforced before jobs reach endpoints, ThinPrint applies centralized print release and routing policies so attribution rules apply during release and not after the fact.
Validate the data model for pages, jobs, and audit traceability
PaperCut MF ties pages and accounting events to user, device, and print job records so audit and reconciliation workflows can use consistent entities. BarTender uses variable binding from external records into templates so counted output can align with template execution history and structured data inputs.
Match automation needs to the API and webhook or automation surface
If near-real-time automation is required for job lifecycle and downstream sync, PrintNode provides job and event webhooks plus API-first submission and status tracking. If automation must react to accounting events with custom logic, PaperCut MF includes automation hooks around job events and accounting records.
Confirm admin governance depth for template, policy, and execution authorization
For controlled administration with RBAC and limited admin actions, PaperCut MF provides RBAC and configuration controls plus audit-oriented reporting exports. For label and template governance, BarTender covers template management and execution authorization with execution history for traceability.
Plan for provisioning and deployment work that impacts counting accuracy
For centralized printer counting across many sites, PrinterLogic requires careful agent deployment and discovery setup because mapping correctness drives accurate attribution. For API and webhook based counting, PrintNode still needs correct workspace configuration and event handling design to prevent throughput bottlenecks in webhook processing.
Pick the tool that fits the dominant workflow type in the organization
If the dominant need is label and barcode template execution with structured field binding, BarTender fits label automation with a schema-driven variable binding model. If the dominant need is workflow output reconciliation across document channels, Kofax fits event-to-document counting tied to workflow reconciliation.
Which teams get measurable value from counting stacks built for their workflow and governance model
Different tools target different workflow entry points and governance requirements. Label automation teams usually prioritize schema-driven template execution and traceable job submission, while network print governance teams prioritize RBAC and event-driven accounting.
Selection should follow the environments implied by each tool’s best_for fit, such as IT identity-based attribution in PrinterLogic or multi-site governed configuration changes in GoFrugal Print Management.
Mid-size teams running controlled label automation with audit traceability
BarTender fits controlled label automation because it binds template fields to structured data inputs and includes an automation interface for print job submission. Governance and traceability come from template management plus execution history across connected systems.
IT teams that need directory-based attribution and governed printer counting at scale
PrinterLogic fits IT-led counting because it uses policy-driven printer provisioning and maps users and printers for automated attribution. RBAC and audit-oriented governance support controlled administration when printer and user mapping must remain consistent.
Mid-size organizations that need governed print accounting on network queues with audit-ready reporting
PaperCut MF fits controlled print accounting because it uses a strong accounting data model based on user, device, print job, and accounting events. Automation hooks and RBAC plus exportable reporting support governance and reconciliation workflows.
Enterprise teams that must reconcile output totals with workflow and document routing
Kofax fits enterprise counting when output totals must tie to workflow and reconciliation records through an event-to-document counting model. Its admin controls and audit-ready operational logs support standardized counting rules across enterprise output streams.
Mid-size teams that want API-first printing operations with job state webhooks
PrintNode fits API-first automation because it provides printer provisioning plus job submission and status webhooks. Governance relies on workspace configuration and API key management rather than granular RBAC, so external access control must be designed around the API surface.
Pitfalls that break counting accuracy or make governance hard to sustain
Many failures come from mismatches between the available metadata and the counting tool’s attribution model. Another common breakage comes from underestimating configuration and deployment work needed to make counting events consistent across devices.
These mistakes show up across tools because each product assigns counting correctness to a specific place in the print path or to a specific configuration system.
Using the tool without validating identity to usage mapping rules
PrinterLogic can misattribute print usage when identity mapping rules are wrong, so mapping policies for user and printer identities must be validated during provisioning. PaperCut MF also requires queue and server scope design because inaccurate scope can distort user and device attribution.
Building automation that assumes event fields exist without checking the underlying data model
Kofax depends on correct device and job metadata mapping for counting accuracy, so schema alignment between counted events and workflow records matters. BarTender automation that binds template fields also requires careful mapping between external data sources and template fields to avoid inconsistent output records.
Underestimating configuration complexity for template logic or release policies
BarTender label template logic can increase configuration time, which delays stable counting when template rules are complex. ThinPrint policy configurations can increase operational overhead, and throughput and queue behavior require careful tuning for high-volume fleets.
Relying on indirect integration surfaces without enough deployment coverage
CUPS Filters provides host-level control through filter chain execution, but its automation surface is indirect because it depends on standard CUPS mechanisms rather than a purpose-built API. PrinterShare also relies more on printer discovery and data collection than on a documented event-first API surface for custom automation.
Assuming governance controls will be equally granular across products
PrintNode governance relies on workspace configuration and API key management rather than granular RBAC, so access control must be handled outside the product. GoFrugal Print Management and PaperCut MF provide clearer governance through RBAC and audit logs for mapping and policy changes, which reduces the risk of unmanaged admin operations.
How We Evaluated and Ranked These Printing Counting Tools
We evaluated BarTender, ZebraDesigner for iOS, PrinterLogic, PaperCut MF, Kofax, GoFrugal Print Management, ThinPrint, PrintNode, PrinterShare, and CUPS Filters using three scored criteria. Features carried the largest share because counting correctness and integration depth depend on the data model, automation interfaces, and extensibility surface. Ease of use and value each carried the next largest shares because agent deployment complexity, template configuration overhead, and operational troubleshooting effort affect sustained governance. The overall rating is a weighted average where features account for the biggest portion, and ease of use and value each account for the remaining portions as editorial scoring criteria.
BarTender set itself apart through a concrete automation capability that submits print jobs while binding template fields to structured data inputs. That strength lifted features through schema-driven variable binding and improved ease of use for repeatable label execution because template-driven field population supports consistent output and traceability under governed execution history.
Frequently Asked Questions About Printing Counting Software
How do printing counting tools integrate with existing workflow systems and job submission paths?
Which tools provide an API or automation surface for pushing counting data into other systems?
What is the best fit when role-based access and audit trails are required for administrators?
How do these tools handle security when identities and user attribution come from directories or authenticated sessions?
Which products are designed for template-driven printing where counting depends on structured data binding?
How do admin teams migrate existing printer mapping and counting rules without losing attribution accuracy?
What common setup problems occur when job attribution or totals do not match expectations, and how do tools mitigate them?
Which solution fits multi-site operations where configuration changes need governance and location-level reporting?
When host-level print processing must be consistent for counting, which approach matches that requirement?
Conclusion
After evaluating 10 data science analytics, BarTender 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
Data Science Analytics alternatives
See side-by-side comparisons of data science analytics tools and pick the right one for your stack.
Compare data science analytics 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.