Prevent duplicate generation by design.
Pearpin's offline SDK generates every unit identity at print time using a deterministic formula. No pre-distributed QR files. No shared datasets. No manual block tracking. Manufacturing-side duplicate generation becomes structurally preventable — not operationally controlled.
From file distribution to deterministic generation.
The right unit of work is not the QR code, but the formula that produces it.
“Here are 1M QR codes — manage them carefully.”
- Files distributed to manufacturers
- Manual block tracking by humans
- Shared datasets between factories
- Reuse depends on people remembering
unit_id = function(line, time, counter, secret)
- No files distributed
- No human block tracking
- Each factory owns a partitioned identity space
- Generation is reproducible and auditable
How every Pearpin code is generated.
Five inputs combine into a hash unique to your factory, line, batch and time — so two factories can never accidentally produce the same identity and no QR file ever needs to leave your supply chain.
unit_id = HASH(
factory_id,
line_id,
timestamp,
serial_counter,
secret_key
)Each input narrows the identity space. factory_id and line_id partition production lines. timestamp + serial_counter guarantee uniqueness within a line. secret_key prevents external generation. The full hash provides ~128 bits of identity space — collision probability is negligible.
Three steps. Zero per-unit API calls.
The SDK runs locally on the printer system, the line PLC or a connected workstation. Production never blocks on Pearpin's servers.
- 01
Local counter increments
Every production line owns a counter. The SDK increments on each unit, never reaching back to a central server.
- 02
Generate live
At print time the SDK computes HASH(factory_id, line_id, timestamp, counter, secret_key). No file lookup. No network call.
- 03
Print immediately
Codes go straight to the printhead. The line never waits on Pearpin's servers — the SDK runs at full production speed offline.
Three failure modes the SDK eliminates.
These are duplicate-generation problems at the factory. Copied printed codes in the market are handled separately by scan intelligence — see the next section.
Printer reloads the wrong file twice
There is no file. Every identity is generated live from the formula; file reuse as a vector for duplicate generation is eliminated.
Two factories share the same dataset
They cannot. factory_id is an input to the hash; different factories occupy different identity spaces by construction.
An old QR file gets reused on a new run
No stored QR file exists at the manufacturer. The reuse vector is removed.
What the SDK does — and what scan intelligence does.
One coherent story, two distinct mechanisms. Pearpin scopes its anti-counterfeit posture honestly.
Duplicate generation prevention.
The deterministic formula plus per-manufacturer secret eliminates QR file distribution, shared datasets and reused files as vectors for duplicate identities being created in the first place. This is structural — it removes the failure modes, not just audits them.
Mechanism: deterministic SDK + secret key.
Copied printed code detection.
A counterfeiter can still photocopy a real printed code from a real product and stick it on a fake. The SDK does not prevent this and Pearpin must not claim it does. These cases surface through scan intelligence after the fact:
- geo-impossible — Same identity scanned in two cities within a window physical travel cannot satisfy.
- scan-velocity — Unusual scan frequency on a single unit — possible code reuse or photographed code.
- code-state-mismatch — A code marked sold or returned is scanned in a new retail context.
- batch-outlier — One unit's scan footprint diverges sharply from its batch's normal pattern.
Mechanism: risk scoring + 5-tier escalation ladder.
On every scan, both layers run: extract embedded data → recompute expected formula → check structure, factory and identity uniqueness → run market-side scan-intelligence checks → produce a tier and a recommended action.
The kit you integrate on your line.
Lightweight SDK
Runs on printer systems, local machines or PLC and production software. No daemon, no network requirement.
Per-manufacturer secret
Rotated on a schedule, used in the hash and prevents identity generation outside your authorized lines.
Optional periodic sync
Counters and production logs flow back to Pearpin when connectivity allows — never real-time critical.
Two paths to identity. One graph.
Most brands start on bulk APIs for fast adoption, then move to the deterministic SDK as manufacturer integration matures. Both modes share the same identity space.
Bulk APIs
Mint identities in batches. Drop the codes into your existing packaging workflow. Tracked through Pearpin's identity ledger. No manufacturer integration required.
See the APIDeterministic SDK
Codes generated on-line, offline, deterministically. Removes file handling, block tracking and shared datasets as vectors for duplicate generation.
Talk to engineeringWhat the SDK gives you. What it asks for.
Not a pros/cons argument — a clear scoping read so the right brands integrate at the right time.
- No human dependency on block tracking
- No QR file handling
- Manufacturing-side duplicate generation structurally prevented
- Infinite scalability
- Better traceability per line and per batch
- Manufacturer system support — SDK runs on the printer, line or local workstation
- Initial integration effort — more than the drop-in bulk-API path, less than a custom build
- Bulk-API onboarding for smaller brands — clear migration path to the SDK as volume scales
- Market-side photocopying handled separately — by Pearpin's scan intelligence and risk model
The same pattern lives behind every large-scale identity system.
Pre-generated IDs do not scale operationally. Deterministic generation does.
Payment tokens
PCI tokenization systems generate per-transaction identifiers without storing card files.
Distributed ID systems
Snowflake, UUIDv7, KSUID — high-cardinality IDs generated locally with negligible collision probability.
Ticketing at scale
Concert and transit systems issue cryptographically-bound tickets at print time, not from a pre-generated pool.
Ready to integrate the SDK on your line?
Get early access to be lined up for the manufacturer-integration cohort. The bulk-API path is available today.