Product Verification & Authentication
Build a counterfeit and expiration detection system
Kliv is an AI app builder. Describe your registry — batches, codes, shipments, verification events, duplicate-scan flags, and expiry holds — and it builds it.
Just enter your idea into the text box and AI will build it for you
What is Kliv?
Kliv isn’t a track-and-trace suite — it’s an AI that builds software for you.
You describe the app you need in plain words, and Kliv builds it: the data, the workflow, the screens, and the rules. What you get is a real web app that’s yours, with public verification pages on your own domain and private review screens for your team. You can change it later by asking. It isn’t a template.
On this page, that app is a registry for product codes, scans, shipments, flags, and expiry holds. Kliv builds all kinds of web apps; this is one example.
Why build your own counterfeit and expiration detection system?
A distributor may not need a multinational compliance platform. It may need to know which packs are real, which shelves they reached, which codes have been checked, and which lots expire soon.
Kliv builds that as a registry: your batches, your codes, your shipments, and your review rules. A code that does not exist, appears twice, shows up off route, or belongs to an expiring lot becomes data the team can act on.
The registry behind the scratch code
Five records tell the story of each pack.
The batch
Manufacture date, expiry date, and quantity sealed live on the batch. Downstream expiry rules read this record.
The unit code
Each pack gets one random scratch code with a state such as unused, verified, or flagged. A code missing from the table was never issued by you.
The verification event
Every check writes who, where, and when. The lookup log is the dataset that duplicate and route checks read.
The shipment
Shipments record which wholesaler received which code ranges. A code verified far from its assigned range can be flagged with the shipment attached.
The hold
Lots inside the expiry window move to a held state, and a held lot cannot be picked onto an order sheet.
An example: Piotr’s veterinary-medicines distributorship
Here’s how one distributor might use a verification system built with Kliv. It’s only an example — you would describe your own products, code rules, shipments, flags, and expiry windows.
A duplicate scan creates the first flag
A scratch code verified in one town on Monday is verified again 200 kilometres away on Wednesday. Two events on one code become the alarm, and the second caller sees that the code was already used.
The shipment record narrows the trace
The code’s shipment row names the wholesaler and range. Nearby codes go onto a watch view in case the copy came from a real carton.
The case file collects evidence
A field rep photographs the suspect pack at the shop. Photos and notes file onto the case with access limited to the quality team.
Expiry checks run the same week
A scheduled sweep finds a batch 90 days from expiry and moves it to held. Slow-moving shops get a pull list.
Wholesalers see only their own ranges
Each affected wholesaler receives an email listing the ranges assigned to them, not other distributors’ data.
Describe the registry you need
Kliv builds from your description, so the more detail you give, the closer the first version. Include batches, codes, scan rules, routes, evidence, and expiry windows. Here are three examples:
Scratch-code verifier
Public verification with logged lookups.
“Build a public verification page for our veterinary medicines. A buyer should type the scratch code from a pack and see genuine, already used, expired, or unknown. Every lookup should log time, approximate location, and result for our quality team.”
Expiry watch list
Batch holds and pull-list emails.
“Build an internal expiry tool that tracks every batch’s expiry date, moves lots to held status at 90 days out, blocks held lots from order picking, and emails each sales rep a pull list for the shops they cover.”
Dealer authenticity portal
Shipment registration and suspect-pack reports.
“Build a dealer portal where authorized dealers register received shipments by code range, report suspect packs with photos and notes, and see verification history only for the codes assigned to them.”
Detection is a database habit
The public check page is the sensor network. A verification page on your own domain takes a buyer ten seconds and creates the scan events every flag rule reads. No app install is required.
Flag rules are functions you can state plainly. “Same code twice,” “verified outside its shipped region,” and “three unknown codes from one shop in a day” can each become server-side checks that create a review item. A human still separates counterfeit cases from typos.
The case file holds evidence. Photos, notes, and a code’s full history stay together with access rules. The quality team reads the case, while a wholesaler sees only what concerns them.
A tool that defends a label is usually custom because the label, batches, and routes are yours. The internal tools born custom share that pattern.
Common questions
What exactly is Kliv?
Kliv is an AI that builds custom web apps from a description. For product verification, it builds the code registry, public check page, flag queue, case files, and expiry rules.
Do I get a real app, or a template?
A real app. It is built around your products, batches, code rules, shipments, dealers, and expiry windows.
Can I change it after it’s built?
Yes. Ask for a new flag rule, expiry window, dealer role, or case-field change, and Kliv updates the app.
Does Kliv detect a fake from a photo?
No. The registry does the detecting: a missing code, reused code, off-route scan, or expired lot is the signal. Photos are evidence for the case file.
What stops someone printing their own codes?
Codes are long and random, so a guessed one is unlikely to exist. Failed lookups are logged too, so repeated unknown codes from one shop can be flagged.
Do buyers and shops need accounts?
No. The public page checks a code without sign-in. Dealers who register shipments and reports can have logins scoped to their own ranges.
How does the expiry side stay current?
Expiry lives on the batch row. A scheduled job compares dates, moves lots to held status, and sends pull lists.
Can held lots be blocked from shipping?
Yes. A held lot can be excluded from order picking so it cannot be added by someone packing in a hurry.
Can wholesalers see each other’s data?
No. Access can be scoped so a wholesaler sees only their own code ranges and cases.
Can the public check page use my own domain?
Yes. The verification page can live on your own domain.
Can I move off Kliv later?
Yes. The code syncs to your own Git repository, and your registry records can be exported.
Can every scan be logged?
Yes. Verification events can record the code, time, approximate location, and result for review.
Built by Creators
Explore What's Possible
See real applications built with Kliv by developers and creators worldwide
Memory Café Coordination Tool
A warm platform for dementia-friendly cafés, connecting caregivers, volunteers, and coordinators.
Remit Record
Track remittances and household budgets seamlessly.
Next Page Book Club
Manage your book club easily with proposals, voting, and history tracking.
Northfern Tattoo Studio
Portfolio and booking site for Northfern Tattoo Studio.
Campo Agua Gestión
Sistema de gestión del agua comunitario para aldeas.
つくりて — 伝統工芸職人サイト
職人が作品を展示し、受注管理を行うサイトです。
Tidal Surf Reports
Crowd-sourced surf condition tracking app.
Riverside Commons HOA Management
A portal for HOA management at Riverside Commons.
よやくん — レストラン予約管理
小規模レストラン向けの予約管理サイトです。
Troop 214 Scout Management
A management tool for Scout Troop 214, focused on outings, advancement, and communication.
Te Kura Kaupapa Māori Whānau Board
A whānau coordination tool for Māori-medium schools.
Tsev Nyeem Ntawv Library
Mobile library coordinator for Hmong and Lao communities.
Memory Café Coordination Tool
A warm platform for dementia-friendly cafés, connecting caregivers, volunteers, and coordinators.
Remit Record
Track remittances and household budgets seamlessly.
Next Page Book Club
Manage your book club easily with proposals, voting, and history tracking.
Northfern Tattoo Studio
Portfolio and booking site for Northfern Tattoo Studio.
Campo Agua Gestión
Sistema de gestión del agua comunitario para aldeas.
つくりて — 伝統工芸職人サイト
職人が作品を展示し、受注管理を行うサイトです。
Tidal Surf Reports
Crowd-sourced surf condition tracking app.
Riverside Commons HOA Management
A portal for HOA management at Riverside Commons.
よやくん — レストラン予約管理
小規模レストラン向けの予約管理サイトです。
Troop 214 Scout Management
A management tool for Scout Troop 214, focused on outings, advancement, and communication.
Te Kura Kaupapa Māori Whānau Board
A whānau coordination tool for Māori-medium schools.
Tsev Nyeem Ntawv Library
Mobile library coordinator for Hmong and Lao communities.
Know what is wearing your label
Describe your packs, codes, shipments, scan rules, and expiry windows. Kliv builds the registry that checks every code.