Beverage authenticity infrastructure
Verify before you drink.
A barcode only says what a pack claims to be. Authentic Sip checks a serialised code against records published by an onboarded manufacturer, then clearly shows what the registry can — and cannot — confirm.
—
Manufacturers
—
Products
—
Live codes
—
Checks run
Coverage
Starting with the three categories where counterfeiting causes the most harm, then widening across packaged consumables.
Bottled & sachet water
Pilot
Soft drinks
Pilot
Alcoholic beverages
Pilot
Juice
Next
Energy drinks
Next
The registry is the product
A phone cannot judge authenticity from a normal barcode. Everything here depends on manufacturers and regulators publishing what they actually produced.
Manufacturer registry
Producers register their company, products, batches and per-pack authenticity codes. Every code belongs to exactly one batch with a production and expiry date.
Open the manufacturer portal →Consumer verification
A shopper enters the code on the pack. The answer is authentic, duplicate, expired, recalled, flagged or not registered — with the batch record behind it.
Regulator oversight
Regulators verify manufacturer licences, watch verification patterns by region, triage consumer reports and issue recalls that reach every future scan.
Regulator desk →Consumer story — Lagos, Nigeria
How a retailer can stop a recalled batch before it reaches the shelf
This illustrative workflow shows how a shop can combine the pack registry with public NAFDAC notices. It is a product scenario, not a customer testimonial.
The shop-counter decision
A new supplier offers packaged water below the retailer’s normal trade price. The seal and label look convincing, but appearance alone cannot validate the batch.
The retailer checks the pack code before accepting the stock, reviews any recall notice attached to the record and keeps the product off the shelf when the registry cannot support the claim.
The product creates a repeatable decision point: check, review, then accept, refuse or report.
Illustrative workflow — not a customer testimonial
- 1
Cheap pallet arrives
A walk-in distributor offers packaged drinks well below the normal trade price.
- 2
Pack code checked
The code printed on the shrink wrap is entered on the verification panel instead of trusting the label.
- 3
Recalled batch
The registry shows whether the code has a published recall record and links the user to the available notice.
- 4
Stock refused, report filed
The crate never reaches the shelf, and a counterfeit report names the seller and the market where he was trading.
Verification belongs at the point of purchase
The installable PWA works now. Native camera scanning comes next.
The core consumer journey is already touch-first and installable. The same account, registry and reporting model can move into iOS and Android with camera scanning, recall notifications and low-data operation.
- Code and batch verification
- Official-notice visibility
- Counterfeit concern reporting
- Producer and regulator workspaces
Check before you sip
Your latest activity
Code and batch verification
Official-notice visibility
Counterfeit concern reporting
Saw something wrong with a pack?
Broken seal, wrong taste, smudged label, a code that fails. Record the concern in the review workflow and link it to the relevant product or producer when known.
Plans
Public verification stays free; producers fund the registry.
The pilot commercial model separates the public-safety experience from producer and national-network tooling. Prices, availability and Stripe Price IDs are managed from the protected backend.
Paid plans remain in pilot mode until Stripe test checkout, webhooks and the customer portal pass launch verification.
Producer and regulator pilot
Start with one producer and one live product.
We want the first deployment to validate real onboarding, code operations and incident response before the programme expands across categories or countries.