This documentation introduces core concepts and how Verifex works end to end for brands. For the full consumer-facing explanation of every verification result, see the Help Center — verification results.

1. Platform overview

Verifex Authentication Solutions Ltd provides a QR- and code-based product authentication and anti-counterfeiting platform.

Each protected product unit maps to a unique verification identity (secret code and/or QR scan token) in a secure database.
QR codes open a brand verification URL on www.verifexglobal.com.
Consumers receive a clear outcome: genuine first scan, duplicate, clone/suspicious, fake, blocked, wrong brand, not yet scannable, or product not active.
Brands use dashboards, Scan Explorer, alerts, and counterfeit reports for investigation and enforcement support.

2. Key concepts

Brand: A company profile with branded verification pages, products, codes, and portal users.
Product: A catalog item codes are linked to. Must be active for public genuine verification.
Verification code / unit: One database row for one physical item (secret code and/or QR token).
QR scan token: Opaque token in URLs such as /{brand-slug}/verify/{token}.
Batch: A named group of codes generated together for printing and activation.
Scan event: A verification attempt with outcome, time, and approximate location (policy may store counters for some repeats).
Brand portal: Dashboard, analytics, Scan Explorer, reports, team, and settings for brand users.

3. How product verification works

3.1 Code and QR generation

Administrators generate a batch of unique codes/tokens for a product.
Each unit is stored with brand, product, and batch metadata.
QR codes point to a verification URL, for example: https://www.verifexglobal.com/{brand-slug}/verify/{32-character-token}
Secure exports are prepared for print vendors; codes remain registered in Verifex.
Batches/codes are activated when products ship so public verification succeeds.

3.2 Consumer verification flow

Consumer scans the QR or opens the brand page and enters the authentication code.
The branded verification page may request location permission.
Verifex checks: exists? correct brand? product active? code status scannable?
The page returns one of the live result statuses (see Help Center).
Where applicable, consumers can submit a counterfeit report with photos and purchase details.

3.3 Result types (summary)

Public marketing previously described only three outcomes. The live system shows all of the following (full detail: Help Center §2):

Verification successful (genuine_first)
Duplicate verification (already scanned; no clone alert)
Possible counterfeit / cloned QR (duplicate + clone triggers; often suspicious_repeat)
Fake product detected (fake_not_found)
Counterfeit alert — do not buy (blocked after confirmed duplication)
Code found — different brand
Code exists but cannot be verified yet (inactive / expired / restricted)
Product not available for verification (catalog product not active)
No verification code received

4. Clone detection, alerts, and enforcement

Clone / suspicious detection is based on inconsistent verification patterns for the same unit, such as:

Scans from multiple countries
Scans from multiple states or regions
Scans from multiple network locations
Scans from multiple devices or visitor sessions

Same-session page refreshes are not treated as a new person. When clone rules fire, consumers see a stronger warning and a report button; brands can receive email/SMS alerts and investigate in Scan Explorer.

Time-stamped histories, locations, and consumer reports support legal and enforcement teams. Verifex provides evidence — it does not replace law enforcement.

5. Fake results and consumer reporting

Unrecognized codes show Fake Product Detected without a genuine product image.
Blocked counterfeit-duplication codes show an explicit do-not-buy alert.
Consumers can submit reports (email, phone, store, channel, price, photos, remarks) protected by Turnstile.
Reports appear in the brand’s counterfeit reports area for triage.

6. Analytics and operations

Dashboard metrics for genuine first scans, suspicious repeats, and fake attempts
Geographic views and product/batch performance
Scan Explorer with filters and exports
Code inventory and inactive-code workflows (admin tools)
Team roles, impersonation (admin), and security settings

7. Integration model

Brands primarily operate through the Verifex web portal and admin-managed onboarding. Day-to-day integration for most customers is:

Print-ready / vendor exports of QR tokens and codes
Branded consumer verification URLs on packaging
Portal analytics, Scan Explorer exports, and alert emails/SMS
Secure admin access for code generation, activation, and blocking

Custom system-to-system API projects are scoped separately with Verifex — contact sales if you need a dedicated integration discussion.

8. Best practices

Keep products active and activate batches only when goods ship
Use correct brand-slug QR URLs on artwork
Educate consumers to scan at purchase and report clone/fake warnings
Monitor clone and fake alerts promptly
Block confirmed duplicated codes after investigation
Coordinate with legal/enforcement using exports and report evidence

Verifex Documentation