GITNUXSOFTWARE ADVICE
Art DesignTop 10 Best Screenprinting Software of 2026
Top 10 Screenprinting Software tools ranked by RIP features, color control, and workflow, with notes on Cadlink C5, Onyx Thrive, and Caldera.
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.
Cadlink C5
A job records-to-screen and film definition data model that keeps production steps synchronized to the same schema.
Built for fits when shops need controlled automation and consistent job-to-screen data across multiple operators..
Onyx Thrive
Editor pickArtwork-to-variant run settings schema keeps screen setup, production tasks, and reprint configurations aligned.
Built for fits when mid-size shops need production automation with an API surface and controlled configuration governance..
Caldera ProductionHouse
Editor pickSchema-led job data ties prepress parameters, proofs, and output targets into one governed workflow context.
Built for fits when mid-size screen shops need repeatable job workflows with controlled proofs and production settings..
Related reading
Comparison Table
This comparison table maps screenprinting software across integration depth, including how each tool connects with RIP workflows, production systems, and external services via API and automation. It also compares the underlying data model and schema for orders, jobs, and artwork assets, plus admin and governance controls such as provisioning, RBAC, and audit log coverage.
Cadlink C5
RIP workflow CADCAD software for screen printing workflows with RIP-oriented output planning, job setup controls, and production-oriented tooling for print production pipelines.
A job records-to-screen and film definition data model that keeps production steps synchronized to the same schema.
Cadlink C5 supports production planning by connecting job records to prepress assets such as screen and stencil definitions, so job changes propagate through downstream steps. The data model links artwork requirements to manufacturing artifacts, which helps maintain schema consistency across departments. Automation and configuration reduce manual handoffs by standardizing setup parameters and job routing logic.
A key tradeoff is that workflow accuracy depends on disciplined mapping between job metadata and the shop's screen and film conventions. Cadlink C5 fits best when a shop needs repeatable throughput with controlled provisioning of templates and roles across multiple operators.
- +Job-to-asset data links reduce rekeying across prepress and production
- +Workflow automation standardizes routing and setup steps
- +Configuration-first design supports repeatable shop templates
- +Production records stay tied to screens and film definitions
- –Workflow quality depends on consistent schema mapping
- –Changes to production conventions require coordinated configuration updates
- –Automation breadth may require process redesign for outlier jobs
Prepress operators
Convert artwork into production-ready assets
Fewer rework loops
Production managers
Standardize routing and setup policies
More predictable throughput
Show 2 more scenarios
Shop administrators
Govern user workflows and templates
Lower process drift
Provisioning and configuration control reduce variation across operator workstations.
Workflow analysts
Audit job status and artifact changes
Faster root-cause checks
The structured production record supports traceability between job changes and downstream artifacts.
Best for: Fits when shops need controlled automation and consistent job-to-screen data across multiple operators.
Onyx Thrive
RIP automationOnyx GFX RIP software for print production with configurable job settings, color management controls, and automation-friendly output workflows.
Artwork-to-variant run settings schema keeps screen setup, production tasks, and reprint configurations aligned.
Onyx Thrive fits print shops that need controlled throughput from prepress through production, not just order entry. The core data model links artwork assets to job variants and run settings so reprints carry the same configuration schema. Automation can drive status transitions and task creation when order milestones are reached. An integration depth centered on API-driven extensibility helps connect estimating, inventory, and fulfillment workflows.
A tradeoff appears when organizations require highly customized schemas for niche production steps that are not expressed in the standard job and run constructs. Teams see the best fit when repeatable workflows can be represented with clear state transitions and consistent configuration. One usage situation involves multi-variant runs where artwork and color selections must stay synchronized across mockups, prepress notes, and screen setup.
- +Job data model ties artwork, variants, and run settings together
- +Workflow automation handles status transitions and task generation
- +API-first extensibility supports integration with external systems
- +Admin configuration governance enables controlled operational changes
- –Custom production steps may require schema mapping work
- –Deep automation depends on consistent internal workflow definitions
Production managers
Automate job status and task handoffs
Fewer manual handoffs
Prepress coordinators
Synchronize artwork variants across steps
Lower remake risk
Show 2 more scenarios
Operations admins
Control configuration changes with governance
Traceable operational changes
RBAC-style access controls and audit trails support controlled updates to job workflows and settings.
Integrations engineers
Provision orders through API
Higher integration throughput
API-based automation enables order ingestion and enrichment from estimating or inventory systems.
Best for: Fits when mid-size shops need production automation with an API surface and controlled configuration governance.
Caldera ProductionHouse
production RIPProduction print software focused on job processing, color management configuration, and repeatable production setup for screen-print adjacent output.
Schema-led job data ties prepress parameters, proofs, and output targets into one governed workflow context.
Caldera ProductionHouse centers on a job-centric data model that keeps rip-ready assets, proofing parameters, and press output targets tied to a single workflow context. The integration depth shows up in how calibration, screening, and output settings can travel with the job rather than living as separate operator memory. Automation relies on configurable workflows and repeatable templates, which reduces rework when throughput needs consistent results across shifts.
A tradeoff appears in governance and onboarding effort because the data model and configuration schema require deliberate setup before teams can run at scale. The best fit shows up in screen shops that need controlled repeats for reorders and standardized proofs, especially when multiple production roles touch the same job artifacts.
- +Job-linked output settings reduce operator guesswork.
- +Workflow templates support repeatable proofs and production runs.
- +Automation configuration supports higher throughput with fewer manual steps.
- +Integration patterns fit orchestrations around prepress and imaging stages.
- –Initial schema setup needs time to match shop conventions.
- –Governance configuration can add friction for small one-press teams.
Production managers
Standardize repeat reorders across presses
Fewer remake incidents
Prepress operators
Generate governed proofs for clients
Faster approval cycles
Show 2 more scenarios
IT and workflow engineers
Automate handoffs with external systems
Lower manual handoff load
Teams wire job state into automation around imaging, imaging queues, and downstream approvals using integration interfaces.
Studio operations with multiple roles
Control edits using RBAC patterns
Clear change accountability
Roles limit who can change configuration and output targets while workflows preserve job-level settings history.
Best for: Fits when mid-size screen shops need repeatable job workflows with controlled proofs and production settings.
SAi Flexi
layout to outputVector and layout tooling with screen-printing-oriented output preparation, including contour cut concepts and production-ready export paths.
Prepress job and output configuration settings that stay consistent across separations and production-ready exports.
SAi Flexi is screenprinting software focused on prepress workflow control and production-ready artwork output. It supports production preparation tasks like job setup, separations handling, and output configuration tied to printing requirements.
Integration depth is driven through file-based exchange, structured job data, and configuration patterns that support automation-style throughput. Data model consistency matters for governance, because schema-like settings for output and production steps can be standardized across teams.
- +Job setup and output configurations reduce manual prepress rework
- +Production-oriented separations workflows support repeatable downstream output
- +Standardized output settings improve throughput across many similar jobs
- +Configuration patterns help enforce consistent prepress handling
- –Automation surface is limited without documented API workflows
- –Governance relies more on configuration consistency than RBAC controls
- –Extensibility depends on external pipeline integration rather than native APIs
- –Audit logging depth for admin actions is not clearly exposed through an API
Best for: Fits when print houses need controlled prepress outputs with standardized configuration across production teams.
MaintainX
operations governanceMaintenance management that supports asset hierarchies, scheduling, work orders, and audit trails for screen-print equipment governance and operational control.
Work order and inspection automation tied to a CMMS data model of assets, locations, and maintenance plans.
MaintainX drives maintenance work through a configurable CMMS data model tied to assets, locations, and maintenance plans. Screenprinting shops can track inspections, work orders, and recurring tasks on presses, dryers, ink systems, and HVAC for consistent production upkeep.
The integration focus centers on a documented API surface for work orders, assets, checklists, and reporting objects, plus automation via rules and triggers. Admin governance is built around role-based access, structured configuration, and audit logging for operational control.
- +Asset and work-order schema covers recurring tasks for production-adjacent equipment
- +API exposes core objects like assets, tasks, and work orders for integration depth
- +Automation rules connect triggers to task creation and assignment without custom code
- +RBAC restricts access by role for operational governance
- +Audit log supports traceability of configuration and record changes
- –Data model customization can require schema discipline across locations and equipment types
- –Automation coverage depends on available triggers and may limit edge-case workflows
- –Reporting flexibility can lag behind highly custom production metrics and KPIs
- –Bulk provisioning workflows may require careful mapping of identifiers and fields
Best for: Fits when screenprinting operations need structured maintenance automation with API-based integrations and controlled admin governance.
monday.com
workflow automationWork management platform that models screen-print job states with custom schemas, automation rules, and role-based permissions for studio operations.
Boards with custom schema plus automations that react to specific field edits.
Monday.com fits screenprinting workflows that need shared job data across prepress, production, and fulfillment teams. It models work in boards with configurable fields, automations, and conditional rules tied to those fields.
Integration depth centers on connectors, webhooks, and an automation layer that can trigger on state and field changes. monday.com also provides an API surface for custom apps that read and write board data, which supports governed configuration with RBAC and audit logging.
- +Board data model supports custom fields for ink, colors, and artwork status
- +Automation rules can trigger on field changes and item state transitions
- +Extensible integration via API and webhooks for custom production tooling
- +RBAC supports role-scoped permissions across workspaces and boards
- +Audit log provides traceability for data and permission changes
- –Workflow logic can sprawl across boards without a documented schema
- –Complex cross-board dependencies require careful automation design
- –High-volume updates can increase automation execution overhead
- –Granular validation constraints on fields are limited versus form engines
- –Admin governance of many boards can become heavy without templates
Best for: Fits when production teams need governed workflow automation with board data shared across departments.
Airtable
data model + APIRelational table data model for screen-print job tracking with schema fields, views, and API-driven automation for end-to-end production status.
Automation with triggers on specific field changes plus webhooks for real-time job status propagation.
Airtable combines a programmable spreadsheet-like data model with a documented REST API and automation workflows. It supports relational records, computed fields, and configurable interfaces that map to repeatable screenprinting job data.
Integration depth comes from webhooks, API access, and automation triggers that push updates between tools. Governance relies on workspace roles, permission boundaries, and audit visibility for administrative actions.
- +Relational data model with schema rules and computed fields
- +REST API and webhooks cover record CRUD, querying, and sync patterns
- +Automation rules trigger on field changes and push to external apps
- +Interface builder supports reusable views for job intake and routing
- +RBAC with workspace roles and record-level sharing controls
- +Extensibility via scripting and connected apps for custom workflows
- –Throughput limits constrain high-frequency updates from printers or scanners
- –Complex schema changes require careful migration planning and validation
- –Automation chains can become hard to trace across multiple steps
- –Audit and admin visibility focus on actions, not deep per-change diffs
Best for: Fits when teams need an API-first job database with automation between estimating, production, and proofing steps.
Smartsheet
schema workflowsSpreadsheet-based workflow tooling with row-level structured data, automated notifications, and admin controls for production planning.
Smartsheet Automation with condition-based triggers tied to cell and workflow events.
Smartsheet centers work management around a configurable sheet-and-grid data model for cross-team workflows. Smartsheet supports automation via Smartsheet Automation and rule triggers tied to cell updates, status changes, and dependencies.
Integration depth includes connectors for common enterprise systems plus extensibility through APIs for reading and updating entities like sheets, rows, and attachments. Admin governance includes RBAC and audit log visibility to track user actions across workspaces and assets.
- +Sheet-centric data model maps cleanly to external records
- +Automation rules trigger from cell edits and workflow state changes
- +REST API supports CRUD for sheets, rows, and attachments
- +RBAC controls access at workspace and sheet scopes
- +Audit log records user activity for governance reviews
- –Automation rule logic can require careful design to avoid loops
- –Large exports and row-level updates can bottleneck throughput
- –Complex relational structures require multiple sheets and joins
- –API requires explicit handling for permissions and sharing boundaries
Best for: Fits when teams need visual workflow automation with an API-driven integration model and governance controls.
Microsoft Power Apps
custom app platformLow-code app platform for building screen-print job management apps with Dataverse-backed data models, RBAC, and automation via connectors and APIs.
Dataverse tables plus environment-based provisioning with RBAC for governed data and app lifecycle control.
Microsoft Power Apps enables screenprinting workflows through custom apps, forms, and approvals that front a structured data model. Built on Dataverse and supported connectors, it ties production orders, customer specs, and inventory into one schema-driven workspace.
Automation is handled with Power Automate flows and triggers, and extensibility comes via custom connectors and Microsoft-managed APIs. Administrative control relies on Azure AD identity, environment separation, and audit visibility across apps and data.
- +Dataverse supports a governed schema for orders, artwork, and inventory entities
- +Power Automate integration enables event-driven production workflows
- +Azure AD and RBAC control user access across apps and data
- +Custom connectors extend automation and API integration beyond Microsoft connectors
- –App performance depends on data modeling and delegation rules in queries
- –Sandboxed extensibility limits direct low-level integration patterns
- –Cross-app changes require careful environment and solution packaging governance
- –Audit coverage varies by connector actions and custom integration approach
Best for: Fits when teams need schema-driven screenprinting order capture with approvals and workflow automation via Power Platform.
Google AppSheet
custom app platformNo-code app builder that creates structured screen-print production workflows tied to data sources, with admin policies and automation via APIs.
Automation triggers and scheduled actions execute workflow steps across apps using the platform’s API and rules engine.
Google AppSheet fits teams that need form-driven apps tied to spreadsheets and app-generated workflows. Its data model uses tables, schema definitions, and relations mapped from sources, then drives UI, validation, and role-based access.
Automation covers scheduled jobs, trigger-based actions, and outbound integration steps that call APIs and connect to external systems. The extensibility surface includes API-based endpoints, scripting via platform functions, and admin configuration for provisioning and governance.
- +Data model maps spreadsheets into relational schema with enforced constraints
- +Trigger-based automation supports multi-step actions and scheduled runs
- +Built-in role-based access controls for views, actions, and data visibility
- +API surface enables custom integrations with external systems and services
- +Admin configuration supports environment separation and deployment controls
- –Complex workflows can become hard to debug across multiple automations
- –Large datasets can hit query and refresh throughput limits under heavy usage
- –Granular auditability depends on configuration and logging coverage
- –Schema changes can require careful propagation to connected views and rules
- –Extensibility via functions can increase maintenance overhead over time
Best for: Fits when spreadsheet-backed operations need RBAC, form automation, and API integrations without custom app engineering.
How to Choose the Right Screenprinting Software
This guide covers Screenprinting Software tools that manage screen, film, job setup, production handoffs, and workflow data from Cadlink C5 and Onyx Thrive through Caldera ProductionHouse and SAi Flexi.
It also includes workflow and governance platforms used around screenprinting operations, including MaintainX, monday.com, Airtable, Smartsheet, Microsoft Power Apps, and Google AppSheet.
Screenprinting workflow software that binds artwork, screens, and production steps
Screenprinting software coordinates prepress planning, job setup, and production-floor execution by tying artwork inputs to downstream run settings, proofs, and output targets. Tools like Cadlink C5 and Onyx Thrive use structured job and production records to reduce rekeying and to keep screen setup aligned to repeatable definitions.
The software also solves the operational problem of keeping status transitions, task handoffs, and reprint configurations consistent across multiple operators and workstations. Teams that manage frequent repeats, multi-person production floors, or controlled change processes typically use these systems.
Evaluation criteria built around data model, automation, integration, and governance
Screenprinting operations break when artwork-to-run parameters drift between stations or when status and task updates depend on manual steps. Evaluation needs to focus on the data model and schema mapping that carry job intent from intake to production output.
Integration depth and automation coverage determine whether the tool can participate in an existing pipeline or requires process redesign. Admin and governance controls decide how change management works across multiple users and connected workstations.
Job-to-asset schema mapping for screens and film definitions
Cadlink C5 keeps production steps synchronized to the same schema by linking job records to screen and film definitions. This reduces rekeying across prepress and production when multiple operators handle different stations.
Artwork-to-variant run settings data model
Onyx Thrive ties artwork, garment variants, and run settings together so screen setup, production tasks, and reprint configurations stay aligned. This matters when one design produces many variant runs across garments and print conditions.
Schema-led job context that ties proofs to output targets
Caldera ProductionHouse builds a governed workflow context that connects prepress parameters, proofs, and output targets. This helps shops repeat controlled runs across imaging and proofing steps with fewer operator decisions.
Rule-based workflow templates for repeatable proofs and output planning
Caldera ProductionHouse uses workflow templates for repeatable proofs and production runs. Cadlink C5 complements this with configuration-first shop templates that standardize routing and job setup steps.
Documented integration surface plus an automation and API surface
Onyx Thrive provides API-first extensibility so external systems can read and write workflow-relevant job data. Airtable and Smartsheet add automation triggers tied to field or cell edits plus a documented REST API and webhooks for record-level propagation.
Admin governance with RBAC and auditable change tracking
MaintainX includes RBAC for operational governance plus an audit log that supports traceability of configuration and record changes. monday.com and Airtable also provide audit visibility for administrative actions while restricting access with workspace roles and record-level sharing controls.
Decision framework for picking screenprinting workflow and governance software
Selection starts by matching the tool’s data model to the shop’s real operational objects such as screens, film definitions, variants, proofs, and run settings. Then integration depth and automation coverage determine whether the system can drive state changes and task generation without manual glue work. Finally, admin and governance controls decide whether changes can be controlled across teams and workstations.
Map the data model to the shop’s production objects
If the core need is keeping production steps synchronized to screen and film definitions, Cadlink C5 fits because its job records-to-screen and film data model keeps steps aligned to the same schema. If the core need is aligning artwork-to-variant run settings across reprints, Onyx Thrive fits because its artwork-to-variant run settings schema ties screen setup and production tasks together.
Check whether automation is schema-aware or depends on manual conventions
Onyx Thrive supports workflow transitions and task generation through automation hooks that depend on consistent internal workflow definitions. Caldera ProductionHouse provides rule-based configuration and workflow templates that tie prepress parameters, proofs, and output targets into one governed workflow context.
Verify integration depth and the automation and API surface
If external systems must integrate into job planning and production events, Onyx Thrive offers API-first extensibility while Airtable uses a documented REST API and webhooks for record updates. If the workflow layer must react to field edits or cell changes, Smartsheet Automation provides condition-based triggers tied to cell updates and workflow events.
Plan governance for multi-user change control and audit visibility
If governance needs to include RBAC and an audit log for operational traceability, MaintainX supports role-based access and audit log traceability for configuration and record changes. If governance needs revolve around shared job data across teams, monday.com provides RBAC plus audit log traceability for data and permission changes at the workspace and board level.
Stress-test schema mapping effort for outlier workflows
Cadlink C5 requires consistent schema mapping because workflow quality depends on coordinated configuration updates when conventions change. Onyx Thrive and Caldera ProductionHouse both require schema mapping work when custom production steps do not match existing workflow definitions.
Who benefits from structured screenprinting job data, automation, and governance controls
Screenprinting teams benefit most when job intent is captured once and carried through to screen setup, proofs, output planning, and production status transitions. The tool choice depends on whether the primary pain is rekeying, variant run alignment, proof repeatability, maintenance governance, or cross-team workflow automation. Some tools serve production workflow orchestration, while others act as the shared data and automation layer around print operations.
Production-floor shops that need controlled job-to-screen and film synchronization across operators
Cadlink C5 fits because its job records-to-screen and film definition data model keeps production steps synchronized to the same schema. This design reduces rekeying across prepress and production for multi-operator workflows.
Mid-size shops that need automation tied to artwork variants with an API-first integration path
Onyx Thrive fits because its artwork-to-variant run settings schema aligns screen setup, production tasks, and reprint configurations. It also provides an API-first extensibility surface for integrating production events and external systems.
Mid-size screen shops that need repeatable job workflows tied to proofs and output targets
Caldera ProductionHouse fits because schema-led job data ties prepress parameters, proofs, and output targets into one governed workflow context. Workflow templates support repeatable proofs and production runs with fewer manual decisions.
Shops that need standardized prepress output exports tied to separations workflows
SAi Flexi fits because its prepress job and output configuration settings stay consistent across separations and production-ready exports. Configuration consistency is the mechanism for throughput across many similar jobs.
Operations teams that need CMMS-grade governance for presses, dryers, and production-adjacent equipment
MaintainX fits because it uses a CMMS data model for assets, locations, and maintenance plans with work order and inspection automation. RBAC and audit logging support operational governance tied to production upkeep.
Pitfalls that break screenprinting automation and governance projects
Many implementation failures come from choosing tools that cannot represent the shop’s production objects in a stable schema. Other failures come from underestimating the work required to make custom steps align with the tool’s workflow definitions and automation triggers. Governance also fails when RBAC and audit visibility do not match how teams change configurations and records across stations.
Assuming automation works the same way for custom production steps
Cadlink C5 and Onyx Thrive both depend on consistent schema mapping and internal workflow definitions. Custom production steps that do not match existing conventions require coordinated configuration updates or schema mapping work.
Treating board or spreadsheet tools as substitutes for production schema alignment
monday.com can react to specific field edits with automations, but it can sprawl across boards without a documented schema. Airtable and Smartsheet can trigger on field or cell updates, but complex relational structures require careful migration and traceability design.
Skipping governance design for multi-user environments
MaintainX includes RBAC and an audit log for traceability of configuration and record changes, which helps prevent uncontrolled operational edits. Tools like SAi Flexi rely more on configuration consistency than RBAC controls, which can raise governance overhead when multiple users administer production settings.
Overbuilding automation chains without planning for update overhead and traceability
monday.com warns that high-volume updates can increase automation execution overhead. Airtable and Smartsheet can chain automations, but automation chains can become hard to trace across multiple steps when too many triggers propagate changes.
How We Selected and Ranked These Tools
We evaluated ten tools for screenprinting workflow needs by scoring features, ease of use, and value using the concrete capabilities and limitations described in the review material. Features carried the most weight at forty percent because structured data models, automation hooks, and integration surfaces determine whether production steps stay consistent across stations. Ease of use and value each accounted for thirty percent because operators must actually work within the workflow and governance model to keep production records accurate.
Cadlink C5 set itself apart by keeping production steps synchronized through a job records-to-screen and film definition data model, and that capability lifted features and the overall performance especially for shops that need controlled automation and consistent job-to-screen data across multiple operators.
Frequently Asked Questions About Screenprinting Software
How does Cadlink C5 keep artwork intake, film, and screen setup synchronized across multiple operators?
Which tool is better for API-driven workflow transitions between order planning and the production floor?
What integration pattern works best for connecting prepress steps to proofing and output planning?
How do admin controls and change traceability differ across Screenprinting software options?
What data migration approach avoids breaking production history when moving job records into a new system?
Which platform supports governance-heavy maintenance workflows tied to presses and dryers?
When team workflows span departments, which tool best centralizes shared job data with conditional automation?
How do SSO and identity controls get handled in Microsoft Power Apps compared with general API-first tools?
What extensibility model is best for teams that need custom app logic reading and writing job and workflow data?
Why might SAi Flexi be chosen over a general work-management tool when the output format is the primary constraint?
Conclusion
After evaluating 10 art design, Cadlink C5 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
Art Design alternatives
See side-by-side comparisons of art design tools and pick the right one for your stack.
Compare art design 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.