GITNUXSOFTWARE ADVICE
Transportation LogisticsTop 10 Best Maritime Software of 2026
Top 10 Maritime Software ranked by features and tradeoffs for operators and freight teams, with examples including MarineTraffic, Windward, CargoSphere.
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.
MarineTraffic
Vessel track and voyage context via API responses used to build ETA and route-progress analytics.
Built for fits when maritime teams need API-based vessel tracking integration with controlled automation around positions..
Windward
Editor pickRule-driven workflow automation tied to maritime voyage and operational status events.
Built for fits when maritime teams need governed automation tied to voyage and ETA event streams..
CargoSphere
Editor pickSchema-driven shipment and document workflow automation controlled through RBAC and audit logging.
Built for fits when mid-size logistics teams need governed workflow automation with schema-backed API integrations..
Related reading
Comparison Table
The comparison table maps maritime software tools across integration depth, focusing on API surface, automation hooks, and how each system provisions data into a shared schema. It also compares data model choices plus admin and governance controls such as RBAC, audit logs, and configuration boundaries, with notes on extensibility and operational throughput.
MarineTraffic
AIS trackingProvides global ship tracking with AIS target visualization, voyage and port insights, and operational analytics for maritime stakeholders.
Vessel track and voyage context via API responses used to build ETA and route-progress analytics.
MarineTraffic functions as a maritime data provider that returns vessel positions, voyage context, and historical track information for operational dashboards. The underlying data model is typically organized around vessels and movements, which makes it suitable for correlating port activity, route progress, and schedule variance. Integration depth is strongest when deployments rely on its API for continuous polling or event-driven enrichment of internal systems. Extensibility tends to flow through configuration and external application logic rather than in-product workflow authoring.
A concrete tradeoff is that automation depth depends on the API endpoints and data availability for the specific entity types needed for a given workflow. Real-time alerting can be limited by polling cadence and the service’s throughput for high-volume queries across many vessels. A common usage situation is creating watch-center dashboards that compute ETA deltas from positional tracks and trigger incident workflows in downstream systems.
- +API-driven access to vessel positions, voyages, and historical tracks
- +Data model fits monitoring use cases tied to vessels and movement states
- +Works well for automation that enriches internal systems and maps
- –Workflow automation is mostly external via API and custom logic
- –High-volume polling can strain throughput and require careful rate control
- –Governance controls depend on external identity mapping for API usage
Best for: Fits when maritime teams need API-based vessel tracking integration with controlled automation around positions.
Windward
Maritime analyticsDelivers maritime analytics that combine satellite imagery and vessel movement data to support weather routing, compliance, and operational visibility.
Rule-driven workflow automation tied to maritime voyage and operational status events.
Windward fits teams that need maritime-specific data modeling rather than generic process tracking. The system centers vessel, voyage, and operational status entities and applies rules to keep downstream steps aligned with schedule and event changes. Configuration supports schema-driven provisioning so integrations can map external feeds into consistent internal fields.
Automation and API surface are strongest when throughput is driven by repeated operational events, such as new voyage legs, schedule updates, or ETA adjustments. A common tradeoff is that schema design and rule configuration require deliberate upfront modeling to avoid rigid mappings later. This approach works best when onboarding new data sources must be controlled through admin governance and repeatable configuration.
Admin and governance controls support RBAC and audit log visibility for changes to configuration, rules, and access. This helps when multiple teams manage different routes or ports and need traceability for who altered workflows and when.
- +Maritime-focused data model for vessels, voyages, and operational status
- +Schema-driven provisioning for consistent integration mapping
- +Rule-based automation that reacts to schedule and event changes
- +RBAC with audit logs for configuration and access traceability
- –Upfront schema and rule design is required to prevent rigid mappings
- –Integration success depends on accurate external field normalization
Best for: Fits when maritime teams need governed automation tied to voyage and ETA event streams.
CargoSphere
freight opsProvides maritime freight forwarding and shipping management workflows with digital booking, tracking, and document handling.
Schema-driven shipment and document workflow automation controlled through RBAC and audit logging.
CargoSphere is distinct for combining a logistics data model with workflow automation that can be governed through RBAC and audit logs. The schema approach keeps shipment entities, parties, events, and documents in a consistent structure that supports automation rules and integration mapping. This reduces re-keying effort when provisioning new lanes, ports, or business units that require the same underlying workflow logic.
A key tradeoff is that deeper configuration and schema alignment require upfront setup to keep automation rules consistent across document types and event taxonomies. CargoSphere fits best when teams need documented API integration and predictable workflow automation across multiple stakeholders like dispatch, documentation, and compliance.
- +Configurable shipment and document data schema improves integration mapping consistency
- +Rule-driven automation reduces manual workflow steps across events and document handling
- +API-first integration supports wiring carrier feeds into internal tools
- +RBAC and audit logs support governance for multi-team operations
- +Configuration-driven provisioning supports repeatable lane and port onboarding
- –Schema and rule setup demand careful upfront alignment across document types
- –Automation correctness depends on event taxonomy and mapping quality from integrations
- –Complex organizations may need extra admin time to manage RBAC boundaries
Best for: Fits when mid-size logistics teams need governed workflow automation with schema-backed API integrations.
Shipamax
chartering workflowRuns an online booking and vessel management workflow for dry bulk and shipping logistics with chartering and voyage planning functions.
API-driven workflow provisioning that ties operational events to document and status transitions.
Shipamax centers maritime operations on a structured data model for vessels, voyages, and documents tied to execution steps. Integration depth comes from an automation surface that supports workflow provisioning, status-driven updates, and API-first extensibility for downstream systems.
The automation layer maps operational events into configurable actions, reducing manual rekeying across planning, execution, and document control. Admin and governance controls focus on role-based access and operational visibility through traceable changes and activity history.
- +Event-driven workflow steps tied to vessel and voyage records
- +API surface supports automation and extensibility for external systems
- +Document model links attachments to operational execution states
- +Role-based access controls support governed operations across teams
- –Automation flexibility depends on schema and workflow configuration constraints
- –Deep third-party integration breadth may require custom API mapping
- –Complex governance scenarios can need careful RBAC modeling
- –Document workflows can require standardized metadata conventions
Best for: Fits when maritime teams need governed automation with an API-first integration surface.
VesselsValue
market intelligenceProvides vessel market data and valuation analytics to support maritime commercial decisions and portfolio analysis.
Schema-driven vessel valuation outputs that support automated ingestion into reporting and workflow systems.
VesselsValue calculates vessel and fleet market values and feeds valuation outputs into maritime workflows. The system supports structured vessel data as a repeatable schema that can be consumed by other tooling.
Integration depth centers on exports, data mapping, and API-style access for automated provisioning into downstream applications. Admin and governance capabilities focus on controlled access to valuation datasets, configuration of views, and traceability of changes through operational logs.
- +Valuation outputs come with consistent vessel identifiers for downstream mapping
- +Data schema supports repeatable market value calculations by vessel and time
- +Exports and integration interfaces support automation into reporting tools
- +Configuration controls help standardize datasets across teams
- –Automation surface can require custom mapping to match internal data models
- –Governance features around RBAC scope are harder to validate without documentation review
- –Audit trail granularity may not cover every configuration change event
- –Throughput limits for bulk valuation updates are not clearly surfaced
Best for: Fits when operations and analytics teams need automated, schema-driven vessel valuations and controlled dataset access.
Navis
terminal operationsSupports terminal and port logistics operations with planning and control capabilities for shipping operations and throughput management.
Schema-driven workflow configuration with RBAC and audit-ready activity logging.
Navis targets maritime operators that need structured digital processes tied to vessel, berth, and port operations. The core value comes from a governed data model that maps operational objects into configurable workflows and exposes those workflows through documented integrations and API surface.
Automation can be orchestrated via provisioning controls and role-based access, with audit-ready activity trails for operational governance. Extensibility focuses on schema-driven configuration so system behavior can change without reworking downstream systems.
- +Object-based data model for vessels, port assets, and operational events
- +Configuration-driven workflows reduce custom code for common operational flows
- +API surface supports integration depth with external planning and execution systems
- +RBAC and governance controls support role separation across operations and admins
- –Schema changes require careful governance to avoid workflow breakage
- –Automation rules can be complex when multiple operational variants overlap
- –Integration projects often need dedicated design work for data mapping
- –Admin setup demands clear ownership across ports, users, and operational entities
Best for: Fits when maritime teams need governed automation and an API-first integration model across operations units.
TradeWinds Software
operations suiteProvides maritime operations and logistics tools for vessels, voyages, bookings, charters, and commercial workflows.
Schema-driven workflow provisioning that ties maritime entities to automation steps via an API.
TradeWinds Software focuses maritime-specific workflows with an integration-first approach that pairs a defined data model with documented schema-driven provisioning. Its automation surface supports API-style configuration for onboarding, document handling, and operational data flows that can be routed through controlled workflows.
Administrative governance centers on RBAC-style access boundaries and traceable changes via audit logging for operational events. Integration depth is emphasized through extensibility points that connect maritime data objects, task states, and partner interactions into repeatable automation.
- +Maritime data model maps operations, documents, and statuses into a consistent schema
- +API-oriented configuration supports automation without UI-only steps
- +Admin controls support RBAC-style permissions and separation across roles
- +Audit logs capture operational changes for governance and incident review
- +Extensibility points allow workflow additions without rebuilding core processes
- –Complex schema setup can slow onboarding for teams without integration engineers
- –Automation throughput depends on workflow design and queue behavior
- –RBAC granularity may require careful role modeling for mixed stakeholder groups
- –API surface breadth can require multiple endpoints to cover a single workflow
Best for: Fits when maritime teams need governed automation driven by a stable schema and API.
SeaRates
freight marketplaceRuns a freight booking and rate request workflow for ocean cargo with visibility into shipping quotes and shipment statuses.
SeaRates API with schema-driven event ingestion for governed automation across shipment lifecycles.
SeaRates focuses on maritime data integration and workflow automation across shipment and trade processes. The core value is the data model and schema mapping needed to normalize carrier, port, route, and event fields for downstream systems.
Its API and extensibility surface support automation and provisioning workflows, which reduces manual reconciliation between operational tools. Admin and governance controls like RBAC scoping and audit logging matter for multi-team throughput and traceability.
- +Maritime-focused data model for schema mapping across carriers, ports, and events
- +Documented API supports automation for provisioning and operational workflows
- +Extensibility via configuration enables adding fields without rebuilding pipelines
- +Audit logging improves traceability for data and workflow changes
- +RBAC supports team-level access control for shared integrations
- –Integration depth depends on available field coverage in provided schemas
- –Automation requires upfront configuration of mappings and event semantics
- –Admin controls may be limited for fine-grained workflow permissions
- –Throughput tuning can become complex when syncing high-frequency updates
Best for: Fits when maritime teams need API-driven integration and governed automation across multiple systems.
ShipServ
maritime procurementSupports procurement and marketplace workflows for maritime buyers and suppliers with digital sourcing and transaction tooling.
Supplier and catalog provisioning tied to structured schemas for buyer-trading-partner document exchange.
ShipServ runs maritime commerce and supplier onboarding workflows by exchanging standardized procurement and tender data between buyers and ship suppliers. Its integration depth is driven by a structured data model for catalog, services, and transactional documents, paired with provisioning for partner access.
Automation and API surface support order, status, and document exchange flows that reduce manual reconciliation across trading partners. Admin and governance controls focus on managing supplier data changes, partner permissions, and operational traceability for high-volume exchange.
- +Partner onboarding centers on structured supplier and catalog data schemas
- +Document and transactional exchanges support higher throughput than email workflows
- +API-driven integration reduces manual status and exception reconciliation
- +Governance workflows control supplier provisioning and partner access scope
- +Audit-friendly operational record supports data change traceability
- –Schema alignment work is required to map internal systems to ShipServ models
- –Automation coverage depends on enabled trading-partner message types
- –Admin operations can become complex with many suppliers and permission changes
- –Workflow configuration requires strong process ownership to avoid drift
Best for: Fits when procurement networks need controlled onboarding and API-based document exchange at scale.
Flexport
freight operationsOperates an ocean freight management workflow for shipment execution with tracking, documentation, and customs support tooling.
Event and status synchronization API tied to shipment milestones for automated downstream workflow updates.
Flexport fits logistics teams that need deep integration between shipment operations, carrier-facing workflows, and internal systems through a documented API and event-driven automation. Its data model maps shipment, order, and logistics milestones into structured entities designed for schema-driven provisioning and downstream system synchronization.
Automation and API surface support workflow actions, status updates, and operational triggers that reduce manual handoffs across planning and execution. Admin and governance controls focus on managing access, operational visibility, and traceability through auditable operational activity.
- +Shipment and milestone schema supports consistent status synchronization across systems
- +API-driven workflow actions reduce manual coordination across departments
- +Extensibility supports connecting carrier and internal tools through consistent data entities
- +Governance features include RBAC and auditability for operational changes
- –Integration depth requires strong internal data modeling and mapping discipline
- –Automation depends on event quality, so inconsistent inputs can create workflow noise
- –Complex shipping edge cases can require custom orchestration beyond standard workflows
- –Operational visibility and audit trails may require careful permission configuration
Best for: Fits when teams need schema-driven provisioning and API automation across shipment operations.
How to Choose the Right Maritime Software
This buyer’s guide covers maritime software tools built around tracking, voyage and shipment workflows, documentation, and partner or terminal operations. It walks through MarineTraffic, Windward, CargoSphere, Shipamax, VesselsValue, Navis, TradeWinds Software, SeaRates, ShipServ, and Flexport.
Evaluation priorities focus on integration depth, the data model and schema shape, automation and API surface, and admin plus governance controls like RBAC and audit logs.
Maritime software built to normalize operations data into governed workflows
Maritime software typically converts vessel, voyage, shipment, port, or partner events into a structured data model with rules that drive automation and downstream synchronization. MarineTraffic turns AIS positions and voyage context into track and route-progress signals through API-driven access.
Windward, CargoSphere, and SeaRates focus on schema-driven workflow automation that ties operational status or event streams to governed actions. These tools serve maritime operations teams, logistics workflow teams, procurement networks, and terminal or port operators that must integrate external data and keep audit-ready change history.
Integration depth, data model fit, and governed automation mechanics
Integration depth is judged by how the tool exposes vessel positions, voyage status, shipment milestones, or partner documents through an API surface that supports automation. MarineTraffic emphasizes API-driven retrieval for vessel positions and historical tracks, which suits enrichment pipelines.
Data model fit determines whether integrations stay stable when events change, especially for voyage, shipment, document, and supplier entities. Windward, CargoSphere, and Navis emphasize schema-driven provisioning and configuration controls with RBAC and audit logging so admin teams can trace configuration and access changes.
API-driven access to vessel tracks, voyages, and route context
MarineTraffic provides API responses that combine vessel track and voyage context used for ETA and route-progress analytics. This supports internal monitoring systems that need consistent positional and voyage signals without relying on UI scraping.
Schema-driven provisioning for stable integration mapping
Windward provisions rule automation tied to voyage and operational status events through configurable schemas. CargoSphere and Navis also emphasize schema-backed onboarding and configuration so teams can wire integrations to a repeatable shipment, document, or operational object model.
Rule-based event automation tied to maritime status changes
Windward automates workflows using rule-driven logic connected to voyage and operational status events. TradeWinds Software and Shipamax also connect maritime entities to automation steps by provisioning workflow actions from a stable schema.
RBAC and audit logs for configuration and access traceability
CargoSphere and Navis combine RBAC boundaries with audit-ready activity trails so admin teams can govern access across teams and operational entities. Windward similarly pairs RBAC with audit trails to support oversight for port, route, and team configuration changes.
Document and milestone linkage to operational execution states
Shipamax links attachments and documents to execution states through an event-driven workflow model. Flexport similarly maps shipment and logistics milestones to structured entities so API-driven workflow actions and status updates stay synchronized.
Extensibility via configuration and integration endpoints
SeaRates extends automation through configuration-driven field mapping and schema-driven event ingestion for shipment lifecycles. ShipServ supports supplier and catalog provisioning through structured schemas that drive buyer-trading-partner document exchange at scale.
A decision path for integration depth, automation surface, and governance depth
Start by defining the integration object that must stay consistent, like vessel tracks, voyage events, shipment milestones, or supplier catalog records. MarineTraffic fits when the primary automation input is vessel position and voyage context delivered through API responses.
Next, validate whether the tool’s data model and schema provisioning reduce mapping churn as events evolve. Windward, CargoSphere, Navis, and TradeWinds Software focus on schema-driven provisioning paired with RBAC and audit logging so admin teams can control changes safely.
Map the core operational object to the tool’s data model
If the operational object is AIS movement and voyage context, MarineTraffic provides a vessel and voyage-centered model with positional tracks used for ETA and route-progress analytics. If the operational object is shipment and documents, CargoSphere and Shipamax center shipment, documents, and status-driven workflow steps in a structured schema.
Verify the API surface matches the automation triggers needed
Choose MarineTraffic when automation depends on API-driven vessel positions, voyages, and historical tracks that feed internal enrichment and alerting rules. Choose Windward or SeaRates when automation depends on rule-driven ingestion of voyage or shipment lifecycle events into governed workflows.
Check schema and rule setup effort against the team’s mapping discipline
Windward requires upfront schema and rule design to avoid rigid mappings, so internal field normalization quality becomes a gating factor. SeaRates and Flexport also depend on event quality for automation signal integrity, so inconsistent inputs can create workflow noise.
Evaluate governance controls through RBAC and audit logging boundaries
CargoSphere and Navis support RBAC and audit-ready activity trails so admin teams can trace operational changes and access scope across ports or operations units. Windward also pairs RBAC with audit trails for configuration oversight across ports, routes, and teams.
Confirm document and milestone linkage for end-to-end workflow continuity
If execution requires documents to move with operational execution states, Shipamax links attachments and documents to execution steps through event-driven workflow mechanics. For shipment execution across departments, Flexport ties shipment milestones to status synchronization via event and status APIs.
Stress-test integration throughput needs against how the tool is consumed
MarineTraffic can require careful rate control under high-volume polling, so automation throughput planning matters for large fleets. SeaRates and ShipServ also involve high-frequency syncing or high-volume partner operations, so validate that queue behavior and field mapping can keep up with operational event rates.
Which maritime teams gain control depth from these tools
Different Maritime Software tools concentrate on different integration objects like vessel tracks, voyage events, shipment milestones, supplier provisioning, or port operations. Picking the wrong object focus leads to schema mismatch and rework across mappings and workflow rules.
The audience segments below match the tools’ stated best fit based on whether their automation is API-driven, schema-driven, or both, and on how governance is handled for multi-team operations.
Maritime operations teams integrating vessel tracking into internal monitoring
MarineTraffic fits teams that need API-based vessel tracking integration with controlled automation around positions because its API responses deliver vessel track and voyage context used for ETA and route-progress analytics.
Logistics and compliance teams automating workflows from voyage and ETA event streams
Windward fits teams that need governed automation tied to voyage and ETA event streams because it uses rule-driven workflow automation connected to voyage and operational status events with RBAC and audit trails.
Freight forwarding and multi-team document workflow operations
CargoSphere fits mid-size logistics teams that need governed workflow automation with schema-backed API integrations because it combines configurable shipment and document schemas, rule-driven automation, and RBAC with audit logging.
Terminal and port operators standardizing execution workflows across assets and events
Navis fits teams that need governed automation and an API-first integration model across operations units because it uses an object-based data model with configuration-driven workflows plus RBAC and audit-ready activity logging.
Procurement networks onboarding suppliers for partner document exchange at scale
ShipServ fits procurement networks that need controlled onboarding and API-based document exchange at scale because it provisions supplier and catalog data via structured schemas and supports higher-throughput transactional exchanges than email workflows.
Common integration and governance failures with maritime workflow tools
Integration failures usually come from mismatching the operational object to the tool’s data model, then underestimating how much schema and rule setup drives automation correctness. Workflow failures also occur when governance controls rely on external identity mapping that is not designed upfront.
The pitfalls below reflect the observed cons across MarineTraffic, Windward, CargoSphere, Shipamax, Navis, TradeWinds Software, SeaRates, ShipServ, and Flexport.
Treating automation as something the tool will handle without external orchestration
MarineTraffic relies on external automation logic driven by API access, so high-value alerting and enrichment pipelines still require external rule engines and rate control. Shipamax also ties automation flexibility to schema and workflow configuration constraints, so expecting out-of-the-box orchestration for every execution variant leads to manual patching.
Skipping upfront schema and event taxonomy alignment
Windward requires upfront schema and rule design to prevent rigid mappings, so inconsistent event field normalization can break rule behavior. CargoSphere and SeaRates depend on event taxonomy and mapping quality, so weak semantics for document types or lifecycle events creates automation that fires incorrectly.
Assuming auditability and RBAC are self-contained without identity design
MarineTraffic governance controls depend on external identity mapping for API usage, so auditability can be incomplete if identity-to-usage mapping is not designed. CargoSphere and Navis provide RBAC and audit trails, but complex RBAC boundary modeling still requires careful role design for multi-team operations.
Underestimating throughput and queue behavior under high-frequency updates
MarineTraffic can strain throughput under high-volume polling, so automation throughput planning and rate control must be part of implementation. SeaRates and TradeWinds Software also show automation throughput sensitivity to workflow design and queue behavior, so event bursts can stall or create backlog if mappings are not tuned.
Choosing a tool that fits the workflow but not the document or milestone linkage
Shipamax ties attachments and documents to execution states, so skipping that linkage requirement causes document handoff drift. Flexport focuses on milestone and status synchronization via shipment milestones and event-driven APIs, so attempting the workflow without consistent milestone quality creates workflow noise.
How We Selected and Ranked These Tools
We evaluated and scored MarineTraffic, Windward, CargoSphere, Shipamax, VesselsValue, Navis, TradeWinds Software, SeaRates, ShipServ, and Flexport across features, ease of use, and value, then used an overall rating where features carried the most weight at 40 percent while ease of use and value each accounted for 30 percent. Each tool was credited for integration depth via its named API and automation surface, scored for the practicality of its vessel, voyage, shipment, document, supplier, or milestone data model, and assessed for governance strength through RBAC and audit logging.
MarineTraffic set the ranking at the top because it delivers vessel track and voyage context through API responses that enable ETA and route-progress analytics, and that capability lifted its features factor more than tools that focus primarily on workflow configuration or analytics views.
Frequently Asked Questions About Maritime Software
How do MarineTraffic and SeaRates differ for API-based vessel and event integration?
Which tools provide schema-driven workflow provisioning for governed automation?
What SSO and RBAC controls are typically used for admin governance across maritime workflows?
How does data migration work when moving from spreadsheets or legacy systems into a structured data model?
What extensibility options exist if partner integrations must be added without reworking downstream systems?
How do audit logs and traceability show up in day-to-day operations and troubleshooting?
Which tool fits rule-driven automation driven by voyage and schedule changes?
What integration surface is best when external systems must receive structured shipment milestones and status updates?
When procurement needs standardized onboarding exchanges, how do ShipServ and other shipment tools compare?
Conclusion
After evaluating 10 transportation logistics, MarineTraffic 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
Transportation Logistics alternatives
See side-by-side comparisons of transportation logistics tools and pick the right one for your stack.
Compare transportation logistics 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.