Receive & Validate
Sweep a shipment or aim a focused scan, qualify the GTIN first, then associate lot, expiration and serial fields before the item is accepted into receiving.
Operational friction
One-by-one scanning loses the shipment's context.
Receiving teams aim, scan, type lot and expiration, correct duplicates and repeat the process for every package. Large orders amplify fatigue and make it harder to confirm that each traceability field is attached to the correct product identity.
Operator journey
A clear path from capture to trusted output
- 1
Capture
Sweep visible labels with a supported camera, or use the device imager for a focused capture of a single package.
- 2
Qualify GTIN first
The product identifier (GTIN) is validated before any dependent field is accepted, so lot, expiration and serial attach to the right product.
- 3
Associate fields
Lot, expiration and serial values are associated to the qualified GTIN. A field without a qualified GTIN stays as temporary evidence and is not treated as a receivable item.
- 4
Review exceptions
Unknown products, ambiguous associations and OCR rescue remain visible to the operator for review rather than being silently auto-corrected.
- 5
Integrate
Send versioned canonical JSON to your ERP, WMS or receiving API through the versioned contract.
Inside the scan
GTIN-first receive
Core handles region localization, deterministic barcode decoding, GS1 interpretation, GTIN-first state, association and constrained OCR rescue. The host owns camera capture, UI, storage, network and tenant identity.
What moves forward
Workflow outputs
- GTIN-qualified receiving event per package
- Associated lot, expiration and serial fields where present
- Suppressed duplicate frames for the same package
- Visible exception list for operator review
- Canonical JSON compatible with the versioned API contract
What stays visible
Operating boundaries
- Designed for visible, sufficiently resolved labels. Unreadable, occluded or unsupported symbologies are surfaced for review.
- Operator review and backend validation remain part of the receiving workflow.
- Repeated video frames are not counted as quantity. This profile qualifies and associates identity; it does not tally a package count.
Build the connection
Add receive and validate to your receiving stack.
Start with the versioned contract, then choose the quickest sample path for your host.