GITNUXSOFTWARE ADVICE
Construction InfrastructureTop 10 Best 3D Plumbing Design Software of 2026
Ranked picks for 3D Plumbing Design Software used in plumbing workflows, with comparisons covering AutoCAD MEP, Revit MEP, and Navisworks.
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.
AutoCAD MEP
MEP routing with connected pipe and fitting objects that update dependent geometry.
Revit MEP
Editor pickRevit API event hooks and element/parameter schema access for plumbing automation and validation.
Navisworks
Editor pickClash Detective with configurable rules, saved clash sets, and tolerance-based evaluation.
Related reading
Comparison Table
This comparison table evaluates 3D plumbing design tools by integration depth, including how each platform maps BIM and CAD objects into its data model and schema. It also compares automation and API surface for tasks like rules-based drawing generation, clash workflows, and batch updates, plus admin and governance controls such as RBAC and audit logs. Readers can use the results to assess provisioning, extensibility, configuration, and model throughput tradeoffs across AutoCAD MEP, Revit MEP, Navisworks, Civil 3D, and other platforms.
AutoCAD MEP
MEP BIM CADAutoCAD MEP provides 3D MEP piping and plumbing modeling with smart objects, duct and pipe tools, and layout workflows for construction infrastructure designs.
MEP routing with connected pipe and fitting objects that update dependent geometry.
AutoCAD MEP supports 3D plumbing routing by modeling pipes and components as MEP objects rather than plain solids. That data model carries connectivity behavior for layout changes, and it supports typical outputs like 2D views, annotation, and reports derived from model content. Integration is strongest when the project workflow uses Autodesk document management and coordination patterns, because the MEP objects map cleanly to CAD-centric deliverables.
A tradeoff appears in large multi-team programs where strict governance and cross-team schema control require custom standards and disciplined template usage. Teams typically hit friction when mixing MEP models authored with different catalog content and property naming conventions, because mapping rules must be defined for consistent quantities and schedules. It fits work where a single team can enforce configuration through templates, library definitions, and repeatable routing parameters.
- +MEP object data model keeps pipe connectivity and routing consistent
- +3D plumbing authoring supports downstream 2D views and annotations
- +Autodesk workflow integration fits CAD-to-document pipelines
- +Templates and standards enable repeatable plant layout production
- –Governance across multiple teams needs strong template and library discipline
- –Cross-system data mapping can require manual property and catalog alignment
- –Automation depends on available scripting and API coverage for MEP objects
- –Catalog variation can fragment quantities and schedules without normalization
Best for: Fits when mid-size teams need visual workflow automation without code.
More related reading
Revit MEP
Parametric BIMRevit supports 3D plumbing and MEP system modeling with parametric families, routing, and coordinated documentation for building infrastructure drawings.
Revit API event hooks and element/parameter schema access for plumbing automation and validation.
Revit MEP is a 3D plumbing design tool that represents pipes, fixtures, and systems inside one Revit database with parameterized connectivity and system composition. The automation surface includes the Revit API for custom commands, event handlers, and model inspection, plus Dynamo for scripted geometry and parameter updates. Integration depth is driven by Revit add-ins that can control fabrication-ready outputs and enforce standards through shared parameters and consistent element schemas.
A common tradeoff is that automation logic and governance usually live inside the Revit environment, so throughput for large batches depends on API performance patterns and modeling conventions. Teams use it when plumbing routing, system classification, and coordinated changes must stay consistent across disciplines with minimal translation. External data exchange can still work, but it typically adds mapping work for schema alignment and parameter naming across tools.
- +Unified MEP data model keeps pipe networks and parameters consistent
- +Revit API supports element-level automation, event-driven logic, and custom exports
- +Dynamo enables repeatable parametric edits tied to Revit elements
- –External workflow throughput depends on model round-trips and translation mapping
- –Governance often requires disciplined shared parameter and schema conventions
Best for: Fits when teams need API-driven plumbing routing control with a single source BIM model.
Navisworks
Model reviewNavisworks enables coordinated 3D clash detection and model review across discipline exports so plumbing designers can validate routing and clearances.
Clash Detective with configurable rules, saved clash sets, and tolerance-based evaluation.
Navisworks centralizes building information from tools commonly used in plumbing design, including IFC, Revit, and many CAD formats, into a unified model database for viewpoint navigation and property lookup. Clash detection is configurable with saved clash sets and tolerance settings, and results can be exported for downstream issue tracking. Time-based simulation can use linked timelining inputs to validate construction sequence against spatial constraints.
A key tradeoff is that Navisworks is not an authoring tool for plumbing geometry or schema management, so edits must be made upstream in the source design tools and then re-imported for analysis. This approach fits when teams need repeatable clash rules and property-based checks across frequent coordination model refreshes.
- +Unifies multiple model formats into one queryable scene graph
- +Rules-based clash detection with saved sets and tolerance control
- +.NET API enables property extraction and automated reporting pipelines
- +Command-line workflows support batch review and export at scale
- –Geometry and schema edits require round-trips to upstream authoring tools
- –Large federated models can slow viewpoint navigation and clash runs
Best for: Fits when plumbing teams need repeatable coordination checks with API-driven automation.
More related reading
Civil 3D
Infrastructure CADCivil 3D models underground utilities and infrastructure workflows that support piping and trench-related design activities in construction projects.
Civil 3D API for custom pipe network creation and property enforcement across large projects
Civil 3D is an Autodesk design authoring environment that anchors 3D plumbing layouts in a civil-aligned data model. It supports workflows that connect pipes, profiles, and alignments through Civil 3D objects, with integration to Autodesk design tools and common GIS formats.
Automation is available via a published API surface that fits add-ins and scripted batch edits, enabling repeatable modeling steps for catalog-driven assets and network creation. Admin and governance rely on Autodesk account controls plus standard add-in deployment patterns that support RBAC via user permissions and audit-oriented operational controls.
- +Civil 3D object model links alignment, profile, and pipe network geometry
- +API and add-ins support repeatable plumbing layout automation at modeling time
- +Works with Autodesk references to coordinate plumbing design with civil context
- +Schema-driven properties help keep fittings, sizes, and naming consistent
- –Plumbing-specific automation needs custom rules for many project standards
- –Automation throughput can drop when regenerating large networks frequently
- –Cross-tool data exchange can require template mapping to keep schema aligned
- –Governance depends on Autodesk permission setup and add-in deployment discipline
Best for: Fits when civil teams need automated plumbing networks driven by alignments and profiles.
Allplan Engineering
Engineering CADAllplan Engineering provides 3D design for building engineering systems with tools for routing and documentation that support plumbing-oriented construction detailing.
Engineering model integration for coordinated 3D plumbing with multidiscipline clash and publishing workflows.
Allplan Engineering produces coordinated 3D plumbing routing and modeling linked to building data, including support for clash checking workflows. The core value is integration depth through an engineering data model used for coordination across disciplines and deliverables.
Automation depends on how Allplan exposes publishing, attribute handling, and project configuration to external workflows, since extensibility hinges on available APIs and integration points. Admin and governance coverage is geared toward project-level control, with auditability and RBAC typically determined by how the underlying Allplan collaboration and document management are configured.
- +Multidiscipline coordination through shared building model data
- +Attribute-driven plumbing elements support structured documentation
- +Works with downstream clash checking and model publication workflows
- +Project configuration supports repeatable engineering setups
- –API surface for external automation is not clearly centered on plumbing-specific schema
- –Custom automation often depends on publisher and workflow integration limits
- –Governance details like RBAC and audit log granularity may require deeper setup
- –Automation and extensibility may be harder without documented end-to-end hooks
Best for: Fits when teams need shared model plumbing coordination with controlled, repeatable engineering configurations.
AVEVA Engineering
Engineering platformAVEVA supports 3D plant and piping design workflows for plumbing-like pipe routing and engineering data management in infrastructure projects.
AVEVA Engineering model governance with controlled attribute schema across 3D piping and plumbing workflows.
AVEVA Engineering is most suitable for engineering teams that need deep integration into an existing AVEVA ecosystem for 3D piping and plumbing design. Its practical value comes from a governed data model that keeps design intent consistent across models, attributes, and downstream engineering outputs.
Automation and extensibility depend on integration with AVEVA APIs and configuration patterns used by the broader platform, with schema control and repeatable provisioning being central to rollout. Admin focus centers on RBAC-style access boundaries, auditability of changes, and configuration management that supports multi-team throughput.
- +Data model supports disciplined attributes across 3D piping and plumbing deliverables
- +Integration depth aligns with AVEVA ecosystems for consistent design intent
- +Extensibility options support automation tied to the platform’s schema
- +Admin controls support RBAC-style access boundaries across engineering roles
- –Automation often requires platform-specific knowledge of AVEVA configuration patterns
- –API coverage is strongest within AVEVA-managed workflows rather than ad hoc design edits
- –Schema changes can require coordinated governance to avoid downstream mismatches
- –Deployment and admin setup can be heavy for teams without platform integration
Best for: Fits when enterprises need governed 3D plumbing design aligned to an AVEVA-integrated delivery chain.
More related reading
SmartPlant 3D
3D piping CADSmartPlant 3D enables detailed 3D piping and piping isometric generation with engineering structure and coordination features.
Schema-driven piping object attributes that propagate into isometrics and fabrication-oriented outputs.
SmartPlant 3D centers on deep integration with AVEVA E3D and engineering data structures used in plant design workflows. Its data model emphasizes classed piping objects with attribute schemas that map to isometrics, BOMs, and fabrication views.
Automation and extensibility depend on an API surface intended for configuration, bulk edits, and model-driven generation across design tasks. Admin governance focuses on project-level control, role-based access, and auditability for model changes in shared environments.
- +Strong model integration with AVEVA design ecosystems and downstream deliverables
- +Attribute-driven data model maps cleanly to piping specs, BOMs, and isometrics
- +Automation hooks support repeatable design generation at model scope
- –Automation depth can require AVEVA-specific knowledge of its schema and commands
- –Change management is heavy in multi-discipline shared models
- –API coverage for niche plumbing drafting edits can be limited
Best for: Fits when plumbing design teams need AVEVA-native integration, governed access, and automation at model scale.
Tekla Structures
Construction modelingTekla Structures supports 3D construction modeling and fabrication-ready detailing that can be used to coordinate embedded services and plumbing-related constraints.
Tekla Model Sharing coordinates concurrent piping model edits with project-level shared model control.
Tekla Structures is a BIM authoring and modeling system used for piping and routing when projects need a shared model governed by configurable standards. Its data model centers on parametric objects, rules, and templates that persist across disciplines through coordinated exchanges.
Integration depth is driven by Tekla Model Sharing and established export workflows, while automation typically relies on the Tekla automation environment rather than an external, model-less scripting layer. Extensibility and governance are handled through configuration management, model permissions controls, and audit-friendly operational practices around model access and change history.
- +Parametric piping objects support rule-based routes and fittings
- +Model Sharing supports multi-user coordination on shared model state
- +Automation surface enables add-ons that work against Tekla objects
- +Configuration and templates persist modeling standards across projects
- –Automation and API workflows require strong knowledge of Tekla object models
- –Schema alignment for external BIM tools can add mapping effort
- –Admin governance for large orgs depends on process and deployment discipline
- –Throughput for heavy assemblies can be constrained by workstation specs
Best for: Fits when coordinated BIM piping needs deep object-level automation and controlled templates.
More related reading
SketchUp
3D modelingSketchUp provides interactive 3D modeling workflows with a large plumbing modeling ecosystem via extensions for conceptual and coordination-level designs.
Ruby extension API for custom modeling tools and procedural creation of plumbing routing geometry.
SketchUp performs interactive 3D modeling for plumbing geometry, fittings, and routing layouts within a single drawing workspace. Its data model relies on a scene graph of geometry entities and components, with exports that preserve scale and object structure for coordination.
Integration is driven mainly through a plugin ecosystem and file-based interchange, not through a first-party plumbing schema or hosted API. Automation options come from Ruby-based extensions and scripted import or export workflows, with limited admin and governance controls for teams.
- +Component system supports reusable plumbing parts and consistent placements
- +Ruby scripting enables custom tools for geometry generation and batch edits
- +Plugin ecosystem covers modeling, import, and export workflows for coordination
- –Data model lacks plumbing-specific schema for validated equipment relationships
- –Limited RBAC and audit logging features for multi-user governance
- –Automation surface is largely file and plugin based, not a hosted plumbing API
Best for: Fits when teams need flexible 3D plumbing layouts with plugin-driven automation, not governed data modeling.
Creo
Parametric CADCreo supports parametric 3D component modeling for plumbing fittings and custom piping hardware used in construction infrastructure coordination.
PLM-linked assembly and part configuration that preserves plumbing routing consistency through revisions.
Creo, from PTC, fits teams that already run PLM and CAD ecosystems and need plumbing-aware design within that data model. It connects 3D routing workflows to shared product definitions, using PTC integration paths rather than isolated drawing-only output.
Creo’s automation surface supports API-driven configuration and scripted change control, which helps keep plumbing parts and assemblies consistent across projects. Governance is shaped by how Creo integrates with PTC’s broader administration features, including role-based access and traceability through managed work states.
- +Deep integration with PTC CAD and PLM data models
- +Consistent component definitions across assemblies and revisions
- +Automation supports scripted configuration and repeatable routing tasks
- +Extensibility via documented PTC developer interfaces
- –Plumbing-specific schema depth depends on installed configuration
- –Integration breadth requires planning across CAD, PLM, and workflow tools
- –Automation coverage can be constrained by licensing and module selection
- –Admin controls rely on the surrounding PTC governance setup
Best for: Fits when engineering teams need plumbing design tied to controlled PLM data and scripted changes.
Conclusion
After evaluating 10 construction infrastructure, AutoCAD MEP 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.
How to Choose the Right 3D Plumbing Design Software
This buyer’s guide covers AutoCAD MEP, Revit MEP, Navisworks, Civil 3D, Allplan Engineering, AVEVA Engineering, SmartPlant 3D, Tekla Structures, SketchUp, and Creo for 3D plumbing design workflows.
The focus stays on integration depth, the underlying data model, automation and API surface, and admin and governance controls across design authoring, coordination, and downstream outputs.
3D plumbing design tools that model pipe networks with connectivity, routing, and downstream documentation outputs
3D plumbing design software creates model objects for pipes, fittings, and fixtures and keeps routing rules tied to a plumbing-aware data model so documentation can reflect the 3D network.
Tools like AutoCAD MEP and Revit MEP keep connectivity and parameter behavior inside the modeling environment so changes propagate to dependent geometry and view outputs.
Teams typically use these tools to produce coordinated routing models for construction infrastructure and building services and to reduce rework when discipline exports, clash checks, and schedules must stay consistent.
Evaluation criteria for integration, plumbing data schemas, and automation governed by roles and audit trails
Integration depth determines whether a tool can act as the system of record for plumbing objects or whether teams must rely on file exchange and manual mapping.
Automation and API surface determine whether pipe-routing validation, attribute extraction, and batch clash reporting can run consistently at model scale rather than as repeated manual steps.
Connectivity-native pipe and fitting objects
AutoCAD MEP excels at connected pipe and fitting objects where dependent geometry updates when routing changes. Revit MEP also maintains connectivity through its unified MEP data model so element-level parameters stay consistent across views and exports.
Plumbing data model schema control with parametric behavior
Revit MEP anchors plumbing design to a shared BIM data model with constraint behavior and access to element and parameter schema. SmartPlant 3D and AVEVA Engineering focus on classed piping objects and governed attribute schemas that propagate into isometrics and fabrication outputs.
Documented automation surface through API and scripting hooks
Revit MEP provides Revit API event hooks and element or parameter schema access for plumbing automation and validation. Navisworks offers a .NET API and command-line workflows for batch viewpoint generation, property extraction, and automated issue outputs.
Coordination and clash detection governed by rules and saved sets
Navisworks includes Clash Detective with configurable rules, saved clash sets, and tolerance-based evaluation to keep plumbing clearance checks repeatable. Allplan Engineering supports coordinated 3D plumbing routing with clash checking and model publication workflows tied to an engineering data model.
Civil or plant network generation tied to alignments and model structures
Civil 3D supports custom pipe network creation and property enforcement across large projects through its API and add-ins tied to alignments and profiles. SmartPlant 3D integrates schema-driven piping attributes into BOMs and isometrics so engineering structure and coordination stay aligned.
Admin and governance controls for multi-team model access and change traceability
AVEVA Engineering centers on RBAC-style access boundaries, auditability of changes, and configuration management for multi-team throughput. Tekla Structures uses model sharing with project-level shared model control and relies on configuration and permissions for audit-friendly operational practices.
Decision framework for picking the right 3D plumbing design tool based on integration depth and governance needs
Start with the system that must own the plumbing truth for routing and parameters. Then validate whether its API and automation surface can execute routing validation, extraction, and coordination at batch scale.
Finally, confirm the governance path for access control, audit log alignment, and schema discipline, because every manual mapping step increases risk when models scale.
Choose the plumbing model authority: authoring tool versus coordination reviewer
AutoCAD MEP and Revit MEP work best when plumbing routing and plumbing object data must be authored and kept consistent inside a single environment. Navisworks fits best when coordination requires a unified scene graph for repeatable clash detection and model review across discipline exports.
Validate the plumbing data model that controls connectivity and parameter behavior
If connected routing updates must stay inside the object model, AutoCAD MEP’s connected pipe and fitting objects are built for dependent geometry updates. If schema control and element or parameter access drive automation, Revit MEP’s unified MEP data model and Revit API event hooks support validation logic.
Confirm the automation and API surface matches the workflow scale
For automated reporting and batch coordination outputs, Navisworks provides .NET APIs and command-line workflows for property extraction and issue output generation. For plumbing routing automation tied to BIM elements, Revit MEP supports Dynamo and the Revit API for event-driven logic and custom exports.
Match network generation requirements to the tool’s native structural context
If piping must be driven by civil alignments and profiles, Civil 3D supports API-driven custom pipe network creation and property enforcement across large projects. If engineering outputs like isometrics and fabrication views must come from governed piping attributes, SmartPlant 3D and AVEVA Engineering align piping object attributes to downstream deliverables.
Set governance expectations for RBAC, permissions, and audit traceability
For multi-team access boundaries and change traceability inside a governed ecosystem, AVEVA Engineering provides RBAC-style access boundaries and auditability of changes. Tekla Structures relies on model sharing and project-level shared model control and uses configuration and permissions to support audit-friendly operational practices.
Plan for integration friction when combining tools across schemas
When multiple environments feed the workflow, Navisworks can review heterogeneous formats but geometry and schema edits still require upstream round-trips. AutoCAD MEP and Revit MEP can both face cross-system mapping effort for property and catalog alignment when schedules and quantities must match across authoring tools.
Teams that benefit most from specific 3D plumbing design tool architectures and governance models
Different tools optimize for different integration paths and different points where control must be enforced.
The best match depends on whether connectivity and plumbing schemas must be authored in one place or validated and coordinated across a federated set of models.
Mid-size plumbing design teams that need routing automation without code
AutoCAD MEP fits teams that need visual workflow automation through connected pipe and fitting objects with dependent geometry updates and repeatable plant layout via templates and standards.
Building services teams building a single source BIM model for parametric routing control
Revit MEP fits teams that want an API-driven plumbing routing control loop with event hooks and element and parameter schema access so automation can validate parameters and generate view outputs.
Coordination groups that must run clash detection at scale across discipline exports
Navisworks fits plumbing teams that need repeatable clearance checks using Clash Detective with configurable rules, saved clash sets, tolerance-based evaluation, and API or command-line automation for batch review.
Civil infrastructure teams that must drive plumbing networks from alignments and profiles
Civil 3D fits civil teams that need automated plumbing network creation tied to civil context because its API and add-ins support custom pipe network creation and property enforcement across large projects.
Enterprises that require governed attribute schemas and audit-ready change traceability
AVEVA Engineering fits enterprises aligned to an AVEVA-integrated delivery chain because it supports governed attribute schemas, RBAC-style access boundaries, auditability of changes, and configuration management for multi-team throughput.
Failure modes that create rework in plumbing model governance, automation, and coordination
Many selection and rollout failures come from mismatches between the plumbing data model, the automation surface, and the governance expectations.
The following pitfalls show up repeatedly when teams combine tools or attempt automation without validating schema and access constraints.
Treating coordination tooling as a substitute for plumbing authoring control
Navisworks is built for clash detection and model review with batch automation, not for plumbing schema edits, so routing and connectivity changes still require round-trips to upstream authoring tools like AutoCAD MEP or Revit MEP.
Skipping schema discipline for shared parameters, attributes, and catalogs
Revit MEP depends on disciplined shared parameter and schema conventions for governance, and AutoCAD MEP can require manual property and catalog alignment to keep cross-system quantities and schedules consistent.
Automating around geometry instead of the plumbing object model
Automation succeeds when it can access element and parameter schema through Revit MEP or use .NET APIs and property extraction through Navisworks, while geometry-only approaches in tools like SketchUp rely on file and plugin behavior rather than validated plumbing schema.
Assuming automation throughput will hold for large networks without regeneration planning
Civil 3D automation can slow when regenerating large networks frequently, and Tekla Structures can constrain throughput for heavy assemblies on workstation resources.
Underestimating governance setup work across multi-team environments
AVEVA Engineering and Tekla Structures both require governance and configuration discipline for RBAC and audit traceability, while Allplan Engineering governance and RBAC granularity can require deeper configuration to reach the expected control depth.
How We Selected and Ranked These Tools
We evaluated AutoCAD MEP, Revit MEP, Navisworks, Civil 3D, Allplan Engineering, AVEVA Engineering, SmartPlant 3D, Tekla Structures, SketchUp, and Creo using three scoring lanes that emphasized features, ease of use, and value, with features carrying the most weight and ease of use and value carrying equal weight. Each tool received an overall rating as a weighted average that favors plumbing-relevant capabilities like connected routing objects, plumbing schema control, and API-driven automation. This ranking reflects editorial research across the provided feature descriptions, automation and API hooks, standout coordination mechanisms, and the reported governance focus for multi-team operations.
AutoCAD MEP separated from lower-ranked tools because it combines an MEP object data model with routing that uses connected pipe and fitting objects to update dependent geometry, and that capability lifted the features and ease-of-use outcomes for a mid-size team workflow where repeatable plant layout production matters most.
Frequently Asked Questions About 3D Plumbing Design Software
Which tool is best for connected 3D plumbing objects that update documentation automatically?
How do Revit MEP and AutoCAD MEP differ for API-driven plumbing routing automation?
What is the role of Navisworks when plumbing design teams need clash detection and batch outputs?
Which software supports automated plumbing networks driven by civil alignments and profiles?
How do Tekla Structures and Revit MEP handle shared-model coordination for piping and routing?
What integration path fits enterprises that already standardize on an AVEVA delivery chain?
How do SmartPlant 3D and AVEVA Engineering differ for schema-driven piping attributes and downstream views?
Can SketchUp support API-style extensibility for 3D plumbing tasks with a team workflow?
What admin controls and audit signals matter when multiple teams share plumbing models?
How should teams plan data migration when moving plumbing models between different authoring tools?
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
Construction Infrastructure alternatives
See side-by-side comparisons of construction infrastructure tools and pick the right one for your stack.
Compare construction infrastructure 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.