Commissioned Research
Top 9 Best Core Logging Software of 2026

GITNUXSOFTWARE REVIEW

Cybersecurity & Information Security

Top 9 Best Core Logging Software of 2026

Compare core logging software options for geology workflows, covering tools like Imago, and outlining tradeoffs for technical teams selecting software.

19 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

Core logging software turns drill-core observations, sample attributes, and images into queryable data models for geologists and project teams. This comparison helps evaluators weigh the tradeoffs between field capture, depth correction and RQD calculations, and integration paths such as database schemas and APIs.

acQuire GIM Suite is the best pick for geotechnical teams that need structured digital core logs because its tray photography binds images to depth context for audit-friendly reviews, while Imago fits teams that want faster photo-assisted depth marker recognition to anchor interval records.

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

acQuire GIM Suite

Tray photography workflows that bind images to logged depth context for audit-friendly digital core logging reviews.

Best for: Fits when geotechnical teams need structured digital core logs with photo-linked depth intervals and repeatable report exports.

2

Leapfrog Geo

Editor pick

Integrated geoscience project context that keeps digital core logs aligned with mapping and model workflows.

Best for: Fits when geotechnical core logging must stay linked to geological interpretation and GIS exports for teams.

3

Imago

Editor pick

Photo-assisted depth marker recognition that anchors interval records to corrected depth positions inside the logging workflow.

Best for: Fits when geology teams need controlled digital core logs with photo-assisted depth alignment.

Comparison Table

1
acQuire GIM SuiteBest overall
enterprise
9.4/10
Overall
2
enterprise
8.9/10
Overall
3
vertical specialist
8.8/10
Overall
4
vertical specialist
8.4/10
Overall
5
8.1/10
Overall
6
vertical specialist
7.8/10
Overall
7
vertical specialist
7.5/10
Overall
8
enterprise
7.1/10
Overall
9
6.9/10
Overall
#1

acQuire GIM Suite

enterprise

Geoscientific information management software for geological logging and sample data.

9.4/10
Overall
Features9.4/10
Ease of Use9.4/10
Value9.4/10
Standout feature

Tray photography workflows that bind images to logged depth context for audit-friendly digital core logging reviews.

acQuire GIM Suite combines geoscience-oriented digital core logging workflows with inventory, photography, and structured export for downstream reporting. It focuses on depth interval records and run-length tracking so teams can capture discontinuities, recoveries, and related measurements in a way that stays consistent across pages and reports.

Integration is centered on structured templates and repeatable configuration for offline field capture and laboratory handoffs, rather than generic free-form logging. Data output supports standardized log artifacts for handover, including PDF-style reporting and GIS-oriented exports for mapping and spatial review.

Pros
  • +Standardized logging templates keep depth interval records consistent across projects
  • +Run length tracking supports recovery-linked calculations during capture
  • +Tray photography workflows tie images to the logged depth context
  • +Export options fit geological core logging handoffs to reporting and mapping
Cons
  • –Requires setup of logging templates to match site coding standards
  • –Geotechnical classification coverage depends on configured domain code libraries
  • –Offline field capture workflows add operational overhead for device synchronization
  • –Complex automation needs admin governance to avoid inconsistent interval data
Use scenarios
  • Geotechnical core logging teams

    Capture depth-linked lithology and recovery

    Validated logs and exportable records

  • Geology lab coordinators

    Handoff runs between field and lab

    Fewer handoff transcription errors

Show 2 more scenarios
  • Resource reporting managers

    Generate PDF-style reporting artifacts

    Shareable reporting packages

    Depth interval records and discontinuity tracking feed standardized PDF-style outputs for distribution and audit.

  • GIS analysts

    Export logs for spatial review

    Logs ready for map QA

    GIS-oriented exports package core logging outputs for mapping workflows tied to downstream spatial assessment.

Best for: Fits when geotechnical teams need structured digital core logs with photo-linked depth intervals and repeatable report exports.

#2

Leapfrog Geo

enterprise

3D geological modeling software with drillhole data integration capabilities.

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

Integrated geoscience project context that keeps digital core logs aligned with mapping and model workflows.

Leapfrog Geo is a geoscience-focused core logging environment from Seequent that ties digital core logs to geological interpretation workflows. Core data capture supports depth-based records, structured logging forms, and scan and photo driven inputs used for traceable field documentation.

Leapfrog Geo also supports project-level lineage for imported sample and interval datasets and produces standardized exports for downstream QA review. Integration with GeoScene and other Seequent services is a key differentiator versus generic logging viewers because it keeps logs aligned with mapping and model context.

Pros
  • +Depth interval logging stays consistent across projects and interpretations.
  • +Photo and scan workflows support tray and marker driven validation.
  • +Structured logging templates reduce drift across geologists.
  • +Exports map cleanly into GIS and reporting pipelines.
Cons
  • –Advanced automation needs disciplined project configuration.
  • –Cross-system API workflows are narrower than general log management tools.
  • –Template governance across many crews takes administrative effort.
  • –Large offline capture sessions can require careful workstation tuning.
Use scenarios
  • Geotechnical core loggers

    Record RQD, fractures, and tray imagery

    Validated digital logs and PDFs

  • Exploration resource geologists

    Build geological domains from drill data

    Structured 3D resource model

Show 2 more scenarios
  • Exploration geologists QA teams

    Check interpretations against drill constraints

    Clearer interpretation gaps

    Model geometry gets compared with collars, surveys, sections, and assays to expose inconsistencies.

  • GIS specialists and project geologists

    Assemble terrain and subsurface baselines

    Shared baseline for reviews

    Terrain and raster or vector inputs combine with subsurface data to provide spatial context for interpretation.

Best for: Fits when geotechnical core logging must stay linked to geological interpretation and GIS exports for teams.

#3

Imago

vertical specialist

Cloud platform for drill-core imagery, geological observations, and visual sample records.

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

Photo-assisted depth marker recognition that anchors interval records to corrected depth positions inside the logging workflow.

Imago targets core logging workflows that produce digital core logs and structured measurements tied to depth intervals. It differentiates through field-first capture and logging templates that convert tray photos and depth markers into consistent run data.

The system then supports validation rules and automated calculations such as RQD style metrics and recovery style metrics from entered discontinuities and recovery observations. Audit trails and governance controls help keep manual geology edits traceable across revisions.

Pros
  • +Depth-interval logging templates reduce repeat data entry across runs
  • +Tray photography and depth marker recognition speed offline field capture
  • +Validation rules catch interval mistakes before exports
  • +Audit trails track edits to structural and discontinuity fields
Cons
  • –Geotechnical classification and code libraries require upfront mapping work
  • –Assay database integration needs careful field mapping per lab format
  • –Large datasets can slow interactive review when media libraries grow
  • –PDF log generation depends on standardized template configuration
Use scenarios
  • Core logging technicians

    Turn tray photos into run data

    Standardized digital records

  • Geologists validating discontinuities

    Apply rules and calculate recovery metrics

    Consistent derived measurements

Show 2 more scenarios
  • Geological QA and governance leads

    Track edits across log revisions

    Traceable change history

    Audit trails make manual geology edits traceable across revisions while keeping the logging data governable.

  • Depth-interval documentation teams

    Maintain measurements tied to depth runs

    Depth-linked searchable logs

    Structured measurements stay linked to depth intervals so the log remains searchable and reviewable by run.

Best for: Fits when geology teams need controlled digital core logs with photo-assisted depth alignment.

#4

GeologicAI

vertical specialist

Digital core logging and scanning platform with AI-assisted lithology classification, RQD calculation, and depth correction.

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

Depth-aligned automation that validates interval continuity and applies derived calculations across logged attributes.

GeologicAI is designed for core logging workflows where depth is the organizing key for every entry, including lithology coding, structural measurements, and interval tagging. It supports standardized logging templates so teams can reuse the same set of fields and constraints across projects. Digital capture is complemented by document outputs such as PDF log generation and export packages for GIS and other review flows. The automation layer enforces consistency checks around depth intervals and repeatable calculations for derived metrics.

Pros
  • +Depth-first logging workflow keeps intervals consistent across runs
  • +Standardized templates reduce variation in lithology and structural entries
  • +Validation rules catch continuity issues before export
  • +Assay database integration preserves lab references tied to depth
Cons
  • –Template setup is required to reach consistent data quality
  • –Advanced rule sets can require logging-code discipline
  • –Bulk edits are less convenient than field-by-field capture
Use scenarios
  • Geotechnical logging teams

    Standardize lithology and structure across runs

    Fewer reworks before reporting

  • Core logging supervisors

    Audit and correct depth-linked entries

    Cleaner run length tracking

Show 2 more scenarios
  • Lab and assay data managers

    Merge assay references into logs

    Reduced manual matching

    Assay database integration aligns lab results to the same depth-based log timeline.

  • Field teams doing offline capture

    Capture and review logs near the core yard

    Faster turnaround to report

    Offline field capture workflows feed depth-aligned digital core logs for later export and review.

Best for: Fits when teams need depth-aligned digital core logs with repeatable validation and downstream-ready exports.

#5

Strater

SMB

Windows software for borehole logs, well construction diagrams, and subsurface data visualization.

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

Depth-aware interval calculations that recompute derived geology metrics directly from corrected sample depths and configured logging rules.

Strater from Golden Software is geared toward digitizing and maintaining geological core logs with a workflow designed around depth-indexed records and log pages. It supports standardized logging template creation, interval-coded attributes, and calculations like RQD and recovery-style metrics using the depths and sample properties on the log.

Pros
  • +Template-driven logging reduces manual entry errors in repeating structures
  • +Depth-indexed intervals map directly to core box and tray-based workflows
  • +Built-in PDF log generation supports repeatable deliverables for stakeholders
  • +Rule-based calculations handle common geology and geotechnical derived fields
Cons
  • –Limited native integration surface for enterprise assay or lab data systems
  • –Structural measurement capture is usable but not as granular as specialized geology CAD
  • –Custom template governance needs local admin discipline across multiple projects
  • –Automation via APIs and scripting is less documented than general engineering logging workflows
Use scenarios
  • Geologists and core logging teams

    Create structured depth-referenced core logs

    Consistent core annotations

  • Subsurface mapping teams

    Generate cross-sections for boreholes

    Cross-section review figures

Show 2 more scenarios
  • Geotechnical deliverable writers

    Produce shareable well report outputs

    Report-ready log figures

    Formatted log diagrams are exported for review and inclusion in documentation as consistent figures.

  • Interpretation teams comparing wells

    Correlate multiple logs in composites

    Better correlation visibility

    Multiple well logs or curves are arranged for pattern review to support correlation and quality checks.

Best for: Fits when geology teams need digital, depth-indexed core logs with repeatable templates and exportable PDFs.

#6

LogChief

vertical specialist

Electronic data capture application for drill core and chip logging.

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

Template-driven depth interval records that maintain corrected depth alignment across run length and interval entries.

LogChief targets geotechnical core logging with depth interval records that connect measurements to corrected depth positions and run length tracking. Standardized logging templates are used to drive alteration coding, structural measurements, and discontinuity logging so logged fields stay consistent across projects and runs. PDF log generation helps produce review-ready documents without reformatting exported spreadsheets.

Pros
  • +Depth interval records keep measurements tied to corrected depth positions
  • +Standardized logging templates support consistent alteration and discontinuity fields
  • +Offline field capture reduces interruptions during core processing
  • +PDF log generation supports geotechnical review cycles
Cons
  • –Depth marker recognition needs disciplined photo and marker practices
  • –Some cross-system workflows depend on manual export or custom integration
Use scenarios
  • Geotechnical logging teams

    Capture interval and recovery during drilling

    Fewer interval alignment errors

  • Core management leads

    Track tray photos and inventory

    Clean core box inventory linkage

Show 2 more scenarios
  • Project controls and QA

    Enforce validation during entry

    More reliable logging changes history

    Applies validation rules and an audit trail behavior to reduce inconsistent edits in structured fields.

  • Assay and lab coordinators

    Integrate lab results into logs

    One reviewed record per interval

    Connects logged intervals to lab-provided assay values for consolidated digital log outputs.

Best for: Fits when field and lab teams need digital core logs with template-driven validation and review-ready PDFs.

#7

Geobank Mobile

vertical specialist

Mobile geological data collection software for field logging, sampling, and drill programs.

7.5/10
Overall
Features7.5/10
Ease of Use7.6/10
Value7.4/10
Standout feature

Tray photography capture tied to depth interval records with depth-anchored editing and later audit trail review.

Geobank Mobile captures geotechnical core logging work in the field and converts observations into structured digital records. It supports depth interval records and run length tracking for RQD and recovery calculation workflows.

Pros
  • +Offline field capture reduces interruptions during shift work
  • +Run length tracking supports consistent RQD and recovery calculations
  • +Tray photography ties visual context to logged depth intervals
  • +Audit trail supports later traceability of edits to logged records
Cons
  • –Depth marker recognition can require consistent field photo framing
  • –Assay database integration is limited for complex lab workflows
  • –Admin and RBAC granularity lags behind enterprise logging platforms
  • –Spreadsheet import supports common formats but struggles with nested interval edits
Use scenarios
  • Field core logging crews

    Capture interval records offline

    Digitized logs ready for review

  • Geotechnical lab and desk teams

    Reconcile run-length data after sync

    Auditable revision history

Show 2 more scenarios
  • Core documentation coordinators

    Record tray photos with structured context

    Context-rich digital records

    Tray photography is captured alongside run data so core context travels into later reporting outputs.

  • GIS analysts

    Export logged core context for mapping

    Mapping-ready core datasets

    Logged data supports GIS export so captured core runs can be included in spatial review and mapping workflows.

Best for: Fits when field teams need structured digital core logs with photography and depth interval workflows.

#8

GeoticLog

enterprise

Geological logging software for capturing, analyzing, and visualizing core sample data with database integration and QA features.

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

Run length tracking tied to depth marker recognition with validation rules for interval consistency during capture.

GeoticLog from alsglobal.com captures and manages geological core logging records with depth-interval fidelity. The core workflow centers on standardized digital log templates that support measurements, discontinuity notes, and coded observations linked to depth runs.

Pros
  • +Depth-interval records keep structural and sample data aligned for runs
  • +Standardized logging templates reduce drift across technicians and shifts
  • +Validation rules catch inconsistent depth markers and coded entries
  • +Exports support downstream reporting and GIS or assay-style workflows
Cons
  • –Template setup requires domain governance to avoid inconsistent coding
  • –Advanced calculations like RQD style metrics depend on configured rule sets
  • –Offline field capture workflows need careful device and synchronization handling
  • –High-volume logging throughput can require tuning of import and export batch sizes
Use scenarios
  • Geological logging operators

    Capture discontinuity notes by depth

    Structured depth-interval records

  • Data integration analysts

    Export files into external systems

    Logs usable in other tools

Show 2 more scenarios
  • Core logging QA teams

    Run repeatable validation during capture

    Lower capture inconsistencies

    Validation rules and repeatable run tracking keep field capture consistent and searchable.

  • Project documentation leads

    Maintain auditable run handling

    Auditable searchable logs

    Run tracking supports consistent documentation of core logging activities for later audit and retrieval.

Best for: Fits when geotechnical teams need governed digital core logs with depth-linked records.

#9

GeoBase

SMB

Free Microsoft Access-based core logging utility storing collars, deviations, lithology, alteration, geochemistry, and RQD in an integrated database.

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

Tray photography paired with depth marker recognition for depth correction during core logging sessions.

GeoBase targets geotechnical core logging workflows with a field-to-digital path for depth-linked records like lithology, structure, and recovery. Core log data is organized around run handling and depth interval records so RQD-style derived metrics and discontinuity measures can be calculated and carried forward.

Pros
  • +Depth interval records keep lithology, structures, and measurements tied to correct positions
  • +Tray photography and depth marker recognition reduce manual depth alignment errors
  • +Spreadsheet import accelerates migration from Excel-based core logs
  • +PDF log generation and GIS export support common handoff formats
Cons
  • –Automation and integration depth depends on external workflows for assay and LIMS sync
  • –Governance controls like RBAC and audit log are not a primary focus in core logging
  • –Validation rules coverage can feel template-bound for custom coding libraries
  • –Offline field capture requires a separate process to avoid later reconciliation work
Use scenarios
  • Geotechnical core logging teams

    Digitize lithology and recovery by run

    Depth-linked core datasets

  • Core photography and digitization staff

    Use tray photos and depth markers

    Faster digitization

Show 2 more scenarios
  • Field survey data teams

    Import spreadsheets for existing records

    Reduced manual entry

    Spreadsheet import helps digitize existing core documentation without re-entering every attribute.

  • Engineering and lab reviewers

    Share PDF-style and GIS-ready exports

    Shareable log outputs

    Exported digital core logs include PDF-style outputs plus GIS-ready files for downstream engineering and lab use.

Best for: Fits when geotechnical teams need depth-corrected digital core logs with photo-assisted capture and shareable outputs.

Conclusion

After evaluating 9 core logging software, acQuire GIM Suite 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
acQuire GIM Suite

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 Core Logging Software

How do GeologicAI and Strater handle depth interval records so discontinuities and recovery stay consistent?
GeologicAI validates interval continuity and applies derived calculations across logged attributes along the depth timeline. Strater recomputes derived geology metrics from corrected sample depths using the project’s configured logging rules.
When does depth marker recognition matter most in MX Deposit and Imago, and what output changes as a result?
MX Deposit uses depth marker recognition to tie tray positions to depth positions so interval-level corrections can be applied during logging. Imago anchors interval records to corrected depth positions using photo-assisted depth marker recognition inside the workflow.
Which tool fits teams that need a field-first offline capture flow with later audit trail review?
Geobank Mobile supports mobile-to-desktop capture with offline field capture and keeps an audit trail for later review. LogChief supports offline field capture with audit trail behavior tied to validation rules during data entry.
How do acQuire GIM Suite and Leapfrog Geo differ when the goal is export into mapping or interpretation workflows?
acQuire GIM Suite emphasizes structured exports for downstream reporting and GIS-oriented handover based on its configured templates and photo-linked depth intervals. Leapfrog Geo ties digital core logs to geological interpretation and mapping context through integrated project workflows and aligned exports.
What integrations and APIs support assay database or lab information system handoffs in GeoticLog and GeologicAI?
GeoticLog focuses on moving logged data into external systems through documented interfaces and file-based exports for downstream analysis and reporting. GeologicAI supports extensibility by connecting external assay data and lab references into the same depth-based log timeline.
What breaks if standardized logging templates and validation rules are not enforced in LogChief and MX Deposit?
LogChief can lose review consistency because template-driven depth interval records and validation rules are what keep corrected depth alignment stable across run length and interval entries. MX Deposit can accumulate manual transcription drift when standardized templates and validation rules are not applied to lithology and structural coding.
How do audit and governance controls show up in Imago compared with Strater during iterative edits?
Imago includes audit trails and governance controls that keep manual geology edits traceable across revisions. Strater reinforces auditability through versioned edits and consistency checks tied to the logging rules configured for a project.
Which tool supports spreadsheet import for existing core documentation while maintaining depth-interval fidelity?
GeoBase supports spreadsheet import to speed up digitization while keeping depth-linked records organized around runs and depth interval records. GeoticLog centers on standardized digital log templates for measurements and coded observations tied to depth runs, which also supports controlled capture when templates are available.
How do tray photography workflows differ between Geobank Mobile and acQuire GIM Suite?
Geobank Mobile ties tray photography capture to depth interval records and later depth-anchored editing with audit trail retention. acQuire GIM Suite uses tray photography workflows that bind images to logged depth context for audit-friendly digital core logging reviews.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Core Logging Software

We separate core logging software by how reliably it keeps depth and events consistent from capture to export. The big differences show up in data model fit, automation and API surface, and admin and governance controls.

Depth-to-event consistency

Why it matters

Core logging breaks when depth and recorded events drift. Depth-to-event consistency determines whether downstream reports, corrections, and re-exports stay trustworthy.

How to check

Load a sample log file and intentionally change a depth value for one interval, then see whether dependent fields update correctly. Ask how the tool handles edits that affect previously entered events and whether it preserves a clear history.

Data model and schema alignment

Why it matters

Core logging teams rarely use identical fields or interval structures. Data model and schema alignment lets the tool represent what your group actually records without awkward workarounds.

How to check

During the demo, review a sample schema for intervals and measurements and compare it to your current template. Ask whether you can add or reorder fields (and required fields) without rebuilding everything later.

Automation and API surface

Why it matters

Batch ingest, re-processing, and controlled updates require more than screen entry. A strong automation and API surface helps keep throughput high while reducing manual transcription errors.

How to check

Request an example workflow: import a small dataset, map fields, run a transformation, and export results. Then ask what API endpoints or automation hooks exist for those steps and whether they support idempotent re-runs.

Admin and governance controls

Why it matters

When multiple loggers touch the same project, governance prevents silent inconsistencies. Admin and governance controls affect how configuration, access, and changes stay controlled across teams.

How to check

Show user roles and permissions and ask whether RBAC can restrict who can change schemas, templates, or validated records. Check whether the system records an audit log of edits tied to user and time.

Validation rules for logging quality

Why it matters

Validation rules catch missing or contradictory entries before export. Validation rule coverage reduces rework when teams compare runs, intervals, and measurement completeness.

How to check

Ask the demo team to enable common checks (required fields, allowed ranges, and missing interval links) and see how errors are presented. Then try saving an incomplete record and confirm what blocks export versus what only warns.

Export consistency for reports

Why it matters

Teams evaluate outputs after re-exports, not just on-screen views. Export consistency ensures the numbers and intervals match what loggers entered, including after edits.

How to check

Create two exports after making a small edit and compare whether interval boundaries and derived totals stay consistent. Ask which export formats are supported and whether you can reproduce the same output from the same project state.

Red flags

  • Edits to depths leave intervals and events out of sync without clear warnings.
  • The product only supports your workflow by forcing awkward spreadsheets or copy-paste steps.
  • Export results change after re-run without a way to trace what differed.

Fit by situation

  • If your team frequently revises interval boundaries after initial capture, prioritize Depth-to-event consistency.
  • If you maintain custom field sets per project, prioritize Data model and schema alignment.
  • If you need batch re-processing and controlled updates across users, prioritize Automation and API surface.
Commissioned Research

Funding and competing interests

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

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

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

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.