GITNUXSOFTWARE ADVICE
Tourism HospitalityTop 9 Best Pitch Booking Software of 2026
Ranked comparison of Pitch Booking Software for booking meetings and pitch calls, with Checkfront API, Setmore, and Calendly.
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.
Checkfront API
Webhook event delivery for reservation and inventory lifecycle changes.
Built for fits when booking teams need API-backed automation with strict access control..
Setmore
Editor pickWebhook events for booking lifecycle changes for event-driven automation
Built for fits when teams need API-driven appointment scheduling and controlled availability..
Calendly
Editor pickRouting rules that assign prospects to hosts using event form answers.
Built for fits when sales teams need pitch scheduling automation with API-driven handoff to CRM..
Related reading
Comparison Table
The comparison table maps Pitch Booking software by integration depth, data model, and automation and API surface, so teams can judge how provisioning, extensibility, and throughput behave in practice. It also breaks out admin and governance controls like RBAC and audit log coverage to show how configuration, policy enforcement, and operational visibility work across providers.
Checkfront API
API integrationDeveloper API endpoints for tours, booking availability, and reservation operations that support automated integration flows.
Webhook event delivery for reservation and inventory lifecycle changes.
Checkfront API maps booking concepts into API entities that mirror operational flows like availability checks, reservation creation, and status changes. The API surface supports automation patterns with synchronous requests for reads and writes plus webhook delivery for downstream systems that must react to booking events.
A key tradeoff is the need to align internal schemas and idempotency handling with Checkfront’s booking and inventory rules. Checkfront API fits best when a team already owns an integration layer and needs controlled throughput for high-volume availability queries or reservation synchronization.
- +Documented endpoints for availability, reservations, pricing, and schedules
- +Webhook-driven automation for booking state and inventory events
- +Consistent data model reduces mapping drift across systems
- +RBAC and admin governance constrain API access by role
- –Complex schema mapping for custom fields and business rules
- –Webhook reconciliation requires idempotent consumers
- –Throughput planning needed for large availability query volume
Revenue operations teams
Sync offers and reservations across systems
Fewer reconciliation gaps
Integrations engineers
Provision inventory and availability queries
More accurate checkout
Show 2 more scenarios
Operations managers
Automate booking changes and cancellations
Lower manual admin work
Drive reservation updates via API workflows that mirror internal policies.
Partner platform teams
Expose booking operations to partners
Controlled partner access
Use RBAC-controlled API identities and webhook feeds to integrate partner channels safely.
Best for: Fits when booking teams need API-backed automation with strict access control.
More related reading
Setmore
appointment schedulingAppointment booking tool that supports scheduling rules, staff management, and integrations for booking automation in hospitality contexts.
Webhook events for booking lifecycle changes for event-driven automation
Setmore fits organizations that need controlled booking operations with consistent scheduling rules across staff members and locations. The data model centers on appointments tied to services, time windows, and team members, which makes it easier to keep downstream systems aligned. Integration depth includes calendar sync and customer notification behaviors, and the API enables schema-driven appointment operations and extensibility for custom systems.
A tradeoff appears in automation flexibility compared to tools that offer more granular workflow branching without external logic. Setmore works well when standard reminders, staff availability, and service definitions are the primary drivers, and when integrations can handle event routing via API calls or webhooks.
Admin and governance controls are geared toward multi-user scheduling administration, with role-based access to booking configuration and operational data access. Audit-friendly operation relies on the combination of API-driven changes and logging in the admin UI rather than a fully externalized policy engine.
- +API supports appointment create and update flows for external systems
- +Webhooks enable event-driven automation around booking lifecycle
- +Service and staff availability model maps cleanly to scheduling logic
- +Calendar sync reduces double-booking risk across connected calendars
- –Complex multi-step branching workflows require external orchestration
- –Some automation depends on webhook consumers rather than native rules
- –Granular governance beyond role access is limited compared with enterprise suites
Revenue operations teams
Sync appointments into CRM scheduling records
Reduced scheduling drift
Multi-location service ops
Standardize staff availability and services
More consistent booking throughput
Show 2 more scenarios
Platform integrators
Provision booking data from internal systems
Faster integration onboarding
Use the data model to programmatically create services and manage appointment state changes.
Customer support teams
Automate confirmations and reschedules
Lower manual coordination
Trigger downstream notifications from booking events and handle reschedule updates through API calls.
Best for: Fits when teams need API-driven appointment scheduling and controlled availability.
Calendly
scheduling automationMeeting scheduling automation that captures booking requests with configurable availability and integration hooks for external systems.
Routing rules that assign prospects to hosts using event form answers.
Calendly models scheduling around event types that map meeting duration, buffer rules, and form questions into a consistent data schema. Teams can connect Google Calendar and Microsoft 365 calendars so booking status reflects real availability and integrates with meeting links. Audience routing can direct prospects to specific hosts based on collected answers, including pitch stage, deal size, or region.
Automation depth is centered on webhooks, scheduling events, and an API for creating bookings and managing availability rather than multi-step workflow builders. A common tradeoff is that orchestration beyond booking often requires external automation via integration targets or the API. Calendly fits best when governance needs focus on scheduling policies and when CRM or sales systems handle follow-up tasks after webhook delivery.
- +Calendar availability sync with conflict prevention
- +Routing rules based on booking form answers
- +API and webhooks for booking events and automation
- +Admin governance for organization-level scheduling policies
- –Limited native multi-step workflow orchestration
- –Extensibility relies on external systems and API consumers
Revenue operations teams
Route pitches by segment answers
Fewer misrouted meetings
Sales enablement teams
Standardize pitch interview scheduling
More consistent handoffs
Show 2 more scenarios
Sales engineering teams
Auto-create meetings from CRM events
Lower manual coordination
The API and webhooks connect CRM triggers to booking creation and downstream tooling.
Sales team managers
Enforce availability and booking rules
Tighter scheduling governance
Admin controls restrict scheduling behavior across users and align host calendars with policy.
Best for: Fits when sales teams need pitch scheduling automation with API-driven handoff to CRM.
Square Appointments
payments schedulingScheduling and booking stack that pairs appointment capture with payment handling and operational configuration in one workflow.
Square webhooks for appointment and payment events.
Square Appointments pairs scheduling and payments with the operational structure of Square’s existing merchant ecosystem. It supports service and staff configuration, recurring availability, customer profiles, and confirmations that flow through Square notifications.
Automation centers on booking rules like deposits, rescheduling behavior, and calendar availability, with updates tied to the appointment lifecycle. Integration depth is driven by Square platform data objects and webhooks that can propagate booking events into downstream systems for provisioning and governance.
- +Square data model ties appointments to customers, staff, and payment records
- +Calendar availability settings reduce double-booking across staff and locations
- +Booking lifecycle events can trigger automation through Square webhooks
- +Admin configuration controls scheduling rules per location and staff group
- –Extensibility depends on Square APIs and available webhook event coverage
- –Fine-grained RBAC for appointment fields is limited versus enterprise scheduling suites
- –Custom data fields and schema customization are constrained by Square objects
- –High-throughput integrations may require careful event ingestion and idempotency handling
Best for: Fits when teams need Square-integrated booking workflows with controlled scheduling rules and event-driven automation.
Acuity Scheduling
webhook schedulingOnline scheduling product that supports availability rules and booking intake with automation via integrations and webhooks.
Public API and webhooks for appointment create, update, cancel, and availability synchronization.
Acuity Scheduling books appointments by collecting availability, confirmations, and intake inputs in one booking flow. It offers a scheduling data model centered on appointment types, services, locations, and event-driven booking rules that administrators can configure.
Automation includes reminders, rescheduling flows, and conditional forms that update attendee state as bookings change. Integration depth relies on a documented API and webhooks that support provisioning, synchronization, and custom routing.
- +API and webhooks support appointment lifecycle sync
- +Configurable booking rules for services, locations, and capacities
- +Intake forms attach to booking records and confirmations
- +Automation handles reminders and rescheduling state changes
- +Admin controls for appointment types and booking configuration
- –Extensive configuration can add governance overhead for large teams
- –RBAC granularity is limited compared with enterprise scheduling suites
- –Multi-location workflows require careful configuration to avoid conflicts
- –Automation logic is constrained when complex approval steps are needed
Best for: Fits when teams need API-driven booking plus webhook automation without custom scheduling infrastructure.
Genbook
appointment bookingScheduling and booking software that provides online booking flows, availability management, and operational controls for service providers.
Role-aware booking workflow states that drive confirmation and downstream automation
Genbook fits organizations that need pitch booking workflows tied to real availability, team roles, and venue or resource constraints. It centers on a structured booking data model for pitches, events, and schedules, so routing and scheduling decisions stay consistent across channels.
Automation features focus on workflow triggers like lead capture to slot selection and confirmation state changes. The key differentiator is its integration depth for calendar synchronization and operational systems via configuration and API-driven provisioning surfaces.
- +Calendar-linked scheduling reduces double-booking risk
- +Structured booking objects support consistent routing decisions
- +Workflow automations tie confirmations to operational status
- +Integration configuration supports mapping external events to internal schema
- +Automation patterns reduce manual pitch scheduling steps
- –Complex role and permission models require careful RBAC setup
- –Custom automation often depends on API and event schema mapping
- –Audit log depth can be harder to validate for every workflow step
- –High-throughput schedule changes need clear rate and queue behavior
Best for: Fits when sales ops teams need role-aware booking automation with API and calendar integrations.
Tokeet
ticket sessionsTour and activity booking and ticketing platform that schedules sessions and manages reservations with administrative tools.
Configurable booking and availability schema designed for pitch request scheduling workflows.
Tokeet is a pitch booking system that centers on a configurable booking data model for venues, availability, and creative requests. The integration approach favors workflow handoff between your intake forms, internal review process, and scheduled pitch slots.
Automation is driven by configurable rules around status changes and approvals, with an API-oriented surface for provisioning and system-to-system updates. Admin controls focus on managing access and operational governance so booking throughput stays predictable during team changes.
- +Configurable booking data model for venues, availability, and pitch requests
- +API surface supports system-to-system booking creation and updates
- +Automation rules trigger on status changes and approval milestones
- +Admin governance enables controlled access across booking workflows
- +Extensibility through configuration instead of hardcoded process steps
- –Governance depth depends on the available RBAC granularity
- –Automation relies on predefined status transitions with limited custom branching
- –Audit and reporting capabilities can require API export for advanced use cases
- –High event volumes may need careful configuration for predictable throughput
Best for: Fits when teams need controlled pitch scheduling with API-driven integration and workflow automation.
Google Calendar
excludedExcluded because a canonical domain for a distinct booking workflow was not provided, and the tool would not be a category-native pitch booking system.
Google Calendar API watch notifications for change-driven automation.
Google Calendar supports appointment-style scheduling via event types, multiple calendars, and visibility controls aligned to Google identity. Integration depth is strongest through the Google Calendar API for event CRUD, recurrence rules, conferencing links, and push notifications via channels.
Automation is driven by supported webhook-like change notifications and by managing attendees, time zones, and resource calendars in a consistent data model. Administrative governance relies on Google Workspace controls, including sharing policies, role-based access for calendar resources, and audit visibility for account and calendar activity.
- +Google Calendar API supports event CRUD, recurrence, and attendee management
- +Push notifications via watch channels reduce polling overhead
- +Resource and shared calendars support multi-location scheduling
- +Identity-based permissions align with Google Workspace RBAC patterns
- –Advanced booking workflows require external orchestration for state tracking
- –Webhooks require handling channel lifecycle and renewal
- –Custom booking forms and routing need external form or app integration
- –Timezone and recurrence edge cases often demand careful configuration
Best for: Fits when teams need calendar-native booking with strong API control and Workspace governance.
Microsoft Bookings
excludedExcluded because a canonical product URL for Microsoft Bookings without ambiguity was not provided, and the tool is not pitch booking specialist software.
Bookings integrates availability and confirmation flows directly from Exchange Online calendars.
Microsoft Bookings schedules customer appointments through a web booking page connected to business calendars. It is tightly integrated with Microsoft 365 so staff calendars and booking availability reflect Exchange Online data.
The data model centers on services, staff, time windows, and booking states, with configuration applied per location and staff membership. Automation and API extensibility are limited compared with booking systems that expose broad webhook and CRUD APIs for appointments.
- +Exchange calendar availability sync keeps scheduling aligned with staff calendars
- +Microsoft 365 identity and RBAC support role-based access for staff and admins
- +Recurring appointments and service durations reduce manual rescheduling
- +Audit-ready operational logs exist through Microsoft 365 security tooling
- –Appointment automation lacks a broad public API for booking events
- –Custom data fields and workflows are constrained to Bookings configuration
- –Multi-location governance can require careful template and assignment management
- –Throughput for large appointment volumes depends on Exchange calendar operations
Best for: Fits when Microsoft 365 tenants need appointment scheduling with calendar alignment and minimal custom automation.
How to Choose the Right Pitch Booking Software
This buyer's guide covers how to select pitch booking software that schedules pitches, manages availability, and routes leads to hosts. It compares integration depth across Checkfront API, Setmore, Calendly, Square Appointments, Acuity Scheduling, Genbook, Tokeet, Google Calendar, and Microsoft Bookings.
The guide focuses on integration breadth, the underlying booking data model, automation and API surface for provisioning flows, and admin and governance controls like RBAC and audit visibility. Each section points to concrete mechanisms in named tools so evaluation stays execution-focused.
Tools that schedule pitch meetings or pitch sessions with availability control and workflow handoff
Pitch booking software coordinates pitch intake and scheduling by turning availability rules into booked appointments, then updating that booking record through notifications, confirmations, and downstream events. It typically solves double-booking prevention, structured routing from lead inputs to a host or resource, and operational state tracking across approval or confirmation steps.
Setmore and Calendly represent appointment-style scheduling that uses availability rules plus routing and handoff logic, while Checkfront API and Acuity Scheduling represent API-led booking operations with structured objects and event-driven automation hooks.
Evaluation criteria that map pitch booking workflows to an integration-ready data model
Pitch booking becomes costly when the tool hides the booking lifecycle or forces custom fields into brittle mappings. The evaluation criteria below focus on integration depth, the data model behind availability and reservations, and the automation hooks that keep external systems consistent.
Tools like Checkfront API, Acuity Scheduling, and Square Appointments succeed when event delivery and CRUD operations cover the full appointment or reservation lifecycle. Tools like Calendly and Setmore succeed when routing and calendar sync reduce manual coordination without requiring bespoke workflow orchestration.
Lifecycle event delivery via webhooks
Event-driven automation should deliver reservation and booking lifecycle changes as discrete events. Checkfront API provides webhook-driven automation for booking state and inventory events, Setmore emits booking lifecycle webhook events, and Square Appointments triggers automation through Square webhooks for appointment and payment events.
Scheduling and availability data model that reduces mapping drift
A consistent schema for schedules, inventory or capacity, and appointment fields reduces field mapping drift when syncing multiple systems. Checkfront API uses a structured data model across availability, reservations, and pricing, and Acuity Scheduling centers booking rules around appointment types, services, locations, and capacities.
Documented API surface for booking create, update, cancel, and availability sync
Booking automation needs CRUD operations and availability synchronization to support provisioning and ongoing state reconciliation. Acuity Scheduling provides a public API and webhooks for appointment create, update, cancel, and availability synchronization, while Checkfront API exposes endpoints for availability, reservations, pricing, and schedules.
Routing logic based on pitch form inputs and host assignment
Lead and pitch answers should flow into deterministic routing so prospects reach the correct host or team. Calendly supports routing rules that assign prospects to hosts using event form answers, and Genbook and Tokeet emphasize pitch workflow states that drive confirmation and downstream automation once routing is complete.
Admin configuration controls for scheduling behavior and operational governance
Admin controls should cover service catalogs, staff or resource availability, and appointment behavior per location or team. Square Appointments provides scheduling rules per location and staff group, and Acuity Scheduling provides admin controls for appointment types and booking configuration with conditional forms that attach to booking records.
RBAC and permission granularity for API and workflow actions
Governance should limit which identities can read or write booking data and which workflow steps different users can operate. Checkfront API includes RBAC and admin governance that constrains API access by role, and Genbook uses role-aware booking workflow states that drive confirmation and downstream automation.
Decision framework for selecting the right pitch booking integration surface
Selection should start with how booking state changes must propagate into CRM, calendar systems, and internal operations. Then the evaluation should match automation requirements to the tool’s API surface and data model so updates stay consistent under throughput.
The framework below turns those needs into measurable checks across Checkfront API, Acuity Scheduling, Calendly, Setmore, Square Appointments, Genbook, Tokeet, Google Calendar, and Microsoft Bookings.
Map the pitch lifecycle to required events and states
List every state transition needed for pitches, including intake, slot selection, confirmation, rescheduling, and cancellation. Checkfront API and Setmore emphasize webhook events for reservation and booking lifecycle changes, while Acuity Scheduling includes webhooks and a public API for appointment create, update, cancel, and availability synchronization.
Verify the data model can represent capacity, services, and routing inputs
Test whether the tool models services, locations, capacities, staff or resources, and pitch-request fields as first-class schema elements. Acuity Scheduling supports appointment types, services, locations, and capacities, and Tokeet provides a configurable booking data model for venues, availability, and pitch requests.
Confirm automation and API coverage for provisioning workflows
For automated provisioning and sync, validate that the tool supports booking CRUD plus availability operations through its documented API. Checkfront API exposes schedules, inventory, pricing, availability, and reservation operations, while Square Appointments relies on Square platform objects and webhooks to propagate appointment and payment lifecycle events.
Assess governance needs for RBAC and workflow step control
If multiple internal roles operate pitches, confirm RBAC and permission controls align with operational responsibilities. Checkfront API constrains API access by role, and Genbook uses role-aware booking workflow states to drive confirmation and downstream automation.
Evaluate integration fit for calendars and meeting delivery
If pitch meetings must avoid double-booking, prioritize tools with strong calendar availability sync and conflict prevention. Calendly synchronizes calendar availability to prevent conflicts and supports routing rules based on event form answers, while Google Calendar provides API watch notifications via change-driven automation and resource calendar sharing under Workspace governance.
Which teams should choose pitch booking tools based on workflow and integration fit
Pitch booking tools fit different operational models depending on whether scheduling must be API-driven, routing must be deterministic, or governance must reflect role-based workflows. The audience segments below align tool selection with the best-fit descriptions for each named product.
Each segment focuses on concrete workflow expectations like reservation lifecycle automation, host routing from pitch inputs, calendar-linked availability, or Microsoft 365 alignment.
Booking teams that need API-backed automation with strict access control
Checkfront API fits because it exposes structured endpoints for availability, reservations, pricing, and schedules and includes RBAC that constrains API identities by role. The tool also delivers webhook event delivery for reservation and inventory lifecycle changes.
Sales teams that run pitch scheduling and need host assignment from form answers
Calendly fits because it routes prospects to hosts using event form answers and coordinates scheduling with configurable availability and routing logic. Calendly also supports API and webhooks for booking events and automation plus calendar availability sync that reduces conflicts.
Hospitality teams that schedule staff and services and want event-driven booking lifecycle automation
Setmore fits because it models service and staff availability and supports API appointment create and update flows with webhook events for booking lifecycle changes. Setmore also uses calendar sync to reduce double-booking risk across connected calendars.
Organizations using Square for payments and want booking events to trigger downstream operations
Square Appointments fits when appointment scheduling must tie directly to Square customer and payment records. Square Appointments triggers automation through Square webhooks for appointment and payment events and uses calendar availability settings to reduce double-booking across staff and locations.
Sales ops teams that require role-aware workflow states tied to confirmation and downstream automation
Genbook fits because it provides role-aware booking workflow states that drive confirmation and downstream automation. Genbook also includes structured booking objects that support consistent routing decisions across channels and calendar synchronization.
Where pitch booking implementations commonly fail across scheduling, integrations, and governance
Pitch booking failures usually show up when the integration surface does not cover the lifecycle the business needs or when governance controls do not match real operational roles. Several tools also introduce complexity when workflows require deep custom branching that the scheduling layer does not natively orchestrate.
The pitfalls below map to concrete cons found across the reviewed tools like schema mapping complexity, webhook reconciliation requirements, RBAC granularity limits, and orchestration gaps.
Choosing a tool that models bookings well but lacks full lifecycle event coverage
Teams that need automation on reschedule and cancellation should validate webhook delivery and API coverage for those states using Acuity Scheduling or Checkfront API. Tools like Google Calendar and Microsoft Bookings can require external state tracking because advanced booking workflows need external orchestration.
Underestimating webhook reconciliation work for idempotency and throughput
High event volumes require ingestion logic that can handle duplicate events and out-of-order delivery, especially with webhook-driven automation. Checkfront API calls out that webhook reconciliation requires idempotent consumers and that throughput planning is needed for large availability query volume.
Overbuilding custom rules that exceed the native workflow orchestration model
If pitch workflows need complex multi-step branching approvals, external orchestration becomes necessary because Setmore notes that complex multi-step branching workflows require external orchestration. Calendly and Acuity Scheduling also constrain automation logic when complex approval steps are needed.
Assuming fine-grained governance exists for all appointment fields and workflow steps
Tools can provide RBAC for access but limited granularity for appointment fields, which matters when different teams manage different subsets of booking data. Square Appointments and Acuity Scheduling note limited RBAC granularity compared with enterprise scheduling suites, and Genbook requires careful RBAC setup for complex role and permission models.
Relying on calendar-native booking without a pitch-specific data model
Calendar-native systems can schedule events but require external form routing and state management for pitch workflows. Google Calendar supports event CRUD and watch notifications, but custom booking forms and routing need external form or app integration.
How We Selected and Ranked These Tools
We evaluated Checkfront API, Setmore, Calendly, Square Appointments, Acuity Scheduling, Genbook, Tokeet, Google Calendar, and Microsoft Bookings using criteria grounded in integration and automation behavior, including feature coverage, ease of setting up the workflow model, and value for those capabilities. Each tool received an overall rating built from those scored categories, with features carrying the largest share of the weighting while ease of use and value each accounted for the remaining major parts.
Checkfront API separated itself from lower-ranked options because it combines documented API endpoints for availability, reservations, pricing, and schedules with webhook event delivery for reservation and inventory lifecycle changes. That combination lifted it across integration depth and automation surface coverage, which are the most predictive inputs when pitch booking must stay consistent across systems under real workflow transitions.
Frequently Asked Questions About Pitch Booking Software
Which pitch booking tools expose APIs that support event-driven automation?
How do pitch booking systems differ in how they model pitch requests versus generic appointments?
What integration choice fits teams that already standardize on Google Calendar for scheduling?
Which tools support routing logic that assigns prospects to hosts based on form answers?
What is the main tradeoff when mixing booking with payments in the same system?
How do admin controls and access governance differ across API-first tools?
Which systems are better for automation that depends on webhook status changes during the booking lifecycle?
What migration steps are common when moving pitch scheduling from spreadsheets or legacy calendars?
Which option fits teams that need calendar-native availability while minimizing custom API work?
Conclusion
After evaluating 9 tourism hospitality, Checkfront API 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
Tourism Hospitality alternatives
See side-by-side comparisons of tourism hospitality tools and pick the right one for your stack.
Compare tourism hospitality 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.