What Tchekz Does
Tchekz is an automated purchase-verification platform.
It connects to a user’s email account, identifies genuine order receipts, extracts structured order data, and verifies whether the items they paid for were delivered correctly.
In short: Tchekz checks online orders on the user’s behalf and finds mistakes, missing items, or discrepancies that are otherwise easy to miss.
________________________________________
The Core Problem Tchekz Solves
Online shopping generates a high volume of errors:
• Missing items
• Incorrect quantities
• Substituted products
• Partial deliveries
• Overcharges
Retailers and delivery platforms rarely flag these proactively. Users are expected to:
• Keep receipts
• Manually compare deliveries
• Notice discrepancies
• Navigate refund processes
Most people don’t — so errors go unclaimed.
Tchekz automates this entire process.
________________________________________
How Tchekz Works (End-to-End)
1. Secure Email Connection
• The user connects their email account (e.g. Gmail).
• Tchekz uses read-only access.
• No emails are modified, sent, or deleted.
________________________________________
2. Receipt-Only Detection (Critical Design Choice)
Tchekz does not process all emails.
It applies a strict receipt-only gate that:
• Allows only genuine order receipts
• Blocks marketing emails, shipping updates, calendars, promotions, etc.
• Prevents unnecessary AI usage and cost
• Avoids false positives
Only emails that can plausibly be verified as purchases are allowed through.
________________________________________
3. Order Extraction & Structuring
For valid receipts, Tchekz:
• Extracts retailer identity
• Order number
• Items, quantities, and prices
• Delivery metadata
• Total amounts
This data is normalized into a consistent internal format, regardless of retailer (Amazon, Uber Eats, Asda, etc.).
________________________________________
4. Verification & Analysis
Tchekz compares:
• What the user paid for
vs
• What was delivered or fulfilled
It identifies:
• Missing items
• Incorrect quantities
• Partial fulfillment
• Pricing inconsistencies
Each order is marked with a verification status (processed, pending, discrepancy found, etc.).
________________________________________
5. Persistence, Deduplication & Cost Control
Tchekz is designed to:
• Never re-process the same receipt twice
• Detect duplicates using Gmail message IDs and order numbers
• Avoid re-sending previously processed content to AI systems
• Only charge for new, verifiable work
This prevents:
• Double charging
• Token waste
• User distrust around “overcharging”
________________________________________
6. User Visibility & Outcomes
In the app, users see:
• A list of verified orders
• Items checked
• Discrepancies detected
• Potential refunds identified
The goal is confidence and transparency, not just data extraction.
________________________________________
What Tchekz Is Not
This is important for positioning:
• ❌ Not an email scanner
• ❌ Not a generic AI inbox reader
• ❌ Not a receipt archive
• ❌ Not a marketing analytics tool
Tchekz is purpose-built for verification — nothing else is allowed through the system.
________________________________________
Why the Architecture Matters
Tchekz deliberately enforces:
• Strict gating (receipt-only)
• Idempotency (no double processing)
• Minimal payloads (token & cost control)
• Deterministic persistence rules
These aren’t accidental — they’re what make the platform:
• Trustworthy
• Scalable
• Cost-efficient
• Defensible