GITNUXSOFTWARE ADVICE
Cybersecurity Information SecurityTop 10 Best Document Forgery Detection Software of 2026
Top 10 document forgery detection software tools ranked for fraud teams, with comparison notes citing Microsoft Defender for Cloud Apps, Google, and AWS.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Sumsub is the best pick if you need automated, review-ready document forgery decisioning with governed escalation, whereas iDenfy fits onboarding teams looking for consistent, threshold-based API scoring when you want a simpler entry point.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Sumsub
Fraud score output with configurable thresholds for deterministic accept, reject, or escalate logic.
iDenfy
Editor pickFraud score plus confidence threshold outputs that map directly to automated approve, review, or reject logic.
Veriff
Editor pickEmbeddable verification sessions with structured decision results that map cleanly into risk policies.
Related reading
- Cybersecurity Information SecurityTop 10 Best Document Authentication Software of 2026
- Cybersecurity Information SecurityTop 10 Best Deep Fake Detection Software of 2026
- Cybersecurity Information SecurityTop 10 Best Audit Protection Services of 2026
- Business Process OutsourcingTop 10 Best Automated Document Services of 2026
Comparison Table
Document forgery detection tools apply forensic document analysis to flag tampering, counterfeits, and invalid identity records, usually through API integration and configurable rules. This ranked list targets teams that need measurable verification quality versus integration effort, using evaluator inputs across Microsoft Defender for Cloud Apps, Google, and AWS to guide comparisons across authentication, automation, and auditability without marketing claims.
Sumsub
enterpriseVerification platform that analyzes identity documents for forgery, tampering, and other fraud indicators.
Fraud score output with configurable thresholds for deterministic accept, reject, or escalate logic.
Sumsub’s document analysis workflow is designed for high-throughput authentication checks that feed into a fraud score and decisioning logic used by identity teams. The API-driven approach supports embedding verification into onboarding flows and back-office review queues without relying on manual exports. Results are returned in machine-readable form, which enables building deterministic accept, reject, and escalate paths per document type.
A key tradeoff is that the strongest accuracy and automation depend on carefully defined verification flows and threshold policy per document category. Sumsub fits when an application needs batch-friendly verification of multiple document types and must consistently route outcomes into automated decisions or human review for exceptions.
- +API-first workflow supports programmatic verification orchestration
- +Multi-document routing supports different outcomes per document type
- +Structured decision results reduce manual interpretation work
- +Configurable thresholds support consistent fraud score policy
- –High automation depends on careful flow and threshold configuration
- –Less suited to teams needing fully on-premise document processing
- –Outcome tuning can require multiple iteration cycles per region
- –Complex edge cases still require human review handling
Risk and fraud engineering teams
Automate decisions during onboarding
Higher automation with consistent thresholds
Identity verification product teams
Handle multiple document categories
More predictable onboarding behavior
Show 2 more scenarios
Compliance operations teams
Manage exceptions and review
Reduced review backlog
Use API responses to send low-confidence cases to human review queues.
Platform integration teams
Embed verification into apps
Fewer manual handoffs
Integrate document upload and decision handling inside existing onboarding UI and backend services.
Best for: Fits when onboarding needs automated document decisioning with API integration and controlled escalation to review.
More related reading
iDenfy
SMBRemote identity verification software that detects fake, altered, and invalid identity documents.
Fraud score plus confidence threshold outputs that map directly to automated approve, review, or reject logic.
iDenfy is a verification engine built for high-throughput document checks where the input is usually an image captured by a user or scanner. It generates structured results for decisioning, including a fraud score and confidence threshold outputs that can feed manual review or automated approval paths. A practical fit signal is that the workflow is designed around API-style consumption rather than analyst-only, UI-first investigation.
A notable tradeoff is that advanced forensics depth depends on the verification configuration used for each document type and the quality of the submitted images. It fits best when onboarding needs fast, consistent screening at scale, while deeper case review is handled by downstream investigators using the provided confidence and failure reasons.
- +Fraud score and confidence outputs support automated decision thresholds
- +API-oriented integration fits onboarding systems that need consistent screening
- +Structured results reduce manual interpretation effort during review
- +Document-type checks help standardize outcomes across ID categories
- –Verification quality is tightly coupled to image capture quality
- –Configuration is needed to align checks with the document types used
- –Deep investigation requires more tooling beyond the returned results
KYC operations teams
Triage risky uploads during onboarding
Fewer wasted analyst cycles
Risk and fraud engineering
Gate account creation with rules
Lower account abuse
Show 1 more scenario
Product onboarding teams
Embed document checks in mobile flow
Faster onboarding completion
API-style consumption enables verification to run as part of the capture to decision step.
Best for: Fits when onboarding teams need API-driven ID authenticity scoring with consistent, threshold-based decisions.
Veriff
API-firstIdentity verification platform that checks document validity and detects manipulation in submitted identity records.
Embeddable verification sessions with structured decision results that map cleanly into risk policies.
Veriff’s core workflow centers on collecting document images from a user session and returning a structured verification result that downstream systems can consume. Document authentication is paired with fraud heuristics and configurable decisioning so teams can map outcomes into risk policies and case handling. Integration is built for embedding into existing onboarding and verification journeys, with API calls that manage session creation and result retrieval.
A key tradeoff is that Veriff is most effective when verification is executed through its session flow, because the automation and scoring signals are tightly coupled to that input structure. The product fits organizations that need consistent, governed forgery detection outcomes for many applicants, while internal forensic workflows or fully custom pixel-level pipelines may require a different approach.
- +API-first session flow for embedding verification into onboarding
- +Fraud signal scoring supports policy-driven outcomes
- +Configurable decision thresholds reduce false rejects
- +Structured results simplify downstream risk case automation
- –Best results depend on using Veriff’s session input flow
- –Deep custom pixel-level forensics is limited compared to research tools
- –Complex governance requires careful mapping to internal risk states
- –Throughput depends on orchestration and retry strategy
Identity verification engineering teams
Embed document authentication into onboarding
Consistent decisioning across channels
Fraud operations teams
Automate case routing from signals
Reduced manual triage volume
Show 1 more scenario
Risk and compliance leaders
Standardize verification governance
Lower variance in outcomes
Risk teams apply thresholds and outcome handling rules to keep document checks consistent across products.
Best for: Fits when identity teams need governed document forgery detection integrated into onboarding decisions.
Regula Document Reader SDK
API-firstDocument authentication SDK with forensic checks for altered, counterfeit, and tampered identity documents.
Regula Document Reader SDK can return granular verification outputs and fraud scoring results for downstream governance in custom workflows.
Regula Document Reader SDK focuses on document forensics as an embedded component for custom ID document authentication workflows. It provides security feature extraction, image and text processing, and configurable verification logic that supports automated scoring and decision thresholds.
It is designed for integration into existing systems that need repeatable processing at controlled throughput. Deployment options support on-premise and controlled environments where access to input images and verification outputs must be managed end to end.
- +Embedded SDK approach for ID authentication workflows inside existing apps
- +Configurable verification logic that supports automated decision thresholds
- +Supports pixel-level forensics style analysis with security feature extraction
- +Batch processing oriented design for controlled throughput
- –Integration work is required to map SDK outputs into internal decision models
- –Complex configuration can increase time-to-production for multi-document flows
- –Model tuning and threshold selection can be sensitive across document types
- –Requires disciplined test coverage for edge-case image quality variations
Best for: Fits when enterprises need on-premise document authentication integration with automated scoring and controlled processing.
AU10TIX
enterpriseIdentity verification platform with document authentication, tamper analysis, and fraud risk signals.
Fraud score generation driven by multi-signal document analysis paired with liveness and biometric match in one decision stream.
AU10TIX performs document forgery detection by extracting security signals from ID documents and producing a fraud score with configurable confidence thresholds. It also supports liveness checks and biometric face match to reduce the risk of using substituted or tampered documents.
AU10TIX is designed for automation, including batch processing and API-based integration into authentication workflows. It supports governance patterns through role-based administration and audit-style activity visibility for verification operations.
- +Fraud score outputs are designed for downstream decisioning logic
- +Liveness checks and face matching cover common identity takeover paths
- +Batch processing supports higher throughput for verification queues
- +API-first integration fits authentication services and KYC pipelines
- –Real performance depends on correct capture guidance and document alignment
- –Complex workflows require careful configuration of confidence thresholds
- –Advanced controls lean on administrative setup rather than defaults
- –Some edge-case document formats may need workflow tailoring
Best for: Fits when identity programs need automated document authentication with fraud scoring and biometric checks.
Shufti Pro
API-firstIdentity verification software with AI-based checks for fake and forged identity documents.
Fraud scoring outputs tied to each verification attempt, designed for workflow routing between automation and manual review.
Shufti Pro fits teams that need automated ID document authentication across high-volume onboarding and ongoing account checks. It combines document image analysis with fraud scoring workflows to return a decision outcome and supporting signals for review.
The product supports liveness checks and identity verification use cases that go beyond plain OCR extraction. Admin teams can control verification flows, manage access for operators, and review decision evidence tied to each attempt.
- +Automates ID authentication workflows with decision outputs and evidence per attempt
- +Includes liveness checks to reduce risk from static photo submissions
- +Provides fraud scoring signals that support manual review escalation
- +Configurable verification journeys for different document and risk paths
- –Requires careful configuration of decision thresholds to reduce false positives
- –Reporting depth for pixel-level forensics is limited compared with specialist tools
- –Batch throughput tuning can be restrictive for very large verification queues
- –Complex governance across many teams takes time to standardize
Best for: Fits when onboarding and KYC teams need automated ID checks plus operator review trails.
IDScan.net
vertical specialistID verification and age validation platform with fake ID and document fraud detection capabilities.
Fraud score outputs combine multiple document signals into a single decision aid for investigators.
IDScan.net focuses on identity document authenticity checks with automated fraud scoring and document feature extraction. The workflow typically includes image validation, barcode and MRZ parsing, and security feature analysis for multiple document types.
It supports API integration for embedding verification into onboarding and case management systems. Admin control centers on configuration, report retention options, and audit trails tied to verification events.
- +API integration supports embedding checks inside onboarding flows
- +Barcode and MRZ parsing reduce manual data entry and reconciliation
- +Verification outputs include fraud score and confidence threshold signals
- +Case reports support review workflows with extractable evidence
- –Higher accuracy depends on document image quality and capture guidance
- –Extensibility outside built-in checks is limited for custom forensic needs
- –Deployments still require operational discipline for configuration and governance
- –Batch throughput and latency can constrain peak-volume verification windows
Best for: Fits when onboarding teams need API-driven document authentication with reviewable fraud outputs.
Incode
enterpriseIdentity verification platform with document validation, anti-spoofing controls, and fraud detection workflows.
A workflow-oriented verification output model that feeds fraud score and confidence thresholds directly into risk decisions through the Incode API.
Incode focuses on document forgery detection for identity and onboarding workflows that need automated ID document authentication. The core offering pairs document image analysis with configurable verification logic that can produce fraud scores and confidence thresholds for downstream decisioning.
Incode also supports integration via APIs so document checks can run inside existing registration and risk workflows. Governance features like audit trails and role-based access controls help teams manage who can configure verification and view outcomes.
- +API-first verification workflow for inserting forgery checks into existing onboarding
- +Configurable verification logic to translate document results into decisioning
- +Audit logging supports forensic review of verification outcomes
- +Role-based access controls reduce risk from misconfiguration
- –Requires integration effort to map results into risk rules and case handling
- –Fine-tuning confidence thresholds can take iterative test cycles
- –Document coverage depends on supported document types and formats
- –Operational oversight needed to keep verification rules aligned with change control
Best for: Fits when teams need API-driven document forgery checks with configurable decision thresholds.
Fraud.com Document Verification
enterpriseFraud prevention platform that offers document verification with checks for manipulated or counterfeit identity documents.
Fraud score outputs tied to document authenticity checks that can be consumed directly by decision logic.
Fraud.com Document Verification ingests ID and proof-of-identity documents to generate document authenticity signals and fraud scores for downstream decisioning. It pairs document image checks with security-feature extraction workflows and produces confidence-oriented outputs intended for API-driven authentication flows.
Automated verification supports batch and integration patterns where document checks run alongside identity and risk rules. Governance is built around configurable verification rules and audit-friendly result outputs for operations teams.
- +API-first document authenticity signals for automated fraud decisioning
- +Security-feature extraction workflow designed for ID security elements
- +Batch-oriented document verification suited for back-office throughput
- +Configurable verification rules for tuning confidence thresholds
- –Integration requires careful mapping of inputs, formats, and thresholds
- –Limited visibility into low-level forensics compared with specialist vendors
- –Higher false-reject risk when images lack capture quality
- –Fewer controls for multi-role governance than broader risk platforms
Best for: Fits when fraud teams need API-driven ID authenticity signals with configurable thresholds for mixed channels.
Persona
enterpriseIdentity platform with government ID verification and automated checks for suspicious or manipulated documents.
Decision-oriented document verification API that returns fraud-relevant outputs suitable for automated pass, fail, and review routing.
Persona is a document forgery detection tool aimed at identity verification workflows that need automated document handling and fraud scoring. It focuses on ingestion of identity documents, security feature extraction, and decisioning for account onboarding and verification steps.
Persona also provides an API and workflow-oriented controls that fit batch and real-time authentication needs. Governance features for teams and environments are supported through configurable access and traceability suitable for audit workflows.
- +API-first document verification flow for onboarding and authentication decisions
- +Configurable verification steps that reduce custom workflow glue code
- +Fraud-oriented confidence outputs that support threshold-based policies
- +Team controls for managing access to verification configurations
- –Limited visibility into per-image analysis internals for deep forensics teams
- –Document coverage can require per-country and per-format tuning
- –Complex workflows still need orchestration for review queues and escalations
- –Operational governance depends on correct environment and access setup
Best for: Fits when identity teams need API-driven document authentication for onboarding with fraud scoring and configurable thresholds.
Conclusion
After evaluating 10 cybersecurity information security, Sumsub 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.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right document forgery detection software
Document forgery detection software is used in onboarding and identity verification workflows to generate fraud scores, confidence thresholds, and decision-ready evidence from submitted document images. This buyer's guide covers Sumsub, iDenfy, Veriff, Regula Document Reader SDK, AU10TIX, Shufti Pro, IDScan.net, Incode, Fraud.com Document Verification, and Persona.
The differentiators across these tools show up in how API integration is built, how deterministic decision thresholds are configured, and how routing between automated approval, manual review, and rejection is represented in outputs. Sumsub and iDenfy lead on threshold-driven fraud score automation, while Regula Document Reader SDK targets on-premise integration and embedded SDK workflows.
Document forgery detection software for API-driven authenticity scoring and automated decisioning
Document forgery detection software ingests document images and returns structured authenticity signals such as fraud scores and confidence threshold outputs that can feed pass, review, or reject logic. In this category, Sumsub is built around an API-first workflow with fraud score outputs that support configurable accept, reject, or escalate logic, which makes decision automation deterministic when thresholds are tuned.
iDenfy also provides fraud score plus confidence threshold outputs mapped directly into automated approve, review, or reject routing, with outcomes tied to the consistency of the captured document images. For teams that need self-hosted integration, Regula Document Reader SDK delivers an embedded SDK approach designed for enterprises that want on-premise document authentication integration and granular verification outputs that can be scored and governed inside custom workflows.
Evaluation criteria for decision-ready forgery detection signals
Document forgery detection software matters most when the output can drive a deterministic workflow that maps fraud scores and confidence thresholds into pass, review, or reject decisions. The tools in this list differ primarily in how directly their signals attach to automation and how much evidence structure they return with each attempt.
Teams also need enough operational control to prevent noisy inputs from turning into unnecessary manual workload. The biggest gaps show up in how API integrations represent routing logic, how much per-image analysis detail is exposed for investigation, and how well the workflow supports multi-document flows.
Fraud score and confidence threshold outputs for automated routing
Sumsub, iDenfy, and Persona return fraud score and confidence-threshold outputs designed for automated accept, review, or reject routing.
API and embedding flow design for onboarding integrations
Veriff provides embeddable verification sessions with structured decision results, while IDScan.net, Incode, and Persona emphasize API-first document authentication signals for onboarding systems.
SDK or self-hosted integration for enterprise deployment control
Regula Document Reader SDK is built for enterprises that want embedded SDK integration with granular verification outputs inside custom apps.
Multi-signal decision streams including liveness and biometric match
AU10TIX and Shufti Pro combine liveness checks and biometric face matching with fraud scoring in one decision stream for identity programs that want reduced static-photo risk.
Decision evidence and investigator-friendly outputs per attempt
Shufti Pro attaches evidence per verification attempt and routes between automation and manual review, while IDScan.net provides fraud score outputs intended as a single decision aid for investigators.
Threshold governance and orchestration depth
Sumsub supports configurable threshold-driven accept, reject, or escalate logic, while iDenfy ties confidence thresholds to automated decisions that remain consistent when document type rules are aligned.
How to choose document forgery detection software for deterministic decisioning
The fastest way to narrow the list is to start from the decision workflow the onboarding system must run. The question is not whether a vendor returns a fraud score, but whether the software exposes enough decision primitives to enforce policy with predictable routing.
Second, the choice depends on deployment shape. Tools aimed at embedded SDK integration and on-premise needs behave differently from API-first session flows that are optimized for rapid onboarding integration.
Map your policy to explicit accept, reject, or escalate logic
If the onboarding system needs deterministic routing, Sumsub fits when threshold configuration must control accept, reject, or escalate to review. If the workflow requires fraud score plus confidence threshold outputs aligned to approve, review, or reject decisions, iDenfy and Persona provide decision-ready signals with consistent routing primitives.
Choose an integration model that matches the product architecture
Pick Veriff when the integration must embed structured verification sessions and return decision results that can plug into onboarding risk policies. Pick Regula Document Reader SDK when the integration must run inside existing apps with embedded SDK outputs and custom governance.
Decide whether liveness and biometric match must be part of the same decision stream
Pick AU10TIX when the program requires a multi-signal stream that couples fraud scoring with liveness and face matching for identity takeover prevention. Pick Shufti Pro when the system needs liveness to reduce static-photo submissions and evidence per attempt to support operator review trails.
Validate capture dependency and throughput assumptions against your input conditions
If document image capture quality varies, iDenfy warns that verification quality is tightly coupled to image capture quality, which makes threshold tuning sensitive. If throughput depends on consistent extraction like MRZ and barcode parsing, IDScan.net focuses on these parsing steps but still expects quality to support accuracy.
Separate decisioning needs from deep pixel-level forensics needs
Choose tools like Sumsub and iDenfy when the priority is threshold-driven automation that produces structured decision signals. Choose Veriff only when pixel-level forensics depth is not the main investigative requirement, since its deep pixel-level forensics is limited compared with research tools.
Who should buy this category of document forgery detection software
Buyers need this software when onboarding and identity verification workflows must turn document uploads into structured authenticity signals with fraud score and confidence threshold outputs. The category becomes a governance system when outputs route requests into automated decisions or operator review based on configured thresholds.
The right fit depends on whether the team is building an API-first onboarding decision engine or embedding verification inside a self-hosted application. It also depends on whether liveness and biometric match must be included as part of the same decision stream rather than handled as separate controls.
KYC and onboarding teams building policy-driven decisioning
Sumsub, iDenfy, and Persona provide fraud scoring and confidence threshold outputs designed for automated accept, review, or reject routing, which reduces workflow glue code in onboarding systems.
Identity teams that need embeddable verification sessions with structured results
Veriff fits onboarding stacks that require governed document verification embedded as sessions with structured decision results that map cleanly into risk policies.
Enterprises that must run verification inside their own apps and deployment boundaries
Regula Document Reader SDK is designed for embedded SDK integration that returns granular verification outputs and fraud scoring inside custom enterprise workflows.
Risk teams that require liveness and face match in the same decision stream
AU10TIX and Shufti Pro combine liveness checks and face matching with fraud scoring so identity programs can reduce static-photo fraud paths during decisioning.
Onboarding investigators who need reviewable fraud outputs per attempt
Shufti Pro and IDScan.net attach decision evidence and provide fraud score outputs intended for routing between automation and manual review or investigator decision support.
Common pitfalls in document forgery detection deployments
Many failures come from treating fraud scoring as a drop-in replacement for workflow governance. The outputs must be mapped into internal risk rules, and thresholds must align with document types and capture conditions.
Another recurring issue is choosing a tool based only on scoring availability instead of integration shape. Embedded SDK integration, embeddable session flows, and API-first verification calls all change how evidence and routing behave inside the onboarding system.
Configuring automation thresholds without aligning them to document types and expected capture quality
Sumsub and iDenfy both depend on careful threshold configuration, and iDenfy specifically ties verification quality to image capture quality which makes threshold outcomes sensitive to poor capture guidance.
Assuming deep pixel-level forensics will be available when the primary requirement is decision automation
Veriff focuses on embedding verification sessions with structured decision results, and deep pixel-level forensics is limited compared with research tools, so forensic teams may need additional investigation tooling.
Treating SDK output as ready-to-use risk rules without building internal mapping
Regula Document Reader SDK returns granular verification outputs, but integration work is required to map SDK outputs into internal decision models which extends time-to-production if mapping is not planned.
Overlooking capture guidance and document alignment in multi-step workflows
AU10TIX notes that real performance depends on correct capture guidance and document alignment, and complex workflows require careful configuration of confidence thresholds to avoid misrouting.
Expecting extensibility for custom forensic needs when built-in checks define the workflow
IDScan.net provides API-driven document authentication signals and includes barcode and MRZ parsing, but extensibility outside built-in checks is limited for custom forensic needs.
How We Selected and Ranked These Tools
We evaluated Sumsub, iDenfy, Veriff, Regula Document Reader SDK, AU10TIX, Shufti Pro, IDScan.net, Incode, Fraud.com Document Verification, and Persona on feature coverage at 40%, ease of integration at 30%, and value at 30%. We scored decision automation fit based on how fraud score and confidence threshold outputs map into accept, review, or reject routing logic.
We scored integration and automation depth by how directly API-first workflows support programmatic orchestration and controlled escalation to review. Sumsub ranked highest because configurable fraud score thresholds support deterministic accept, reject, or escalate logic with API-first workflow orchestration and multi-document routing outcomes.
Frequently Asked Questions About document forgery detection software
How do Sumsub and Veriff structure fraud-score outputs for automated onboarding decisions?
Which tools provide an API that fits real-time authentication workflows rather than batch-only processing?
When teams need an on-premise document authentication component, how does Regula Document Reader SDK compare with cloud-first offerings like Incode?
What breaks if an implementation treats MRZ parsing and barcode decoding as optional when using IDScan.net?
How do AU10TIX and Shufti Pro handle multi-signal decisioning when documents show possible tampering?
Which tool outputs include both confidence thresholds and fraud scores for routing to approve, review, or reject?
How do admin controls and audit visibility differ between Shufti Pro and IDScan.net?
What integration and data-handling gaps appear when engineering teams require a custom verification data model and strict throughput controls?
How do Sumsub and Fraud.com support extensibility for different document types and fraud taxonomy inputs?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Cybersecurity Information Security alternatives
See side-by-side comparisons of cybersecurity information security tools and pick the right one for your stack.
Compare cybersecurity information security tools→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 ListingWHAT 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.