Skip to main content

Signal Tags

Physical product authentication integrated with the Better Data platform — scan events that trigger compliance and brand-protection loops.

What are Signal Tags?

Signal Tags are scannable identifiers (QR, NFC, barcode) bound to verifiable product identity and provenance. Each resolution is backed by structured records suitable for regulated supply chains and anti-counterfeit programs.

How Signal Tags connect to the platform

A Signal Tag interaction is a loop trigger. Pharmaceutical serialization (illustrative)
Pharmacist scans a package → verification API returns status → on failed or recalled, a quarantine / investigation loop opens with evidence attached.
Luxury / brand protection (illustrative)
Consumer scans → authentic vs counterfeit outcome → counterfeit path can start a brand protection loop for enforcement workflows.

Verification flow

  1. Client obtains tag id from scan.
  2. Call the verification HTTP API hosted at verify.betterdata.co (or your self-hosted deployment).
  3. Receive a structured response with status (for example authentic, tampered, expired, recalled) plus timestamps and correlation metadata.
Exact path and JSON shape depend on your contract version. Use @betterdata/signal-tags-schema for JSON Schema–aligned payloads and validation.

Compliance context

The hosted platform is designed to support regimes that require serialization, authentication, and traceability, including:
  • DSCSA (US pharmaceutical supply chain)
  • EU FMD
  • FDA UDI (medical devices)
  • GS1 GTIN compatibility
Always validate against your legal and regulatory program — docs here describe architecture, not legal advice.

OSS vs hosted

OSSHosted
Schema & fixtures@betterdata/signal-tags-schema · tagd.shN/A
Verification APISelf-hosted endpoint you operateverify.betterdata.co
Signal Tags OSS
Signal Tags integration