Ship every unit with its own scannable authenticity code — printed on the hang tag, bound to the garment at packing, and backed by a verification page and scan dashboard your brand controls.
The verification platform is open source — github.com/jiashunclothing/tag-tracing — auditable end to end. We run it, you brand it, your buyers scan it.
Typical buyer problems
This path connects the buyer scenario to product intent, customization details and manufacturing checkpoints before sending an inquiry.
How it works
Codes are generated per batch before packing, printed with your hang tag artwork, and bound to each product during final packing — the same station as your AQL inspection. From that moment every garment has its own scannable identity: buyers see an authenticity page with your product and company details; you see the scan land on the dashboard.
Scan logs are field data, not theater: which regions actually check codes, which products get verified most, resale activity signaled by repeat scans of one unit, and gray-market movement when scans appear where you never shipped. For a small brand this is distribution intelligence you otherwise never get.
Every code is unique to one garment and lives under a verification domain only you control. Guessing a valid code is a one-in-hundreds-of-trillions event, and mass-duplicating a real tag produces scan patterns a genuine unit never shows: one garment verifying dozens of times across cities. Those anomalies surface on your dashboard and become evidence you can take to platforms and enforcement.
The numbers
What ships with an authenticity tag program on a standard order.
| Item | What you get | Notes |
|---|---|---|
| Codes | Unique 8-character code per unit, batch-generated | Random space of hundreds of trillions of codes |
| Tag | QR printed on your hang tag artwork or a dedicated tag | Designed alongside the rest of your label package |
| Verify page | Branded page: logo, colors, product photos, company info | 8 languages: EN, 中文, 日本語, 한국어, FR, DE, ES, PT |
| Dashboard | Scans over time, regions, top products, per-code history | Secured admin access for your team |
| Domain | Hosted verification, or your own domain | Your own domain strengthens the trust model |
| Platform | Open source under MIT | github.com/jiashunclothing/tag-tracing |
Recommended sourcing path
A client found counterfeits; the factory built its own tag-tracing system and open-sourced it.
Codes ride on the same hang tags, neck labels and polybags you are already speccing.
Code binding happens at final packing, inside the same inspection flow as your AQL check.
Send styles, quantities and whether you want your own verification domain; the quote itemizes the tag program.
Why brands stay
Related product categories
Add unique verification codes to premium hoodies before each finished piece leaves final packing.
Bind each graphic tee to its own authenticity record during the same production run.
Protect coordinated pieces with scannable tags applied before sets are packed and shipped.
Related customization pages
Plan hang tag artwork and per-garment code binding alongside custom hoodie specifications.
Approve QR tag placement and artwork while finalizing each custom T-shirt program.
Coordinate authenticity tags across matching tops and bottoms before the set reaches packing.
Related manufacturing capabilities
Buyer guides
Use these guides to prepare the specifications, approvals and trade-offs behind this buyer path.
The five components of a real private label package — neck labels, care labels, size markers, hang tags, packaging — and the dozen one-time decisions inside them.
Read guide →Sourcing GuidesInspect a garment sample in 15 steps, then turn every issue into measured, photo-linked revision comments a factory can execute.
Read guide →FAQ
We generate a unique code for every unit in your run, print the QR into your hang tag artwork (or a dedicated authenticity tag), and bind codes to products at final packing. Your buyers scan the tag and land on a branded verification page; you watch scans arrive on a dashboard. The garment MOQ starts at 50 pieces, with the final minimum confirmed after project review.
Copying gets a counterfeiter much less than it looks. Valid codes cannot be invented — the random space runs to hundreds of trillions — and verification lives on a domain you control. A duplicated code betrays itself: one unit scanning repeatedly across cities and months is a pattern a genuine garment never produces, and the dashboard surfaces exactly those anomalies. The scan log then becomes evidence for marketplace takedowns.
A dashboard with scans over time, regions, top products and per-code scan history: when, where and how often each unit is checked. The platform is open source under MIT, so your team can audit exactly what is collected.
Yes — logo, colors, fonts and badge text are configured per brand, and the consumer page speaks 8 languages. Verification can also run on your own domain if you want the URL itself to be part of the brand trust.