What your sample scan data actually tells you about buyer intent
Different scan patterns carry different meanings. Here is how to read scan history across your sample programme and use it to make better follow-up decisions.
Ollie Micek
8 August 2026 · 5 min read
A scan record tells you that someone looked at a material passport. It does not tell you whether that person will specify the material, shortlist it, or file it away and never return.
What the data can tell you is something more modest and often more useful: whether activity is increasing, decreasing, or concentrated in a way that suggests a project is in motion.
Here is how to read each pattern and what it warrants acting on.
Single scan, no registration
The simplest outcome. The code worked, the passport loaded, someone looked at it.
This might be the primary contact verifying the passport before passing the sample on. It might be a junior colleague checking what the QR code does. It might be an architect scanning it briefly at a trade show and moving on.
Without registration or further activity, a single scan is not a strong follow-up prompt on its own. It is worth knowing the code was used, but it does not distinguish an active evaluation from a passing glance.
Multiple scans from the same device
Repeat scans from an unregistered device, typically within a short time window, suggest someone is using the passport regularly — checking specifications, downloading documents, or returning to confirm details.
This is more useful than a single scan, but the follow-up still has to be inferred. You know the material is being consulted. You do not know for what project, or where in the evaluation the firm sits.
Worth watching. Note whether activity picks up or fades.
Registration + scan history
When a contact registers, subsequent scans connect to a specific person at a named firm. Now the data becomes interpretable in context.
A contact who registered once and never scanned again is probably not an active evaluation. A contact who registered and has scanned multiple times across multiple weeks is a different situation: the passport is being used as a working reference.
This is the pattern worth prioritising. Not because it proves anything, but because the downside of a well-timed call is low.
Read when to follow up after sending material samples for a practical cadence once you see this pattern.
Scan clusters around specific dates
Concentration matters as much as total volume. A contact who scans once a week for twelve weeks suggests slow, consistent reference use. A contact who scans ten times in three days suggests something changed — a deadline, a client meeting, a specification review.
Clusters like this align with how architectural specification actually works. Projects move in phases. At key moments — client presentation, technical review, contractor tender — the team pulls relevant materials back out and evaluates them again.
A cluster is worth noting because the timing is probably not random. It does not prove a decision point is approaching, but it is a reason to make contact while the material is actively being reviewed.
The Plasticiet case study is a concrete example of how rescan activity pointed to an opportunity that was otherwise invisible.
Multi-person activity from one firm
In SampleSync, registered scans are attributed to the contact who registered. If two different people at the same firm register and scan the same passport, the same material is being evaluated at multiple levels within the organisation.
This pattern — multiple registrations from one firm — is one of the stronger signals in the dataset, because specification decisions at architecture firms typically involve more than one person. The materials director, the project architect, and the technical lead may all need to consult the same passport.
When you see this, a follow-up that acknowledges the team-level interest rather than targeting a single contact is often more effective.
Decay versus reactivation
Most scan histories follow a declining curve: higher activity immediately after receiving the sample, tapering off over weeks. This is normal. It does not mean disinterest.
The more interesting signal is reactivation: a contact who scanned several times at the start, went quiet for two months, and then returned to the passport multiple times this week.
Reactivation often means a project that was paused has moved forward, or that the firm is now in a phase where the material specification is relevant again. This is worth acting on quickly — a contact who has returned to a material after a long gap has often made a narrowing decision and is cross-checking details.
What scan data does not tell you
Scans record access, not decision. A firm can return to a passport forty times and still not specify the material. Another can scan once and sign a contract.
Use scan patterns to decide where to invest follow-up time, not to forecast orders. The output of good scan monitoring is better prioritisation: more calls to contacts showing active interest, fewer generic check-ins with contacts who have not engaged.
Aggregate statistics — total scans, total registered contacts, scan volume over time — describe your sample programme's reach. They do not substitute for the judgment call that comes at the end of a follow-up conversation.
The short version
The most actionable scan patterns are: repeated scans from a registered contact, scan clusters around specific dates, and reactivation after a period of silence. These are reasons to make contact, not proof of an outcome.
For the data behind long-tail scan behaviour, read why material samples go silent — and what scan patterns show. For setup and what data is collected, see the FAQ or how SampleSync works.
See which of your samples get rescanned
Setup takes one weekend. Your first scan data is live from the moment samples go out.
Or read how Plasticiet spotted a high-intent account from repeated scans. See how SampleSync compares to a spreadsheet when managing 100+ samples.

Ollie Micek
Founder of SampleSync. Former architect turned material producer — I built this because I lived the problem on both sides. More about me →