Luxury and brand protection

The problem

Counterfeits have stopped looking wrong. The gap that remains is not the object, it is the story: where it came from, who has owned it, whether it was ever serviced, and whether the person selling it is entitled to.

Most brand protection answers this with an authentication mark that says this is genuine. The weakness is that the mark travels with the object, so a good copy of the mark is a good copy of the claim. And once the item is sold, the brand loses sight of it entirely, which means the resale market, the servicing relationship and the warranty are all somebody else’s business.

How VCode is deployed

A VCode is applied at manufacture and belongs to that individual item, not the model. It stays readable down to about 5 mm, so it can go on a caseback, a clasp, a certificate card or inside the packaging rather than across the product.

The record behind it carries the item’s life: manufacture, authorised retailer, first owner, service events, ownership transfers. Rules control who sees what. A prospective buyer is not shown the previous owner’s identity, and the brand is not obliged to expose its distribution data to the public.

What happens when it is scanned

The answer depends on who is asking, which is the whole point.

• A customer in a boutique sees authenticity and provenance.
• The registered owner sees ownership, warranty status and service history.
• A resale platform or service centre can be given a verification response that confirms the item and its status without exposing the owner.
• A grey-market unit resolves too, and that is the useful part: the brand sees an item scanned in a market it was never distributed to.

Because a code can be revoked, an item reported stolen stops returning a clean authenticity result and starts returning whatever the brand chooses instead.

Why a QR code or NFC alone is not enough

A QR code on a luxury item is a marketing link. It carries its destination, so cloning it clones the claim, and it tells the brand nothing about who scanned it.

NFC deserves a straight answer here, because it is the serious incumbent in this category. A cryptographically authenticated NFC tag is genuinely hard to clone, works through packaging, and needs no line of sight. If your only requirement is prove this specific object is real at the point of sale, NFC is an excellent choice and often the right one.

Where it gets harder is everything around that moment: chip cost at volume, industrial designers who do not want a tag in the product, materials that interfere, and the fact that the tag proves the object without deciding what each different party is allowed to learn about it. VCode’s contribution is not a better authenticity check, it is that the response is decided per scan, per audience, and can change after the item has left the factory.

Why it reads in the field

The constraint on a luxury item is that the mark must be almost invisible and still work. The symbology stays readable at about 5 mm from a standard smartphone, and down to 100 microns with an assisted scan, so it can sit on a caseback, a clasp, an inner seam or a certificate rather than across the product.

It also reads at up to 170 degrees, which matters when a customer in a boutique is holding a curved, polished object and not aligning it carefully.

What it changes commercially

• Resale becomes visible. Ownership transfer through the brand turns the secondary market from a blind spot into a channel.
• Grey-market detection. Scans in unexpected geographies are a distribution signal, not a guess.
• Warranty and service attach to the item. Not to a receipt somebody lost.
• A relationship with the second owner. Who, today, you never meet.

Integration

Codes are minted per item through the platform API as part of the production run, and applied by whatever marking process the product allows. Reading runs through the brand’s own application using the SDK, so the customer stays in the brand’s experience rather than a generic scanner. Scan history provides the distribution and resale picture. See the developer documentation.