Vision ScanBarcode Intelligence
Start evaluation

Platform concepts

GTIN-first pharmaceutical receiving intelligence: what Vision Scan is, how the portable core works, and the ideas every integration builds on.

Why GTIN first

A single, qualified product identity anchors the entire receiving workflow.

  • A qualified GTIN anchors every receiving event before any dependent data is trusted.
  • Lot, expiry, quantity and serial fields associate only after the GTIN validates.
  • The portable core — not the host application — owns image processing, barcode decoding, GS1 handling and OCR rescue.
  • Out-of-policy or unreadable scans are surfaced for explicit, audited handling rather than guessed.
Illustration: a qualified GTIN anchors lot, expiry, and serial before a receiving event is trusted
A qualified GTIN anchors every receiving event before any dependent data is trusted.

Because identity is settled before anything else attaches, your host code can consume every canonical event as a known product — nothing arrives as an unqualified scan, and nothing unqualified is guessed into the flow.

See the principle in practice: Receive & Validate and Find & Pick.

The qualified scan becomes a structured host event — its shape is documented in canonical JSON events.

From scan to canonical event

Each capture follows a deterministic, replayable progression.

The progression is also the ownership boundary: the host hands frames to the core and receives canonical events back — everything in between is the core’s job.

Illustration: capture moves through Vision Scan processing into a canonical event

Treat the order as a contract: if any step fails — a GTIN that will not validate, fields that will not associate — the scan stops there and is surfaced for audited handling instead of continuing as a partially qualified event.

Core and host separation

A clear boundary keeps the intelligence portable and the integration explicit.

Illustration: Vision Scan portable core owns image intelligence while the host application owns workflow and integration

Use the boundary to place your code. Everything the host owns — workflow, business rules, audit, integration — is code you write and control. Everything the core owns is image intelligence you consume: it stays portable across environments, and the host side stays explicit and testable because it only ever sees canonical events.

Read the SDK overview

Portable core capabilities

The core ships the same intelligence across host environments.

  • Live low-latency sweep

    Continuous sweep feedback at the dock without blocking the line.

  • Deterministic replay

    The same captured frames reproduce the same decoded result for audit.

  • Canonical events

    Checkpointed, structured events keep the host integration explicit and testable.