Solutions · Product · For fashion and product brands

The sale is the last timeyou hear from most products.

A tag in the product is a channel that leaves the shop with it: proof it is real, a page for whoever owns it, and a way back to you months later.

See what a programme like this costs

Navinder Nangla tees in the END. doorway
Navinder Nangla tees in the END. doorwayNavinder Nangla × END.

The Receipt Is Where It Ends

Once something is sold it changes hands, gets resold and gets copied, and none of that comes back to the brand that made it. A listing photograph is the only proof it is real.

The receipt records one sale. Nothing stays with the thing itself.

What you cannot answer today

  • Who owns it now
  • Whether it is real
  • How to reach them after the sale

What You Can Prove with TapTech

Presence, recorded at the moment it happens, with consent from the people who chose to take part.

That it is real
Advance tags are signed on every tap and cannot be cloned, so a copy fails.
Who owns it
The first tap lets the owner claim it, and the claim stays with the piece.
Which drops landed
Entries by hour and day, so the calendar learns what a launch needs.
Who to talk to next
Consent from people who already own something you made.

What you could run

Connect a product

A garment or an object that proves itself and knows its owner. A tap walks people through 5 screens, each built from Portal Design Studio modules you can change.

  1. 01

    Verify

    • Product
  2. 02

    Claim

    • Profile
  3. 03

    The story

    • Content
    • Video
  4. 04

    Care

    • File Download
    • Notifications
  5. 05

    Collection

    • Collection
    • Page Lock

Build this journey and see what it costs

Already running · Navinder Nangla × END., E Gucewicz

  • Navinder Nangla: claim the piece

    Navinder Nangla: claim the piece

  • Navinder Nangla: verified

    Navinder Nangla: verified

  • Navinder Nangla: the owner feed

    Navinder Nangla: the owner feed

  • E Gucewicz (concept): verify and claim

    E Gucewicz (concept): verify and claim

What it returned

The Work, in Numbers

Three Formats That Go with the Product

Every format opens the same Portal and reports into the same Core.

Core views you would live in

Claims · Entries · Owners

Configure a Portal like this, and get a tier and a cost

What People Ask First

Is this just a QR code with extra steps?

For mass distribution, a QR code is the better tool and cheaper. Print a QR code on a poster and anyone can scan it from across the room, or from a screenshot of it. That is the point of a QR code and it is a real advantage. A tap requires physical proximity to a specific object, which is what makes it usable as proof of presence rather than proof of interest.

What happens after the campaign ends?

Nothing, unless someone decides to do something, and most people do not. A tag stays live and stays updatable. On one deployment, page views were still landing four months after the activation nominally ended. Pointing those tags at the next drop is a database change rather than a print run, which is the cheapest campaign anyone can run. It only works if it is somebody’s job to remember.

What does a tap actually know about me?

On its own, nothing about you. A tap records that a tap happened: which tag, when, and the category of device. It is a record of presence, not of a person. If you give an email address or make an account that is a deliberate act, and you can ask for that record or ask for it to be deleted.

Every question we get asked

How to Start

Usually

Studio for a drop, Label for a collection

See what each tier includes

How it runs

Order tags and set up a Portal yourself, with us on hand.

First step

Tell us the moment and the date. We will come back with formats, a Portal outline and lead times.

Where Next

In the docsProduct in the knowledge base ↗