Commissioned Research
Top 10 Best Song Request Software of 2026

GITNUXSOFTWARE REVIEW

Entertainment & Events

Top 10 Best Song Request Software of 2026

Editorial roundup comparing song request software for karaoke venues, with tradeoffs noted for Rockbot and related options.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Song request software tools manage guest submissions, queue ordering, and live playback decisions for DJs and licensed venues. This comparison helps operators weigh automation, data model fit, and integration paths against workflow friction, including mobile request handling and singer or host rotation.

Kanto Karaoke is the best pick for venues that need moderated song requests, because its venue-first approval workflow keeps the DJ-facing queue clean during peak guest demand, whereas Rockbot fits licensed SMB venues that want catalog-matched requests with request history visibility for smoother queue operations.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Kanto Karaoke

Venue-first approval workflow that keeps the DJ-facing queue clean during peak guest demand.

Best for: Fits when venues need moderated song requests that stay stable across mobile and tabletop entry points.

2

PCDJ Karaoki

Editor pick

Request-to-play pipeline designed around karaoke hosting, including queue state visibility for the DJ operator.

Best for: Fits when karaoke venues need fast DJ queue polling with curated moderation.

3

Rockbot

Editor pick

Request handling couples catalog-matched picks to DJ-facing queue operations and ongoing request history visibility.

Best for: Fits when venues need fast guest requests with DJ visibility and explicit moderation controls.

Comparison Table

1
Kanto KaraokeBest overall
vertical specialist
9.0/10
Overall
2
vertical specialist
8.7/10
Overall
3
8.6/10
Overall
4
8.5/10
Overall
5
vertical specialist
8.0/10
Overall
6
vertical specialist
7.9/10
Overall
7
7.6/10
Overall
8
7.3/10
Overall
9
vertical specialist
6.8/10
Overall
10
vertical specialist
6.6/10
Overall
#1

Kanto Karaoke

vertical specialist

Karaoke player software for Windows and Mac with singer management and song queue capabilities.

9.0/10
Overall
Features9.0/10
Ease of Use9.0/10
Value9.0/10
Standout feature

Venue-first approval workflow that keeps the DJ-facing queue clean during peak guest demand.

Kanto Karaoke manages a guest-facing song request flow and routes requests to a DJ view with venue-controlled approval. It supports tabletop and mobile entry points with status updates that help keep the request queue synchronized during live sessions.

Administrative tooling focuses on moderation, request timing behavior, and queue visibility so staff can correct mistakes before songs hit the DJ display. Kanto Karaoke also supports setlist-style exports for after-session reporting and operational follow-up.

Pros
  • +DJ queue delivery is designed around rapid selection and handoff during sets
  • +Moderation controls help prevent inappropriate or unwanted requests entering rotation
  • +Setlist export output supports operational reporting after live sessions
  • +Multi-device entry points reduce bottlenecks at busy tables
Cons
  • –Webhook event delivery and API depth are not a primary focus for advanced automation
  • –Advanced routing like multi-room prioritization needs careful configuration discipline
  • –Queue governance features can require staff training for consistent approvals
  • –Duplicate request deduplication rules are limited compared with heavier platforms
Use scenarios
  • Venue staff and event operators

    Approve and queue guest requests

    Moderated show control

  • Small venues and independent DJs

    Sequence locally stored karaoke library

    Quicker song selection

Show 2 more scenarios
  • Karaoke venue hosts and DJs

    Manage singers and playback timing

    More orderly transitions

    Hosts coordinate request order, playback timing, and audience lyrics through an operator workflow.

  • Home performers and small teams

    Prepare custom karaoke tracks

    Custom practice versions

    Users reduce vocals, adjust pitch and tempo, sync lyrics, and create karaoke files from source media.

Best for: Fits when venues need moderated song requests that stay stable across mobile and tabletop entry points.

#2

PCDJ Karaoki

vertical specialist

Windows-based karaoke hosting software with singer rotation, song search, and request queue management.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Request-to-play pipeline designed around karaoke hosting, including queue state visibility for the DJ operator.

PCDJ Karaoki is built around a live guest request queue that feeds a DJ-facing display for polling and selection during sets. The product includes configuration for filtering and approval behavior, plus operational logs that track what was requested and when it entered the workflow. Spotify and Apple Music integration support helps map requests to tracks without relying on manual ID entry for every song.

A key tradeoff is that karaoke-focused request workflows can feel more structured than generic DJ song request boards, especially for venues that want SMS keyword routing or per-table rate limiting. Karaoki fits best for karaoke-heavy nights where the DJ or host regularly polls the queue and needs fast transitions from request to playing.

Pros
  • +Karaoke-oriented request workflow maps cleanly to live DJ polling
  • +Spotify and Apple Music catalog matching reduces manual song lookup
  • +Request history and queue visibility help staff resolve disputes
  • +Moderation controls support venue-specific approval behavior
Cons
  • –Karaoke-first workflow can be rigid for non-karaoke DJ request nights
  • –External guest channels like SMS shortcodes are not the core path
  • –Deep automation and API extensibility are limited compared with custom stacks
  • –Multi-room routing and venue capacity enforcement need careful configuration
Use scenarios
  • Karaoke bar operators

    Host polls queue between songs

    Fewer missed requests

  • Mobile DJ entertainers

    Multi-night events need consistent workflow

    Lower lookup time

Show 2 more scenarios
  • Venue managers

    Control what appears on DJ screens

    More consistent guest experience

    Moderation configuration supports clear rules for which requests enter the play queue.

  • Karaoke staff and bartenders

    Resolve request disputes from logs

    Faster resolution

    Request history provides traceability for what was submitted and how it progressed.

Best for: Fits when karaoke venues need fast DJ queue polling with curated moderation.

#3

Rockbot

SMB

Business music streaming platform with a patron-facing song request feature for licensed venues.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Request handling couples catalog-matched picks to DJ-facing queue operations and ongoing request history visibility.

Rockbot fits venues that need a structured guest request flow, because it combines guest interfaces, a DJ-facing display, and a request history that keeps operators aligned during busy service. The Spotify integration and Apple Music API help translate text requests into catalog matches, which improves turnaround when guests request current or niche tracks. The governance story emphasizes approval controls and moderation logic, which matters when explicit content rules must be enforced.

A key tradeoff is that Rockbot is optimized for venue-style deployments rather than highly custom fan experiences, so teams that want deep bespoke queue logic may hit limits without product configuration. It is a strong fit when a radio host or DJ runs frequent set changes and needs predictable request handling with minimal live interruptions.

Pros
  • +DJ-facing display aligns requests with what is playing in real time
  • +Spotify integration and Apple Music API improve request-to-catalog matching
  • +Moderation and approval controls support explicit content policy enforcement
  • +Request history logging helps operators audit guest demand
Cons
  • –Queue customization is limited compared with fully custom request services
  • –Catalog matching depends on provider availability for edge-case requests
Use scenarios
  • Bar operators and venue managers

    Manage guest requests during peak hours

    Fewer interruptions during service

  • Mobile DJs

    Run consistent requests across gigs

    Tighter set pacing

Show 1 more scenario
  • Radio hosts and streaming teams

    Feed live queue decisions from venues

    Faster on-air selection

    A shared request flow helps hosts see what guests want without manual handoffs.

Best for: Fits when venues need fast guest requests with DJ visibility and explicit moderation controls.

#4

DJ Intelligence

SMB

Online event tools for DJs including a guest music request system for weddings and private events.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Request workflow configuration that combines catalog matching with staff approval to keep the DJ queue policy-compliant.

DJ Intelligence centers on a request queue that serves both back-end moderation and front-end DJ visibility, so staff can manage throughput while DJs poll for new items. The configuration supports allowlist-style governance via approval flows and content rules, which helps venues enforce brand-safe playback. Catalog matching reduces friction by turning user-entered search into structured request candidates that are easier to accept or reject.

Pros
  • +Venue moderation workflow routes requests with consistent rule enforcement
  • +Request history logging supports later operational review
  • +Streaming catalog matching reduces manual searching during live traffic
  • +DJ-facing queue design supports fast polling during active sets
Cons
  • –Catalog matching can degrade with imprecise song titles from requesters
  • –Complex approval rules can add extra operator steps during peak hours
Use scenarios
  • Radio operations teams

    Moderate requests during live broadcasts

    Lower misplays during on-air hours

  • Live event staff

    Maintain brand-safe playback across DJs

    Consistent set alignment

Show 1 more scenario
  • Community radio volunteers

    Handle high request volume efficiently

    Fewer manual follow-ups

    Staff can triage incoming requests using structured queue routing and history tracking.

Best for: Fits when venues need moderated song requests with fast DJ visibility and logged history.

#5

TouchTunes

vertical specialist

Digital jukebox platform letting bar and restaurant patrons request and pay for songs via a mobile app.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

DJ-facing display routing tied to a moderated guest request queue for real-time set control.

TouchTunes focuses on venue-based music requesting with a guest request queue that DJs can use through on-site displays. Requests move through moderation controls such as allowlist-based approval and profanity filter options, which help venues keep content aligned with local standards.

Pros
  • +Venue guest request queue designed for high-traffic on-site use
  • +Allowlist moderation and profanity filter reduce off-policy requests
  • +DJ-facing display supports operational flow during live sets
  • +Request history log and exportable reporting support venue operations
Cons
  • –Multi-room routing and capacity enforcement require tighter venue planning
  • –Automation and API extensibility are limited compared with developer-first tools
Use scenarios
  • Bar and club venue staff

    Moderate guest song queue at the bar

    Cleaner content on the floor

  • DJs running multi-song sets

    Select next songs from queue display

    Faster in-set song selection

Show 1 more scenario
  • Events operations coordinators

    Export request history for reporting

    Actionable post-event records

    Operations teams pull request history reports after the event for review and follow-up workflows.

Best for: Fits when venues need moderated, display-driven song requests for DJs and live events.

#6

RequestBox

vertical specialist

Online song request software for DJs with guest submissions and queue management.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Venue-first moderation that blocks guest submissions until approval rules release them into the DJ queue.

RequestBox processes audience song requests through a hosted interface and venue-ready displays, with queue management built around real-time polling. The system supports request intake via multiple front ends, plus moderation gates for approving or rejecting items before they reach the DJ view.

Pros
  • +DJ queue updates via polling behavior for low-latency request visibility
  • +Moderation flow separates guest submission from what reaches the DJ-facing display
  • +Request history supports audits and post-event troubleshooting
  • +Setlist-style export supports downstream reporting workflows
Cons
  • –Catalog matching and filtering can require tuning to avoid noisy candidates
  • –Operational governance needs ongoing moderation for busy venues
  • –Multi-room routing is limited compared with larger request suites
  • –Webhook event delivery coverage appears less complete than API-first competitors
Use scenarios
  • Event venues

    Approve queue items before DJ view

    Reduced off-limits songs

  • DJs on live sets

    Manage real-time next-song queue

    Smoother in-set decisions

Show 2 more scenarios
  • Operations and promoters

    Review request history after events

    Better event recap reporting

    Teams review request history and export setlist-style reports for post-action review.

  • Programming staff

    Filter DJ list using catalog matching

    Consistent DJ queue

    Staff rely on playlist matching and catalog filtering to keep the DJ-facing list aligned with venue playability.

Best for: Fits when venues need a moderated guest request queue with DJ-visible ordering and exportable logs.

#7

DJ Event Planner

SMB

DJ business management platform with online music request lists for event clients and guests.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Venue approval workflow that routes guest requests through moderation before DJ polling exposes them to sets.

DJ Event Planner is a song request system built for live DJ events, with a focus on venue-side moderation and a request intake workflow. The core workflow supports guest requests that land in a DJ-facing queue, with controls for approvals and filtering before songs enter rotation.

Pros
  • +DJ-facing request queue reduces interruptions during active mixing
  • +Venue approval workflow helps keep off-rotation requests out of sets
  • +Allowlist moderation supports targeted song intake for controlled events
  • +Mobile-friendly guest requests lower friction versus QR-only flows
Cons
  • –API and webhook automation coverage is limited compared with higher-ranked tools
  • –Spotify integration can lag for niche catalogs during fast rotation changes
  • –Fine-grained moderation policies require consistent operational discipline
  • –Multi-room routing support is not as documented for complex setups
Use scenarios
  • Event staff at DJ venues

    Approve and filter guest requests

    More controlled music selection

  • DJ event production teams

    Run a mobile-first guest request workflow

    More orderly request intake

Show 1 more scenario
  • Music operators

    Match requests to Spotify catalog

    More relevant queue items

    Operators rely on Spotify catalog matching to align requested songs with what the event can play.

Best for: Fits when small teams need a moderated guest request queue with dependable DJ-side control.

#8

Jukestar

SMB

Social jukebox software that lets guests request songs from streaming-based event playlists.

7.3/10
Overall
Features7.3/10
Ease of Use7.3/10
Value7.3/10
Standout feature

QR-first guest entry plus a DJ-facing queue workflow that keeps request handling fast without installs.

Jukestar targets venues that want audience song requests delivered into a DJ selection queue with minimal setup friction. Guest requests are submitted through mobile web entry points that work well for tabletop signage.

Pros
  • +Mobile web request form avoids app friction for guests
  • +DJ-facing request queue reduces between-song decision latency
  • +Moderation rules help keep questionable requests out of the stream
  • +QR code tabletop entry fits quick kiosk-style deployments
Cons
  • –Live stream DJ workflows need a tighter integration story than queue-only setups
  • –Automation depth depends on rule coverage rather than configurable pipelines
  • –Catalog matching quality can constrain requests when metadata is incomplete
  • –Venue governance requires careful moderation policy to prevent backlog buildup
Use scenarios
  • Venues with tabletop signage

    Collect mobile web song requests

    Lower friction requesting

  • Venue managers

    Enforce moderation rules without pausing

    Less interruption during shows

Show 2 more scenarios
  • Performing DJs

    Scan and select from DJ queue

    Quicker selection at showtime

    DJs use a queue designed for quick scanning so the next songs can be chosen during performance.

  • Event planners

    Export setlists and review history

    Clear post-event set documentation

    Teams review request history and export setlists for operational continuity after each event.

Best for: Fits when venues need fast guest requests on mobile web with moderated queue control during live sets.

#9

RequestNow

vertical specialist

Event music request software for DJs and venues with phone-based guest interaction.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Venue moderation workflow that gates what guests can ultimately publish to the DJ-facing request list.

RequestNow is a song request system built for venues and live broadcasters that prioritize an operator workflow over DJ-only input screens. It supports a guest-facing request queue plus moderated publishing so requests can be validated before they appear in on-air or stage view. The solution includes playlist and catalog matching with rules for request handling so the system stays consistent during repeated guest submissions.

Pros
  • +Moderation workflow keeps live output aligned with venue policies
  • +Operator controls fit shared hosting across multiple staff members
Cons
  • –Automation depth is limited if the workflow needs custom routing logic
  • –Integration options depend on available music source matching behavior
Use scenarios
  • Venue operators

    Moderate requests before on-air display

    Controlled request publishing

  • Live broadcasters

    Match requests to playlist rules

    More predictable request flow

Show 1 more scenario
  • Show producers

    Run operator-first request workflow

    Fewer invalid requests

    Producers use an operator workflow with a moderated queue that prioritizes control over DJ-only screens.

Best for: Fits when a venue or radio team needs moderated guest requests with predictable publishing control.

#10

DJ Queue

vertical specialist

Digital request queue software for DJs and event guests.

6.6/10
Overall
Features6.6/10
Ease of Use6.6/10
Value6.6/10
Standout feature

DJ Queue’s admin-configured request handling rules automate approvals so DJs can focus on playing instead of triaging every request.

DJ Queue targets DJs and venues that need a browser-based song request workflow with queue moderation and on-screen control. It supports guest requests with automated handling rules and a DJ-facing display that keeps the next songs visible during a set.

Pros
  • +Real-time queue management with a DJ-facing display during live sets
  • +Moderation rules reduce manual approvals for routine request patterns
  • +Request history supports setlist export workflows for later reporting
  • +Browser-first guest experience avoids dedicated hardware for basic use
Cons
  • –Advanced workflow tuning needs careful setup of request handling rules
  • –Limited depth for multi-room routing and complex approval chains
  • –Web-based deployments can be sensitive to network stability at event sites
  • –External catalog matching for music metadata can lag for less common tracks
Use scenarios
  • Club DJs and hosts

    Use automated handling rules for requests

    Less manual queue management

  • Broadcast and multi-DJ venues

    Tune limits and approval behavior

    Queue behavior fits the schedule

Show 1 more scenario
  • Operators running live events

    Moderate requests with history for later review

    Repeatable post-event review

    Operators manage moderation in real time and preserve history for subsequent set analysis.

Best for: Fits when a DJ needs moderated requests with a reliable live queue and exportable request history.

Conclusion

After evaluating 10 song request software, Kanto Karaoke 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.

Our Top Pick
Kanto Karaoke

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Song Request Software

How do DJ Intelligence and Rockbot route guest requests to what DJs can see during a set?
DJ Intelligence routes requests into a DJ-facing queue with venue-specific workflow configuration and staff approval when needed. Rockbot ties venue-facing request screens and DJ-facing controls to what is actually playing, so eligible requests flow into the active DJ queue while disallowed items stay blocked by automation rules.
Which tools use catalog matching to reduce manual search work, and how does that affect throughput?
DJ Intelligence and PCDJ Karaoki both include catalog matching tied to major streaming catalogs, which reduces lookup time during busy rotations. TouchTunes also relies on matching so the DJ-facing list stays consistent with playable tracks, which lowers triage time when request volume spikes.
How does moderation gating differ between RequestNow and TouchTunes when a guest requests content that fails rules?
RequestNow gates publication so requests can be validated before they appear in on-air or stage view in a moderated guest queue. TouchTunes uses allowlist-based approval plus profanity filter options, so disallowed requests are held or rejected before the DJ display reflects them.
What breaks if a venue needs multi-room routing or multiple DJ positions with separate queue behavior?
DJ Queue is the most aligned option because admins can tune request limits and approval behavior for a live broadcast or multi-DJ schedule. Tools like Kanto Karaoke focus on a venue-first approval workflow and queue visibility across tabletop and mobile, but they do not target multi-room or multi-DJ routing as the primary configuration model.
When should a venue prioritize a QR-code guest entry flow, and which tools provide it natively?
Jukestar is built around QR-first guest entry so guests can submit via mobile web without installs. Jukestar also pairs that with a DJ-facing queue workflow that keeps moderation rules in place during live sets.
How do Kanto Karaoke and RequestBox handle duplicate requests and request timing behavior in the queue?
Kanto Karaoke includes administrative tooling for request timing behavior so staff can correct issues before songs reach the DJ display. RequestBox focuses on moderated intake with real-time polling and request history tracking, so duplicates and timing problems are managed through its approval gates and queue controls rather than DJ-side cleanup.
Which tool provides a setlist export and request history log designed for after-session reporting?
TouchTunes includes request history tracking and exportable reporting for follow-up workflows. RequestBox also includes request history tracking plus setlist-style exports, which helps venues reconcile what entered the DJ list against what guests requested.
How do web and kiosk deployment options differ across Jukestar and TouchTunes?
Jukestar centers on a mobile web request experience using QR-style entry points, which supports immediate guest intake without app installation. TouchTunes is designed for mobile web and kiosk-style use so guests can submit songs on-site through shared displays during peak demand.
What security controls are most relevant for access separation between operators and DJs, and which tools support admin-focused control?
DJ Queue is the most explicit match for admins who need to set queue moderation behavior because it includes admin-configured request handling rules and a DJ-facing display for live control. Rockbot also maintains moderation controls with automation rules that route eligible requests to the DJ display, which reduces the chance that out-of-policy items reach DJs without operator oversight.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Song Request Software

In song request software, the real differences are how requests move from viewers to the person on the controls, and how much automation and visibility the system gives to staff. Look closely at API and automation depth and admin and governance controls so your queue behavior stays consistent during real event traffic.

Request lifecycle controls

Why it matters

Request lifecycle controls determine whether requests wait, get reviewed, or auto-progress, which affects latency and fairness during a busy show. In this category, staff need predictable states from submission to play.

How to check

Ask the demo team to show the full path of a single test request: where it lands, which status it shows, and what happens when you change your rules. Then submit two requests quickly and confirm their order and current statuses in the system view.

Queue sync with playback workflow

Why it matters

Queue sync with playback workflow matters because song requests only become useful when they map cleanly to what’s next to play. If the system can’t keep the queue and the controls aligned, requests stall or get skipped.

How to check

During the demo, run a request end-to-end and check whether the “next” item is reflected consistently anywhere staff operate. Ask how updates work when you reorder the queue and when you cancel a request after submission.

API and automation surface

Why it matters

API and automation surface affects how well you can connect event ops to the request flow without manual re-entry. It also determines whether advanced routing and reporting can be automated when you change rules mid-event.

How to check

Request to see an API walkthrough: endpoints or actions for creating a request, updating status, and pulling queue data. If they have webhooks or similar triggers, ask what events they emit and what payload fields they include.

RBAC and audit log for changes

Why it matters

RBAC and audit log for changes protect event integrity when multiple staff touch requests and rules. Without audit trails, it’s hard to explain why a request was approved, delayed, or removed.

How to check

Ask the demo team to set up at least two roles and show which role can change request rules and which can only view. Then run an action (like approving or removing a request) and show where the system records who did what and when.

Request data model and fields

Why it matters

Request data model and fields matter because viewers’ intent must survive the journey from submission to playback. If key attributes are missing or hard to map, automation and reporting become limited.

How to check

Ask for a sample request form and inspect which fields exist (for example, requester identity, comments, request time, and status). Then test whether you can filter or sort based on those fields in the admin view.

Red flags

  • Statuses change but the workflow doesn’t, so requests appear to “get stuck.”
  • Role permissions are vague, and there’s no clear audit trail for queue-rule changes.
  • The system lacks any practical API or automation path beyond manual steps.

Fit by situation

  • If we run frequent staff rotations during shows, prioritize RBAC and audit log for changes.
  • If we need to connect request flow to our playback operations, prioritize queue sync with playback workflow.
  • If we plan to automate reporting or routing, prioritize API and automation surface.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

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 Listing

WHAT 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.