Commissioned Research
Top 10 Best Printing Security Software of 2026

GITNUXSOFTWARE REVIEW

Cybersecurity & Information Security

Top 10 Best Printing Security Software of 2026

Compare printing security software options for print fleets, including Celiveo, SafeCom, and Printix, with tradeoffs for IT teams.

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

Search agents gather the source set and the review record, including transcriptions of 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

Printing security software is a control layer for pull printing, access policies, and traceability across fleets and document workflows. This comparison helps teams weigh identity-based release, capture and governance rules, and integration options against operational constraints like device compatibility and throughput.

Celiveo is the best pick for enterprises that need controlled pull release across multiple sites because its policy-driven enforcement maps release decisions to user identity and print workflow context, while Printix is a strong fit for distributed office teams thanks to its secure release workflow with job traceability at release time.

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

Celiveo

Policy-driven print release enforcement mapped to user identity and print workflow context.

Best for: Fits when document handling requires controlled print release and consistent policy enforcement across multiple sites.

2

SafeCom

Editor pick

Print job release control driven by authentication at the server side, with logged allow and deny outcomes.

Best for: Fits when enterprises need consistent print release enforcement across a printer fleet and audit-ready logs.

3

Printix

Editor pick

Secure print release policy enforcement with job traceability at release time, not just queue-level controls.

Best for: Fits when office teams need consistent secure release controls across mixed user groups and shared printers.

Comparison Table

1
CeliveoBest overall
enterprise
9.0/10
Overall
2
enterprise
8.9/10
Overall
3
8.7/10
Overall
4
8.4/10
Overall
5
enterprise
8.3/10
Overall
6
enterprise
7.7/10
Overall
7
7.6/10
Overall
8
7.1/10
Overall
9
6.9/10
Overall
10
6.5/10
Overall
#1

Celiveo

enterprise

Zero-server secure pull printing with blockchain-based audit trails.

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

Policy-driven print release enforcement mapped to user identity and print workflow context.

Celiveo focuses on printing security controls that connect policy enforcement to the print workflow rather than treating printers as standalone endpoints. The core capabilities center on access control for print release and job handling rules that help keep sensitive documents out of the wrong hands.

Celiveo also supports administrative governance for managing which users and devices can print under which policies. Automation is oriented toward maintaining consistent enforcement across a printer fleet without relying on manual per-printer changes.

Pros
  • +Policy-based print release controls align enforcement with document handling needs
  • +Administrative governance supports consistent settings across a printer fleet
  • +Workflow automation reduces the need for per-printer manual exception work
  • +Security controls target print access and job release behaviors
Cons
  • –Integration depth with existing print environments can require careful planning
  • –Advanced configuration changes may demand stronger operational governance discipline
  • –Visibility into job-level outcomes may feel limited without disciplined logging habits
  • –Rollouts across mixed printer models can take time to normalize
Use scenarios
  • Information security managers

    Require user release of sensitive print jobs

    Less unattended sensitive output

  • IT teams for branch offices

    Route jobs to remote shared printers

    Predictable pickup across locations

Show 2 more scenarios
  • Enterprise IT infrastructure teams

    Deploy direct-to-printer secure workflow

    Centralized print control

    Supports serverless approaches that reduce reliance on conventional print server dependencies.

  • Managed print providers

    Reconcile monthly page volumes by device

    More repeatable reconciliation

    Collects meter data and reviews page counts by device, location, and reporting period.

Best for: Fits when document handling requires controlled print release and consistent policy enforcement across multiple sites.

#2

SafeCom

enterprise

Pull printing and cost management with user authentication at the device.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Print job release control driven by authentication at the server side, with logged allow and deny outcomes.

SafeCom targets organizations that need controlled print release instead of open spool queues. It uses user identity and configurable rules to gate what can be printed and when, then logs outcomes for review. Administration focuses on printer and user policy configuration, plus reporting that shows which jobs were allowed or denied.

A tradeoff appears in rollout effort, because identity integration and policy mapping require careful alignment with the print infrastructure. SafeCom fits best when print release must be enforced across a printer fleet where users print from multiple stations and the organization needs consistent, server-side control.

Pros
  • +Release-time control that gates jobs after authentication
  • +Policy configuration tied to printers and user identities
  • +Audit logs for allowed and blocked print attempts
  • +Supports integration with common enterprise print workflows
Cons
  • –Rollout requires careful mapping of identity to print rules
  • –Policy tuning can be slow when printer groups change often
Use scenarios
  • IT administrators

    Gate print jobs by user identity

    Reduced unauthorized printing

  • Security and compliance teams

    Review print activity for investigations

    Faster incident triage

Show 2 more scenarios
  • Facilities and helpdesk

    Handle printer access and release issues

    Lower resolution time

    Helpdesk resolves access problems using policy outcomes recorded for each print request.

  • Finance and cost controllers

    Control printing by organizational rules

    Better adherence to rules

    Admins enforce printing permissions that align to internal usage policies for specific printers.

Best for: Fits when enterprises need consistent print release enforcement across a printer fleet and audit-ready logs.

#3

Printix

SMB

Printix provides cloud print management, identity-based access, and secure printing for distributed teams.

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

Secure print release policy enforcement with job traceability at release time, not just queue-level controls.

Printix fits organizations that already run print servers or cloud-managed print access and need consistent secure release without forcing users to learn complex client tooling. Admin configuration focuses on assigning release requirements per printer or group and routing print jobs into a controlled queue until the user authenticates at release time. Reporting output emphasizes operational traceability for who released which job, which is useful for investigations and internal controls.

A clear tradeoff is that Printix depends on the print release workflow and the integration points that feed it, so environments with unusual print paths or direct device printing may need additional alignment work. It is a strong fit for offices with shared printers where multiple departments submit jobs and where policy needs to be enforced at the moment of printing rather than after the job reaches the device.

Pros
  • +Central secure release workflow reduces accidental disclosure at shared printers
  • +Admin reporting captures release events for practical audit trails
  • +Group-based configuration supports consistent policy across printer fleets
  • +Automation-friendly onboarding reduces per-printer manual setup
Cons
  • –Direct IP or atypical print paths can require extra integration work
  • –Admin policy changes can temporarily impact release behavior during updates
Use scenarios
  • IT operations teams

    Enforce secure release across departments

    Lower exposure from wrong-device printing

  • Compliance and security teams

    Investigate confidential print incidents

    Faster incident scoping

Show 1 more scenario
  • Finance and cost-center owners

    Track print release by user groups

    Clearer accountability for printing

    Operational visibility helps attribute released jobs to the correct business area for governance reviews.

Best for: Fits when office teams need consistent secure release controls across mixed user groups and shared printers.

#4

Tungsten ControlSuite

enterprise

Tungsten ControlSuite manages secure printing, capture workflows, authentication, and output governance.

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

Policy-driven secure release that ties job handling, release authorization, and audit logging into one workflow.

Tungsten ControlSuite is designed around controlling print job flow end-to-end, from submission through release, rather than treating printing as an application feature. The product targets organizations that need consistent printer access control, job policy enforcement, and print audit trails tied to users and documents.

Pros
  • +End-to-end secure release workflow controls job handling before printing
  • +Centralized policy management supports consistent printer behavior across locations
  • +Audit trails link release events to users and print actions
  • +Automation-oriented admin capabilities support repeatable rollout
Cons
  • –Rollout requires careful printer mapping and policy scoping across sites
  • –Automation depth is stronger for administrators than end users at the printer
  • –Initial integration work can be heavier than basic pull-print tools
  • –Governance changes can require coordinated updates to identity sources
Use scenarios
  • IT governance teams

    Centralize secure release policy rollout

    Reduced compliance gaps

  • Security engineering teams

    Harden print server workflows

    Lower exposure from misroutes

Show 2 more scenarios
  • Compliance and risk teams

    Track print release accountability

    Stronger audit readiness

    Provides traceable records for document handling and release events tied to identity.

  • Managed print operations

    Scale controlled release across sites

    Fewer site-specific exceptions

    Uses centralized administration to manage release behavior for a changing printer fleet.

Best for: Fits when centralized teams need controlled print release with auditable enforcement across printer fleets.

#5

uniFLOW Online

enterprise

uniFLOW Online provides cloud print management, secure release, authentication, and usage reporting.

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

Canon-centric secure release workflow with job authorization and audit trails integrated into the print management experience.

uniFLOW Online intercepts print release and access decisions from the print ecosystem, using Canon-managed workflows for document release and control. The product supports secure release patterns like PIN or badge-based authorization, plus centralized policy enforcement across Canon devices and connected print paths.

Pros
  • +Badge and PIN print release support for controlled job pickup
  • +Centralized administration for release policies across Canon print environments
  • +Audit trails tie print activity back to user and job context
  • +Workflow integration supports standard enterprise identity-driven use cases
Cons
  • –Security outcome depends on correct connector and printer-side deployment
  • –Policy coverage is strongest in Canon-managed device ecosystems
Use scenarios
  • Enterprise IT administrators

    Enforce PIN or badge release for print output

    Fewer unauthorized printouts

  • Compliance and audit teams

    Trace job actions with identity-linked logs

    Stronger audit trail

Show 2 more scenarios
  • Workplace print governance owners

    Standardize policy rules across Canon devices

    Consistent enterprise enforcement

    Centralizes role-based administration and configurable print rules across connected print paths.

  • Large organizations rolling out policies

    Move beyond basic pull printing controls

    More controlled print consumption

    Coordinates repeatable enterprise print policies instead of device-by-device release handling.

Best for: Fits when organizations want controlled secure print release with governance and audit trails across Canon fleets.

#6

MyQ X

enterprise

MyQ X provides secure print release, user authentication, scanning workflows, and print accounting.

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

Central policy management for secure release decisions based on job, user, and printer context.

MyQ X focuses on secure print release workflow control, with a policy-driven path from print job submission to authorized release. The product centers on printer access control patterns that can align user identity with release rules and audit evidence.

Pros
  • +Release policies can be tied to user identity for controlled output
  • +Admin controls support consistent enforcement across multiple printers
  • +Audit trails provide traceability from job submission through release
  • +Configurable policies reduce reliance on ad hoc user behavior
Cons
  • –Deployment often requires careful integration with existing print infrastructure
  • –Automation coverage can lag products that provide deeper workflow scripting
  • –Some security controls depend on disciplined endpoint and identity hygiene
  • –Fine-grained exception handling may require more admin effort
Use scenarios
  • Security-conscious office teams

    Authenticate users before printing sensitive documents

    Reduced unattended output

  • Secure print room operators

    Run governed templates for consistent output

    Improved run traceability

Show 2 more scenarios
  • Office managers

    Track page counts and print activity

    Clear usage baselines

    Collects page counts from managed devices for recurring operational reporting.

  • IT and compliance administrators

    Apply policy controls to quotas and release behavior

    More controlled print handling

    Enforces access, quotas, routing, and release behavior using centrally managed release permissions.

Best for: Fits when organizations need controlled print release tied to identity and want audit traceability.

#7

Thales CipherTrust

enterprise

CipherTrust data security tools include encryption and key management used to protect sensitive data at rest and in transit for enterprise printing and document workflows.

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

CipherTrust key-centric encryption control for protecting sensitive print data with centralized cryptographic governance.

Thales CipherTrust is a print security and document-protection control that focuses on protecting sensitive data at the cryptographic layer before it reaches printers.

Pros
  • +Strong cryptographic controls designed around centralized key management
  • +Audit trails support investigations and compliance workflows
  • +Policy-based enforcement helps keep print handling consistent
  • +Clear administrative separation supports controlled operations
Cons
  • –Printing workflow integration can require more systems engineering than print-specific tools
  • –Release flow usability depends on how the print ecosystem is configured
  • –Advanced deployments benefit from disciplined governance and change control
  • –Limited visibility into printer UX compared with purpose-built print release products
Use scenarios
  • Regulated enterprise security teams

    Enforce encryption and key handling for prints

    Protected sensitive print data

  • Identity and access administrators

    Control credentialed administration and access

    Tighter administrative control

Show 2 more scenarios
  • IT security architecture teams

    Integrate print protections with key management workflows

    Centralized security operations

    Connects to enterprise security stacks using key management workflows and administrative controls.

  • Compliance and auditing teams

    Use audit trails for regulated printing

    Easier compliance evidence

    Maintains audit trails designed for environments that require documented enforcement of protection controls.

Best for: Fits when enterprises need cryptographic document protection and controlled administration for print-related data paths.

#8

Ringdale FollowMe

enterprise

Secure pull printing and document release with multi-factor authentication.

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

Badge or PIN-based release tied to centralized print server queue enforcement for consistent behavior across locations.

Ringdale FollowMe drives pull printing by routing print jobs through a user release workflow that supports badge or PIN entry. It adds print server enforcement hooks so access control can be applied before a job is released to the printer queue.

Pros
  • +Pull printing workflow ties release to user credential entry
  • +Centralized policy configuration for printer access and release behavior
  • +Audit trails record print release events for traceability
  • +Designed for managed print server environments and queue control
Cons
  • –Strong reliance on integrating with identity or credential sources
  • –Misconfiguration can leave queues blocked or jobs stuck in release state
  • –Release workflow complexity increases with multiple credential types
  • –Advanced reporting depth depends on how the environment is set up
Use scenarios
  • Distributed office users

    Submit once and release at enrolled printers

    More flexible print pickup

  • School lab administrators

    Control shared device pickup for multiple users

    Better device access control

Show 2 more scenarios
  • IT and security teams

    Hold sensitive documents until authorized retrieval

    Fewer unattended sensitive pages

    Secures shared-printer output by requiring authorized user retrieval before release to the printer queue.

  • Enterprise print administrators

    Apply consistent release rules across sites

    More consistent print operations

    Uses centralized configuration to enforce queue, device, and release rules for multiple locations.

Best for: Fits when IT teams need pull printing with credential-based release and auditable job release events across printer fleets.

#9

Barracuda Secure Printer

enterprise

Network security appliance for protecting printer infrastructure from cyber threats.

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

User-authenticated secure print release that blocks job access until release conditions are satisfied.

Barracuda Secure Printer is designed to control and harden document printing workflows by adding policy enforcement around print release and queue access. It supports secure print release using user authentication so printers can deny jobs until release conditions are met.

Pros
  • +Centralized control of secure release behavior across the managed print environment
  • +Authentication-gated print release reduces exposure from unattended queues
  • +Policy enforcement at the print workflow layer supports consistent confidential handling
  • +Audit-oriented visibility helps track who released and printed documents
Cons
  • –Integration with existing print infrastructure can require careful configuration
  • –Advanced deployment patterns may depend on print server and queue design
  • –Secure release workflows can add friction versus basic direct printing
  • –Smaller environments may find governance features more than required
Use scenarios
  • IT admins for managed print

    Block production until release conditions are met

    Reduced unauthorized printing

  • Information security teams

    Standardize print security settings centrally

    Consistent enforcement across devices

Show 2 more scenarios
  • Operations leaders monitoring printing

    Review audit-oriented activity visibility

    Better oversight of print behavior

    Provides audit-oriented visibility into printing activity to support investigations and governance.

  • Organizations reducing workflow friction

    Harden queue access with policy enforcement

    More governed print consumption

    Adds policy controls around print release and queue access to manage document handling from submission onward.

Best for: Fits when mid-market IT teams need authenticated secure release and consistent print policy enforcement across a printer fleet.

#10

Pharos Secure Release

enterprise

Pharos Secure Release holds print jobs until users authenticate at an approved device.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Release auditing that ties user authentication events to job release outcomes in a way built for investigations.

Pharos Secure Release targets secure print release for organizations that need stronger control over who can print confidential documents.

Pros
  • +Policy-driven release behavior reduces accidental disclosure at printers
  • +Release auditing supports investigations tied to users and jobs
  • +Centralized release control fits organizations with shared printer queues
  • +Authentication at release time limits unauthorized job retrieval
Cons
  • –Admin workflows can require careful queue and release policy mapping
  • –Integration depth depends on the surrounding print architecture
  • –Operational tuning is needed to avoid release delays for busy sites
  • –Some governance actions may be slower than rule-based releases in lighter tools
Use scenarios
  • Enterprise IT teams

    Retrieve queued print jobs using badges

    Controlled document retrieval

  • Security-conscious organizations

    Require authentication at shared office printers

    Reduced document exposure

Show 2 more scenarios
  • Distributed fleet administrators

    Standardize authentication and release rules

    Consistent print handling

    Applies consistent authentication and policy-driven release behavior across printers, floors, and locations.

  • Document production teams

    Gate production output with approval rules

    Fewer incorrect production runs

    Requires approval before document or variable-data jobs enter a controlled production workflow.

Best for: Fits when enterprises need centrally governed secure print release with auditable user access control across many printers.

Conclusion

After evaluating 10 printing security software, Celiveo 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
Celiveo

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 Printing Security Software

How do Tungsten ControlSuite and Printix enforce secure print release differently?
Tungsten ControlSuite enforces release behavior through policy-driven job handling tied to centralized printer-fleet configuration and auditable enforcement across on-premises or hybrid deployments. Printix gates confidential release through a browser-based end-user workflow and records release decisions at release time for audit review.
What breaks if a print workflow bypasses the secure release gate in SafeCom or Pharos Secure Release?
SafeCom and Pharos Secure Release depend on server-side release control, so bypassing the release enforcement path sends jobs to the printer queue without the identity check they log and enforce. That breaks audit trails because release outcomes and allow or deny decisions cannot be tied to the authentication event.
Which tools support automation for onboarding printers and users at fleet scale?
Printix supports automation paths that help onboard printers and users at scale and reduce ad hoc release overrides. Tungsten ControlSuite supports centralized configuration and administrative interfaces used to provision printers and release behavior across fleets in controlled deployments.
How does uniFLOW Online handle badge or PIN-based authorization compared with Ringdale FollowMe?
uniFLOW Online uses Canon-managed workflows for secure authorization patterns like PIN or badge-based release across Canon devices and connected print paths. Ringdale FollowMe routes jobs through a badge or PIN entry workflow and adds server enforcement hooks before jobs reach the printer queue.
When admins need role-based administration and audit logging, which products align best?
uniFLOW Online provides role-based administration plus audit logging tied to user and job identity, which supports repeatable enterprise governance. Pharos Secure Release provides reporting for release activity and printer usage so administrators can audit access patterns tied to authentication events.
How does Celiveo map print release policy to user identity and workflow context?
Celiveo focuses on policy-driven release enforcement mapped to user identity and print workflow rules instead of treating printers as standalone endpoints. Its automation targets consistent enforcement across sites without relying on manual per-printer changes.
How do Thales CipherTrust and print release tools differ when data must be protected before it reaches printers?
Thales CipherTrust targets protection at the cryptographic layer by enforcing encryption and key handling before print data reaches printers. Release-focused tools like Printix and SafeCom primarily control who can release jobs and what happens at release time with identity checks and audit outcomes.
Which products fit organizations that must run controlled printing across mixed user groups and shared printers?
Printix fits office environments where mixed user groups need consistent release controls because the browser workflow enforces release decisions and captures audit evidence. Barracuda Secure Printer fits mid-market IT teams that need authenticated secure release and consistent enforcement across a managed printer fleet with centralized security settings.
Where do admin controls typically fall short if centralized governance is required, based on SafeCom and MyQ X?
SafeCom centers on print server release-time control and audit trails, so it can rely on the existing environment for broader governance patterns beyond the release decision. MyQ X centralizes policy management for release decisions based on job, user, and printer context, but governance depends on aligning those rules to the deployed release workflow across the environment.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Printing Security Software

What separates options is how tightly they control print releases and how well they prove what happened after jobs run. Focus on criteria like access control enforcement, audit log coverage, and key management behavior so the product’s security stays consistent from setup through daily print workflows.

Print release workflow coverage

Why it matters

Print release workflow coverage matters because “secure” tools fail when real users can’t follow the enforced release path. The better the coverage, the fewer bypasses slip in during busy workflows.

How to check

In a demo, walk through at least one job submitted from the expected client, then require a release action at the device or release station. Ask what happens if the user skips the release step and whether the job still appears at the printer.

RBAC and admin role separation

Why it matters

RBAC and admin role separation prevents broad access to release settings and audit data. When roles are specific, the daily admin team can manage printers without exposing security-sensitive configuration.

How to check

Request a roles view in the admin console and check whether you can create at least two distinct roles (for example, printer admin vs security admin). Then try a task that should be denied (like changing release rules) using the lower-privilege role.

Audit log event completeness

Why it matters

Audit log event completeness matters because investigations rely on traceable outcomes, not just job status. Strong logging links submissions, releases, and outcomes in a way you can review later.

How to check

Submit a test job, release it, and attempt one failed or blocked job. In the audit log, confirm the events include who submitted, when released, where it was released, and whether the job was accepted or rejected.

Encryption and key management behavior

Why it matters

Encryption and key management behavior matters because print protection can weaken if keys are handled inconsistently across components. You want clear boundaries for what gets protected and where keys live.

How to check

During the demo, ask where encryption is applied (at submission, in transit, and at rest) and whether key rotation is supported. Review a security settings page for key handling options and request a screenshot or export of relevant configuration.

Device and protocol compatibility

Why it matters

Device and protocol compatibility matters because security features only work when the product can correctly talk to the printer path in your environment. Mismatches often show up as missing controls or plain-text fallbacks.

How to check

Bring a representative device model list and check whether release enforcement can be applied to those devices. If the product supports multiple print paths, ask which ones are fully controlled and which ones are limited, then test one job end-to-end on a non-default path.

Red flags

  • Release rules exist in the console but real jobs still print without the required release step.
  • Audit logs show only “job status” instead of submission, release, and block/allow outcomes.
  • Key handling and encryption settings are vague, undocumented, or impossible to verify in configuration exports.

Fit by situation

  • If we need users to release confidential output with strict at-device steps, prioritize Print release workflow coverage.
  • If multiple teams share admin tasks, prioritize RBAC and admin role separation.
  • If we expect incident reviews after printer events, prioritize Audit log event completeness.
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.