GITNUXSOFTWARE ADVICE
Food Service RestaurantsTop 10 Best Meal Software of 2026
Top 10 Meal Software ranked by features and cost fit, covering Toast POS, Square for Restaurants, and Lightspeed Restaurant for teams.
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.
Toast POS
Webhooks and APIs that emit order and check events for automation and third-party synchronization.
Built for fits when multi-location teams need governed automation across ordering, kitchen status, and reporting data..
Square for Restaurants
Editor pickSquare for Restaurants supports location-based menu, modifier, and order synchronization for kitchen routing and reporting.
Built for fits when multi-location restaurants need controlled automation with an integration-first operational data model..
Lightspeed Restaurant
Editor pickRole-based access control with audit visibility for operational and configuration changes.
Built for fits when multi-location teams need RBAC-governed automation with a structured menu data model..
Related reading
Comparison Table
This comparison table maps Meal Software tools across integration depth, data model, automation and API surface, and admin and governance controls. It highlights how each platform provisions integrations, exposes schemas, supports RBAC, and records audit logs, so tradeoffs in extensibility and configuration can be evaluated. Coverage includes POS, ordering, and delivery workflow systems, including Toast POS, Square for Restaurants, Lightspeed Restaurant, Upserve, Olo, and other commonly used options.
Toast POS
restaurant POSToast POS runs restaurant ordering, payments, KDS routing, table management, and reporting with menu and inventory control features.
Webhooks and APIs that emit order and check events for automation and third-party synchronization.
Toast POS records orders, modifiers, discounts, and kitchen states into a consistent schema that can be used across reporting and downstream systems. Integration depth is strongest when external systems need to keep menu and ordering state aligned with Toast POS and when events must be streamed via API or webhooks.
A key tradeoff is that automation and extension work tends to follow Toast POS workflows, so nonstandard data structures often require mapping into Toast POS entities like items, modifiers, and checks. Toast POS fits when a multi-location team needs controlled provisioning of users and permissions and when integrations must handle high throughput during peak service.
- +Clear operational data model for checks, modifiers, and kitchen states
- +API and webhooks support event-driven integrations with ordering workflows
- +RBAC-style user roles reduce unauthorized access to operational controls
- +Location scoping supports multi-restaurant governance and configuration separation
- –External systems may need heavy field mapping to match Toast POS entities
- –Complex custom automations often depend on specific workflow triggers
- –Automation coverage can be constrained by the event types Toast exposes
Best for: Fits when multi-location teams need governed automation across ordering, kitchen status, and reporting data.
Square for Restaurants
POS and orderingSquare for Restaurants provides restaurant POS, online ordering, KDS-style kitchen workflows, and inventory and analytics from one backend.
Square for Restaurants supports location-based menu, modifier, and order synchronization for kitchen routing and reporting.
This tool fits operations teams that need tight integration between the front-of-house register, kitchen routing, and back office reporting by location. The data model groups menu configuration, modifiers, and item availability into a structure that stays aligned when orders move from POS to kitchen screens. Inventory and reporting roll up using the same item identifiers used during order capture, which reduces mapping drift across systems. Extensibility is driven by documented integration paths that focus on order flow and operational events rather than manual exports.
A common tradeoff is that complex enterprise customizations often require careful scoping of how much menu and modifier logic is maintained in Square versus an external system. For example, if an integration provisions item catalogs frequently, the workflow must handle modifier compatibility and out-of-stock rules to avoid order rejections. The best fit appears in multi-location restaurants where throughput and governance matter, and where changes need controlled propagation across terminals and kitchen devices.
For automation, the practical value comes from event-driven synchronization and configuration of operational rules that affect order capture and downstream processing. Admin and governance controls help limit who can alter menu setup, staff access, and terminal behavior. Audit visibility supports traceability of changes during audits or incident reviews.
- +Location-scoped data model keeps menus, modifiers, and orders consistent across sites
- +Kitchen and POS workflows share item identifiers for fewer integration mismatches
- +Automation and integrations center on order and operational events
- +Role-based access supports separation between menu setup and operations staff
- +Audit visibility helps track configuration changes and staff actions
- –Highly custom menu logic can be harder to maintain across external systems
- –High-frequency catalog syncing requires careful handling of modifier and availability rules
Best for: Fits when multi-location restaurants need controlled automation with an integration-first operational data model.
Lightspeed Restaurant
restaurant POSLightspeed Restaurant centralizes POS, kitchen display workflows, online ordering integrations, and inventory and reporting for food service operations.
Role-based access control with audit visibility for operational and configuration changes.
Integration depth is driven by POS-connected data objects that map to ordering, menu, inventory, and modifier structures. Automation is exposed through an API surface that supports provisioning-related tasks like creating and syncing catalog entities and operational settings across connected systems. The data model is practical for restaurant workflows because it treats menu composition, availability, and service context as first-class entities rather than flat item lists. Admin and governance controls include RBAC and change traceability so operational configuration and user permissions can be managed with separation of duties.
A tradeoff is that deeper automation tends to require careful alignment of the external system schema with Lightspeed’s menu and modifier structures. Teams also need to validate sync rules for edge cases like partial availability, time-based promotions, and item overrides across locations. This fits usage situations where a chain or multi-venue operator needs consistent catalog and operational configuration while keeping local staff permissions constrained. It also fits integration projects that require steady throughput and deterministic updates, like inventory-driven menu availability and aggregator ordering syncs.
- +POS-first data model keeps menu, availability, and modifiers consistent across integrations
- +API supports automation for catalog syncing and operational configuration updates
- +RBAC and audit log support admin governance for staff access and change tracking
- +Multi-location configuration supports controlled rollout of shared menu and inventory logic
- –Automation needs strict schema alignment for modifiers and structured menu entities
- –Edge cases like time-based availability require testing to prevent drift between systems
Best for: Fits when multi-location teams need RBAC-governed automation with a structured menu data model.
Upserve
restaurant analyticsUpserve provides restaurant analytics, menu insights, and operational data tooling built on a POS-connected reporting workflow.
Upserve API and webhook-driven event automation for orders, menu updates, and operational changes.
Upserve focuses on restaurant back office and kitchen-facing operations connected through an integration and API surface. Its core data model organizes menu, POS mappings, orders, inventory, and operational events so automation can act on consistent schemas.
Automation and provisioning are driven by configurable workflows that support integration depth across ordering, inventory, and reporting. Admin governance centers on user permissions and operational logs so teams can monitor changes and manage access boundaries.
- +Integration depth across restaurant workflows with a documented API surface
- +Menu, order, and inventory schemas support automation from consistent entities
- +Configurable workflows reduce manual reconciliation between systems
- +RBAC-style access boundaries and audit visibility support governance
- –Automation design can require careful schema mapping across systems
- –Throughput tuning depends on integration patterns and payload design
- –Extensibility often relies on API-first development for advanced cases
- –Admin configuration can be complex when managing many locations
Best for: Fits when multi-location teams need API-driven automation with controlled RBAC and audit visibility.
Olo
online ordering orchestrationOlo powers restaurant online ordering orchestration with integration-friendly menu, ordering, and operational workflow components.
Order orchestration that applies eligibility and availability rules through the full order lifecycle.
Olo provides meal ordering and fulfillment workflows with configuration options for menu, substitutions, and eligibility. The integration depth is driven by an API surface for provisioning, order lifecycle events, and connected systems that need consistent data exchange.
Automation hinges on rule-based orchestration across availability windows, customer eligibility, and downstream routing so throughput stays predictable during peak ordering. Governance centers on RBAC controls, audit logging for administrative actions, and change management around configuration and schema-aligned integrations.
- +API supports order lifecycle events for downstream fulfillment systems
- +Eligibility and availability rules reduce manual exception handling
- +Configuration supports menu options, substitutions, and constraints
- +RBAC restricts administrative actions by role
- +Audit log captures configuration and governance changes
- –Complex eligibility rules require careful data model mapping
- –High customization increases integration testing and regression load
- –Sandbox and replay tools are limited for event-driven workflows
- –Admin configuration can be difficult to diff across environments
- –Some automation paths depend on upstream system data quality
Best for: Fits when enterprises need controlled meal workflows with deep API integration and governance.
7shifts
labor scheduling7shifts supports restaurant schedules and labor costing workflows using shift planning, time tracking integrations, and reporting.
Workflow-based shift and time-off approvals with RBAC-protected actions and audit visibility.
7shifts fits restaurant and multi-location operators that need schedule, time-off, and labor workflows wired into daily execution. The product centers a structured data model for shifts, roles, and approvals that supports automation through configurable rules and workflow triggers.
Integration depth depends on documented API and system-to-system provisioning for scheduling and staffing data, with an automation surface that works best for predictable operational events. Admin governance emphasizes role-based access controls and visibility for operational changes through auditable actions.
- +Role-based access controls for scheduling and time-off permissions
- +Configurable approval flows for shift changes and requests
- +API enables provisioning and synchronization of staffing data
- +Audit visibility for key edits to schedules and time requests
- –Automation complexity increases as approval paths multiply
- –Integration throughput can bottleneck during bulk schedule updates
- –Data model constraints limit custom non-standard staffing schemas
- –Admin oversight requires consistent role mapping across locations
Best for: Fits when multi-location teams need schedule governance with API-driven automation and clear approvals.
When I Work
shift schedulingWhen I Work delivers self-serve shift scheduling and time tracking for restaurant teams with role-based permissions and exports.
Shift-event scheduling model that drives meal-related notifications and work assignment mapping.
When I Work pairs workforce scheduling with a structured location and role data model that feeds meal workflows. The automation surface centers on shift-based assignments, notifications, and worksite coverage so meal requests can align to staffing events.
Integration depth is strongest when the API can map these entities into downstream meal inventory, ordering, or approval systems. Admin governance relies on role-based access controls and audit-style operational visibility for changes and approvals.
- +Shift-linked meal workflows reduce mismatch between staffing and meal requests
- +Entity-first data model with locations, roles, and schedules supports predictable integrations
- +API-driven configuration supports provisioning and synchronized downstream systems
- +Role-based access controls narrow admin actions by user function
- –Automation depends on scheduling events, not free-form workflow triggers
- –Complex approval chains require careful mapping to the available states
- –Data model coverage can lag behind specialized meal operations and exceptions
- –Throughput for batch synchronization depends on the integration strategy
Best for: Fits when multi-site teams need scheduling-driven meal workflows with controlled admin access.
HotSchedules
workforce managementHotSchedules manages restaurant workforce schedules with labor tracking workflows and manager dashboards for staffing decisions.
Location-based scheduling with rules that automatically update staffing assignments.
HotSchedules centers its meal operations around scheduling workflows tied to workforce staffing, inventory inputs, and menu planning constraints. Its value shows up in integration breadth through partner ecosystem support and published interfaces for exchanging production, labor, and calendar data.
The data model aligns schedules, locations, and assignment rules so automation can propagate changes with controlled impact. Admin controls focus on governance for multi-location rollouts using role-based access, configuration settings, and change visibility.
- +Strong integration depth with meal and labor scheduling workflows
- +Data model maps schedules to locations and assignment rules
- +Automation propagates configuration changes across planning artifacts
- +RBAC supports role separation across administrators and operators
- –API surface depends heavily on supported endpoints and partners
- –Automation rules can require careful configuration for large rollouts
- –Sandbox and test harness coverage for custom integrations is limited
- –Audit log granularity may be insufficient for strict compliance needs
Best for: Fits when multi-location meal teams need scheduled labor orchestration with controlled governance and integrations.
Kounta
inventory and accountingKounta handles restaurant and hospitality inventory, accounting workflows, and purchase and receiving processes in one system.
Event-driven API endpoints for syncing order and catalog changes with external systems.
Kounta provides meal management workflows for hospitality teams through configurable order, menu, and inventory states. The integration depth centers on its API surface for syncing catalog data and operational events with external systems.
Its data model supports structured entities like products and availability, enabling automation based on changes to those entities. Admin governance includes role-based access control and audit logging to track configuration edits and operational actions.
- +Documented API supports catalog and availability synchronization with external systems
- +Configurable data model ties products to availability and inventory states
- +Automation triggers can react to order and operational status changes
- +Role-based access control limits permissions across admin and operators
- +Audit logs track changes to configuration and operational actions
- –Complex automations require careful schema mapping across integrated systems
- –High-throughput syncs depend on consistent event ordering from external sources
- –RBAC granularity may not match every custom job-role workflow
- –Some admin tasks rely on UI configuration instead of API-first provisioning
Best for: Fits when hospitality teams need API-driven menu and order workflows with controlled admin access.
inFlow Inventory
inventory managementinFlow Inventory manages restaurant and food inventory counts, purchase tracking, and reorder planning with multi-location support.
Inventory movement ledger tied to receiving and adjustments for auditable stock state changes.
inFlow Inventory fits organizations that need tighter integration between inventory, purchasing, and restaurant operations with controlled data changes. The system uses a structured data model for items, locations, stock movements, and receiving so workflows can be automated around consistent records.
Automation depends on configurable rules and repeatable workflows rather than custom code, and it exposes integration paths through its API surface for provisioning and data sync. Admin and governance controls focus on managing access and auditability for operational changes across multiple locations.
- +Structured inventory data model supports consistent stock movement tracking
- +API surface enables programmatic item and location provisioning
- +Configuration-driven workflows reduce manual receiving and stock adjustments
- +Multi-location inventory controls align operations to the correct stock pools
- –API breadth for advanced schema extensions can be limited
- –Complex automation can require careful workflow configuration
- –Admin governance features like RBAC granularity may not cover every edge case
- –Throughput and rate limits for heavy sync jobs can constrain migrations
Best for: Fits when multi-location food operators need inventory control with integration and automation.
How to Choose the Right Meal Software
This guide covers meal software tooling patterns across Toast POS, Square for Restaurants, Lightspeed Restaurant, Upserve, Olo, 7shifts, When I Work, HotSchedules, Kounta, and inFlow Inventory.
It focuses on integration depth, the underlying data model, and automation plus API surface areas that determine how reliably orders, inventory, scheduling, and kitchen workflows stay in sync.
Meal workflow software that connects ordering, fulfillment, inventory, and staffing records
Meal software coordinates operational records for orders and kitchen execution, or for upstream feeds like menu catalogs, inventory movements, and scheduling events. Toast POS and Square for Restaurants show how a consistent check and modifier data model can power reporting, kitchen routing, and transaction-linked workflows.
Teams use these tools to reduce manual reconciliation between systems by relying on integrations that emit operational events and accept configuration through defined schemas, rather than copying spreadsheets between tools.
Evaluation criteria built around integration, schema governance, and automation control
Integration depth matters when orders, menu catalogs, and inventory states must stay aligned across POS, kitchen workflows, delivery partners, and reporting tools. Toast POS, Square for Restaurants, and Lightspeed Restaurant emphasize structured entities that support automation and synchronization across sites.
Admin and governance controls determine whether integrations can change configuration safely and whether staff permissions restrict access to operational actions. Tools like Lightspeed Restaurant, Upserve, and Olo combine RBAC controls with audit visibility to support controlled changes to workflows and eligibility rules.
Event-driven automation via API and webhooks for order and check lifecycle
Toast POS publishes webhooks and APIs that emit order and check events for third-party synchronization. Upserve extends that same event pattern into menu updates and operational changes, which reduces manual polling when throughput spikes.
Location-scoped data model for menu, modifiers, and operational records
Square for Restaurants keeps menus, modifiers, and orders consistent per location so kitchen routing and reporting use the same item identifiers. Toast POS adds location scoping for governance separation across multi-restaurant teams.
RBAC permissions and audit visibility for configuration and operational edits
Lightspeed Restaurant ties role-based access controls to audit visibility for both operational changes and configuration updates. Upserve and Olo provide RBAC-style boundaries plus operational logs so administrative actions remain traceable.
Eligibility and availability rule engines tied to the order lifecycle
Olo applies eligibility and availability rules across the full order lifecycle so downstream systems receive fewer exceptions. This approach helps maintain predictable throughput during peak ordering when substitutions and constraints must be enforced consistently.
Workflow-based approvals and scheduling governance tied to operational states
7shifts and When I Work support shift-event models where workflow triggers and approvals protect scheduling edits. HotSchedules uses rules to update staffing assignments per location, which reduces mismatch between planned labor coverage and meal operations that depend on staffing.
Inventory state modeling with auditable stock movement ledgers
inFlow Inventory tracks inventory movement through receiving and adjustments so stock state changes remain auditable. Kounta similarly supports product and availability entities with event-driven API endpoints for syncing catalog and operational changes.
Pick the right meal platform by mapping your workflows to its data model and automation surface
Start by listing the operational flows that must integrate without drift. Toast POS and Square for Restaurants excel when ordering, kitchen routing, and reporting must share a structured schema for checks, modifiers, and kitchen states.
Then verify that the tool offers an API and automation surface aligned to the events that matter for those flows. Upserve and Olo show how order lifecycle events and webhook-driven triggers reduce reconciliation work when systems change frequently.
Match your core workflow to a tool with a compatible operational schema
Choose Toast POS when the organization needs check-level ordering structures and kitchen routing states with event emission for downstream systems. Choose Square for Restaurants when location-based menu and modifier synchronization drives consistent kitchen routing and item-level reporting across sites.
Confirm the automation events your integrations require are actually exposed
If integrations depend on order and check events, prioritize Toast POS because its standout feature is webhooks and APIs that emit those events. If automation includes menu updates and operational changes beyond orders, Upserve provides API and webhook-driven event automation.
Define governance boundaries using RBAC and audit visibility
Pick Lightspeed Restaurant when RBAC and audit visibility for operational and configuration changes are needed for multi-location staff separation. Pick Olo when eligibility rules require governed admin actions captured through audit logging and RBAC-protected configuration changes.
Evaluate rule complexity and testability for availability and timing edge cases
Choose Olo when eligibility and availability rules are central to how orders should be accepted and routed through the full lifecycle. Choose Lightspeed Restaurant with time-based availability testing if availability logic uses time windows that can drift across systems.
Align scheduling and approvals to meal workflows that depend on staffing events
Select 7shifts or When I Work when meal-related workflows should attach to shift assignments and approval states rather than free-form triggers. Select HotSchedules when location-based scheduling rules must automatically update staffing assignments used by meal planning and production.
For inventory-first requirements, validate stock movement and catalog sync modeling
Choose inFlow Inventory when auditable inventory movement ledgers tied to receiving and adjustments are the control point for operational changes. Choose Kounta when API-driven syncing of products and availability entities must react to order and catalog changes.
Which meal software buyers benefit from these integration and governance traits
Different teams need different integration anchors, like order events from POS systems or inventory and scheduling feeds that upstream meal operations consume. The best fit depends on whether the organization needs governed automation across ordering and kitchen execution, or governed state changes across labor and stock records.
The tools listed below map to those needs using their best-for profiles.
Multi-location operators that need governed ordering-to-kitchen automation
Toast POS and Square for Restaurants fit when location-scoped menu and modifier synchronization must drive kitchen routing and reporting with RBAC-style controls around operational changes. Toast POS adds webhooks and APIs that emit order and check events for third-party synchronization.
Teams building API-driven orchestration across menu, orders, and operational updates
Upserve fits when workflow automation must act on consistent menu, order, and inventory schemas through a documented API surface. Olo fits when orchestration must apply eligibility and availability rules across the full order lifecycle.
Multi-location teams that need RBAC-governed configuration changes with audit traceability
Lightspeed Restaurant fits when admin governance requires RBAC plus audit visibility for operational and configuration changes. Upserve and Olo also match when administrative actions must be monitored through operational logs and audit capture.
Organizations where staffing approvals and shift events drive meal-related workflow timing
7shifts and When I Work fit when workflow triggers depend on scheduling events, shift assignments, notifications, and approvals. HotSchedules fits when location-based scheduling rules automatically update staffing assignments across planning artifacts.
Hospitality and food operators that center control on inventory movements and catalog availability entities
inFlow Inventory fits when stock movement ledgers tied to receiving and adjustments must be auditable across locations. Kounta fits when event-driven API endpoints must sync product and availability entities as order and catalog changes occur.
Failure patterns that cause integration drift, governance gaps, and automation brittleness
Meal software projects commonly fail when integration assumptions do not match exposed event types or the schema differences between systems. Tools like Toast POS and Square for Restaurants can require heavy field mapping when external systems do not use compatible entity shapes for checks, modifiers, and kitchen states.
Governance mistakes also appear when roles and audit expectations are not mapped to the available RBAC and audit log granularity in the selected tool.
Assuming all automation needs will be covered by the same set of exposed events
Toast POS supports order and check event automation through webhooks and APIs, but complex custom automations may depend on specific workflow triggers. When event coverage is unclear for a workflow, Upserve’s broader order and menu update automation can reduce the need for polling.
Treating catalog and modifier synchronization as a simple copy process
Square for Restaurants and Lightspeed Restaurant can require careful handling of modifier and availability rules during high-frequency catalog syncing. Structured menu entities and modifier alignment reduce drift, but time-based availability logic needs testing to prevent inconsistencies.
Designing admin permissions without validating RBAC and audit visibility granularity
Lightspeed Restaurant provides RBAC plus audit visibility for operational and configuration changes, which supports change tracking. Kounta can log configuration and operational actions, but RBAC granularity may not match every custom job-role workflow, so role mapping needs a concrete authorization plan.
Building meal workflows on scheduling events that do not match the tool’s approval model
7shifts and When I Work focus on shift-based assignments and approvals, so free-form workflow triggers are harder to implement than scheduling-driven paths. If automation needs broad trigger coverage beyond schedule states, HotSchedules partner ecosystem support and published interfaces may be a better fit.
How We Selected and Ranked These Tools
We evaluated Toast POS, Square for Restaurants, Lightspeed Restaurant, Upserve, Olo, 7shifts, When I Work, HotSchedules, Kounta, and inFlow Inventory on features and ease of use with value as a third axis. Each tool received a weighted overall rating where features carried the most weight at 40%. Ease of use and value each accounted for the remaining share at 30% each, so integration depth and automation surface mattered most.
Toast POS separated itself from lower-ranked tools by combining webhooks and APIs that emit order and check events with a clear operational data model for checks, modifiers, and kitchen states. That event emission lifted both integration breadth and control depth because event-driven automation can start from the same structured entities that drive kitchen execution.
Frequently Asked Questions About Meal Software
Which meal software products provide webhook and event feeds for order and check state changes?
How do location-based data models differ between Toast POS, Square for Restaurants, and Lightspeed Restaurant?
What tools support RBAC with audit visibility for configuration and operational changes?
Which meal software is best for API-driven provisioning of meal workflows tied to eligibility and availability rules?
How does each platform handle menu and modifier updates without breaking downstream systems?
What are the common admin control tradeoffs between restaurant POS platforms and workforce-first scheduling tools?
Which tools connect meal operations to labor and worksite coverage so meal requests match staffing?
What options exist for inventory movement traceability and auditable stock state changes?
Which meal software best supports multi-system integrations by exposing a consistent data schema for automation?
What setup and data migration concerns typically appear when adopting these platforms for multi-location operations?
Conclusion
After evaluating 10 food service restaurants, Toast POS 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
Food Service Restaurants alternatives
See side-by-side comparisons of food service restaurants tools and pick the right one for your stack.
Compare food service restaurants 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.