Commissioned Research
Top 10 Best Client Proofing Software of 2026

GITNUXSOFTWARE REVIEW

Business & Finance

Top 10 Best Client Proofing Software of 2026

Compare client proofing software options for agencies and freelancers, with tools like Pixieset and key tradeoffs for client review.

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

Client proofing tools matter because approvals require a dependable data model for files, permissions, and version history across teams and clients. This comparison helps operators and technical evaluators weigh automation depth, integration options like API and webhooks, and gallery delivery workflows, including platforms aimed at photographers versus agencies.

CloudSpot is the best pick for design teams that need link-based client reviews because its round-based proof sessions keep comments and approval status aligned to each revision. For stricter moment-by-moment traceability, Frame.io fits teams running video and design reviews since timestamped markup preserves the audit trail across versions.

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

CloudSpot

Round-based proof sessions that keep comments and approval status aligned to each uploaded revision.

Best for: Fits when design teams need client link reviews with approval tracking across multiple rounds.

2

Pixieset

Editor pick

Anchored comment markup inside high-resolution asset previews makes client feedback precise without file handoffs.

Best for: Fits when image-centric teams need browser proofing with anchored comments and revision links for external clients.

3

Pixpa

Editor pick

Shareable proof pages that tie annotations and threaded comments to a specific proof link and version context.

Best for: Fits when creative teams need client proof links with clear review rounds and approval tracking.

Comparison Table

1
CloudSpotBest overall
SMB
9.1/10
Overall
2
8.8/10
Overall
3
8.6/10
Overall
4
8.4/10
Overall
5
enterprise
8.3/10
Overall
6
enterprise
7.7/10
Overall
7
enterprise
7.4/10
Overall
8
7.1/10
Overall
9
enterprise
6.9/10
Overall
10
6.7/10
Overall
#1

CloudSpot

SMB

Client gallery and proofing software for photographers with automated workflows.

9.1/10
Overall
Features9.1/10
Ease of Use9.2/10
Value9.0/10
Standout feature

Round-based proof sessions that keep comments and approval status aligned to each uploaded revision.

CloudSpot’s core workflow centers on creating proof rounds, generating links for external reviewers, and collecting markup and comments against the same uploaded version. Threaded discussions help separate design feedback from approval decisions, and comment timestamps map feedback to the review timeline. Approval status updates are visible at the proof level, which makes it easier to consolidate feedback across multiple reviewers and revisions.

The tradeoff is that automation depends on how reviewers and rounds are managed inside CloudSpot, so high-volume pipelines may require process discipline to avoid creating duplicate rounds. CloudSpot fits teams that send frequent design proofs to clients who need link-based review and a clear approval record before the next revision.

Pros
  • +Link-based external reviews with per-proof approval states
  • +Threaded comment threads keep feedback tied to a specific round
  • +Revision history clarifies what changed between review cycles
  • +Reviewer access control limits external exposure to projects
Cons
  • –Automation surface is limited compared with code-first workflow tools
  • –Proof organization can get messy when rounds are duplicated
Use scenarios
  • Creative production teams

    Client approves artwork rounds

    Faster sign-off cycles

  • Brand and marketing ops

    Multiple agencies share one approval record

    Fewer approval handoffs

Show 2 more scenarios
  • Agency project managers

    Track feedback across review cycles

    Clear revision accountability

    Managers use proof-level status and activity history to coordinate next steps.

  • In-house designers

    Review image and layout proofs

    Actionable client notes

    Designers run browser-based annotation and threaded feedback tied to uploaded versions.

Best for: Fits when design teams need client link reviews with approval tracking across multiple rounds.

#2

Pixieset

SMB

Online client galleries and proofing platform designed for visual creators.

8.8/10
Overall
Features8.8/10
Ease of Use8.9/10
Value8.7/10
Standout feature

Anchored comment markup inside high-resolution asset previews makes client feedback precise without file handoffs.

Pixieset supports browser-based client proofing for design and photography workflows, with a viewer optimized for large images rather than document-only review.

Proof links include markup and revision navigation so creative teams can consolidate comment threads and track changes across rounds.

Access is handled through per-proof invitations, which reduces cross-project exposure for external collaborators.

Automation and extensibility are mostly driven by proof creation patterns and link delivery instead of a broad API-centered integration model.

Pros
  • +High-resolution proof viewing reduces the need for local downloads
  • +Markup comments stay anchored to assets for faster client feedback
  • +Versioned proof links help teams maintain a clean approval history
  • +Invite-based access keeps external reviewers separated per proof
Cons
  • –Automation and integration depth is limited compared with workflow-first rivals
  • –Best results require consistent naming and structure in proof sets
Use scenarios
  • Portrait, wedding photographers

    Controlled gallery for proofing images

    Structured review and approvals

  • Photography studio administrators

    Tie client galleries to operations

    Connected client workflow

Show 2 more scenarios
  • Fine-art and print photographers

    Proof then route clients to checkout

    Viewing-to-purchase flow

    Present client proof galleries that connect viewing to print or product purchase paths.

  • Freelance photographers

    Deliver curated sets with download access

    Consistent delivery without portals

    Send branded galleries with defined download access for completed image selections.

Best for: Fits when image-centric teams need browser proofing with anchored comments and revision links for external clients.

#3

Pixpa

SMB

Portfolio website builder with integrated client proofing galleries.

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

Shareable proof pages that tie annotations and threaded comments to a specific proof link and version context.

Pixpa’s client proofing experience is built around shareable proof pages that collect annotations and threaded comments against a specific asset. Reviewers can add feedback directly where it matters, while the proof owner can manage review rounds through the proof status flow. The system is suited to teams that need consistent review sharing for images, design previews, and presentation-style exports rather than only PDF-centric markups.

A tradeoff appears in automation depth and extensibility for enterprise governance. Pixpa offers workflow control for review and status, but it does not emphasize deep API-driven provisioning or role automation for complex multi-team review operations. Pixpa works best when a small to mid-size team wants fast client feedback loops with clear per-link review context and straightforward handoff to approvals.

Pros
  • +Client feedback stays attached to a shared proof page per version
  • +Annotation and threaded comments reduce back-and-forth across review rounds
  • +Approval status visibility makes sign-off stages easier to track
  • +Setup focuses on proof links rather than engineering integration work
Cons
  • –Automation options for reviewer provisioning are limited without manual setup
  • –File handling prioritizes previews and exports over high-end production review formats
Use scenarios
  • Brand and design teams

    Collect client feedback on visual previews

    Fewer revisions from clearer feedback

  • Creative agencies

    Manage multi-review sign-off workflows

    More predictable client approvals

Show 1 more scenario
  • Marketing ops teams

    Coordinate external stakeholder reviews

    Consolidated feedback in one place

    Marketing ops centralize feedback on shared proof pages to consolidate input from remote collaborators.

Best for: Fits when creative teams need client proof links with clear review rounds and approval tracking.

#4

Studio Ninja

SMB

Client communication and proofing platform for professional photographers.

8.4/10
Overall
Features8.4/10
Ease of Use8.5/10
Value8.3/10
Standout feature

Approval workflow ties approval decisions to the specific proof version and preserves a review history for later reference.

Studio Ninja fits teams that run repeated review cycles for presentation proofs, image proofs, and file-based deliverables with guest reviewers. The approval workflow keeps review status attached to each proof version, which reduces ambiguity when clients request revisions across multiple rounds. Feedback is organized through comment threads and markup tied to the underlying preview content, which helps route feedback to the right asset.

Pros
  • +Approval status stays linked to each proof version
  • +Threaded comment threads keep feedback attached to markup context
  • +Reviewer permissions separate view, comment, and approval access
  • +Integrations reduce manual upload handoff for review
Cons
  • –Automation depth is limited without consistent versioning and access setup
  • –Less suited for heavy side-by-side version comparisons
  • –Markup precision depends on preview generation quality
  • –Managing many reviewers requires stronger internal access hygiene
Use scenarios
  • Creative agencies

    Client reviews for design deliverables

    Fewer approval misunderstandings

  • Brand production teams

    Marketing asset revision cycles

    Clean revision trail

Show 2 more scenarios
  • In-house design groups

    Guest reviewers on presentation proofs

    Controlled external feedback

    In-house teams assign reviewer roles to external collaborators for view, comment, and approval actions.

  • Operations and PMO

    Review coordination across projects

    More predictable handoffs

    Ops teams track review status and feedback outputs per proof version to coordinate downstream revisions.

Best for: Fits when agencies need multi-round client approvals with clear version ownership and comment traceability.

#5

Frame.io

enterprise

Video and photo review platform with time-stamped client proofing.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Timestamped video markup with threaded comment threads linked to exact moments, then preserved through versioned review history.

Frame.io turns review requests into shareable proof links for video, image, and document workflows with threaded comments tied to timestamps or file regions. Admins can manage reviewer roles, restrict access with invite-based collaboration, and generate an approval audit trail for each proof version.

Pros
  • +Comments map to video timestamps and keep context across revisions
  • +Approval audit trail ties decisions to specific proof versions
  • +Version history makes review rounds traceable without manual bookkeeping
  • +Extensibility supports integration with asset and review workflows
Cons
  • –File organization can become complex for large parallel review batches
  • –Advanced automation depends on integration setup rather than built-in templates
  • –External reviewer permissions need clear role design to avoid access drift
  • –High-volume comment activity can increase navigation time during signoff
Use scenarios
  • Agencies and production companies

    Invite stakeholders for versioned approvals

    Approval trail per asset version

  • Creative teams reviewing media

    Threaded feedback anchored to moments

    Clearer feedback interpretation

Show 2 more scenarios
  • Film and television production teams

    Remote dailies review for new footage

    Faster remote feedback cycles

    Share newly captured clips with distributed editors and supervisors for timely review.

  • Creative operations teams

    Automate status and downstream actions

    Less manual review handling

    Connect review events and approval states to internal tools via APIs and automation workflows.

Best for: Fits when creative teams run frequent video and design reviews with strict approval traceability requirements.

#6

Ziflow

enterprise

Proofing and approval automation platform for creative teams and agencies.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

API-driven workflow integration that synchronizes external status and handoffs with proof activity.

Ziflow supports client proofing by hosting review links for design and creative files with inline comments and markup. Teams can run approval workflows across multiple proof versions while keeping review threads attached to specific stages.

Pros
  • +Approval workflows support multi-round review with structured status tracking
  • +Markup and threaded comments stay tied to proof versions
  • +Audit trails record review activity and change history for accountability
  • +Integrations and API support workflow handoffs and external automation
Cons
  • –Some governance features require careful role setup for consistent reviewer access
  • –Complex workflows can require more configuration than lightweight proofing tools
Use scenarios
  • Agencies and external partners

    Send review links without file transfers

    Shared workflow for approvals

  • Design, product, marketing teams

    Region comments on image proofs

    Faster issue resolution

Show 2 more scenarios
  • Print production and document teams

    Review PDFs through revision rounds

    Audit-ready correction trail

    Annotate PDFs and recheck corrected revisions with traceable approval history.

  • Creative and marketing teams

    Threaded markup across design assets

    Feedback tied to review stage

    Collect feedback with markup on designs and other marketing assets across rounds.

Best for: Fits when agencies need controlled client review cycles with version-linked feedback and audit trails.

#7

ReviewStudio

enterprise

Online review and approval platform for creative and media assets.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Role-based reviewer permissions tied to specific proofs, so external collaborators only see and comment on allowed assets.

ReviewStudio is a client proofing tool focused on controlling who can review which asset and what each reviewer can do. It supports annotation and markup on shared proof links, along with review rounds that capture status and feedback in one place.

Pros
  • +Permissioned proof access limits external reviewer visibility by project or file set
  • +Inline markup and threaded comments keep feedback organized on each proof revision
  • +Revision-aware proof history reduces confusion between review rounds
  • +External reviewer invitations support multi-party creative review workflows
Cons
  • –Finer-grained role control can take more configuration than simple invite-based models
  • –Large proof sets can slow navigation when reviewers open many assets
Use scenarios
  • Creative agencies and client services

    Send proofs with revision feedback

    Documented deliverable sign-off

  • Video editors and producers

    Time-coded comments across cut revisions

    Precise change requests

Show 2 more scenarios
  • Brand teams and designers

    Discuss design changes tied to versions

    Fewer disconnected review threads

    Mark up creative assets and keep threads tied to specific versions for stakeholder review.

  • Prepress and marketing teams

    Annotate images and PDFs for soft proofs

    Remote proof record of revisions

    Review image and PDF proofs with markup retained across successive proof rounds.

Best for: Fits when agencies or brand teams need controlled external review links with revision-specific comments and status.

#8

HoneyBook

SMB

Business management platform with client proofing and gallery features for creatives.

7.1/10
Overall
Features7.1/10
Ease of Use7.0/10
Value7.2/10
Standout feature

Proof links and feedback are attached to HoneyBook proposal and project steps, keeping approvals tied to job context.

HoneyBook centralizes client-facing workflows for service businesses, pairing proposal delivery with approval-oriented review paths and structured feedback collection. Its client portal focuses on sending proof links and collecting comments tied to specific assets and steps in the job timeline.

Pros
  • +Client portal ties reviews to proposals and job records
  • +Proof links and comment capture reduce lost feedback between threads
  • +Team collaboration stays attached to the same project context
  • +Workflow steps help enforce review order and response timing
Cons
  • –Markup depth can lag dedicated design proofing tools
  • –Advanced version comparison is less granular than file-centric review systems
Use scenarios
  • Small service teams

    Coordinate client proof status messaging

    Fewer status request messages

  • Creative studios and project teams

    Connect proofs to milestones and tasks

    Clear ownership and visibility

Show 2 more scenarios
  • Retainer-based consultants

    Keep billing tied to client relationships

    More consistent recurring billing

    Use recurring invoices while reviews stay connected to the underlying order or job record.

  • Independent photographers and designers

    Guide inquiry into an approved engagement

    More consistent path to booking

    Capture inquiry details, schedule consultation, send proposals, and route the client toward booking.

Best for: Fits when service studios need proof links, feedback capture, and approval flow inside one client portal.

#9

Filestage

enterprise

Review and approval software for creative assets with client proofing.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

API-driven automation for provisioning review workflows and managing proof state across revisions.

Filestage organizes online proofing around approval workflows that attach reviewers to specific proof links.

Pros
  • +Approval workflow links reviewers to a specific proof version
  • +Threaded comment threads stay tied to exact markup locations
  • +Audit trail records review actions across revision history
  • +API supports automation for creating proofs and managing workflow state
Cons
  • –Some governance needs rely on consistent role and permission configuration
  • –High-volume projects can require more manual organization of proof versions
  • –Markup depth varies by file type and preview rendering choices
  • –Complex integrations may require development effort around the API surface
Use scenarios
  • Advertising agencies

    Approve ad assets in recurring checkpoints

    Repeatable variant proofing

  • Video production teams

    Collect time-specific cut feedback

    Clearer approvals across revisions

Show 2 more scenarios
  • Content and document teams

    Anchor comments to document pages

    More traceable document revisions

    Collect page-anchored comments and approval decisions on PDFs and documents.

  • Cross-functional content operations

    Coordinate reviews across departments

    Clear approval history

    Manage sequential internal and external reviews with organized handoffs and ownership.

Best for: Fits when teams need repeatable approval workflows with external reviewers and version-specific audit trails.

#10

Picdrop

SMB

Simple client proofing and photo delivery tool for professional photographers.

6.7/10
Overall
Features6.7/10
Ease of Use6.7/10
Value6.7/10
Standout feature

Permission-scoped guest reviewer access combined with watermarking for presentation proofs.

Picdrop centers on online proofing with browser-based review links that support image and PDF markups inside a controlled approval flow. The system focuses on comment threads tied to proof versions and on managing revision rounds through status changes and reviewer assignment.

Pros
  • +Browser-based markup tied to specific proof versions and review rounds
  • +Comment threads keep feedback organized for iterative revisions
  • +Watermarking helps protect presentation proofs during client review
  • +Permission controls support restricting what external reviewers can do
Cons
  • –Automation and API surface are limited for end-to-end workflow integration
  • –Large teams can hit friction when managing many concurrent proof links
  • –Version comparisons are less granular than in tooling built for detailed diff workflows
  • –Admin governance controls are not as deep as enterprise approval systems
Use scenarios
  • Professional photographers

    Run proof rounds for client feedback

    Consolidated review decisions

  • Photographers delivering to clients

    Set download permissions for client access

    Controlled image handoff

Show 2 more scenarios
  • Wedding photographers and studios

    Client proofing workflow for wedding photos

    Client-facing proof and selection

    Present wedding galleries where clients review, comment, and select images.

  • Photographers delivering selectable sets

    Collect ratings and selections from clients

    Clear next-step selections

    Offer curated galleries so clients choose or rate images for the next production step.

Best for: Fits when design and marketing teams need fast client review links with structured feedback and controlled access.

Conclusion

After evaluating 10 client proofing software, CloudSpot 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
CloudSpot

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 Client Proofing Software

How do Pixpa and Studio Ninja handle approval workflow across multiple review rounds without mixing feedback from different versions?
Pixpa ties threaded comments and approval status to a specific proof link and version context for each review round. Studio Ninja preserves approval decisions at the proof version level and keeps a review history that later rounds can reference without overwriting earlier comments.
Which tool keeps comment threads attached to exact points in the asset for video or region-based review?
Frame.io supports threaded comments linked to timestamps or file regions for video and other creative review inputs. This differs from Pixieset and CloudSpot, which center on image-focused or round-based proof sessions rather than time-indexed markup.
How do Filestage and Ziflow support admin provisioning and workflow automation using an API?
Filestage provides API hooks for provisioning review workflows and managing proof state across revisions. Ziflow uses API-driven integration to synchronize external status and handoffs with proof activity.
When does guest reviewer access work differently between Picdrop and ReviewStudio?
Picdrop uses permission-scoped guest reviewer access with watermarking to keep presentation proofs controlled during feedback collection. ReviewStudio applies role-based reviewer permissions tied to specific proofs, so external collaborators can only comment on assets allowed by the permission setup.
What security controls prevent external collaborators from gaining broader access than intended in CloudSpot and Frame.io?
CloudSpot uses administrator workflows that govern reviewer access control for external collaborators who participate without full workspace access. Frame.io restricts access through invite-based collaboration and reviewer roles while keeping an approval audit trail per proof version.
How do Pixieset and Frame.io manage high-resolution previews and anchored feedback inside the viewer?
Pixieset anchors client feedback inside high-resolution asset previews so markup stays visually tied to the exact area in the image. Frame.io focuses on rich review for media workflows and preserves feedback through versioned review history, including timestamped threads for video.
What breaks in client review workflows when version pinning is missing in a proof link, and how do Studio Ninja and Pixpa avoid that issue?
Without version pinning, reviewers can comment on a different iteration than the one being approved, which leads to mismatched approval status and unclear revision tracking. Studio Ninja ties review and approval history to specific proof versions, while Pixpa ties annotations and threaded comments to the proof link and version context.
How do HoneyBook and Filestage differ when client proofing needs to stay attached to job context instead of running as standalone review pages?
HoneyBook attaches proof links and feedback to proposal and project steps so approvals remain connected to an order record and job timeline. Filestage centers on approval workflows with external reviewer handling and API-driven automation, which fits processes where review is managed as a dedicated workflow layer.
Where does CloudSpot fall short compared with API-forward tools when integrations must update proof status automatically?
CloudSpot focuses on shareable proof sessions and round-based approvals with activity history, which can require more manual coordination when external systems must react instantly. Ziflow and Filestage provide API-driven synchronization that connects proof activity to external status updates and workflow provisioning.
What admin capability separates ReviewStudio from tools that prioritize link-based reviews over granular permission modeling?
ReviewStudio emphasizes role-based reviewer permissions tied to specific proofs, which supports controlled multi-stakeholder review across allowed assets. Tools like Pixpa and CloudSpot can manage review rounds and access, but their core strength is link and round visibility rather than permission modeling at the same granularity.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Client Proofing Software

We see options separate mainly by how they handle reviewer interaction and traceability inside approval workflow—especially what the audit log actually captures and how well automation and API surface reduce manual back-and-forth. When you compare products, focus on the proof lifecycle and the controls around who can act and when, using approval workflow and audit log as your anchors.

Approval workflow states and transitions

Why it matters

Approval workflow clarity reduces stalled projects and makes outcomes predictable for both teams and clients. The difference shows up in whether status changes match what people expect during each review round.

How to check

Start a demo workflow, then move a single proof through at least two states (e.g., submitted and approved or rejected). Ask what happens if you change the proof after a client decision and which actions are blocked at each state.

Audit log for proof actions

Why it matters

A strong audit log for proof actions matters when clients dispute timing or content changes. Without it, teams lose confidence in what was reviewed, by whom, and when.

How to check

In the demo, perform a few actions: upload a new proof, add a note, and change the approval state. Then open the audit log and confirm it records timestamps and the specific action types you just took.

Annotation tools match real review behavior

Why it matters

Annotation tools shape how quickly feedback turns into decisions. The key difference is whether feedback stays attached to the correct part of the proof and remains usable across proof updates.

How to check

Upload a sample design and add at least two different comment types to distinct locations. Then request a proof update and verify whether the new proof keeps the annotations correctly or clearly flags what did not carry over.

Version comparison and proof versioning

Why it matters

Version comparison and proof versioning prevent teams from debating which artifact a comment refers to. When a newer proof replaces an older one, the tool should make the relationship explicit.

How to check

Create a proof, collect a comment, then upload a revised proof. Check whether the interface shows the delta or at least links the comment to the specific proof version it came from.

API and automation for proof handoff

Why it matters

If your workflow already lives in other tools, the API and automation surface determines whether handoff becomes a manual chore. The difference is whether you can trigger proofs, sync statuses, and provision access through configuration.

How to check

Ask the demo to show an API call or webhook-like event for: creating a proof, updating status, and pushing a link to a client. Then verify you can map those events back to approval workflow states without manual copying.

Red flags

  • Approval workflow states don’t match what the client sees during review.
  • Audit log entries are vague or omit the specific action type and timestamp.
  • Annotations don’t stay tied to the correct proof version after an update.

Fit by situation

  • If you run multi-step approvals with frequent status changes, prioritize approval workflow states and transitions.
  • If clients or internal stakeholders need accountability, prioritize audit log for proof actions.
  • If you pass proofs between systems automatically, prioritize API and automation for proof handoff.
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.