Commissioned Research
Top 9 Best Document Data Extraction Software of 2026

GITNUXSOFTWARE REVIEW

Data Science & Analytics

Top 9 Best Document Data Extraction Software of 2026

Compare document data extraction software options for parsing PDFs and forms, with tradeoffs and use cases for teams evaluating tools like Parseur.

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

Document data extraction software turns OCR text, layout cues, and structured templates into repeatable field outputs for analytics, billing, and back-office workflows. This comparison helps scanners, operations, and engineers weigh tradeoffs between configurable parsing like Docparser and document conversion pipelines like ABBYY FineReader, including integration paths, API design, and how teams provision schemas for predictable throughput.

ABBYY FineReader is the best fit for teams that need accurate multilingual conversion with reliable document comparison because its Document Comparison flags text and formatting changes across versions, while Parseur suits SMBs chasing mailbox-driven extraction with reusable parsing templates for recurring emails and attachments.

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

ABBYY FineReader

FineReader PDF's Document Comparison identifies text and formatting changes across two document versions.

Best for: Fits when teams need accurate multilingual conversion, document comparison, and searchable archives from scanned files.

2

Parseur

Editor pick

Mailbox-level routing with reusable parsing templates for email bodies and attachments

Best for: Fits when teams need mailbox-driven extraction for recurring documents and email attachments.

3

Grooper

Editor pick

Grooper’s exception handling routes low-confidence fields into a review workflow that updates extracted outputs for final export.

Best for: Fits when teams need template-driven extraction with review queues and API-driven handoff to back-office systems.

Comparison Table

1
ABBYY FineReaderBest overall
enterprise
9.5/10
Overall
2
8.9/10
Overall
3
enterprise
8.7/10
Overall
4
8.5/10
Overall
5
API-first
8.3/10
Overall
6
enterprise
7.8/10
Overall
7
vertical specialist
7.6/10
Overall
8
enterprise
7.1/10
Overall
9
enterprise
6.8/10
Overall
#1

ABBYY FineReader

enterprise

OCR and document conversion software for text extraction.

9.5/10
Overall
Features9.5/10
Ease of Use9.5/10
Value9.5/10
Standout feature

FineReader PDF's Document Comparison identifies text and formatting changes across two document versions.

FineReader PDF combines recognition with zone editing, page reordering, searchable PDF creation, and conversion to Microsoft Office formats. Its document comparison view identifies text and formatting differences between two files, supporting controlled review of revised contracts and procedures. FineReader Engine extends the recognition technology into custom applications through an SDK, but it is separate from FineReader PDF.

Accuracy depends on scan quality, language selection, and page complexity. The desktop product suits analysts processing document batches manually, while unattended ingestion and structured field capture require a broader ABBYY deployment.

Pros
  • +Preserves page structure during editable Office export
  • +Recognizes multilingual scans and mixed document layouts
  • +Compares text and formatting across document versions
  • +Exports searchable PDF and PDF/A files
Cons
  • –Desktop workflows lack native unattended server ingestion
  • –Field-level extraction is not the desktop application's primary workflow
  • –OCR accuracy drops on poor scans and handwriting
  • –Custom SDK automation requires the separate FineReader Engine product
Use scenarios
  • Legal operations teams

    Revised contract comparison

    Faster revision checks

  • Records management teams

    Scanned archive conversion

    Searchable digital archives

Show 2 more scenarios
  • Finance analysts

    Invoice spreadsheet conversion

    Reduced manual transcription

    Table recognition transfers tabular invoice pages into XLSX files for downstream reconciliation.

  • Software engineering teams

    Embedded document recognition

    Embedded conversion workflows

    FineReader Engine SDK adds ABBYY recognition capabilities to custom document-processing applications.

Best for: Fits when teams need accurate multilingual conversion, document comparison, and searchable archives from scanned files.

#2

Parseur

SMB

Automated data extraction from emails, PDFs, and other documents.

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

Mailbox-level routing with reusable parsing templates for email bodies and attachments

Parseur gives teams separate mailboxes for different document sources, then applies reusable templates to incoming files. The visual editor supports named fields, repeating line items, tables, and custom output formats. Connectors for Zapier, Make, and Power Automate extend parsed data into accounting, CRM, logistics, and spreadsheet workflows.

Template maintenance becomes necessary when suppliers change layouts or email formats. Parseur fits accounts payable teams that receive recurring invoice attachments from many vendors and need consistent structured records without building a custom parser.

Pros
  • +Mailbox routing separates document sources before parsing
  • +Visual templates support fields and repeating line items
  • +Native connectors cover Zapier, Make, and Power Automate
  • +API access and webhooks support downstream automation
Cons
  • –Template updates require maintenance after supplier layout changes
  • –Complex cross-document entity matching needs external logic
  • –Advanced governance controls are lighter than enterprise IDP suites
  • –Unusual layouts can require field-level correction
Use scenarios
  • accounts payable teams

    vendor invoice intake

    Structured invoice records

  • logistics operations teams

    shipping document processing

    Faster shipment updates

Show 1 more scenario
  • customer support teams

    email attachment extraction

    Fewer manual entries

    Mailbox rules capture submitted forms and attachments before sending fields into service workflows.

Best for: Fits when teams need mailbox-driven extraction for recurring documents and email attachments.

#3

Grooper

enterprise

Data integration and document processing platform.

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

Grooper’s exception handling routes low-confidence fields into a review workflow that updates extracted outputs for final export.

Grooper extracts data from documents using a human-validated workflow that turns messy uploads into structured fields. It pairs OCR with template-based form understanding so teams can map inputs to consistent outputs across repeat document types.

Grooper also supports exception handling so low-confidence fields can be reviewed instead of silently accepted. Integrations focus on moving extracted results out of the system through API calls and webhooks for downstream processing.

Pros
  • +Human-in-the-loop review reduces errors from low-confidence extractions.
  • +Template-based mapping keeps extracted outputs consistent across similar documents.
  • +Webhook callbacks support near real-time pushing of extraction results.
  • +Exception queues help route problematic documents to reviewers.
Cons
  • –Field mapping and review routing require careful operational configuration.
  • –Throughput tuning can become necessary for high-volume batches.
  • –Table extraction depth is weaker than for tools focused on complex layouts.
  • –Governance features like detailed audit trails are limited for strict compliance needs.
Use scenarios
  • data integration and automation teams

    Convert PDFs and scans into fields

    Structured data for pipelines

  • data operations and information teams

    Route uncertain fields to review

    Validated records from documents

Show 2 more scenarios
  • records and content management teams

    Search scanned documents by extracted fields

    Faster retrieval from archives

    Uses OCR text and index fields so teams can retrieve scanned items by document type and field values.

  • high-volume document operations teams

    Control automation with exception handling

    Controlled automation

    Applies validation rules to separate reliable outputs from items needing correction before downstream delivery.

Best for: Fits when teams need template-driven extraction with review queues and API-driven handoff to back-office systems.

#4

Docparser

SMB

Cloud-based document parsing and data extraction tool.

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

Template-driven extraction that supports human review of extracted fields with an annotation workflow for fast exception resolution.

Docparser focuses on document data extraction with template-driven field mapping for repeating document types. It converts PDFs and DOCX inputs into structured outputs using configurable extraction rules and layout-aware parsing.

Pros
  • +Template-based field mapping for repeatable extraction workflows
  • +Annotation and review loop to correct low-confidence results
  • +API plus webhook callbacks for integrating extraction into pipelines
  • +Consistent output formatting for downstream ingestion and validation
Cons
  • –Best results depend on maintaining and evolving extraction templates
  • –Complex multi-table layouts can require manual refinement
  • –Governance features like fine-grained RBAC are limited compared to enterprise IDP suites
  • –Large document volumes can increase operational overhead for review queues
Use scenarios
  • operations and verification teams

    Extract identity fields from scans

    Identity data ready for review

  • legal, insurance, and records teams

    Index clauses into structured fields

    Searchable structured content

Show 2 more scenarios
  • developers and automation teams

    Ingest extracted fields via API

    Less manual transcription

    Delivers extracted fields using API and file outputs so incoming documents feed operational workflows.

  • finance and accounts payable teams

    Capture invoice totals and line items

    Consistent invoice datasets

    Extracts invoice headers, totals, taxes, and line items from PDF and scans for consistent review processing.

Best for: Fits when teams need reliable field extraction from recurring PDFs and DOCX files, with API automation and review for exceptions.

#5

Nanonets

API-first

AI-based OCR and document automation platform.

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

Human-in-the-loop review with confidence-based exception routing before data is exported from extraction jobs.

Nanonets performs document data extraction by turning uploaded PDFs and images into structured fields with confidence scoring and review workflows. It supports form understanding for key-value capture and can extract tables when documents contain consistent grid layouts.

Pros
  • +Human-in-the-loop review workflow reduces errors from low-confidence fields
  • +Document ingestion and extraction API supports automated processing
  • +Table extraction works best with consistent layouts and clear boundaries
  • +Confidence scoring helps route exceptions for manual verification
Cons
  • –Model performance degrades on highly variable templates without retraining
  • –Exception handling and routing require careful configuration to match workflows
  • –Deep layout control is limited compared with tools built for complex page geometry
  • –Normalization rules can take iteration to match downstream schema requirements
Use scenarios
  • legal operations and data teams

    Extract clauses and table data

    Structured contract data

  • procurement and operations teams

    Capture purchase order fields and tables

    Ready for operational workflows

Show 2 more scenarios
  • claims and document processing teams

    Extract key-value fields from claims

    Structured claim records

    Captures key-value fields and validation data from forms and semi-structured claim documents with review support.

  • accounts payable teams

    Extract invoice header and line items

    Normalized invoice data

    Pulls vendor, header, totals, and line-item data from uploaded or email-received invoices for review and accounting use.

Best for: Fits when teams need trained form understanding plus API-driven ingestion for semi-structured documents.

#6

AntWorks CMR+

enterprise

Cognitive machine reading for document processing.

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

Exception handling that combines confidence scoring with structured human review queues tied to extraction runs.

AntWorks CMR+ targets document data extraction workflows with configuration centered on template-driven field capture and rule-based exception handling. It focuses on converting unstructured inputs into structured outputs with confidence scoring and human-in-the-loop review paths for low-confidence fields.

Pros
  • +Template-driven extraction rules reduce manual correction volume
  • +Confidence scoring routes low-confidence fields to review workflows
  • +Human-in-the-loop annotation supports repeatable exception handling
  • +Audit trail captures extraction run and review decision history
Cons
  • –Table extraction coverage depends on document layout consistency
  • –Field normalization needs tuning for edge-case formatting variants
  • –Scaling review throughput requires careful queue and role design
  • –Deeper API automation requires stronger engineering involvement
Use scenarios
  • Accounts payable operations teams

    Extract vendor invoices from mixed document sets

    Faster invoice processing with fewer errors

  • Document-intensive compliance teams

    Identify and validate required fields in audits

    Audit-ready records with traceable edits

Show 2 more scenarios
  • Logistics data operations teams

    Capture shipping details from bills of lading

    More reliable downstream shipment records

    Ingestion endpoints normalize unstructured inputs into structured outputs with confidence scoring.

  • Finance reconciliation teams

    Extract transaction references for matching

    Reduced manual matching workload

    Integration hooks push extracted fields into downstream systems for review and reconciliation decisioning.

Best for: Fits when document templates vary mildly and teams need governed exception review with automated routing.

#7

DocuClipper

vertical specialist

Bank statement and document data extraction software.

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

Bank statement conversion preserves transaction rows and maps them into CSV, Excel, or QuickBooks-ready exports.

DocuClipper handles bank statements, invoices, receipts, and other financial records through a browser upload workflow. Bank statement processing captures transaction dates, descriptions, amounts, and balances, while invoice processing can capture vendor details, invoice numbers, totals, and line items. The service supports common accounting exports, including CSV, Excel, and QuickBooks-compatible files.

Pros
  • +Converts bank statements into CSV, Excel, and QuickBooks-compatible files.
  • +Processes bank statements, invoices, and receipts in one browser workflow.
  • +Captures transaction details, invoice fields, and receipt totals.
  • +Lets users review and correct extracted records before export.
Cons
  • –Browser uploads remain the primary intake path for recurring document batches.
  • –Custom schemas and branching workflows are less developed than developer-focused IDP products.
  • –Poor scans and unusual layouts can require manual correction.
  • –Export coverage may not match every accounting system's native import format.
Use scenarios
  • Accounting departments

    Monthly bank statement processing

    Faster transaction entry

  • Bookkeeping firms

    Client receipt batch processing

    Reduced manual posting

Show 1 more scenario
  • Small businesses

    Supplier invoice entry

    Cleaner payable records

    Staff extract vendor, date, total, and line-item details from invoices without retyping each document.

Best for: Fits when accounting teams need bank statements and receipts converted into editable import files.

#8

Indico Data

enterprise

Intelligent document processing for enterprise workflows.

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

Confidence-driven human review routing that turns extraction uncertainty into an annotation workflow.

Indico Data targets document data extraction workflows that need tight review loops and production-grade handling of messy inputs. It combines OCR and layout-driven parsing with field-level confidence scoring so teams can route low-confidence cases into human-in-the-loop annotation.

Pros
  • +Human-in-the-loop review supports exception handling for low-confidence fields
  • +Layout-aware extraction improves results on forms with inconsistent spacing
  • +API-first integration fits custom pipelines and bulk extraction jobs
  • +Confidence scoring enables targeted validation instead of full manual review
Cons
  • –Better results require governance over annotation guidelines and retraining loops
  • –Table extraction needs careful model configuration for complex grid documents
  • –Deep field normalization often depends on post-processing logic outside the UI
  • –Complex document sets can create higher operational overhead than single-template flows
Use scenarios
  • Accounts payable operations teams

    Extract invoice fields from scanned PDFs

    Faster invoice processing with less rework

  • Claims processing teams

    Parse adjuster documents into structured claims

    More consistent claims intake

Show 2 more scenarios
  • Legal ops teams

    Extract clauses and parties from contracts

    Reduced manual contract review effort

    Produces normalized outputs and confidence scores to route uncertain extractions to annotators.

  • Enterprise document automation teams

    Integrate extraction via API into pipelines

    Lower manual data entry workload

    Connects OCR and extraction to downstream systems using an API-first workflow.

Best for: Fits when teams need production extraction with review routing, confidence-based QA, and API-led workflow integration.

#9

DocAcquire

enterprise

Intelligent document processing platform.

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

Field-level human review records that keep corrected output tied to prior extraction results.

DocAcquire focuses on document capture workflows that turn key fields into structured outputs with a review step for low-confidence cases.

Pros
  • +Human-in-the-loop review workflow for field-level corrections
  • +API-driven extraction and export for connecting capture to back-office systems
  • +Supports multiple document inputs including PDF and DOCX
  • +Exception handling workflow reduces silent extraction failures
Cons
  • –Advanced setups require careful configuration of extraction mappings
  • –Table extraction coverage is less consistent across complex layouts
  • –Limited evidence of deep template governance for large form portfolios
  • –Less streamlined iteration loops for field tuning than workflow-first tools
Use scenarios
  • Accounts payable operations teams

    Extract invoice fields from scanned documents

    Faster invoice processing

  • Legal operations teams

    Capture clauses and parties from DOCX

    Standardized case records

Show 2 more scenarios
  • Insurance claims teams

    Extract policy and claim identifiers from PDFs

    Reduced manual data entry

    Supports searchable PDFs and routes uncertain fields to a review workflow for accuracy.

  • IT integration teams

    Ingest documents via API for systems

    Automated data flow

    Provides API-based document ingestion and structured outputs that map into existing case management pipelines.

Best for: Fits when teams need API-integrated document extraction with reviewable exceptions.

Conclusion

After evaluating 9 document data extraction software, ABBYY FineReader 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
ABBYY FineReader

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 Document Data Extraction Software

How do API-driven workflows differ across Parseur, Indico Data, and Grooper?
Parseur sends extracted fields through API calls and webhook callbacks so downstream systems can ingest structured outputs immediately. Indico Data is API-first for production pipelines where confidence scoring decides which cases go into human-in-the-loop annotation. Grooper also uses API and webhooks, but it emphasizes review queues tied to low-confidence exceptions before export.
Which tool is better for routing extraction tasks from an email mailbox into structured fields?
Parseur and Grooper both focus on extracting from document inputs, but Parseur is the one built around mailbox-driven routing. Parseur can route email bodies and attachments into structured fields using mailbox-level templates. Grooper centers on template-driven extraction plus exception review inside its workflow, not on inbox routing.
When does human-in-the-loop review become necessary for document data extraction jobs?
Docparser triggers human-in-the-loop corrections when extraction confidence drops for specific mapped fields. Grooper routes low-confidence fields into a review workflow so questionable values do not silently enter exports. Nanonets also uses confidence-based exception routing so table or key-value outputs get corrected before normalized data is sent out.
What breaks if a system cannot preserve layout for table extraction, and how do FineReader and Nanonets handle that?
Table extraction degrades when reading order and grid boundaries are lost, because column alignment and row boundaries become ambiguous. ABBYY FineReader prioritizes layout-aware OCR and table recognition, which helps it export accurate table content into formats like XLSX and searchable PDFs. Nanonets supports table extraction when documents have consistent grid layouts, so irregular grids increase the chance of misaligned rows or missing cells.
How do admin controls and audit trails differ between AntWorks CMR+ and DocAcquire?
AntWorks CMR+ uses RBAC and audit trail records tied to extraction runs, edits, and review decisions. DocAcquire emphasizes auditability through field-level human review records that tie corrected output to the prior extraction results. Fine-grained RBAC is not described as a core governance mechanism in DocAcquire’s extraction flow.
Which security setup options are most relevant for teams using SSO and enterprise identity systems?
ABBYY FineReader is the most enterprise-oriented option in this list because server-side capture and embedding are handled through ABBYY’s separate Server or Engine products. AntWorks CMR+ explicitly ties governance to RBAC and audit trail records around extraction runs and review decisions. The remaining tools focus on API, webhooks, and review workflows, but they do not describe SSO provisioning in the same terms.
How does extensibility work when templates and parsing rules must evolve over time in Extensible OCR and Docparser?
Extensible OCR is built to refine OCR output and parsing logic through configuration per document type without replacing the full pipeline. Docparser relies on template-driven field mapping with configurable extraction rules, and it supports human review to handle exceptions when confidence drops. Extensible OCR is framed around configuration-driven behavior changes, while Docparser is framed around evolving extraction templates plus review for outliers.
What are common integration friction points when switching ingestion formats, and which tool outputs normalized data for downstream systems?
Ingestion friction appears when PDFs, images, and DOCX inputs require different parsing paths, since field extraction often depends on layout analysis. DocAcquire supports both scanned and digital documents and maps extracted fields to downstream outputs with API-driven ingestion and export. Indico Data focuses on normalized outputs exported after extraction and review routing, which reduces downstream schema drift when inputs vary.
Which tool is best suited for accountants who need bank statement and receipt extraction into accounting-ready files?
DocuClipper targets that workflow directly by converting bank statements and receipts into editable accounting files and CSV or Excel exports. Parseur and Grooper can extract structured fields from invoices and operational documents, but their emphasis is broader mailbox or template-driven extraction with review. DocuClipper’s standout capability is preserving transaction rows while mapping them into statement-ready exports.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Document Data Extraction Software

We separate document data extraction options by how well they turn real documents into usable fields, not just by which OCR they use. Look hardest at data model, automation and API surface, and how each system handles layout variation and confidence.

Field accuracy on messy layouts

Why it matters

Field accuracy on messy layouts determines whether extraction survives the real world: rotated text, inconsistent spacing, and mixed templates. This is where many tools look good on examples but break in day-to-day batches.

How to check

In the demo, test with at least two document samples per layout type: one clean and one with skewed headers, varying table spacing, or slight template drift. Ask the reviewer to show extracted values alongside the source page and note any systematically wrong fields.

Data model and mapping controls

Why it matters

Data model and mapping controls affect whether outputs fit your downstream workflow without guesswork. If you must rebuild mappings every time a template changes, automation slows and errors spread.

How to check

Ask for a live example where you map fields into the output structure (keys, types, and nested objects). Then modify one template element (e.g., move a label) and check whether the mapping stays stable or requires rework.

Automation and API surface

Why it matters

Automation and API surface determines whether extraction fits into a larger ingestion workflow or stays stuck in manual review. Deeper automation also improves throughput by reducing human steps between upload and structured output.

How to check

Confirm what triggers extraction (batch, single document, or event-based) and what the output looks like (field-by-field JSON or equivalent). Test an API call or webhook-style simulation and verify you receive structured results plus any per-field metadata you need.

Confidence and review workflow fit

Why it matters

Confidence and review workflow fit decides how much exception handling you’ll do when layouts don’t match. If confidence is vague or unusable, teams either miss errors or review too much.

How to check

During the demo, request a case with known mismatches (blank labels, partial scans, or altered tables). Check whether the system returns usable confidence per field and whether you can route low-confidence fields into a predictable review step.

Table and multiline extraction quality

Why it matters

Table and multiline extraction quality impacts invoices, statements, and any document where values repeat across rows. Weak table handling forces manual cleanup or loses row-level meaning.

How to check

Use a sample with at least one multi-row table and at least one multiline field (e.g., addresses or descriptions). Compare extracted row counts, column alignment, and whether multiline fields preserve line breaks or delimiters you can work with.

Admin governance over templates

Why it matters

Admin governance over templates matters when multiple teams manage mappings and configurations. Without clear controls, you risk inconsistent outputs and hard-to-audit changes.

How to check

Ask how administrators manage template versions, role-based permissions, and configuration changes. Then request a scenario where two users edit mappings and verify the system logs changes and prevents conflicting edits.

Red flags

  • Outputs look accurate only on the cleanest example pages
  • Field mappings break when small layout drift appears
  • Confidence signals don’t help you route exceptions reliably

Fit by situation

  • If your documents vary by form version within the same business process, prioritize field accuracy on messy layouts.
  • If your outputs must land in a specific downstream structure every time, prioritize data model and mapping controls.
  • If you need hands-off processing between ingestion and routing, 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.