Commissioned Research
Top 10 Best Email Review Software of 2026

GITNUXSOFTWARE REVIEW

Communication & Media

Top 10 Best Email Review Software of 2026

Compare email review software tools for testing deliverability and formatting, with tradeoffs and use cases for Mailosaur.

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

Agents extract product evidence with provenance, then collect written reviews and 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

Email review software matters because the same template can render differently across clients and because approval gaps can turn small markup changes into deliverability or compliance defects. This comparison helps QA and marketing operators weigh test automation, sandbox previews, and workflow governance when choosing between tools built for developers and tools built for production teams.

Mailosaur is the best pick for QA teams that need automated, API-based verification of rendered email outputs after sends, because disposable inboxes with an HTTP API let you repeat message retrieval and assertions reliably, whereas Email on Acid suits SMB teams wanting client rendering previews with section-level reviewer annotations that make fix review faster.

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

Mailosaur

Disposable inboxes with HTTP API allow automated retrieval and programmatic assertions on received messages.

Best for: Fits when QA teams need automated, API-based verification of rendered email output after sends.

2

Email on Acid

Editor pick

Client rendering preview combined with section-level reviewer annotations accelerates fix review without losing context.

Best for: Fits when teams need consistent pre-send email review with client rendering evidence and annotated feedback.

3

BEE

Editor pick

Annotated review comments attached to specific render outputs with version comparison for tighter approval audit trails.

Best for: Fits when marketing teams need shared pre-send approval workflow with annotated renders and change tracking.

Comparison Table

1
MailosaurBest overall
API-first
9.3/10
Overall
2
8.9/10
Overall
3
SMB
8.8/10
Overall
4
enterprise
8.5/10
Overall
5
8.1/10
Overall
6
enterprise
7.8/10
Overall
7
enterprise
7.4/10
Overall
8
specialist
7.3/10
Overall
9
API-first
6.9/10
Overall
10
enterprise
6.7/10
Overall
#1

Mailosaur

API-first

Automated email and SMS testing for applications, workflows, and user journeys.

9.3/10
Overall
Features9.3/10
Ease of Use9.3/10
Value9.3/10
Standout feature

Disposable inboxes with HTTP API allow automated retrieval and programmatic assertions on received messages.

Mailosaur creates sandbox inboxes that capture inbound email so QA teams can validate subject lines, preheaders, link URLs, and merge-tag behavior after an ESP or automation sends. The API surface supports automated test-send verification by polling for messages and retrieving the raw or parsed email payload. This makes it practical for CI jobs that need deterministic results across changes to templates, subject lines, and rendering paths.

A tradeoff is that inbox creation and assertions are code-led, so pre-send approval workflows and human annotation require external tooling and review steps. Mailosaur fits teams that already have a design-to-email pipeline that can run test sends and then programmatically validate the received output before deployment.

Pros
  • +API-controlled inbox lifecycle supports repeatable test-send verification
  • +Received message retrieval enables automated HTML and attachment assertions
  • +Header-level inspection helps validate from fields, subjects, and delivery markers
  • +Sandbox inboxes reduce risk from using real employee inboxes
Cons
  • –Human pre-send approval workflows need external process and tooling
  • –Email rendering checks require additional steps beyond message capture
  • –Complex validations depend on custom assertions and parsing logic
Use scenarios
  • QA automation engineers

    Verify email output in CI runs

    Deterministic regression checks

  • Marketing operations teams

    Validate personalization and merge behavior

    Fewer personalization defects

Show 2 more scenarios
  • Email platform developers

    Test ESP integrations with seeds

    Integration confidence per release

    Provision sandbox inboxes per test and confirm each send produces expected attachments and links.

  • Accessibility and QA reviewers

    Inspect raw HTML for compliance issues

    Earlier defect detection

    Retrieve message HTML and check structure and link destinations before approving template changes.

Best for: Fits when QA teams need automated, API-based verification of rendered email output after sends.

#2

Email on Acid

SMB

Email pre-deployment testing with previews, validation, and review workflows.

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

Client rendering preview combined with section-level reviewer annotations accelerates fix review without losing context.

Email on Acid targets email campaign review with a rendering and QA workflow that catches client-specific differences before sends. The tool supports HTML inspection, rendering preview across major clients and devices, and test-send validation for links and tracking behavior.

It also provides annotation style review so teams can leave reviewer notes against specific sections of an email build. For governance, it supports controlled collaboration so approvals and reviewer decisions stay tied to the reviewed asset.

Pros
  • +Cross-client rendering preview highlights layout shifts in real inbox contexts
  • +HTML inspection surfaces structural issues that rendering previews can hide
  • +Reviewer annotations tie comments to specific parts of a message
  • +Link and tracking checks reduce avoidable QA failures in pre-send workflow
Cons
  • –Pre-send workflows require disciplined asset versioning to stay audit-friendly
  • –Advanced governance needs tighter process design than teams expect
Use scenarios
  • Creative and engineering teams

    Review table layouts and CSS behavior

    Earlier layout issue detection

  • Front-end email developers

    Validate responsive template behavior

    More consistent layouts

Show 2 more scenarios
  • Email QA and compliance reviewers

    Check accessibility and required elements

    Fewer omissions

    Reviewers verify alt text, preheaders, unsubscribe elements, and other compliance requirements.

  • Email approvers and creatives

    Compare revised variants with evidence

    Faster sign-off decisions

    Teams review A/B or updated assets using shared visual evidence and issue-focused reports.

Best for: Fits when teams need consistent pre-send email review with client rendering evidence and annotated feedback.

#3

BEE

SMB

Collaborative email design software with reusable templates and client review workflows.

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

Annotated review comments attached to specific render outputs with version comparison for tighter approval audit trails.

BEE handles email campaign review by turning an email HTML and its template variables into a structured preview and checklist for approval. It supports reviewer annotation and version comparisons so teams can track what changed between revisions.

The workflow focuses on pre-send review steps like visual rendering preview and merge-tag validation before a test send. Collaboration is centered on shared review states rather than file sharing or chat threads.

Pros
  • +Reviewer annotation tied to specific renders to reduce review ambiguity
  • +Template-variable checks catch merge-tag issues before approval
  • +Version-to-version comparison supports faster approval of small edits
  • +Shared approval states coordinate QA and marketing stakeholders
Cons
  • –Cross-client testing depth depends on what preview targets are configured
  • –API automation surface is limited for complex programmatic review orchestration
Use scenarios
  • Design and marketing approvers

    Review rendered previews before test sends

    Earlier layout issue detection

  • Lifecycle and growth teams

    Build nurture sequences from components

    Consistent sequence design

Show 2 more scenarios
  • Email developers and marketing ops

    Export responsive email markup

    Less manual markup work

    Developers export structured responsive HTML for downstream publishing and sending workflows.

  • Ecommerce and campaign marketers

    Create frequent promotional emails faster

    Quicker campaign creation

    Campaign teams use approved blocks and repeatable baselines to reduce layout rework.

Best for: Fits when marketing teams need shared pre-send approval workflow with annotated renders and change tracking.

#4

Knak

enterprise

Enterprise email creation and approval software for marketing operations teams.

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

Element-level reviewer annotations persist through email version changes so approvals map to the exact draft revision.

Knak’s core value is reviewer annotation that remains attached to the email artifact as versions change, which makes cross-round reviews less ambiguous. Pre-send steps support an approval sequence that maps comments to the draft under review, which helps QA and marketers coordinate on the same output. Rendering preview coverage supports cross-client sanity checks like mobile layout inspection, and the system keeps a review trail tied to each revision.

Pros
  • +Reviewer comments stay linked to specific email elements across versions
  • +Pre-send approval workflow preserves a clear review trail
  • +Rendering preview helps catch layout issues before test sends
  • +Markup and link checks reduce common publish-time errors
Cons
  • –Comment tracking relies on using Knak-managed versions, not external copies
  • –Advanced governance depends on disciplined review rounds and ownership
Use scenarios
  • Marketing operations teams

    Template updates with controlled sign-off

    Fewer approval loops and rework

  • Email QA analysts

    Mobile layout verification pre-send

    Faster fixes before test sends

Show 1 more scenario
  • Brand and compliance reviewers

    Consistency checks across campaigns

    Clear accountability for approvals

    Compliance feedback is recorded in the approval trail so subsequent drafts show what changed and why.

Best for: Fits when QA and marketing need element-level email review with audit-ready approval history.

#5

Stripo

SMB

Email production software with template testing, collaboration, and approval controls.

8.1/10
Overall
Features8.1/10
Ease of Use8.0/10
Value8.2/10
Standout feature

Reviewer feedback attaches to template versions, which keeps approvals tied to the specific generated HTML.

Stripo combines email design and review in one workspace, which reduces the handoff gap between marketers and QA. Versioning and change history support repeatable template updates, so reviewers can track what changed rather than compare copied HTML. Preview views help validate layout behavior across common viewport sizes, which supports quick iteration during pre-send approval workflow reviews.

Pros
  • +Versioned templates keep reviewer feedback tied to the exact HTML draft
  • +Device and rendering previews reduce late-stage layout regression risk
  • +Annotation-style review workflows support faster QA signoff cycles
  • +Export-ready outputs fit common ESP and marketing automation publish flows
Cons
  • –Cross-client testing depth is limited compared with dedicated test lab tools
  • –Automated link and personalization checks are not comprehensive for all edge cases
Use scenarios
  • Email marketing QA teams

    Review HTML drafts before approval

    Fewer approval reversals

  • Marketing ops teams

    Maintain reusable template governance

    Lower template drift

Show 1 more scenario
  • Design teams

    Hand off review-ready emails

    Faster design-to-approval

    Designers generate structured HTML drafts that reviewers can inspect and annotate without rework.

Best for: Fits when teams need reviewable HTML drafts, version history, and preview-driven QA before approvals.

#6

Taxi for Email

enterprise

Enterprise email production software with modular content, governance, and approvals.

7.8/10
Overall
Features7.8/10
Ease of Use7.9/10
Value7.7/10
Standout feature

Render-linked reviewer annotations with change tracking that preserve an approval audit trail.

Taxi for Email targets email campaign review with a browser-first workflow for content proofing before send. It focuses on review states, reviewer annotations, and change tracking tied to specific email renders, rather than only static document sharing.

Pros
  • +Approval flow ties comments to specific email renders
  • +Reviewer annotations make handoffs between design and marketing concrete
  • +Template versioning supports controlled updates across campaigns
  • +Change tracking supports review audit trail for what changed
Cons
  • –Cross-client testing depth is limited versus dedicated rendering labs
  • –Advanced validation coverage depends on manual reviewer checks
Use scenarios
  • Email designers and QA reviewers

    Proof content in-browser before send

    Fewer pre-send surprises

  • Email operations approvers

    Compare approved versus pending template versions

    Clearer sign-off changes

Show 1 more scenario
  • Design-to-email production teams

    Catch issues during review inputs

    Earlier issue detection

    Teams use inspection and rendering inputs to identify problems earlier in the workflow.

Best for: Fits when QA and marketing need structured pre-send approval and clear reviewer feedback.

#7

Litmus

enterprise

Email testing, preview, collaboration, and approval software for marketing teams.

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

Cross-client rendering previews with issue-focused reporting that maps problems back to email components.

Litmus is an email review and testing suite used to catch rendering and deliverability issues before launch. It provides cross-client rendering preview, structured test reports, and actionable remediation guidance for responsive layouts, typography, and interactive elements.

Pros
  • +Rendering previews cover many desktop and mobile clients in one report view
  • +Test reporting groups issues by component so fixes are easier to verify
  • +Repeatable test-send workflows support faster regression testing
  • +Validation checks catch common link and tracking mistakes pre-send
Cons
  • –Higher-volume testing needs careful workflow planning to avoid review bottlenecks
  • –Some validations depend on proper tracking and template conventions
  • –Sharing review artifacts across teams can require extra process discipline
  • –Deep automation hinges on the available integrations and rollout practices
Use scenarios
  • Email designers and developers

    Iterate on responsive templates

    Reusable templates improve

  • Email marketing teams

    Run pre-send screenshot comparisons

    Fewer defects reach inboxes

Show 2 more scenarios
  • Email production content teams

    Validate accessibility and content signals

    Earlier defect identification

    Teams review accessibility signals, link behavior, image behavior, HTML issues, and spam requirements.

  • Email operations and governance teams

    Compare campaign changes to baselines

    More consistent evaluation

    Teams evaluate updates by reviewing changes against prior campaign results using consistent test evidence.

Best for: Fits when marketing and QA teams need consistent cross-client review with repeatable test-send workflows.

#8

GlockApps

specialist

Email testing software for spam analysis, inbox placement, and deliverability review.

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

Seed-style deliverability testing that reports inbox placement outcomes and spam risk signals per test send.

GlockApps focuses on email deliverability and campaign testing rather than approval workflows, so QA and marketers can validate sending behavior before wider rollout. The core workflow centers on seed-list style test sends and monitoring of inbox placement signals across major providers.

Pros
  • +In-depth inbox placement style signals across major webmail providers
  • +Test-send workflow ties results to the exact message that was sent
  • +Clear reporting for deliverability risk areas like spam filtering patterns
  • +Useful for iterative subject and content changes with fast feedback
Cons
  • –Less focused on visual email content proofing and reviewer annotations
  • –Automation and API coverage is narrower than review-centric platforms
  • –Cross-client rendering checks are not as comprehensive as dedicated preview tools
  • –Requires disciplined test asset management to avoid ambiguous results
Use scenarios
  • Email QA specialists

    Compare rendering across inboxes

    Common issues caught early

  • Small outbound email teams

    Oversee warm-up delivery ramp-up

    Delivery changes observed early

Show 2 more scenarios
  • Email security and deliverability teams

    Investigate DMARC alignment failures

    Affected sources identified

    Security teams review report patterns by sender and subdomain to pinpoint recurring alignment problems.

  • Email marketing and lifecycle teams

    Validate placement and authentication before broadcast

    Delivery risks surfaced early

    Teams check placement signals, spam risk, and authentication before sending to the full audience.

Best for: Fits when QA teams need inbox placement and spam risk checks before broader email sends.

#9

Mailtrap

API-first

Email sandbox software for testing messages, templates, links, and delivery behavior.

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

Dedicated inbox-style sandbox for inspecting captured messages from automated test-send runs via API.

Mailtrap routes outgoing email through a controlled testing environment so QA and marketing teams can run repeatable email campaign review without risking real recipients. The system provides message inspection, rendering checks, and traceable test-send runs, with APIs designed for automation in CI and release workflows.

Pros
  • +Sandbox email testing prevents accidental sends during campaign review
  • +Message inspection includes headers and raw content for debugging
  • +API-driven test runs fit CI and automated email verification
  • +Environment separation supports parallel releases and reviewer workflows
Cons
  • –Cross-client testing depth depends on external preview behavior
  • –Pre-send approval workflow requires careful process setup across teams
Use scenarios
  • Email developers and marketing teams

    Review cross-client rendering before release

    Problems found before release

  • QA automation and DevOps teams

    Run automated regression checks

    Repeatable email verification

Show 2 more scenarios
  • Application developers and QA engineers

    Test transactional templates pre-release

    Fewer broken transactional emails

    Application teams inspect receipts, alerts, and account messages to prevent broken layouts and missing content.

  • Developers and test engineers

    Capture staging mail in isolated inboxes

    Test traffic stays separate

    Staging messages are routed to isolated inboxes to avoid contacting real production users.

Best for: Fits when QA and marketing need repeatable email rendering preview and inspection tied to automated test-send runs.

#10

Stensul

enterprise

Email and landing page production software with review and approval workflows.

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

In-editor reviewer annotations tied to specific email sections, with an approval audit trail per revision.

Stensul centers email and message feedback around visual, in-editor review workflows rather than side-channel comments. It supports annotated reviewer feedback and structured approval steps so teams can move from design to pre-send signoff with traceability. The tool also focuses on rendering checks that help reviewers spot layout issues before test sends.

Pros
  • +Visual annotations keep reviewer context tied to specific email elements
  • +Approval steps support an approval audit trail across iterations
  • +Rendering previews reduce rework from last-minute formatting surprises
  • +Version history makes it easier to compare edits between review rounds
Cons
  • –Native link validation and UTM validation are limited for QA-style checks
  • –API coverage is narrower than tools built around extensive ESP automation
  • –Cross-client testing depth depends on how previews are configured
  • –Review governance needs consistent reviewer routing and naming discipline
Use scenarios
  • Design teams and reviewers

    Give in-editor annotated feedback

    Feedback tied to visuals

  • Marketing and pre-send approvers

    Complete structured approval steps

    Traceable approval trail

Show 1 more scenario
  • Email QA reviewers

    Spot layout issues before test sends

    Layout defects caught earlier

    Reviewers use rendering checks to identify layout problems before running test sends.

Best for: Fits when teams need visual email review with approval tracking for marketing and design stakeholders.

Conclusion

After evaluating 10 email review software, Mailosaur 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
Mailosaur

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 Email Review Software

How do Mailosaur and Litmus differ in what they validate during email campaign review?
Mailosaur validates received messages by polling a disposable inbox via HTTP API and running assertions on parsed headers, body content, and attachments after test sends. Litmus validates what recipients see by running cross-client rendering preview and producing component-mapped reports that focus on layout and interactive rendering differences.
Which tool is better for automating pre-send checks in CI pipelines, Mailtrap or Mailosaur?
Mailtrap supports sandbox endpoints and CI-friendly APIs that capture and inspect test sends tied to automated runs. Mailosaur runs disposable, API-driven inboxes that control inbox lifecycle and retrieval so QA can programmatically assert received messages.
How does Stripo keep approvals tied to the exact HTML revision compared with Knak?
Stripo attaches reviewer feedback to template versions so the approval context stays aligned to the generated HTML output. Knak keeps approvals traceable through structured, element-level annotations that persist through email version changes so reviewers can map decisions to the exact draft revision.
When do pre-send rendering previews matter more than inbox placement testing, GlockApps vs Email on Acid?
GlockApps emphasizes seed-style test sends and reports inbox placement and spam risk signals, which matter for send-risk validation. Email on Acid emphasizes rendering preview across major clients and devices and provides HTML inspection plus validation so teams can catch client-specific differences before sends.
What breaks if an email review workflow lacks element-level annotations, and how do Knak and Email on Acid handle it differently?
Without element-level annotations, teams lose a direct mapping between reviewer comments and the exact part of the email that needs change. Knak anchors comments to specific sections in the draft so approvals stay traceable across iterations, while Email on Acid ties annotated feedback to sections of an email build alongside rendering evidence.
How do Mailosaur and Mailtrap handle message retrieval for verification after test-send workflow runs?
Mailosaur uses its HTTP API to control disposable inboxes and to poll for messages so QA can inspect received outputs programmatically. Mailtrap routes outgoing messages into a controlled testing environment and exposes sandbox endpoints designed for captured message inspection tied to test-send runs.
How do accessibility and content integrity checks differ across tools that focus on rendering preview versus proofing lists, for example Litmus and BEE?
Litmus generates cross-client rendering previews and issue-focused reports that map rendering problems back to email components, which helps detect responsive and typography regressions. BEE converts HTML and template variables into a structured preview and checklist so reviewers can run merge-tag validation and track what changed between revisions as part of shared approval states.
Which tool supports a browser-first proofing workflow with change tracking tied to specific renders, Taxi for Email or Stensul?
Taxi for Email uses a browser-first workflow that links reviewer annotations to renders and keeps change tracking tied to what is about to be deployed versus what was approved. Stensul runs visual in-editor feedback with structured approval steps and an approval audit trail per revision.
When teams need audit-ready approval history during controlled publishing, what workflow gap appears between GlockApps and Knak?
GlockApps centers on deliverability and seed-list style testing rather than approval workflows, so it does not provide the same controlled publishing and traceable approval history for draft iterations. Knak provides an approval flow designed for controlled publishing with element-level reviewer annotations that remain tied to version changes.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Email Review Software

We separate email review software by how tightly it supports the review loop: the quality of the rendering and comparison you can trust, and the control you get over comments, approvals, and audit logs. Look for strong configuration and an automation surface so reviews stay consistent as templates and content change.

Approval workflow with RBAC

Why it matters

Reviewers need clarity on who can move an email forward and who can only comment. An RBAC-aware approval workflow reduces accidental publishing and keeps accountability tied to the email version.

How to check

Ask to see an end-to-end flow: draft → review → approve → publish. Confirm you can assign roles (reviewer vs approver) and that the system blocks publishing until the required approvals complete.

Rendering preview for key clients

Why it matters

Rendering preview quality determines whether reviewers catch layout issues early. If the preview is vague or inconsistent, the team will rely on last-minute manual checks.

How to check

In a demo, load a sample HTML email with tables, images, and long text, then compare the preview across at least a few common clients. Ask whether the preview shows the same HTML the product will send and what happens when unsupported markup is used.

Version diff and change history

Why it matters

Version diff and change history help reviewers focus on what actually changed between iterations. Without it, teams miss small but risky edits in templates and reused components.

How to check

Have the demo user create two versions of the same email, then show a visual diff that highlights changes. Ask whether the audit trail links the diff to reviewer actions (comments, approvals) tied to each version.

Inline commenting on render and HTML

Why it matters

Inline annotation speeds convergence because reviewers can reference exactly what they see. The best tools connect comments to a specific place in the email, not only to the whole file.

How to check

Test with a message that contains multiple sections and ask the demo to place comments at specific blocks. Check whether replies resolve or reopen the same comment thread and whether comments persist across revisions using the version diff.

API and automation hooks for reviews

Why it matters

An automation and API surface lets teams integrate review steps into their content pipeline and avoid manual handoffs. When content changes frequently, automation prevents review drift across branches and environments.

How to check

Ask what triggers reviews automatically (on content update, template publish, or new version). In a sandbox, request a sample API call or webhook event that creates a review task and attaches it to the correct version.

Red flags

  • Preview looks like a generic mock instead of a client-accurate render
  • Approvals can be bypassed or roles can’t restrict publish actions
  • Version history doesn’t clearly connect changes to reviewer decisions

Fit by situation

  • If your team needs controlled sign-off across multiple reviewers, prioritize approval workflow with RBAC.
  • If reviewers often discover layout problems late, prioritize rendering preview for key clients.
  • If templates change frequently, prioritize version diff and change history.
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.